Not compatable with latest kCauldron

I can't get it to work with kCauldron to save my life.
Please take a look.

https://github.com/ShadowNode/TickDynamic/releases

Yeah, sorry about no KCauldron compatibility. I'm thinking of playing some more Minecraft soon, so I will probably have a look at making the mod compatible some time soon.

That would be awesome.  Proactive tick-time rationing is something modded Minecraft has needed for a long time.

:+1:

Maybe if your ambitious enough you could keep this going for 1.7.10 as well... Even attempting to make it kCauldron compatable is a big plus though.

Would absolutely love to see a Kcauldron compatible version as well. I got so excited when I saw this mod then saddened when I saw the server not launch. :P

Have some progress lately, the new implementation for 0.2.0 seems to be working fine on normal Forge so far, using the new patching method it should in theory also work for Cauldron and kCauldron with very few modifications.
I have a bit work left to ensure the timing calculation works correctly, and the commands and output needs some more work.
I'll try to have something for testing soon.
Some housecleaning of combining all the issues about compatibility:
https://github.com/wildex999/TickDynamic/issues/17
https://github.com/wildex999/TickDynamic/issues/18
https://github.com/wildex999/TickDynamic/issues/20

I assume that you already know that the git repo for KCauldron is at https://gitlab.prok.pw/KCauldron/KCauldron .
Once you have a testing build I'm more then willing to test @wildex999. While using KCauldron of course :smile:

I also would be glad to test on KCauldron.  I already have a test server online.  I'm running KCauldron-1.7.10-1448.121-server at the moment, but I have KCauldron-1.7.10-1517.168-server and KCauldron-1.7.10-1614.174-server downloaded (but not yet tested with my modpack).

Been looking at the KCauldron source code for the part which is pertinent for TickDynamic's work.
It seems that KCauldron has a very basic limiter implemented lately, which essentially stops ticking Entities/TileEntities if the whole loop uses more than x milliseconds(Default 50ms it seems = One world tick).
This might be a problem if the limiter decides to break off in the middle of TickDynamic's ticking, as TickDynamic would not notice that the ticking has ended, and continue timing the last Entity/TileEntity.
At best this would cause mistiming and weird TPS, at worst it would crash the server.
KCauldron has also removed the nice Iterator loop that was used for TileEntities before, replacing it with a for-loop.
I can still make TickDynamic work with this, but it will mean that I have to maintain a version especially for KCauldron.
I'll continue working on it and see how it goes =)

Been looking at the KCauldron source code for the part which is pertinent for TickDynamic's work.

Did you see at which commit it was changed?

The limiter was added here: https://gitlab.prok.pw/KCauldron/KCauldron/commit/4496eada0ad96669a6d5556231921c32de6a7034
However, I think I can work around it by (ab)using the profiler a bit =P
I think I can make it play nice with the limiter, but I will still recommend server owners to turn off the limit(Set it to a unlikely high value)

I assume you mean set KCauldron's limit to an unlikely high value.  How do we do that?  I'm not seeing anything that looks obviously relevant in my kcauldron.yml file, which is where I assume it would be.  However, kcauldron adding tick-limiting might be why after upgrading kcauldron and about half a dozen mods, my total tick CPU time dropped from 65-70ms down to 38-42ms.

The config options seems to have been added under spigot.yml for some reason:
max-tick-time:
tile: 50
entity: 50
It defaults to 50 ms, which essentially means that if it takes more than 50 ms to update just Entities or just TileEntities, it will simply stop the updates at that point, and continue from there on the next tick. It's the same idea as TickDynamic, but it's a hard limit instead of a dynamic one.
Right now, it seems to be more of a way to stop the server from crashing due to long-ticking Entities, rather than trying to maintain any decent TPS(One Tick is 50 ms).

I already set both to 1000 due to some spigot timing issues
More information can be read via http://aikar.co/2015/10/08/spigot-tick-limiter-dont-use-max-tick-time/

Ok, I have an early KCauldron build ready, using the new Grouping system.
So far I have tested it on a vanilla KCauldron server, and KCauldron on FTB Infinity.
I have pointed out some known issues on the release page.
I'm not currently running a Minecraft server myself, so I don't have the ability to test it out on a fully running server with stuff happening. I would really appreciate it if any of you would be able to test it out, and provide some feedback on problems =)
Note: It is buggy, and will most likely crash at some point. I recommend doing a world backup(As you should be doing anyway)
Release: https://github.com/wildex999/TickDynamic/releases/tag/KCauldron_0.2.0-dev1

I could give you access to the repo that the unofficial builds were built from @wildex999
Those builds were a little more stable then what the current builds are - as you would have seen by looking at the kcauldron issue tracker.

Hehe. The only problem I have found when using TickDynamic with KCauldron so far, is that it randomly decides that it can't remove an entity. I'm pretty sure that is a problem with TickDynamic, I just haven't found the reason yet.
I have also put out TickDynamic dev builds for Forge 1.7.10 and Forge 1.8 now, so you guys are free to test it out. Development builds are under "Resources" on github.
I'm moving the coming week, so I won't do much work on TickDynamic during that time. Feel free to post a new issue if you encounter any problems while testing it, and I'll take a look when I can =)

is that it randomly decides that it can't remove an entity. I'm pretty sure that is a problem with TickDynamic, I just haven't found the reason yet.

Well I've added you in anyway - you should have access.  Feel free to compile or you can grab pre-compiled from the release tab :stuck_out_tongue:
You'll be able to see from the commit history.  And if in fact tickdynamic was able to remove an entity without an issue on the unofficial builds then its something that wasn't reverted back or was added at commit https://gitlab.prok.pw/KCauldron/KCauldron/commit/f722fccdcea1a0faec61c1bd72d5dd56b0c17c14

Now KCauldron is just out to screw with TickDynamic -_-
https://gitlab.prok.pw/KCauldron/KCauldron/commit/097252b5bf8fc95b4ceb059bdff83ca992f13dbe

oh my

Now KCauldron is just out to screw with TickDynamic -_-

Sigh.... I know what Prototik is trying to do but that doesn't help you @wildex999
What about the unofficial repo that I gave you access to?   That was built from kcauldron builds 152 - and also on Yives mirror

I haven't had the time to check it out yet, moving tomorrow and won't have access to my desktop until then end of the week.
The top google result(For me at least) for KCauldron, is https://gitlab.prok.pw/KCauldron/KCauldron. So that is what I'm developing against right now, as I assume that is the version most people will use.

True - although it looks like build 152 (or builds based on 152) seem to have the least issues.  Anything onwards ... well here are some issues so far
Just now - https://gitlab.prok.pw/KCauldron/KCauldron/issues/301 (most recent)
Ongoing - https://gitlab.prok.pw/KCauldron/KCauldron/issues/289

KCauldron has the same problem Cauldron did. It's a mix of so many different servers, with it's own addition of 'fixes', that things will just break at every corner.
All it takes is a mod which makes a certain assumption that KCauldron does not.
Though https://gitlab.prok.pw/KCauldron/KCauldron/issues/289 does seem kinda bad.

Though https://gitlab.prok.pw/KCauldron/KCauldron/issues/289 does seem kinda bad.

Yeah - thats why many server admins have kept to 152 builds or have branched off their own builds based on 152 - as you prob have seen yourself :stuck_out_tongue:
I'm staying with kcauldron until the majority of the mods that I use (80%) have moved over to 1.8/1.9 then I'll be moving to SpongeForge

Well one use has moved back to one of the builds I did https://gitlab.prok.pw/KCauldron/KCauldron/issues/289#note_2356 - for now.
You could state that you support up to build 152 while within spigot.yml the options under max-tick-time must be set to 1000 or higher.

I've made a couple of updates that should be more in line to what would be ideal for tickdynamic (via https://github.com/spannerman79/KCauldron/releases) that you have access to @wildex999

Yeah, I noticed. Github informs me when you do releases on there.
However, as I mentioned before, I can't base TickDynamic on your builds, as they are not what most people will find when they search for kCauldron for their servers =(

@spannerman79 can you give me access to you rep?

@wildex999 I suggesting closing this issue - you have released dev builds which should be tested.

Yeah you are right.
Closing, use the dev issues for any questions/feedback instead.


Low maximum limit for batch jobSpec pushParallelism

On batch jobs processing lots of segments for a table, they often run into Zookeeper conflicts when updating idealState. This causes contention on updates, slowing down everything. To resolve that the pushParallelism on a job spec had to be reduced to ~5, so that it would conflicts less recently. There was another issue y'all resolved which helped ensure progress happened on conflicts.
Being able to upload segments faster will drastically reduce the burden for operating Pinot (backfilling, large segment uploads, or for adjusting existing data).

I feel is is due to we upload segments to all the controller hosts and the idealStats update requests coming from all controllers will cause the slowness and update conflicts.
This issue wasn't there as controller needs to download the segment tar and untar the metadata then do the update, so it's a costly behavior in controller. With segment metadata only push mode, we may need to rethink this.
cc: @siddharthteotia @mayankshriv @snleee

Not sure what you mean by rethink.
A metadata only or URI push is a cheaper operation, so there is less likelyhood of contention.
We can also make the backoff be in smaller increments?

Here was the stripped down jobSpec we are using
executionFrameworkSpec:
  name: spark
  segmentMetadataPushJobRunnerClassName: org.apache.pinot.plugin.ingestion.batch.spark.SparkSegmentMetadataPushJobRunner
  segmentGenerationJobRunnerClassName: org.apache.pinot.plugin.ingestion.batch.spark.SparkSegmentGenerationJobRunner
  segmentUriPushJobRunnerClassName: org.apache.pinot.plugin.ingestion.batch.spark.SparkSegmentUriPushJobRunner
jobType: SegmentCreationAndMetadataPush
overwriteOutput: true
pinotFSSpecs:
- scheme: s3
  className: org.apache.pinot.plugin.filesystem.S3PinotFS
  configs:
    region: ...
recordReaderSpec:
  dataFormat: ...
  className: ...
tableSpec:
  tableName: ...
pinotClusterSpecs:
- controllerURI: ...
segmentNameGeneratorSpec:
  type: normalizedDate
  configs:
   segment.name.prefix: ...
pushJobSpec:
  segmentUriPrefix: ...
  segmentUriSuffix: ''
  pushParallelism: 5
  pushAttempts: 5
  pushRetryIntervalMillis: 3000

And, a few relevant chunks from the pinot server conf
pinot.server.instance.enable.split.commit=true

As well as the controller conf.
controller.enable.split.commit=true

An improvement for this: https://github.com/apache/incubator-pinot/pull/6165
This will limit the idealstates update parallelism to at most the number of pinot-controllers.


*** No rule to make target 'C:/........./sccb.c', needed by 'sccb.o' Stop.

Hi i am getting this error. How can i solve it?
make[1]: *** No rule to make target 'C:/msys32/home/isti-pc/esp/esp32-cam/components/camera/sccb.c', needed by 'sccb.o'.                                                                        Stop.
make: *** [C:/msys32/home/isti-pc/esp/esp-idf/make/project.mk:468: component-camera-build] Error 2

Solved it after adding include line on component.mk file.


Fix #8649: Future(Nil).get when the future raises

See #8649

CI failure (on preview_mt) seems unrelated


Win X64: ModuleNotFoundError: No module named 'staticcodecov_languages'

not able to run codecovcli without below errors
no command codecov is available
install method: 'pip install codecov-cli'
Windows 11, x64
python 3.11.7
codecov-cli: 0.4.9
PS D:\MyPython\micropython-stubber> codecovcli --version
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "D:\MyPython\micropython-stubber\.venv\Scripts\codecovcli.exe\__main__.py", line 4, in <module>
  File "D:\MyPython\micropython-stubber\.venv\Lib\site-packages\codecov_cli\main.py", line 16, in <module>
    from codecov_cli.commands.staticanalysis import static_analysis
  File "D:\MyPython\micropython-stubber\.venv\Lib\site-packages\codecov_cli\commands\staticanalysis.py", line 10, in <module>
    from codecov_cli.services.staticanalysis import run_analysis_entrypoint
  File "D:\MyPython\micropython-stubber\.venv\Lib\site-packages\codecov_cli\services\staticanalysis\__init__.py", line 15, in <module>
    from codecov_cli.services.staticanalysis.analyzers import get_best_analyzer
  File "D:\MyPython\micropython-stubber\.venv\Lib\site-packages\codecov_cli\services\staticanalysis\analyzers\__init__.py", line 2, in <module>
    from codecov_cli.services.staticanalysis.analyzers.javascript_es6 import ES6Analyzer
  File "D:\MyPython\micropython-stubber\.venv\Lib\site-packages\codecov_cli\services\staticanalysis\analyzers\javascript_es6\__init__.py", line 5, in <module>
    import staticcodecov_languages
ModuleNotFoundError: No module named 'staticcodecov_languages'

while removing, a part of the cause seems to be that someone assumed that the tool will only be used on *nix systems.
pip uninstall codecov-cli
Found existing installation: codecov-cli 0.4.5
Uninstalling codecov-cli-0.4.5:
  Would remove:
  ....
d:\mypython\micropython-stubber\.venv\lib\site-packages\staticcodecov_languages.cpython-311-x86_64-linux-gnu.so

### Tasks
- [ ] Document supported OSes (and CPU architectures)
- [ ] Add support for Windows

Note that this seemed to be broken for https://github.com/codecov/codecov-cli/issues/413 but using python3.11

#413 was closed as a Dup of itself ?

@Josverl gah, thanks

I'm having the same issue on python3.11 for versions back to 5.1.0 (didn't check lower). Works with python3.12 on version 0.7.3 (didn't check others).


Papermerge behind Traefik v2 transparent proxy

Hello,
I run all my containers behind a transparent proxy to provide https and dns (eg container.mysubdomain.mydomain.tld)
I modified the docker-compose.yml file for the elastic search version.
The app starts up and works as I think it should, but here and there errors start to occur, like creating a API key didn't show the key the first time, deleting a key gets the front end stuck and leaves me having to delete cookies to re log back in.
I have attached a copy of my docker-compose file for reference.
Any assistance greatly appreciated.
papermerge_docker-compose.yml.txt

Can you please attach docker logs of app + worker container(s)?

Silence, silence...


i'm not allowed to use the covers.

do not know why I can not use the covers without is in the op.
My Config
RankSystem
permissions:

energy.cape
firework.cape

try to use capital letters at the beginning of words such as
Firework.cape
Energi.cape


Support for Lua 5.3

Any plan?

I haven't looked into it.

What is holding support back?
I found this fork: https://github.com/dnestorov/golua
Worth merging?

Last time I checked lua5.3 wasn't in ubuntu's repositories. I took a stab at this and published it as the lua5.3 branch, it seems to work.


Upgrade beego

"concurrent map read and map write" error occurs sometimes in Harbor, this is a bug of beego. Upgrade it to version 1.6.1 can solve this issue.

thanks wenkai, please add the link to the beego issue.

https://github.com/astaxie/beego/issues/1682

fixed in #423


OAuth signature verification not handling + characters

note: dupe of https://github.com/Brightspace/sample-LTI-WHMIS-quiz/issues/2
At (https://github.com/Brightspace/sample-CourseBuilder-RemotePlugin/blob/master/OAuth1p0.php#L70) in CheckSignatureForFormUrlEncoded():
    $oauthParameters[urldecode( $key )] = urldecode( $value );

Urldecode() converts a + in $value to whitespace, which is then rawurlencode'd as %20 later on, instead of %2B (rawurlencode() does not decode plus symbols into spaces, urldecode() does). Since we use rawurlencode() later on, perhaps we should use it here as well, instead of urldecode().

Follow up note from Jordan (OP on this issue):
A side-note though: urldecode also exists on Line 73 and Line 106. I needed to change line 73 to get my localhost whmis quiz to work (line 73 was the actual problem in this case - sorry about that). Line 106 is for query parameters, so that hasn’t caused problems, but has potential to.

So what is this suggested fix for this issue?
Also see:
https://community.brightspace.com/devcop/f_technical/sporadic_invalid_oauth_signiture_errors

I can confirm switching to rawurldecode() in the CheckSignatureForFormUrlEncoded() method fixed the issue for us.


Open modal without onpress

Hi, I am wondering to open a modal when the page is loading?
Thanks!

<Modal  ref={"detailFindingModal"} />
componentDidMount() {
this.refs.detailFindingModal.open();
}


Update to Sequelize v 5.22 (at least)

The latest version improved support for passing options in the URL.
https://github.com/sequelize/sequelize/releases/tag/v5.22.0
This will enable storing metadata into an Azure SQL database. It would be great if you can make a new release targeting this new version, thanks!

@yorek are you / will you be using #668?

Yes. So that one can do, for example:
mssql://user:password@server.database.windows.net/database?options={"encrypt":true}&anotherOption=1

Yay I'm so proud  💪


Issue with the new boder drawing for cowsay

I saw #237 getting merged, but for some reason something in mine seems out of order. Could it be just my setup?

Maybe the quote in the image was not just a coincidence and it could be just my config.

Sorry to put this up, it was just my font.


[CARBONDATA-3593] Fix TOTAL_BLOCKLET_NUM not right when blocklet filt…

Fix TOTAL_BLOCKLET_NUM not right when blocklet filtered
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[x] Any interfaces changed? No

[x] Any backward compatibility impacted? No

[x] Document update required? No

[x] Testing done Yes
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[x] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA. OK

Can one of the admins verify this patch?

add to whitelist

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/980/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/989/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/992/

@shenh062326 Thanks for fixing this, could you paste a comparison of the statistics printing before and after this change?

@shenh062326 Thanks for fixing this, could you paste a comparison of the statistics printing before and after this change?

ok, I have paste the comparison in the comment.

@jackylk Can you take a look at the comment?Thanks.

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/1063/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/1054/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/1070/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/1064/

@jackylk Can you take a look at the pull request? Thanks.

LGTM
Thanks for this contribution


Binding failure with bike power sensors

Describe the bug
The user controls for bike power sensors have a binding failure and don't display the sensor variant data.
Additional context
WpfUsbStickApp

Bug fixed.


Calling Web API using Reference Token

Can any body tell me how to call web api using Reference Token.
I am using below code if I pass access token type JWT token the below API works fine but if I pass Reference Token  it gave unauthorize 401 error
WebClient client = new WebClient();
                client.Headers.Add("content-type", "application/json");
                client.Headers.Add("Authorization", "bearer " + Session["AccessToken"].ToString());
                try
                {
                    Stream data = client.OpenRead("http://localhost:5001/api/Values/GetPerson");
                    StreamReader reader = new StreamReader(data);
                    string s = reader.ReadToEnd();
                    data.Close();
                    reader.Close();
                    Label1.Text = Label1.Text + "" + s + "";
                }
                catch (Exception ex)
                {
                    Label1.Text = Label1.Text + "" + ex.ToString() + "";
                }

Which middleware are you using to validate the ref token - how is that setup? What's the logging output?

I am simple ASP.NET Web.API and added Identity Server Relation as below code (Code 2), I came to know that token revocation can be done on Reference Type Token not JWT Access Token so I define Token Type as Reference Type in Client Definition but When I used that Reference Token type to Call API method it gave me unauthorized error  the sample code to call Web api is below Code 1
Please suggest me where I am doing wrong.
I want to make simple web api accessible web application using Token service of Identity Server and when I logout from my web application the token should not be accessible or the API should not be accessible using that revoke token.
Code 1
WebClient client = new WebClient();
client.Headers.Add("content-type", "application/json");
//client.Headers.Add("Authorization", "bearer " + Session["AccessToken"].ToString());
client.Headers.Add("Authorization",  Session["AccessToken"].ToString());
try
{
Stream data = client.OpenRead("http://localhost:5001/api/Values/Get/1");
StreamReader reader = new StreamReader(data);
string s = reader.ReadToEnd();
data.Close();
reader.Close();
Label1.Text = Label1.Text + "" + s + "";
}
catch (Exception ex)
{
Label1.Text = Label1.Text + "" + ex.ToString() + "";
}
Code 2
public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
       {
           loggerFactory.AddConsole(Configuration.GetSection("Logging"));
           loggerFactory.AddDebug();

           app.UseApplicationInsightsRequestTelemetry();

           app.UseApplicationInsightsExceptionTelemetry();

           app.UseIdentityServerAuthentication(new IdentityServerAuthenticationOptions
           {
               Authority = "http://localhost:5000",
               ScopeName = "api1",
               RequireHttpsMetadata = false,
               ScopeSecret = "secret",
               AutomaticAuthenticate = true,
               AutomaticChallenge = true

           });

           app.UseMvc();
       }

enable logging to see whats going on.

@leastprivilege , Do you have any sample or documentation link about the middleware that validates the ref token

Sure - it's in our docs.
https://identityserver4.readthedocs.io/en/release/topics/apis.html


[Backport to main]Adding backwards compatibility test for ml-commons plugin (#681)

Description
Backport #681 to main branch
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

BWC has some issue. Will backport other PRs first.
Close this PR


Add harlequin as a database management tool

Feature description
使用 harlequin作为数据库管理工具，就像git管理使用lazygit一样
Additional information
No response

i'm not sure if it's necessary to include this feature in the repo, since not all needs to work with databases.
maybe it would suit better in your own fork?

lazygit and harlequin both are external tools instead of nvim plugin. They don't have direct relationship with nvim and you can use them in terminal directly. What we can do is only adding a keymap for it like <leader>gg for lazygit in toggleterm.
As @CharlesChiuGit said, not all need to work with databases. You can set it on your own.


Overwritten styles for tables, breadcrumbs, paginations and default/primary buttons

This PR appears to have been intended for a different repo.


open service cron start

Hope to open service cron start in docker-entrypoint.sh
This provides the ability to delete log files with the help of the mirror itself.

There's no services in the container as there is no init system or supervisor, most users have a second container running cron that shares folders with the other container. You could also use your host system's cron to docker exec into the container.
If you have further questions you should ask the Docker Community Forums, the Docker Community Slack, or Stack Overflow. As these repositories are for issues with the image and not necessarily for questions of usability


[CHORE] 4.3.0 release

[ ] Fix concat funcs script to clear ESLint errors (dangling commas)
[ ] Abstract fetch subscriptions function to shared utility functions
[ ] Use fetch subs function in checkmarks mod
[ ]  Abstract getComputedFontSize() function to safeGM
[ ] Implement stricter CSS on noti panel (cf. #251)
[ ] Expand troubleshooting section in docs with common issues

https://developer.chrome.com/docs/extensions/reference/api/userScripts#developer_mode_for_extension_users

[ ] Add screenshots to links field

[ ] Document purpose of link/preview key in manifest

You might want to rename it to mbin/kes

It seems reasonable. The name can be changed entirely if necessary. But I have not thought of a satisfactory alternative yet.

Yeah, I'm afraid /kbin is no more. Also feel free to contribute directly to the Mbin core. So your improvements will be available for everybody by default, without the need for additional CSS scripts. Assuming there are some CSS improvements that is beneficial for everybody. And even then, special features can be placed behind settings/switches.
We are on Matrix: https://matrix.to/#/#mbin-general:melroy.org.


[Spotify Player] ...

Extension
https://www.raycast.com/mattisssa/spotify-player
Description
If a song has been already liked, and you like it again, the extension removes the liked status and reapplies it. This causes already liked songs to come up again on the top list of your liked songs. It  obviously also as well resets the date at which you can see when you liked a song,
Steps To Reproduce

Like an already liked song on Spotify and watch how it hops on the top of your liked songs (as well as that the added date gets resetted)

Current Behaviour
No response
Expected Behaviour
No response

I could pick this up!

This has been fixed in v2 of this extension, see PR #5602 to follow along.


Allow passing cached JSON with methods

Currently, you have to put all code that might need WebAPI into the callback to Steam.ready. This is inconvenient and not technically necessary, since existing methods don't change.
I propose to add an ability to pass prepared JSON from GetSupportedAPIList to the library, thereby avoiding the need to download it dynamically every time. For example, Steam.ready could accept the parsed JSON instead of the callback.

Not a bad idea. However, there would then be two code-paths to go through; one if they didn't have a cache (like currently) and one if they did (so more work for the user). Also, wouldn't that be violating node's guideline of a method not being both async and sync?
Granted, it would work alright if you didn't really mean not keeping everything in the callback to Steam.ready, which would merge back the code-paths. But, I think it would make more sense to just manage file caching entirely inside the library, maybe making the first argument of .ready an optional object with 'cacheFile' (and 'key') field(s). Thoughts?

That's the thing, having everything in the callback makes things more complicated. Consider, for example, that you also use a MongoDB connection. If you need both MongoDB and Web API for anything, you end up with a nested callback.
Actually, some time after posting this issue I decided to start working on a simpler Web API wrapper that doesn't generate methods and thus doesn't require the method descriptions, so this isn't that relevant to me anymore. But I'm glad that you found the suggestion interesting.

Yeah, that's one of the major gripes about Node. But there are a lot of ways to mainly avoid the nested callback issue from async callbacks, even without libraries. (For example:)
// Some initial state
var steamReady=false, mongoReady=false;

// Initialize stuff (that's not guaranteed to finish in any particular order)
Steam.ready(function() {
  steamReady=true;
  main();
});
// Just psuedo code..
Mongo.ready(function() {
  mongoReady=true;
  main();
});

function main() {
  if ( !steamReady || !mongoReady) return; // Not ready yet
  // rest of code that can know everything is initialized..
}

Ah, okay. Yeah, it's really just a simple library that can easily be rewritten, any number of ways. Happy coding.


Library damaged when working on shared Storage

Apple Feedback Assistant ID: MISSING
DESCRIBE THE BUG:
A message appear when working saying the Library is damaged. We were experiencing FCP library corruption when they were stored on our SMB shares. It happens randomly in different Macs in our network connected to our NAS, Intel Macs or Apple Silicon with Ventura or Sonoma.
All these Libraries works ok locally but they could get damaged when working on shared storage in any moment. However, after the warning you could copy the Library to local drive and it works. After that you can copy from local Drive to NAS and it works again! However you could find the issue later with the same Library or another one.
Madia, cache and backups are external.

TO REPRODUCE:
You only need to open a FCP Library and work, it will happen during the day.

EXPECTED BEHAVIOUR:
When the warning message appears you accept it and keep working. Sometimes the Library is really damaged (probably you will lose the open project) and sometimes it's not. There's o clear pattern.

SPECS:
Attached report.

2022 Mac Studio (M1 Max, 64GB RAM)
macOS Ventura 13.6.5
Final Cut Pro 10.6.5

ADDITIONAL COMMENTS:
Final Cut Pro_2024-04-02-112539_Inaki-IT.hang.zip

See my previous comments here: https://github.com/CommandPost/FCPCafe/issues/250
LumaForge (who are experts at FCP/NAS integration) says: "On most NAS based storage, FCPX Libraries and media management commands will not work because NAS storage is typically shared through AFP or SMB Protocols, which are not designed to work with the FCPX Library Architecture."
https://www.lumaforge.com/fcpx-shared-storage
Apple says: "If you’re using a shared storage system that uses the SMB protocol, the SMB volume must originate from a macOS server or a Linux server running Samba 4.3.4 or later configured with modules for Apple compatibility."
https://support.apple.com/en-us/101919
See this archived post by Thomas Berglund on fcp.co about an investigation of NAS tuning parameters possibly needed to make FCP libraries work reliably on an SMB:  https://web.archive.org/web/20200918143902/https://fcp.co/forum/4-final-cut-pro-x-fcpx/31510-media-cache-on-shared-storage-network?start=40#109131

Hi,
Thanks for your feedback.
It happens our NAS is from Lumaforge, it has been desgined to work with FCPX since the very beggining. It has been working properly with FCP and SMB for 3 years. All these time, Libraries, caches, backups, fotage have been placed in the NAS with a very good performance.
A year ago when this issue start happening. We have been working (still doing it) with Lumaforge to figure it out. Also we've tried to reach Apple through Lumaforge but still waiting from feedback.
Meanwhile I was looking for more info here. I'll update as soon as I have news.

There are apparently few (maybe no) network-specific calls in the FCP source code. The Flexo framework class FFStorageManager handles the setup and identification of storage locations. That class has a method URLIsSMBVolume, which takes a URL as input, retrieves the file system information using the statfs function, and checks if the file system type is "smbfs" to determine if it is an SMB volume. The method returns 1 if it is an SMB volume and 0 otherwise.
I ran FCP under XCode, put a library on a Mac network server and set a breakpoint on the +[FFStorageManager URLIsSMBVolume:] method, but it never hit that. I verified they were using SMB by using the terminal 'mount' command on the client and the 'sudo nettop -m' command on the server, so I don't know why it never hit the breakpoint.
In general FCP uses normal file I/O calls and relies on the network layer and the NAS to safely execute those. E.g, when FCP on a client machine does the 'fsync' call to flush any open buffers to disk. For redirected I/O to a NAS, the server must interpret that and use whatever is the equivalent call on its local filesystem. If any slight mixup occurs, the remote file buffers may not get flushed and could be susceptible to damage.
Most Unix-heritage filesystems, including HFS+ and APFS, don't have "mandatory" file locking. Unlike Windows you normally don't get a "file in use" error. However if another process is doing I/O to an FCP library, it is very easy to corrupt one. This is especially easy to happen in a NAS situation if multiple people are working on a set of libraries.
One way to troubleshoot a problem like this is by using synchronized concurrent tracing on both Mac client and NAS server. E.g, fs_usage on the client and strace on the server, then analyze those using trace visualization tools. E.g: Trace Compass: https://eclipse.dev/tracecompass/
Another step would be to open the damaged FCP library using a tool like SQLPro for SQLite and mount each CurrentVersion.fcpevent file (each of which are SQLite databases) and on each one, run the command 'PRAGMA integrity_check.' That checks for lower-level damage in the SQLite database, such as a damaged index. It does not check for logical-level inconsistencies with FCP data. That can be checked by selecting the project and while pressing the OPT key, doing Clip>Verify and Repair Project. Make sure the library is backed up before doing that.
If the SQLite database has damage which shows up using PRAGMA integrity_check, that likely has nothing to do with FCP.

Hi,
Thanks for your feedback.
It happens our NAS is from Lumaforge, it has been desgined to work with FCPX since the very beggining. It has been working properly with FCP and SMB for 3 years. All these time, Libraries, caches, backups, fotage have been placed in the NAS with a very good performance.
A year ago when this issue start happening. We have been working (still doing it) with Lumaforge to figure it out. Also we've tried to reach Apple through Lumaforge but still waiting from feedback.
Meanwhile I was looking for more info here. I'll update as soon as I have news.

I don't know if this will encourage you, but here we have four editors working collaboratively on a NAS. All media, assets, and libraries are on the NAS, and we don't copy libraries locally. We've been doing this for seven years with different Macs without any hiccups. Recently, we bought four Mac Studios and ran into some issues, but now everything is running smoothly as before. A well-known guy named Bob Z. configured our NAS, and we couldn't be happier.
Apple M1 Ultra
128GB
Sonoma 14.3.1
For the workflow part: We duplicate the library on the NAS for each editor who needs to work on the TV episode. We work simultaneously on different parts of the episode and have access to the same media and assets. When everyone is finished, we consolidate everything into the same library and share the final video. We haven't encountered library corruption yet, and I was not aware that it could occur with this setup. We will keep that in mind if it happens someday.

Hi,
thanks for your comments and your workflow tips. In fact, our workflow is very similar to yours, but we have more editors (around 20-22) working simultaneously. We have some issues when we get the first Mac Studio (with M1) but I think the problem could be a combination of factors including big FCP Libraries, number of Macs connected to the network and Apple Silicon and Mac Intel working with the same Libraries.
Lately we have fewer editors (between 10-15) and our projects have less complex FCP Libraries, and we have less damaged Libraries. So it looks like it's related to connection issues, it could be our 10Gb switch or our NAS (Jellyfish).
We will continue investigating. Thanks!

We have updated our systems, now most of them ara Mac Studio with M1 and M2 macOS Sonoma 14.5 with FCP 10.8.
The issue is stil there when working with Libraries in the NAS. When duplicating projects sometimes FCP freezes , when moving projects from one Library to another the same. Then Libraries get corrupted but still can be opened in local storage.
Libraries don't need to be big, it happens with small projects. New Final Cut Pro version doesn't fix anything.

Also, as a general note, you never really want to ever duplicate Libraries at the Finder level. It's much better to create a new Library then drag events from one to another.

Also, as a general note, you never really want to ever duplicate Libraries at the Finder level. It's much better to create a new Library then drag events from one to another.

Interesting! Is there a technical reason for this? We've never had an issue doing it, but I'll take your word for it.

Each library has a unique identifier. When you duplicate things at the Finder level, you now have two libraries with the same unique identifier. This means, for things like render caches, etc. Final Cut Pro gets confused if you have two libraries with the same unique identifier. This can lead to all kinds of weird issues.

Also, as a general note, you never really want to ever duplicate Libraries at the Finder level. It's much better to create a new Library then drag events from one to another.

Thing is we have some Libraries we need to duplicate because they're "Template Libraries" with custom settings, predefined events and projects. They are not heavy, and we can duplicate them with no issues. Issues appear when we duplicate WIP Libraries with several projects, titles and so on.

You're much better off creating a new library then dragging all your events from the template library to the new library.


New User: PowerReviews

Name: PowerReviews
Homepage url: http://www.powerreviews.com
Brand Guidelines/Licensing:  Nothing important!
Logo: http://www.powerreviews.com/wp-content/uploads/2015/04/PowerReviews_logo_RGB.png

We're now serving Babelified ES6 code in front of 250m users a month.  Thanks, guys!

Brand Guidelines/Licensing: Nothing important!

I need to know even the unimportant things

Hey @thejameskyle,
By nothing important, I actually mean "nothing" - we have no brand licensing policy at the moment.  Should that change sometime in the future, I'll let you know.
Is there anything else you need?

That's fine, just need clarity


Install spack-stack 1.8.0 (and all add-on envs needed for UFS WM @ develop) with LLVM compilers on Hera

Is your feature request related to a problem? Please describe.
Install spack-stack @ v1.8.0 with LLVM compilers on hera
Describe the solution you'd like
Configure and build spack-stack @ v1.8.0 for LLVM compilers installed on hera (as noted here: Track availability / installation of Intel oneAPI (LLVM) compilers on tier1 hosts
Additional context
Build and test the UFS WM @ branch develop against the installed stack.
Build with both ifort and ifx (different stacks) as the Fortran compiler.

On hera, trying to configure spack-stack @ release/1.8.0 for LLVM compilers.
For these two modules (per module available):
intel/2024.2.1  and  impi/2024.2.1
configs/sites/tier1/hera/compilers.yaml
compilers:
- compiler:
  spec<EMAIL_ADDRESS>  paths:
   cc: /apps/oneapi/compiler/2024.2/bin/icx
   cxx: /apps/oneapi/compiler/2024.2/bin/icx
   f77: /apps/oneapi/compiler/2024.2/bin/ifx
   fc: /apps/oneapi/compiler/2024.2/bin/ifx
  flags: {}
  operating_system: rocky8
  modules:
  - intel/2024.2.1
  environment:
   prepend_path:
    PATH: '/apps/spack/linux-rocky8-x86_64/gcc-8.5.0/gcc-14.2.0-27o6emykdlx4ze3ooerg4bofx7lgn35p/bin'
    LD_LIBRARY_PATH: '/apps/spack/linux-rocky8-x86_64/gcc-8.5.0/gcc-14.2.0-27o6emykdlx4ze3ooerg4bofx7lgn35p/lib64'
    CPATH: '/apps/spack/linux-rocky8-x86_64/gcc-8.5.0/gcc-14.2.0-27o6emykdlx4ze3ooerg4bofx7lgn35p/include'
  extra_rpaths: []

configs/sites/tier1/hera/packages_oneapi.yaml
packages:
 all:
  compiler<EMAIL_ADDRESS>  providers:
   mpi<EMAIL_ADDRESS>   # Remove the next three lines to switch to intel-oneapi-mkl
   blas:: [openblas]
   fftw-api:: [fftw]
   lapack:: [openblas]
 mpi:
  buildable: False
 intel-oneapi-mpi:
  externals:
  - spec: intel-oneapi-mpi<EMAIL_ADDRESS>   modules:
   - impi/2024.2.1
   prefix: /apps/oneapi
[...]

Choosing mpi<EMAIL_ADDRESS>because
% module show impi/2024.2.1
-----------------------------------------------------------------------------------------------------------------------------
  /apps/modules/modulefamilies/intel_2024.2.1/impi/2024.2.1:
-----------------------------------------------------------------------------------------------------------------------------
whatis("Name: Intel(R) MPI Library")
whatis("Version: modulefiles/2021.13")
setenv("I_MPI_ROOT","/apps/oneapi/mpi/2021.13")

Concretization fails as:
% spack concretize --force 2>&1 | tee $DIR/$ENV/log.concretize
==> Error: concretization failed for the following reasons:

  1. Attempted to use external for 'intel-oneapi-mpi' which does not satisfy any configured external spec
  2. Attempted to build package intel-oneapi-mpi which is not buildable and does not have a satisfying external
    attr('node_compiler_version_satisfies', 'intel-oneapi-mpi', 'oneapi', '2024.2.1') is an external constraint for intel-oneapi-mpi which was not satisfied

hera does provide a module named intel-llvm/2024.2.1 (not sure why), which is functionally identical to intel/2024.2.1 -- using it yields the same result.
Ideas / suggestions?

compilers:
- compiler:
  spec<EMAIL_ADDRESS>
Oops.
Corrected typo yields a concretized env; fails to build<EMAIL_ADDRESS>with ifx.

compilers:
- compiler:
  spec<EMAIL_ADDRESS>
Oops.

You are not planning to retire before 2042?

compilers:
- compiler:
  spec<EMAIL_ADDRESS>

Oops.

You are not planning to retire before 2042?

Might be dead and gone by then!

As of Monday November 04: using ifx as the Fortran compiler, bumped versions for

gfsio --> 1.4.2
landsfcutil --> 2.4.2
sfcio --> 1.4.2

as release notes for each state: "adds Intel oneAPI support" and each successfully built.
Failing in cdo:
Bitrounding.cc:81:18: error: no member named 'clamp' in namespace 'std'
   81 |   int nsb = std::clamp(keepMantissaBits, 1, 23);
      |             ~~~~~^
Bitrounding.cc:415:36: error: no member named 'clamp' in namespace 'std'
  415 |                         nsb = std::clamp(nsb, params.minBits, params.maxBits);
      |                               ~~~~~^

Failing in cdo:
Bitrounding.cc:81:18: error: no member named 'clamp' in namespace 'std'
   81 |   int nsb = std::clamp(keepMantissaBits, 1, 23);
      |             ~~~~~^
Bitrounding.cc:415:36: error: no member named 'clamp' in namespace 'std'
  415 |                         nsb = std::clamp(nsb, params.minBits, params.maxBits);
      |                               ~~~~~^

Solved by returning to using pathing for gcc-9.2.0 for C++ libraries / headers (had been trying v14.2.0).

On hera:
spack-stack/configs/sites/tier1/hera/compilers.yaml
compilers:
- compiler:
    spec<EMAIL_ADDRESS>    paths:
      cc: /apps/oneapi/compiler/2024.2/bin/icx
      cxx: /apps/oneapi/compiler/2024.2/bin/icpx
      f77: /apps/oneapi/compiler/2024.2/bin/ifx
      fc: /apps/oneapi/compiler/2024.2/bin/ifx
    flags: {}
    operating_system: rocky8
    modules:
    - intel/2024.2.1
    environment:
      prepend_path:
        PATH: '/apps/gnu/gcc-9.2.0/bin'
        LD_LIBRARY_PATH: '/apps/gnu/gcc-9.2.0/lib64'
        CPATH: '/apps/gnu/gcc-9.2.0/include'

and the packages noted in Unified environment build errors with ifx #1279 -- gfsio | landsfcutil | sfcio | sigio -- updated to reflect versions that build with ifx<EMAIL_ADDRESS>successfully builds; it does so, however, with some duplicates (20 of them), all of which concretize identically excepting their hash:
base-env<EMAIL_ADDRESS>build_system=bundle  arch=linux-rocky8-haswell
bufr-query<EMAIL_ADDRESS>build_system=cmake  build_type=Release  generator=make  patches=3ae2f2f  arch=linux-rocky8-haswell
crtm<EMAIL_ADDRESS>build_system=cmake  build_type=Release  generator=make  arch=linux-rocky8-haswell
crtm<EMAIL_ADDRESS>build_system=cmake  build_type=Release  generator=make  arch=linux-rocky8-haswell
esmf<EMAIL_ADDRESS>build_system=makefile  esmf_comm=auto  esmf_os=auto  esmf_pio=auto  patches=f63d405  snapshot=none  arch=linux-rocky8-haswell
esmf<EMAIL_ADDRESS>build_system=makefile  esmf_comm=auto  esmf_os=auto  esmf_pio=auto  patches=f63d405  snapshot=b11  arch=linux-rocky8-haswell fms<EMAIL_ADDRESS>build_system=cmake  build_type=Release  constants=GFS  generator=make  patches=2b12a6c  precision=32,64  arch=linux-rocky8-haswell
gsibec<EMAIL_ADDRESS>build_system=cmake  build_type=Release  generator=make  arch=linux-rocky8-haswell hdf5<EMAIL_ADDRESS>api=default  build_system=cmake  build_type=Release  generator=make  patches=82088c8  arch=linux-rocky8-haswell
jedi-base-env<EMAIL_ADDRESS>build_system=bundle  arch=linux-rocky8-haswell
mapl<EMAIL_ADDRESS>build_system=cmake  build_type=Release  generator=make  arch=linux-rocky8-haswell
nccmp<EMAIL_ADDRESS>build_system=cmake  build_type=Release  generator=make  arch=linux-rocky8-haswell
nco<EMAIL_ADDRESS>build_system=autotools  arch=linux-rocky8-haswell
ncview<EMAIL_ADDRESS>build_system=autotools  arch=linux-rocky8-haswell
netcdf-c<EMAIL_ADDRESS>build_system=autotools  patches=0161eb8  arch=linux-rocky8-haswell
netcdf-cxx4<EMAIL_ADDRESS>build_system=autotools  arch=linux-rocky8-haswell
netcdf-fortran<EMAIL_ADDRESS>build_system=autotools  arch=linux-rocky8-haswell
parallelio<EMAIL_ADDRESS>build_system=cmake  build_type=Release  generator=make  arch=linux-rocky8-haswell
py-h5py<EMAIL_ADDRESS>build_system=python_pip  arch=linux-rocky8-haswell
py-netcdf4<EMAIL_ADDRESS>build_system=python_pip  patches=255b5ae  arch=linux-rocky8-haswell
ufs-pyenv<EMAIL_ADDRESS>build_system=bundle  arch=linux-rocky8-haswell

so modules can't be refreshed and a valid set of stack modules can't be created.
I've not encountered this before, and don't know where to start looking.

great progress, @rickgrubin-noaa. @RatkoVasic-NOAA @AlexanderRichert-NOAA @climbfuji any idea why these package duplicates would be happening?

Ref. this comment above, containing a list of duplicates:
Trying to track this down using spack find -N in an activated / fully built env, and looking at, for example<EMAIL_ADDRESS>% file hdf5*
hdf5-1.14.3-7jz6yub: setgid, directory
hdf5-1.14.3-rvoosit: setgid, directory

Within each of those installed directories, looking at the file .spack/spack-build-env.txt, the only differences are:
arch=linux-rocky8-haswell/7jz6yub
arch=linux-rocky8-haswell/rvoosit

As one would expect, rocky8 is specified in various files under the configs directory, when specifying a host's underlying OS, e.g.
sites/tier1/hera/compilers.yaml:    operating_system: rocky8

The tag haswell shows up in one place:
./sites/tier1/hera/packages.yaml:    target: [haswell]

@climbfuji @AlexanderRichert-NOAA @RatkoVasic-NOAA  -- any thoughts on how this occurs / where to start looking?

% spack diff /7jz6yub /rvoosit
==> Warning: This interface is subject to change.

---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ hash @@
- hdf5 7jz6yubonaibnjtujho7dqaznnvter5u
+ hdf5 rvoosittc42optuwucdyxjzo5rcldz6p
@@ virtual_node @@
+ fortran-rt
@@ virtual_on_edge @@
+ hdf5 intel-oneapi-runtime fortran-rt
@@ virtual_on_incoming_edges @@
+ intel-oneapi-runtime fortran-rt

After saving the output of each of spack spec hdf5 /7jz6yub and spack spec hdf5 /rvoosit
% diff 7jz6yub rvoosit
3c3
< -  hdf5/7jz6yub
---
> -  hdf5/rvoosit
16d15
< [+]   ^gcc-runtime<EMAIL_ADDRESS>build_system=generic arch=linux-rocky8-haswell
20a20
> [+]     ^gcc-runtime<EMAIL_ADDRESS>build_system=generic arch=linux-rocky8-haswell

so in one case, gcc-runtime is its own dependency, and in another case, it's a dependent of something else.
For hash /7jz6yub:
[+]   ^gcc-runtime<EMAIL_ADDRESS>build_system=generic arch=linux-rocky8-haswell
[...]
[+]   ^intel-oneapi-runtime<EMAIL_ADDRESS>build_system=generic arch=linux-rocky8-haswell

and for hash /rvoosit:
[+]   ^intel-oneapi-runtime<EMAIL_ADDRESS>build_system=generic arch=linux-rocky8-haswell
[+]     ^gcc-runtime<EMAIL_ADDRESS>build_system=generic arch=linux-rocky8-haswell

In looking at some of the other duplicates, they have a dependency on hdf5 in one form or another, and some exhibit the dependency interplay between intel-oneapi-runtime and gcc-runtime, some do not.

Per @climbfuji 's suggestion, attached is log.concretize, and spack.yaml (each slightly renamed to conform to github's filename upload rules).
See also this comment from the spack slack channel.
log-concretize.txt
spack-yaml.txt

You should declare the intel-oneapi-runtime package as an external package (since you declare the compiler and MPI library as external, too). Several tier1 or tier2 site configs do have this setting already, please check.

You should declare the intel-oneapi-runtime package as an external package (since you declare the compiler and MPI library as external, too). Several tier1 or tier2 site configs do have this setting already, please check.

intel-oneapi-runtime added as an external in packages_oneapi.yaml per the ### nautilus config (the only tier1 host which specifies this).
$SPACK_STACK_DIR/util/show_duplicate_packages.py -d envs/unified-dev.hera.oneapi-ifort/log.concretize
p4yjfrb  crtm<EMAIL_ADDRESS>build_system=cmake  build_type=Release  generator=make  arch=linux-rocky8-haswell
gqra4zu  crtm<EMAIL_ADDRESS>build_system=cmake  build_type=Release  generator=make  arch=linux-rocky8-haswell
74cux3x  crtm<EMAIL_ADDRESS>build_system=cmake  build_type=Release  generator=make  arch=linux-rocky8-haswell
jlb2o5n  esmf<EMAIL_ADDRESS>build_system=makefile  esmf_comm=auto  esmf_os=auto  esmf_pio=auto  patches=f63d405  snapshot=b11  arch=linux-rocky8-haswell
gylhdlc  esmf<EMAIL_ADDRESS>build_system=makefile  esmf_comm=auto  esmf_os=auto  esmf_pio=auto  patches=f63d405  snapshot=none  arch=linux-rocky8-haswell
===
Duplicates found!

Safe to assume that, given different package versions, this is acceptable?
<EMAIL_ADDRESS>/74cux3x appears standalone, and in global-workflow-env / gsi-env / soca-env / ufs-weather-model-env at that hash, so seems OK.

This looks promising. We do need two different ESMF versions and three different CRTM versions at the moment

Adding intel-oneapi-runtime as an external (as with the compiler and MPI specs) to packages_oneapi.yaml, e.g.
  intel-oneapi-runtime:
    externals:
    - spec: intel-oneapi-runtime<EMAIL_ADDRESS>      prefix: /apps/oneapi/compiler/2024.2
      modules:
      - compiler-rt/2024.2.1

resolves duplicates and envs build successfully.

hera
% ls /scratch1/NCEPDEV/nems/role.epic/spack-stack/spack-stack-1.8.0-llvm/envs
ue-llvm-ifort-2024.2.1
ue-llvm-ifx-2024.2.1

ifx
% module use /scratch1/NCEPDEV/nems/role.epic/spack-stack/spack-stack-1.8.0-llvm/envs/ue-llvm-ifx-2024.2.1/install/modulefiles/Core
% module load stack-oneapi/2024.2.1
% module load stack-intel-oneapi-mpi/2021.13

ifort
% module use /scratch1/NCEPDEV/nems/role.epic/spack-stack/spack-stack-1.8.0-llvm/envs/ue-llvm-ifort-2024.2.1/install/modulefiles/Core
% module load stack-oneapi/2024.2.1
% module load stack-intel-oneapi-mpi/2021.13

Done!


[-PreferenceMoveFrequency ]  | upper limit

[Enter feedback here]
From a recent case opened with MS support, it was found that setting this value higher than 49.7 days is causing the MSExchangeRepl.exe to crash on all the DAG members.
Upon investigation, it was found that the TimerConstructor when passed a value higher than 2^32-2 causes the service to crash with ArgumentOutOfRangeException
\
[12:53:39] Exception: E0434F4D.System.ArgumentOutOfRangeException ("Time-out interval must be less than 2^32-2.")
[12:53:39] Dump 1 initiated: C:\Sources\Procdump(1)\msexchangerepl.exe_201112_125339.dmp
//
This limit is mentioned here as well.
https://docs.microsoft.com/en-us/dotnet/api/system.threading.timer.-ctor?view=net-5.0#System_Threading_Timer__ctor_System_Threading_TimerCallback_System_Object_System_TimeSpan_System_TimeSpan_
\
Exceptions
ArgumentOutOfRangeException
The number of milliseconds in the value of dueTime or period is negative and not equal to Infinite, or is greater than MaxValue.
(Int32.MaxValue)
//
What i suggest to add an upper limit to the parameter in this doc. and not leaving it up to the user to set any time value.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 525f60d1-1dbe-a6ab-e559-783808d84dfe
Version Independent ID: da93731f-2fc2-5422-ea20-feda192a62d5
Content: Set-DatabaseAvailabilityGroup (ExchangePowerShell)
Content Source: exchange/exchange-ps/exchange/Set-DatabaseAvailabilityGroup.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@AbdallahmGalal, based on what you are saying, is the existing statement in the parameter description valid or invalid?
To disable this feature, specify the value ([System.Threading.Timeout]::InfiniteTimeSpan).

Hi Chris,
I ‘ve not tested that personally but I assume yes, this parameter turns off the feature completely.
If you want to keep it running, then the admin should provide a value,  and this is left open in this doc. with no cap however in reality the value can’t be higher than 49.7 days as the max value for 32bit timespan object, otherwise the MSExchangeRepl service will start crashing with and this what I would like to be added here.
Thanks,
Abdallah
From: Chris Davis<EMAIL_ADDRESS>Sent: Monday, November 16, 2020 7:24 PM
To: MicrosoftDocs/office-docs-powershell<EMAIL_ADDRESS>Cc: Abdallah Galal<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/office-docs-powershell] [-PreferenceMoveFrequency ] | upper limit (#6856)
@AbdallahmGalalhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAbdallahmGalal&data=04|01|Abdallah.Galal%40microsoft.com|61fed22e603c4bfa557c08d88a54715f|72f988bf86f141af91ab2d7cd011db47|1|0|637411442576485183|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=XVfRYEWt16YdknAnWSDxwoE3oz0yGnK2JRRuVX4A2RY%3D&reserved=0, based on what you are saying, is the existing statement in the parameter description valid or invalid?
To disable this feature, specify the value ([System.Threading.Timeout]::InfiniteTimeSpan).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Foffice-docs-powershell%2Fissues%2F6856%23issuecomment-728207248&data=04|01|Abdallah.Galal%40microsoft.com|61fed22e603c4bfa557c08d88a54715f|72f988bf86f141af91ab2d7cd011db47|1|0|637411442576495178|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=MatsrGPRHpeczUdn4V4evu9Su6xMYOcd%2BpmY1YJANiI%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FARYI2VFFHEZDT5JKQVKQQVDSQFN35ANCNFSM4TWA6BIA&data=04|01|Abdallah.Galal%40microsoft.com|61fed22e603c4bfa557c08d88a54715f|72f988bf86f141af91ab2d7cd011db47|1|0|637411442576495178|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=1GCRYBVUhkHpq%2BpUVg1zlhD%2BjM8Qzq78gEx2KVczulc%3D&reserved=0.

Thanks, I'll leave that line in there.
I updated the topic as you described.
Thanks for the feedback.
Closing

When this will reflect in the online version?
From: Chris Davis<EMAIL_ADDRESS>Sent: Monday, November 16, 2020 9:49 PM
To: MicrosoftDocs/office-docs-powershell<EMAIL_ADDRESS>Cc: Abdallah Galal<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/office-docs-powershell] [-PreferenceMoveFrequency ] | upper limit (#6856)
Closed #6856https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Foffice-docs-powershell%2Fissues%2F6856&data=04|01|Abdallah.Galal%40microsoft.com|13ade2a4fc514f9067f808d88a68aab2|72f988bf86f141af91ab2d7cd011db47|1|0|637411529437508406|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=fsJFZ0C8%2FWLAx6N5wyX%2FS2e81d4ih%2FIZVYGN%2FYReKR0%3D&reserved=0.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Foffice-docs-powershell%2Fissues%2F6856%23event-4002041078&data=04|01|Abdallah.Galal%40microsoft.com|13ade2a4fc514f9067f808d88a68aab2|72f988bf86f141af91ab2d7cd011db47|1|0|637411529437508406|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=lXghz2VBw%2BAe%2B9iJDHxOWa7KOxTP%2BGwJ2NdN2uFN4H4%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FARYI2VCNEHBAV4MM2NZDJGLSQF623ANCNFSM4TWA6BIA&data=04|01|Abdallah.Galal%40microsoft.com|13ade2a4fc514f9067f808d88a68aab2|72f988bf86f141af91ab2d7cd011db47|1|0|637411529437518405|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=dOg6vIWB3nHFVqGNy4jLfXk3z%2FwKN3X2jOf0oTpnFqg%3D&reserved=0.

Sorry, I forgot to merge Master to Live. It should be visible within a few minutes.


feat(#167): Remove Code Duplication between ImprovementDistilledObjects and XmlClass

Remove duplicated methods in ImprovementDistilledObjects. Use XmlClass methods instead.
Closes: #167.

History:

feat(#167): remove duplicated methods
feat(#167): remove redundant methos
feat(#167): remove redundant methods
feat(#167): use XmlClass to retrieve fields
feat(#167): add 'constructors' method to XmlClass
feat(#167): remove duplicated method
feat(#167): fix all qulice suggestions

PR-Codex overview
Detailed summary

Added XmlClass constructor that takes a Node parameter
Added constructors method to XmlClass that retrieves all constructors from XMIR
Refactored removeOldConstructors method in ImprovementDistilledObjects to use XmlClass and XmlMethod
Refactored replaceMethodContent method in ImprovementDistilledObjects to use XmlClass and XmlMethod
Removed unused methods in ImprovementDistilledObjects (methods, objects, instructions, sequence, isInstruction)

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@maxonfjvipon reminder

@maxonfjvipon Done. Could you have a look one more time, please?

@rultor merge

@rultor merge

@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@volodya-lombrozo Done! FYI, the full log is here (took me 3min)


Beta - Waypoint: Use Comments to Clarify Code - No or wrong validation

Challenge http://beta.freecodecamp.com/challenges/waypoint-use-comments-to-clarify-code has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
First check: "Start a comment with ." is not validated correctly.
This is my code:

jQuery Playground

#left-well

        <button class='btn btn-default target' id='target1'>#target1</button>
        <button class='btn btn-default target' id='target2'>#target2</button>
        <button class='btn btn-default target' id='target3'>#target3</button>

#right-well

        <button class='btn btn-default target' id='target4'>#target4</button>
        <button class='btn btn-default target' id='target5'>#target5</button>
        <button class='btn btn-default target' id='target6'>#target6</button>

https://github.com/FreeCodeCamp/FreeCodeCamp/issues/1534

Closing as duplicate
Please see https://github.com/FreeCodeCamp/FreeCodeCamp/wiki/Searching-for-Your-Issue-on-Github


ractive.observe should always be async

I've run into the case of needing to run the callback in ractive.observe on init and on changes, but there's a chance that the callback will cancel the observer itself. This fails in cases where the canceling happens in the init. A trivial example:
console.log('output 1');
var observer = ractive.observe('property', function() {
    // some code
    console.log('output 3');
    if (somethingtrue) {    // if this happens to be true on init...
        observer.cancel();  // ...this throws a TypeError
    }
    // some more code
}, { defer: true, init: true });
console.log('output 2');

This will throw a TypeError: Cannot read property 'cancel' of undefined. The callback is being called before ractive.observe can return the object to set to observer, so the observer.cancel call is being called on an undefined value. I can't rely on observer existing within the callback. The ideal flow would end up outputing:
output 1
output 2
output 3

but instead it outputs:
output 1
output 3
output 2

If there were more code after the output 2, I can't be sure if the observer has already run once yet.
In @isaacs's blog post about async apis, the problem is explained pretty well:

If you have an API which takes a callback,
and sometimes that callback is called immediately,
and other times that callback is called at some point in the future,
then you will render any code using this API impossible to reason about, and cause the release of Zalgo.

The only true work around (that I can think of) would look like:
// some code
if (somethingtrue) {
    var observer = ractive.observe('property', function() {
        // some code (same code as above)
        if (somethingtrue) {
            observer.cancel();
        }
        // some more code (same code as below)
    }, { defer: true, init: true });
}
// some more code

Though there's obviously some way to not write the same code twice (defining the before and after code in separate function, for example), this is the sort of thing that having ractive.observe running on init by default should prevent, afaik.

Observer callbacks, by default, execute immediately when created. To prevent it from firing during creation, observe accepts a config object as second argument where you can set init to false.

That doesn't deal with the issue completely. If we did want the callback to run initially but there was a condition that could cancel the observer, that wouldn't be possible as is.
i.e.
var observer = ractive.observe('property', function(some_value) {
    // maybe do some stuff
    if (some_value === 'DONE_OBSERVING') {
        observer.cancel(); // This throws a TypeError if it happens the first time
    }
    // maybe do some other stuff
});

Well, your first post didn't include your use case, so we are left guessing what you are really doing. Would you mind putting a sample use case on the first post?

In @isaacs's blog post about async apis, the problem is explained pretty well

This doesn't apply to this api because ractive.observe is an event emitter, not an asynchronous api. (For the later case, promises work, for event emitters promises don't work).
Furthermore, ractive.observe without { init: false } (and without { defer: true }( should always fire immediately and synchronously. Please post an example if you are seeing this behavior.

I updated my initial post, hopefully it adds clarity.
I tried using the options { init: true, defer: true } but this did nothing different. Is that not what @martypdx meant?
I suppose a use case is that the observer can be cancelled based on the value its observing. If I'm approaching this incorrectly, what is the expected way of:

Running the same code for initialization and value changes AND
having a condition where the observer can be cancelled within the callback (or in the case of init... not being setup up to begin with?)

Or is this a use case that Ractive is not designed to handle?

I was under the assumption that a large part of ractive was asynchronous, i.e. doing an ractive.set would affect the dom later in the event loop. I see that I am wrong. Closing issue.

I tried using the options { init: true, defer: true } but this did nothing different. Is that not what @martypdx meant?

init: true is the default, setting it to false prevents initial firing, but I don't think that's what you want (see http://docs.ractivejs.org/latest/ractive-observe for info on options).
For your use case, I think you need to just guard against an initial value:

if ( ractive.get('property') !== 'DONE_OBSERVING' ) {
    var observer = ractive.observe('property', function(some_value) {
        if (some_value === 'DONE_OBSERVING') {
            observer.cancel();
        }
        // maybe do some other stuff
    });
}

You could even wrap that in a prototype method:
Ractive.prototype.observeUntil = function ( keypath, cancel, handler, options ) {
    if ( cancel( this.get(keypath) ) ) return;
    var observer = this.observe(keypath, function(n, o, k){
        if ( condition(n) ) return observer.cancel();
        handler.call( this, n, o, k );
    }, options);
}


Pickle detected this about the MODELS, how do I know they are safe?

Hello I noticed this about the models, PICKEL detected these lines:

How can I be sure they are safe?
Thanks

Warning
The pickle module is not secure. Only unpickle data you trust.
It is possible to construct malicious pickle data which will execute arbitrary code during unpickling. Never unpickle data that could have come from an untrusted source, or that could have been tampered with.
Consider signing data with hmac if you need to ensure that it has not been tampered with.
Safer serialization formats such as json may be more appropriate if you are processing untrusted data. See Comparison with json.
source: https://docs.python.org/3/library/pickle.html

Thanks a lot, we will check it and try to fix it soon


Search works only into 2/3 providers since version 0.0.58

Hi Denis @elgatito
starting from Burst version 0.0.58 the search is made only into 2/3 providers also if I have more then 2 enabled...
It seems to search only on 1337x and on Zoogle (that seems why 1337x is the first one and Zoogle is the last one).
Here the Kodi log of the same search criteria:
search with version 0.0.57 (search working on multiple providers): https://paste.ee/p/O0qGd
search with version 0.0.60 (search NOT working on multiple providers): https://paste.ee/p/rk9gW
Thanks!

@iz8mbw change logging level to DEBUG in Burst settings and make new logs.

Hi @elgatito
here the new logs with Debug:
search with version 0.0.57 (search working on multiple providers): https://paste.ee/p/AUTAJ
search with version 0.0.60 (search NOT working on multiple providers): https://paste.ee/p/ZlUjq
Thanks.

@iz8mbw It is not with Debug. It the same log level.
In Burst addon setting there is a setting for log level inside this specific addon.

@elgatito this is what I did.
This is the setting I enabled:

@iz8mbw That is not the required setting. You need the one that is selecting log level. And enable debug logging in Kodi, if not yet enabled.

so you mean Kodi Debug level, not Burst Debug level. Ture?

@iz8mbw Sorry, Burst does not have log level setting. That is managed by Elementum setting of Log level.
It should help to get full log.

Check that if now are OK.
LOG.zip

ping

@iz8mbw No, it's the same. You can enable debug logging everywhere, maybe something is cutting log for you.
Enable debugging in Kodi.
Enable DEBUG level in Elementum addon settings.
Disable proxy internal proxy debugging in Elementum settings.
Disable parser logging in Burst settings.

@elgatito hope now it's OK, see attached file.
last.zip
Denis may be this details can help you: with version of Burst from 0.0.58 to more recent (the versions with issues), graphically I don't see that Burst will go to search into all enabled provider.. In fact the search is very very fast because, in my opinion, Burst will NOT really use all enabled providers (so don't access on them website).

@elgatito hope now it's OK, see attached file.
last.zip
Denis may be this details can help you: with version of Burst from 0.0.58 to more recent (the versions with issues), graphically I don't see that Burst will go to search into all enabled provider.. In fact the search is very very fast because, in my opinion, Burst will NOT really use all enabled providers (so don't access on them website).

How do you use jacket? I've installed it but don't have an API.

Jackett is not working well with Elementum.
So ignore it, it was a test

@iz8mbw Yes, now log is complete.
When the issue started for you?

@elgatito starting from version 0.0.58.
So the problem is with 0.0.58, 0.0.59 and 0.0.60.
0.0.57 was OK.

Tested both on Android TV and Windows, same behavior (same issue)

@iz8mbw Please, try v0.0.61

@elgatito thanks Danis, 0.0.61 works again!
Many thanks for your support.
Going to close this issue.


Grid power down does not work as expected

Oh yeah, good ol Sermatec and their horrible naming. Need to find the correct sensor.

Fixed, it was caused by parsing at wrong indexes...


Covert wait_time to integer

In the following line, sleep() is expecting an Integer while the user input --wait-time will be a string
https://github.com/fullhunt/log4j-scan/blob/7be0f1c02ce3494469dc73a177e6f0c96f0016d9/log4j-scan.py#L337
This causes the following exception
Traceback (most recent call last):
  File "/home/KING/Code/Python/log4j-scan/log4j-scan.py", line 336, in <module>
    main()
  File "/home/KING/Code/Python/log4j-scan/log4j-scan.py", line 324, in main
    time.sleep(args.wait_time)
TypeError: an integer is required (got type str)

Solution

time.sleep(int(args.wait_time))

@KINGSABRI Just pushed a fix now, thank you!! :)
https://github.com/fullhunt/log4j-scan/commit/5607ee6d0831af59f2c79b6cb6ea23427916dcc9


Failed to install grpcio on OpenBSD 7.2

What version of gRPC and what language are you using?
grpcio-1.51.1
What operating system (Linux, Windows,...) and version?
OpenBSD 7.2
What runtime / compiler are you using (e.g. python version or version of gcc)
$ c++ --version
OpenBSD clang version 13.0.0
Target: amd64-unknown-openbsd7.2
Thread model: posix
InstalledDir: /usr/bin
What did you do?
pip install grpcio
What did you expect to see?
successfully installed package
What did you see instead?
  In file included from third_party/abseil-cpp/absl/time/internal/cctz/src/time_zone_format.cc:28:
  In file included from third_party/abseil-cpp/absl/time/internal/cctz/include/cctz/time_zone.h:30:
  In file included from third_party/abseil-cpp/absl/time/internal/cctz/include/cctz/civil_time.h:19:
  In file included from third_party/abseil-cpp/absl/time/internal/cctz/include/cctz/civil_time_detail.h:20:
  In file included from /usr/include/c++/v1/ostream:140:
  In file included from /usr/include/c++/v1/locale:218:
  /usr/include/c++/v1/__bsd_locale_fallbacks.h:122:17: error: use of undeclared identifier 'vasprintf'; did you mean 'vsprintf'?
      int __res = vasprintf(__s, __format, __va);
                  ^
  /usr/include/c++/v1/cstdio:124:9: note: 'vsprintf' declared here
  using ::vsprintf _LIBCPP_USING_IF_EXISTS;
          ^
  In file included from third_party/abseil-cpp/absl/time/internal/cctz/src/time_zone_format.cc:28:
  In file included from third_party/abseil-cpp/absl/time/internal/cctz/include/cctz/time_zone.h:30:
  In file included from third_party/abseil-cpp/absl/time/internal/cctz/include/cctz/civil_time.h:19:
  In file included from third_party/abseil-cpp/absl/time/internal/cctz/include/cctz/civil_time_detail.h:20:
  In file included from /usr/include/c++/v1/ostream:140:
  In file included from /usr/include/c++/v1/locale:218:
  /usr/include/c++/v1/__bsd_locale_fallbacks.h:122:27: error: cannot initialize a parameter of type 'char *' with an lvalue of type 'char **'
      int __res = vasprintf(__s, __format, __va);
                            ^~~
  /usr/include/stdio.h:269:21: note: passing argument to parameter here
  int      vsprintf(char *, const char *, __va_list);
                          ^
  third_party/abseil-cpp/absl/time/internal/cctz/src/time_zone_format.cc:651:10: error: use of undeclared identifier 'strptime'
      dp = strptime(dp, fmt, tm);
           ^
  3 errors generated.
  creating tmp
  creating tmp/tmp3rilb33i
  cc -pthread -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -O2 -pipe -g -fPIC -O2 -pipe -g -O2 -pipe -g -fPIC -I/home/segoon/projects/userver/build/venv-userver-testenv/include -I/usr/local/include/python3.9 -c /tmp/tmp3rilb33i/a.c -o tmp/tmp3rilb33i/a.o
  Traceback (most recent call last):
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/unixccompiler.py", line 186, in _compile
      self.spawn(compiler_so + cc_args + [src, '-o', obj] + extra_postargs)
    File "/tmp/pip-install-2swyyr9q/grpcio_fe47679f1ff244029f2a115f2302c92c/src/python/grpcio/_spawn_patch.py", line 54, in _commandfile_spawn
      _classic_spawn(self, command)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/ccompiler.py", line 1007, in spawn
      spawn(cmd, dry_run=self.dry_run, **kwargs)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/spawn.py", line 70, in spawn
      raise DistutilsExecError(
  distutils.errors.DistutilsExecError: command '/usr/bin/cc' failed with exit code 1

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/tmp/pip-install-2swyyr9q/grpcio_fe47679f1ff244029f2a115f2302c92c/src/python/grpcio/commands.py", line 280, in build_extensions
      build_ext.build_ext.build_extensions(self)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 468, in build_extensions
      self._build_extensions_serial()
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 494, in _build_extensions_serial
      self.build_extension(ext)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/command/build_ext.py", line 246, in build_extension
      _build_ext.build_extension(self, ext)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 549, in build_extension
      objects = self.compiler.compile(
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/ccompiler.py", line 599, in compile
      self._compile(obj, src, ext, cc_args, extra_postargs, pp_opts)
    File "/tmp/pip-install-2swyyr9q/grpcio_fe47679f1ff244029f2a115f2302c92c/src/python/grpcio/commands.py", line 263, in new_compile
      return old_compile(obj, src, ext, cc_args, extra_postargs,
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/unixccompiler.py", line 188, in _compile
      raise CompileError(msg)
  distutils.errors.CompileError: command '/usr/bin/cc' failed with exit code 1

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "<string>", line 2, in <module>
    File "<pip-setuptools-caller>", line 34, in <module>
    File "/tmp/pip-install-2swyyr9q/grpcio_fe47679f1ff244029f2a115f2302c92c/setup.py", line 535, in <module>
      setuptools.setup(
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/__init__.py", line 87, in setup
      return distutils.core.setup(**attrs)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 185, in setup
      return run_commands(dist)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
      dist.run_commands()
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
      self.run_command(cmd)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/dist.py", line 1208, in run_command
      super().run_command(command)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
      cmd_obj.run()
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/wheel/bdist_wheel.py", line 325, in run
      self.run_command("build")
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
      self.distribution.run_command(command)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/dist.py", line 1208, in run_command
      super().run_command(command)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
      cmd_obj.run()
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/command/build.py", line 132, in run
      self.run_command(cmd_name)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
      self.distribution.run_command(command)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/dist.py", line 1208, in run_command
      super().run_command(command)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
      cmd_obj.run()
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/command/build_ext.py", line 84, in run
      _build_ext.run(self)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 346, in run
      self.build_extensions()
    File "/tmp/pip-install-2swyyr9q/grpcio_fe47679f1ff244029f2a115f2302c92c/src/python/grpcio/commands.py", line 284, in build_extensions
      raise CommandError(
  commands.CommandError: Failed `build_ext` step:
  Traceback (most recent call last):
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/unixccompiler.py", line 186, in _compile
      self.spawn(compiler_so + cc_args + [src, '-o', obj] + extra_postargs)
    File "/tmp/pip-install-2swyyr9q/grpcio_fe47679f1ff244029f2a115f2302c92c/src/python/grpcio/_spawn_patch.py", line 54, in _commandfile_spawn
      _classic_spawn(self, command)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/ccompiler.py", line 1007, in spawn
      spawn(cmd, dry_run=self.dry_run, **kwargs)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/spawn.py", line 70, in spawn
      raise DistutilsExecError(
  distutils.errors.DistutilsExecError: command '/usr/bin/cc' failed with exit code 1

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/tmp/pip-install-2swyyr9q/grpcio_fe47679f1ff244029f2a115f2302c92c/src/python/grpcio/commands.py", line 280, in build_extensions
      build_ext.build_ext.build_extensions(self)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 468, in build_extensions
      self._build_extensions_serial()
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 494, in _build_extensions_serial
      self.build_extension(ext)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/command/build_ext.py", line 246, in build_extension
      _build_ext.build_extension(self, ext)
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 549, in build_extension
      objects = self.compiler.compile(
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/ccompiler.py", line 599, in compile
      self._compile(obj, src, ext, cc_args, extra_postargs, pp_opts)
    File "/tmp/pip-install-2swyyr9q/grpcio_fe47679f1ff244029f2a115f2302c92c/src/python/grpcio/commands.py", line 263, in new_compile
      return old_compile(obj, src, ext, cc_args, extra_postargs,
    File "/home/segoon/projects/userver/build/venv-userver-testenv/lib/python3.9/site-packages/setuptools/_distutils/unixccompiler.py", line 188, in _compile
      raise CompileError(msg)
  distutils.errors.CompileError: command '/usr/bin/cc' failed with exit code 1

  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for grpcio

OpenBSD is not a officially supported platform for BSD
This looks like a compilation failure unrelated to gRPC.

  /usr/include/c++/v1/__bsd_locale_fallbacks.h:122:17: error: use of undeclared identifier 'vasprintf'; did you mean 'vsprintf'?
      int __res = vasprintf(__s, __format, __va);

OpenBSD does seem to have vasprintf. Are you sure your build environment is set up correctly?


Atomic Recipes do not work when importing values from other files

Description
Don't know if this is a limitation or a bug, currently when using sva and importing values from other modules doesn't work.
import { checkboxAnatomy } from '@ark-ui/solid'
import { sva } from '../styled-system/css'

export const checkbox = sva({
	slots: checkboxAnatomy.keys(),
})

Tho' it works when defining recipes:
import { checkboxAnatomy } from '@ark-ui/solid'
import { defineSlotRecipe } from '@pandacss/dev'

export const checkbox = defineSlotRecipe({
	slots: checkboxAnatomy.keys(),
})

If this is a limitation, it would be useful to add a note in the documentation.
Link to Reproduction
https://stackblitz.com/edit/vitejs-vite-4nh1aj?file=src%2Fsva.ts
Panda CSS Version
0.14

@navaru the whole of Panda works by static extraction, Panda reads your files, so it can't know the value of imported stuff


Request to not configure logging as an import-time side-effect (on Python 2)

We just tracked down some surprising behaviour in our test runs to the fact that fontTools configures logging at import time, swapping out the default Logger class for a custom implementation and adding a handler of last resort. The relevant code is in the py23 module here. I understand the motivation here (having consistent behaviour between Python 2 and Python 3), but it's a surprise to find a library doing logging configuration: in general, my understanding of logging best practices is that logging configuration should be the domain of an application (where a test runner also counts as a form of application) using libraries that do logging, rather than the libraries themselves. (Imagine if each of the many libraries being used in an application tried to do its own logging configuration...)
Would you consider removing the logging configuration as an import-time side-effect of importing fontTools?
Code to reproduce the issue. Part of the surprise here is just in the logger's repr resulting from the patched Logger class: seeing fontTools.misc.py23 turn up in the repr of a logger that has nothing to do with the fontTools library.
Enthought Deployment Manager -- https://www.enthought.com
Python 2.7.13 |Enthought, Inc. (x86_64)| (default, Mar  2 2017, 08:20:50)
[GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import logging
>>> logging.lastResort
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'module' object has no attribute 'lastResort'
>>> import fontTools
>>> logging.lastResort
<fontTools.misc.py23._StderrHandler object at 0x1007a4310>

Thanks for opening this issue.
Just out of curiosity, what is this "surprising behaviour in your test runs"?
I don't really see what we are doing here as a "logging configuration", but rather more like adding a compatibility shim to enable logging code to behave the same way on python 2 and 3.
the recommendation to set lastResort to None, comes from the python 3 docs actually:
https://docs.python.org/3.6/howto/logging.html#what-happens-if-no-configuration-is-provided

But I see your point that just the mere import fontTools should not automatically swap the default python2 Logger class with one that defines a lastResort handler (like the python3 Logger).
I'll move that code to our own configLogger function, which is used only by our own command line scripts.
I'll fix this soon, sorry the trouble!

what is this "surprising behaviour in your test runs"

Simply that we were seeing messages printed out during the test run, and since they didn't have any kind of "WARNING: ..." prefix, it wasn't immediately clear that they were coming from the logging system. When it did become clear that they were logging messages, it wasn't clear why they were being printed out, and we needed to do some digging to find out how this was happening. This is (currently, at least) a Python 2-only application, and the behaviour we expect to see if no logging is configured is the usual "No handlers could be found" message. fontTools is just one of many (over 100) packages used by the application. The new messages started showing up in the test suite after various package updates, and it wasn't clear which of those updates caused the behaviour change.

the recommendation to set lastResort to None, comes from the python 3 docs actually

Understood; that's definitely the right way for a Python 3 application to get back the Python 2 behaviour. But it's surprising when a Python 2 application isn't following the usual logging behaviour, without the application having explicitly configured the logging system.

fixed by https://github.com/fonttools/fonttools/commit/e6a5db543d8a5be34db5d007a9d5634ae2a2edde
a new release is coming before end of the week
thanks for using fonttools!

Wow! Thanks for the quick fix!


Bug: Fix geocoding sample

Sample
Geocoding Sample
Checklist

[x] PR title follows convention - keyword: Short description of change
[x] PR targets the correct branch
[x] New Blueprints follow Unreal Naming Convention
[x] Self-review of changes
[x] There are no warnings related to changes
[x] A build was made and tested on all relevant platforms
[x] No unrelated changes have been made to any other code or project files
[x] No unnecessary includes or namespaces added
[x] Code follows plugin coding style
[x] New code and changed code has proper formatting
[x] No unintentional formatting changes
[x] Commits have descriptive titles

Blueprints
N/A
ArcGIS Maps SDK Version
Maps SDK 1.7 w/ UE 5.3

Copying my comments from another PR to here:
While testing I do notice a UX improvement which is that when users enter incomplete address there's no feedback. Although I think this can be a different PR.
Still trying to figure out when this happens because when I enter "1919 McIntyre Street" it doesn't take me anywhere, which I guess is because of incomplete address? Because "1919 McIntyre Street, Ann Arbor" does return a place.
but when I enter "380 new york street" which is also incomplete, it does take me to somewhere

Maybe this is just because of the issue with REST API?
It would still be useful if on the instruction banner below we can show a message when this happens.

is just because of the issue with REST API?
It would still be useful if on the instruction banner below we can show a message when this happens.
Yes it is because that address doesn't return any candidates. You can check it by opening https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?f=pjson&singleLine=1919 McIntyre Street&token=

I think it is useful to have a note (similar to the one for multiple candidates). I will leave it to @mmgaw113 and @ZackAllen whether that should be done in this PR.

I think it is useful to have a note (similar to the one for multiple candidates). I will leave it to @mmgaw113 and @ZackAllen whether that should be done in this PR.

I created this issue https://devtopia.esri.com/runtime/normandy/issues/2997 in case we forget about these things


Issue #223: added oc-env step for minishift

@cmoulliard mind taking a look?

@Ladicek updated per feedback. Let me know what you think, otherwise, i'll merge later today

Thanks @Ladicek, merging.

resolves #223


RendermanForBlender Renderman 24 version makes Blender preferences window incredibly laggy

Pretty self-explanatory
RendermanForBlender Renderman 24 version makes Blender preferences window incredibly laggy when the "Renderman For Blender" add-on preferences are rolled out. Interestingly the preferences window goes back to being snappy the moment you un-roll the preferences.

Just committed a fix for this.


erroneous "en" config in parquet-and-info for dataset aakanksha/udpos

Here:
https://github.com/huggingface/datasets-server/blob/09e3f9827048d552c4aefc8125fe6366dbeabc34/services/worker/src/worker/job_runners/config/parquet_and_info.py#L422
builder.config.name is changed from default(the correct value) to en, which breaks the final response (parquet files are created under en/ directory, which later does not match with the expected default config).
I have no idea why, or how to fix that.

I assign you @lhoestq, I imagine you should have a better idea.

Once fixed, close #1582 and refresh the datasets listed in
db.cachedResponsesBlue.aggregate([
    {$match: {error_code: "PreviousStepFormatError", "kind": "config-parquet-metadata"}},
    {$group: {_id: 0, datasets: {"$addToSet": "$dataset"}}},
])

Taking a look

Just opened https://github.com/huggingface/datasets/pull/6253
We'll have to refresh those datasets when the fix will be released

Is this issue obsolete now that dataset scripts are disabled?
I just refreshed the example dataset https://huggingface.co/datasets/aakanksha/udpos, and it shows

should we close @lhoestq ?


Revert 29 docs/footer

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 6 committers have signed the CLA.:white_check_mark: Palanikannan1437:white_check_mark: anjy7:x: Chiranjeev-droid:x: KapadiaNaitik:x: rohitg00:x: KadlagAkashYou have signed the CLA already but the status is still pending? Let us recheck it.


Exclusive audio device lock.

From @romeojulietthotel on May 30, 2017 1:46
Pothos takes an exclusive lock on the audio device.  I can't think of a reason why it would need to do this. I can run multiple ffplay and they get along fine. But if I then start Pothos while an ffplay is running Pothos spews out errors constantly into the "Message Window".
On stdout I see this:

Expression 'parameters->channelCount <= maxChans' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1513
Expression 'ValidateParameters( outputParameters, hostApi, StreamDirection_Out )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1845

If I start Pothos and then try to play audio via ffplay, ffplay cannot acquire an audio device due the exclusive lock by Pothos.
I read this:
http://portaudio.com/docs/v19-doxydocs/api_overview.html

I/O Methods: callback and read/write
PortAudio offers two methods for communicating audio data between an open Stream and your Application: (1) an asynchronous callback interface, where PortAudio calls a user defined callback function when new audio data is available or required, and (2) synchronous read and write functions which can be used in a blocking or non-blocking manner. You choose between the two methods when you open a Stream. The two methods are discussed in more detail below.

Copied from original issue: pothosware/pothos-gui#150

@romeojulietthotel I'm not sure what takes the lock, but I was thinking that one possibility would be to move the call to Pa_OpenStream (from AudioBlock::setupStream) to the AudioSource/Sink::activate() function. That way there would be no lock acquired until the topology is actually activated.

 I have found some apps will use audio at the same time and some will not.  CubicSDR uses https://github.com/thestk/rtaudio/ and it also wants exclusive access to audio.


Set metadata source_code_uri

This commit adds 'source_code_uri' key to gemspec's metadata, which makes nanoc and the plugins compatible with  gem-src's functionality: without it there is no way to detect the source repo unless actually opening the homepage and navigate through it, which I believe is rather tedious.
The 'source_code_uri' item in gemspec's metadata is described in the guideline rubygems.org publishes, and it is what gem-src uses to prioritize when inferring which repo to clone.
I guess there are not many who have come across this issue, but what do you think of it anyway?
And last but not least, thanks for letting me have a chance to touch your product. I have had a lot of fun and I appreciate your effort 🤝

@sato11 Thank you!
I made two changes:

Fix Rubocop style (rubocop -a)

Fix the URL for nanoc. This one is tagged with just the version number, not as nanoc-v#{VERSION} for historical reasons.

In any case, the change is merged!

This is released in Nanoc 4.12.19.

@denisdefreyne Thanks for your passionate work!


Enabled editing allowedTags in runtime, which allows adding and remov…

Enabled editing allowedTags in runtime, which allows adding and removing allowed tags dynamically.

Coverage decreased (-0.2%) to 84.164% when pulling 0d0bfdb495b80790493a4015a2cfab52977a2d90 on odedd:access_allowedTags into 361503ab947a060bf333080785fc7cacb589b60c on okcoker:master.

You can use the setOptions method added here https://github.com/okcoker/taggle.js/commit/275c8a16e4391f8553643d25bdd1992482e3f24d


Update to React 18

We should update to React 18 as it has many advantages like automatic batching and the new hooks.

We will get to it in the next release as part of updating all the frontend deps.
Related to

https://github.com/headlamp-k8s/headlamp/issues/1992


Updated issue template

IMO we should consider github's new multi-template feature. We could have separate templates for feature requests, bug reports, and questions about how to use the product.

👍 seems like a better way to do it. @Eilon / @muratg / @mkArtakMSFT probably have permissions to enable it.

As long as we have agreement on what to do from @Eilon , we don't need special GitHub permissions to add these. The templates are stored as files in the repo. Example: https://github.com/natemcmaster/CommandLineUtils/tree/master/.github/ISSUE_TEMPLATE

Great!

Cool

I updated our regular issue template, as seen here: https://github.com/aspnet/Home/blob/master/.github/ISSUE_TEMPLATE.md
The multi-issue-template thing is certainly cool, and something to consider in the future.