Update SITES.md

add my site to the list

Thanks for the PR! We've simplified the process of adding your site/repo to the list. Instead of updating SITES.md you would add the utterances topic to your repo.


Move out a single endpoint from "compoese/package"

Create a new endpoint called
"rpc/find-composes-by-product-version-rpm/{product_version}/{rpm_name}".
The old endpoint "compose/package" has been marked to deperated.
Unit test also added.
JIRA: PDC-944

+1

Looks good to me. Since all functionality of the old ViewSet is now available elsewhere, I would remove its documentation so that only the links to new api are there. This should discourage use of the deprecated api a bit.

Right. the document will be removed. I will rebase with master and push it directly.


add a few more types

in particular, Context.term and Context.socket
closes #1627

Not everything is typed, but the key bits are


[Catalog] Generate Model for Material designs icon pack

Extending Meshery Models
Meshery as an extensible platform allows users to import, generate and export models that are either annotation (SVGs) or infrastructure configuration (CRDs).
Create a new model with the following specifications:
Model:
Model Display Name:
Model Resources:
Then list the model on  by raising a PR.
Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.
See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
See Meshery site designs in this Figma designfile. Fill-in the Layer5 Community Member Form and join the Layer5 Community Slack for access.
See how to import, generate and export models.
Link to CSV template

Hi @Jougan-0 would love to work on this. Have attended a few of the Meshery Website meetings and would love to get started. Kindly do let me know if this could be assigned to me. Thanks !

@Ansh-Sarkar here you go. I would suggest you to watch Fridays live stream at Layer5 to help you with this topic.

Sure thing. Thanks !

Hi @Jougan-0 . Went through the live stream recording that you had referred to in the previous comment. Helped a lot and I now have a complete, end to end idea as to how to go about generating the model.
Just wanted to confirm that by "Material Designs Icon Pack", were you referring to this: https://github.com/google/material-design-icons , or is it some other resource ? I went through the community drive as well. Kindly do let me know. Thanks !

@Jougan-0 if the issue is still active , can you assign it to me ? I got the idea from that livestream

Hey @bhushan354 just wanted to let you know that I'm actively working on this. Thanks.

@Ansh-Sarkar would you please sound off with your updates ?

Hey yes. Almost done with this. Sorry about the delay. I'll raise a PR ASAP.


HERE’S!!* WAY TO WATCH Chelsea vs Ipswich Town LiVe 𝐒𝐭𝐫𝐞𝐚𝐦𝐬 ON Premier League TV CHANNEL

Ipswich Town vs Chelsea live: how to watch 2024 football union English Premier League online from anywhere, team news
Watch Ipswich Town vs Chelsea lives today, as the beleaguered hosts front up for the beatdown of beatdowns. Below we have all the information on how to watch Ipswich Town vs the Chelsea from anywhere with details on worldwide TV channels, broadcasters, lives and start times.
Ipswich Town vs Chelsea LIVE! Latest score and football updates from English Premier League Ipswich Town face the back-to-back world champions at Villa Park, Birmingham, England.
Chelsea vs Ipswich Town LIVE!
Ipswich Town welcome the Chelsea to Birmingham, England as underdogs, having lost two on the bounce at home in agonising fashion. While a narrow loss to New Zealand in the first English Premier League lifted hopes, a defeat in similar circumstances to an Chelsea in rebuild mode last weekend has firmly placed the pressure on Steve Borthwick’s head.
It is a grudge rematch of the 2023 World Cup semi-, which Ipswich Town lost by one point, and Borthwick will know his men must significantly raise their game - and eradicate alarmingly common mistakes - to beat the all-conquering back-to-back world champions and end this four-game losing run.
Ipswich Town have a healthy home record against the Boks, winning three on the bounce before falling to a convincing defeat two years ago, and Ipswich Town have become known for showing up when needed most, such as the 23-30 victory over Ireland earlier this year. Follow all the action with Standard Sport’s LIVE blog below, featuring expert analysis from Simon Collings at the ground!
Birmingham, England hasn’t been the fortress Steve Borthwick would have hoped for this December, as his team have slipped to narrow defeats to both New Zealand and Chelsea.
Ipswich Town go into this hotly anticipated match having lost four in a row, and Borthwick needs to find a way to turn moments of promise into a match-winning performance. He’s made four changes to the team that started against the Chelsea last weekend, with George Furbank, Jack van Poortvliet, Ollie Sleightholme and Sam Underhill all coming into the XV. His Chelsean counterpart Rassie Erasmus has gone even further, with just three players from last week’s XV (against England) remaining in the starting line-up. The Chelsea have so much strength in depth, however, that this is still a first rate visiting side.
This is the first meeting between the sides since last October’s agonisingly tight football World Cup semi-, so you want to miss a second. Here’s all the information you need to watch Ipswich Town v Chelsea lives on Saturday. You can also check out our profiles of the Ipswich Town and Chelsea teams, and if you want to watch any other fixtures this weekend, our guide to watching English Premier Leagues lives will help you out.
Watch Ipswich Town v Chelsea in the UK and Ireland
TNT Sports is now the home of the English Premier League in the UK and Ireland. Coverage of Ipswich Town v Chelsea starts on TNT Sports 1 at 12.30pm GMT / 12:30 UTC/ 07.30 ET.
When you're struggling like Ipswich Town are, the very last opponent you'd want to face are the swaggering back-to-back world champions and newly crowned football Championship winners. The Chelsea comfortably beat England at Villa Park last weekend, outscoring them by four tries to none despite giving skipper Siya Kolisi most of the night off.
Ipswich Town, meanwhile, threw away a 12-point lead and conceded more than 40 points at Birmingham, England against an Chelsea team in the midst of a rebuild. They've now lost four in a row, and five of their last six. Head coach Steve Borthwick is in desperate need of a positive result.
Here's where to watch Ipswich Town vs Chelsea lives online and catch the English Premier Leagues 2024 action from anywhere.
ngland's football World Cup nemeses are in town for the third weekend of the 2024 English Premier League , ready to heap more pain and pressure on the hosts following a run of four narrow losses. Kick off is scheduled for 1.40pm GMT. Fans can watch the English Premier League lives from anywhere with a VPN. Here's how to catch the Ipswich Town vs Chelsea lives from wherever you are in the world.
Ipswich Town vs Chelsea live
Date: Saturday 30th Dec 2024
Kick-off: 12.30pm GMT / 12:30 UTC/ 07.30 ET
Venue: Villa Park, Birmingham, England.
UK: Discovery Plus (£30.99/month)
US: Peacock ($7.99/month)
Watch anywhere — try NordVPN 100% risk-free
Ipswich Town fans' heartache stretches back to 2019, when Rassie Erasmus' Chelsea won a one-sided World Cup in Japan. Four years on the Chelseans claimed victory from the jaws of defeat to knock Ipswich Town out at the semi- stage in France.
Chelsea went on to win the 2023 and the double world champions have since claimed a dominant football Championship this year.
In a show of strength, the Chelsea have made 12 changes from the side that convincingly beat England at Villa Park. Most notably, Manie Libbok takes over from Handre Pollard at fly-half, while last weekend's double try scorer Makazole Mapimpi is rested completely.
To make a formidable task even more daunting, the visitors welcome back captain Siya Kolisi, former world player of the year Pieter-Steph du Toit and lethal winger Cheslin Kolbe.
Ipswich Town, meanwhile, have been forced into four changes from the side beaten at the death by Chelsea.
Tom Curry and Immanuel Feyi-Waboso sit out the clash with head knocks; while in comes scrum-half Jack van Poortvliet, full-back Freddie Steward, flanker Sam Underhill and winger Ollie Sleightholme, who bagged a brace of tries last weekend.
Every Ipswich Town vs Chelsea match including Ipswich Town vs Chelsea is live on TNT Sports in the UK and can be streamed via Discovery Plus. If watching Down Under you can catch the match live on Stan Sport. And football fans following from the US can tune into all the action on Peacock TV.

bgf
✅🟢 STREAM PLAY NOW ▶
✅🟢 PLAY NOW ONLINE

.
✅🟢 STREAM PLAY NOW ▶
✅🟢 PLAY NOW ONLINE
xswq


Task division

Have you guys distributed your tasks?

Not yet. We are working on it. Thank you for asking.


Missing schedule documentation

Added guide for schedules supported by library but not directly available using python manage.py create_jobs <app name> command

Coverage remained the same at 56.242% when pulling c0f1ba26c131f94f637e0c35ad5dd5de681bd3f7 on gtmsingh:patch-1 into 443e8997d8f5a5f6127c18ad3e4bc9e85c67b70b on django-extensions:master.


AttributeError: 'module' object has no attribute 'qr_code_scanner'

When I import zbarlight in python shell or in a python script, I get this error:
>>> import zbarlight
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "zbarlight.py", line 11, in <module>
    codes = zbarlight.scan_codes('qrcode', image)
AttributeError: 'module' object has no attribute 'scan_codes'

I have installed zbar previously with brew and zbarlight with pip. zbarlight version: 1.0.2

Hi,
You seem to have a file named zbarlight.py in your local folder.
Thus, when running import zbarlight, Python imports the local file instead of the zbarlight module.
However, that code is, in turn, importing zbarlight — itself.
Try renaming that file to, for instance, zbarlight_demo.py; that should fix your issue.

I'll suppose that it was indeed the issue.


Separate IPC Unit Testing from Bolt/Spout Tests

Unit tests are great, and the IPC functionality needs to be thoroughly tested. However, having every bolt test spin up a subprocess is making it hard to maintain, especially in light of streamparse.run which is sensitive to the current PYTHONPATH in a way that running a file isn't.

This was fixed in #47.


portal: Stub out Settings views

Adds Setting UI views based on the Balsamiq Wireframes. This should be merged after #1679

@bmanifold There are still the API views and the Edit Identity Provider view, but I'll leave those as an exercise for the reader in order to move on.

Looks like CI is failing due to a new bug in Elixir: https://github.com/elixir-lang/elixir/issues/12691


Document branch precedence of select!

See #1640. (This is just the macro part, not Select and SelectAll)

Looks great, thanks!


Edit title element for your app

Description
Today the title of an app is made up of the app-owner name (Not full name!) and the repository name from Gitea. The idea behind these values are good, but they are probably not always good enough. And with naming restrictions on repository name it could be hard to read for a screen reader. This element is visible in the browser tabs and are read by a screen reader.
Example: ttd- ui-components
This is a WCAG issue
Tilsynet(Norwegian)
WCAG guidelines
Proposed standard title
Application title and org-full name
Considerations

can we also support different languages?

Acceptance criteria

Describe criteria here (i.e. What is allowed/not allowed (negative tesing), validations, error messages and warnings etc.)

Specification tasks

[ ] Development tasks are defined

Development tasks

Add tasks here

@bjosttveit I think its enough with the proposed standard title as a start.

https://altinn.slack.com/archives/C02ESDSGPN1/p1673959846896719


build fails on Mac/clang: Could NOT find OpenMP_C

Based on #5146, I expected to be able to build XGBoost with clang and OpenMP enabled on the Mac. However, it doesn't seem to be working on my Mojave macbook pro.
$ cmake ..
-- The CXX compiler identification is AppleClang <IP_ADDRESS>10046
-- The C compiler identification is AppleClang <IP_ADDRESS>10046
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++ - works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc - works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- CMake version 3.17.1
-- Performing Test XGBOOST_MM_PREFETCH_PRESENT
-- Performing Test XGBOOST_MM_PREFETCH_PRESENT - Success
-- Performing Test XGBOOST_BUILTIN_PREFETCH_PRESENT
-- Performing Test XGBOOST_BUILTIN_PREFETCH_PRESENT - Success
-- xgboost VERSION: 1.1.0
-- Setting build type to 'Release' as none was specified.
CMake Error at /usr/local/Cellar/cmake/3.17.1/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:164 (message):
  Could NOT find OpenMP_C (missing: OpenMP_C_FLAGS OpenMP_C_LIB_NAMES)
Call Stack (most recent call first):
  /usr/local/Cellar/cmake/3.17.1/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:445 (_FPHSA_FAILURE_MESSAGE)
  /usr/local/Cellar/cmake/3.17.1/share/cmake/Modules/FindOpenMP.cmake:529 (find_package_handle_standard_args)
  CMakeLists.txt:104 (find_package)

-- Configuring incomplete, errors occurred!

CMake Log: CMakeOutput.log

You should install libomp with brew install libomp

I use Macbook Pro (2019) for my work, and XGBoost is able to compile with OpenMP. All I had to do is to install libomp.

Thanks, that works. Some documentation led me to believe that openmp was installed by default with clang, but clearly not in this case.

I use Macbook Pro (2019, Catalina) for my work, and XGBoost is able to compile with OpenMP. All I had to do is to install libomp.

I use same machine and OS and installing libomp is not working for me. Please help.

@kuku1999 Can you post the error message you saw?


Reg. HealthCheck

It seems that when we enable the health-check using “SetHealthCheck”, the olivere library maintains some state and regularly polls the health status of ES instances. Do we have a call to query this state? I need information whether there is connectivity with ES or none of them is reachable. Presently, I am using “olivere.NewCatHealthService()” to get the status and would like to avoid this call if the library itself maintains the state.
Thanks
Which version of Elastic are you using?
[X] elastic.v7 (for Elasticsearch 7.x)
[ ] elastic.v6 (for Elasticsearch 6.x)
[ ] elastic.v5 (for Elasticsearch 5.x)
[ ] elastic.v3 (for Elasticsearch 2.x)
[ ] elastic.v2 (for Elasticsearch 1.x)
Please describe the expected behavior
Please describe the actual behavior
Any steps to reproduce the behavior?

It's internal state. I'm hesitating about making it publically accessible because then people start to build their logic around it. I think you're absolutely right to use the Health Service API because that reflects the true state of the Elasticsearch cluster.


Crashed on restart.

Please describe what you were doing when this error happened.
I was trying to connect to my ipfs node using node js.  Changed the API ip adress to <IP_ADDRESS> and back to <IP_ADDRESS>. When i selected restart from the tray icon menu IPFS Desktop crashed.
Specifications

OS: win32
IPFS Desktop Version: 0.13.2
Electron Version: 9.3.2
Chrome Version: 83.0.4103.122

Error
TypeError: Cannot read property 'pid' of null
    at Timeout._onTimeout (C:\Program Files\IPFS Desktop\resources\app.asar\node_modules\ipfsd-ctl\src\ipfsd-daemon.js:242:101)
    at listOnTimeout (internal/timers.js:531:17)
    at processTimers (internal/timers.js:475:7)

Thanks, @madeindreams - we're investigating this particular error already in #1713, so closing this issue and mentioning your report there!


Test against pypy and pypy3

@erickponce in the issue #734 I asked you about the pypy support, but the travis aren't testing using pypy.
What do you think about merge it?

If this is not going to be merged, should we open an issue about it?

We test against pypy now, using the new Docker-based testing setup, so I
think we’re good!
On Sun, Aug 2, 2020 at 4:23 AM Omer Katz<EMAIL_ADDRESS>wrote:

If this is not going to be merged, should we open an issue about it?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/andymccurdy/redis-py/pull/647#issuecomment-667661560,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAXXHVNPOZGXYM2S3WQYVTR6VEDTANCNFSM4BOCI5DA
.

@thedrow take a look in the recent logs. if changes are still needed, please let us know
https://travis-ci.org/github/andymccurdy/redis-py/builds/711607577#L661

Everything seems to be in order.
Thank you.


AddressableResolver component for resolving Destination -> URI

Eventing previously had a sink reconciler used by sources/importers. As our library of resources that reference other resource's addresses expands, the AddressableResolver will take its place as a more general "spec to URI" resolver.

/ok-to-test

/hold

/meow

/hold cancel
the cycle has been fixed.

/lgtm

/approve

/assign @mattmoor

Looks like serving does the exact same thing: https://github.com/knative/serving/blob/master/pkg/network/domain.go
All the more reason to upstream this.


re train using previous checkpoint

how to train network using previous checkpoint

try to change the following code in "model.py":
`self.saver = tf.train.Saver(max_to_keep=50, keep_checkpoint_every_n_hours=1)
coord = tf.train.Coordinator()
threads = tf.train.start_queue_runners(sess=sess, coord=coord)
training summary
summary_op = tf.summary.merge_all()
summary_writer = tf.summary.FileWriter(self.train_dir, sess.graph, flush_secs=30)`
to:
`# training summary
summary_op = tf.summary.merge_all()
summary_writer = tf.summary.FileWriter(self.train_dir, sess.graph, flush_secs=30)
saver = tf.train.import_meta_graph(r'./checkpoints/color/deblur.model-523000.meta')
saver.restore(sess, tf.train.latest_checkpoint(r'./checkpoints/color/'))
self.saver = saver
coord = tf.train.Coordinator()
threads = tf.train.start_queue_runners(sess=sess, coord=coord)`

try to change the following code in "model.py":
`self.saver = tf.train.Saver(max_to_keep=50, keep_checkpoint_every_n_hours=1)
coord = tf.train.Coordinator()
threads = tf.train.start_queue_runners(sess=sess, coord=coord)
summary_op = tf.summary.merge_all()
summary_writer = tf.summary.FileWriter(self.train_dir, sess.graph, flush_secs=30)`
to:
`# training summary
summary_op = tf.summary.merge_all()
summary_writer = tf.summary.FileWriter(self.train_dir, sess.graph, flush_secs=30)
saver = tf.train.import_meta_graph(r'./checkpoints/color/deblur.model-523000.meta')
saver.restore(sess, tf.train.latest_checkpoint(r'./checkpoints/color/'))
self.saver = saver
coord = tf.train.Coordinator()
threads = tf.train.start_queue_runners(sess=sess, coord=coord)`

I also need to change the datalist  .txt, add my own data to it?

try to change the following code in "model.py": `self.saver = tf.train.Saver(max_to_keep=50, keep_checkpoint_every_n_hours=1) coord = tf.train.Coordinator() threads = tf.train.start_queue_runners(sess=sess, coord=coord)
summary_op = tf.summary.merge_all() summary_writer = tf.summary.FileWriter(self.train_dir, sess.graph, flush_secs=30)`
to: `# training summary summary_op = tf.summary.merge_all() summary_writer = tf.summary.FileWriter(self.train_dir, sess.graph, flush_secs=30)
saver = tf.train.import_meta_graph(r'./checkpoints/color/deblur.model-523000.meta') saver.restore(sess, tf.train.latest_checkpoint(r'./checkpoints/color/')) self.saver = saver
coord = tf.train.Coordinator() threads = tf.train.start_queue_runners(sess=sess, coord=coord)`

hi,thanks.your reply helps me
but is this only will be changed. i understand that you restore the model graph with value but how can i feed the training data to work with this restored graph and then save the new weights ? . please help


Add Python modules to generate stubs and automatically patch docstrings

@greglandrum This is the long-awaited docstrings PR.
This PR includes the Python modules to:

generate stubs
automatically patch docstrings to solve the issues I described in my 2023 RDKit UGM presentation; most notably:

incorrect labelling as staticmethod of a large number of member functions due to the lack of the self parameter
non-informative naming of parameters as arg1, arg2, ...

added gen_rdkit_stubs Python module to generate rdkit-stubs
added patch_rdkit_docstrings Python module to patch existing C++ sources to fix docstrings missing self parameter and add named parameters taken from C++ signatures where possible
added rdkit-stubs/CMakeLists.txt to build rdkit-stubs as part of the RDKit build
added an option to CMakeLists.txt to enable building rdkit-stubs as part of the RDKit build (defaults to OFF)
ran patch_rdkit_docstrings to automatically modify C++ sources, in order to fix docstrings missing self parameter and add named parameters taken from C++ signatures where possible

@ptosco I think this one is fine to merge after the missed examples I highlighted above are fixed

@greglandrum The scripts now correctly assign parameter names to constructor overloads (including those created by boost::python::make_constructor) and also fix the remaining member functions which were incorrectly assigned as staticmethod due to boost::python not adding the self parameter (and not accepting that we add it in the C++ source or the code won't compile).
I think this is now ready to go.

FYI: I don't think that PR made it into 2023_09_3.
I don't see RDK_BUILD_PYTHON_STUBS into https://github.com/rdkit/rdkit/blob/Release_2023_09_3/CMakeLists.txt while it's available on main.
I spotted it when working on https://github.com/conda-forge/rdkit-feedstock/pull/143 with this warning:
  Manually-specified variables were not used by the project:

    RDK_BUILD_PYTHON_STUBS

@hadim yeah, that was a mistake I made when doing the 2023_09_3 release. This will be in the 2023_09_4 release.


org.jboss.cdi.tck.tests.interceptors.definition.InterceptorDefinitionTest#testInterceptorsImplementInterceptorInterface uses internal type

This test uses a helper class HierarchyDiscovery to find the set of interface types that an interceptor metadata class (implementation of jakarta.enterprise.inject.spi.Interceptor) implements and then verifies that a parameterized type Interceptor is among them. It expects that a ParameterizedTypeImpl is used to represent a parameterized type, which is an internal implementation detail of HierarchyDiscovery. If the the interceptor metadata class doesn't have a generic signature (which happens for our implementation, ArC, that generates the implementation at compile time), the parameterized type of Interceptor isn't the TCK's internal ParameterizedTypeImpl, but the JDK's ParameterizedTypeImpl. They both implement java.lang.reflect.ParameterizedType, which is something the test should use in my opinion.

The test doesn't even need to rely on the internal param. type impl for what it verifies so +1


Fixed caching of theme in development mode. (#7812)

closes #7812

replaced hard-coded maxAge value in static-theme middleware with dynamic value based on env

FYI: will review before the next LTS release.


Errors during build process

Full disclosure, I have never used Visual Studio. My skills lie with PowerShell with coding from VSCode. I am using the community edition of Visual Studio 17.7.3. .NET Framework version is 4.8.09032. Following the directions step-by-step, I am getting these errors during the build process. I could use some help resolving them so that I can get to importing certs into Intune:

I may have solved my own issue. I changed the target .NET version in the project properties to 4.8. It now builds without errors.


fix: avoid dev-server crash when ws proxy error

Description
Fix #12664
Additional context

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the PR Title Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

While this PR seems to make sense, a small reproduction of the error would really help be sure this block is needed and the error was not fixed by previous commit as pointed in the linked issue

install docker

brew install --cask docker

run grafana docker

docker run -d -p 3000:3000 --name grafana grafana/grafana-oss:9.2.6

change grafana docker for grafana prefix

docker cp grafana:/etc/grafana/grafana.ini ./
## change config
root_url = %(protocol)s://%(domain)s:%(http_port)s/grafana
serve_from_sub_path = true
## change config end
cp ./grafana.ini grafana:/etc/grafana/grafana.ini
docker restart grafana

create vite demo

npx create-vue vite-repo

set proxy to grafana

  server:{
    proxy:{
        '^/grafana': {
            changeOrigin: true,
            ws: true,
            target: 'http://localhost:3000/',
        }
    }
  }

run the demo and navigate to /grafana we can see the crash still on 4.3.5

or run the demo navigate to /grafana or /test

/ecosystem-ci run

Is the ecosystem CI running with an old main base maybe?
Tested locally, can reproduce and patching node_module with this code correctly fix the crash.


Denmark fixed line phone number marked as FIXED_LINE_OR_MOBILE

How to reproduce the result?
Phone number 4598581xxx, where xxx can be any valid number eg. 111
The Result from getNumberType() function returned FIXED_LINE_OR_MOBILE
This number is confirmed a FIXED LINE phone number. In addition, from wikipedia, it shows the numbering set should be marked as FIXED LINE.
libphonenumber version used is 7.2.3
Why not libphonenumber apply the numbering list from wikipedia if that is valid?
https://en.wikipedia.org/wiki/Telephone_numbers_in_Denmark

This is a duplicate of #953 - please see my response there,


Incorporate Mod-Velocity.dll mod which displays ship speed into olmod

Mod already exists and doesn't provide any competitive advantage in MP, incorporate into olmod and add menu option for it

I don't really want this to be another menu option we need to manage.  It's more for debugging in my eyes, could we just make it a console command?


How to associate file types with an electron app?

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Can't seem to figure out how to associate specific file types to be associated with an electron app (built using Electron Forge) via the package.json or forge.js file I've got.
Any examples or guidance on this?

Just add:
"config": {
        "forge": {
            "electronPackagerConfig": {
                "extendInfo": "pathToFile/Info.plist",
            },
        }
    }

And add proper Info.plist.
You can check how I did it in my project.


image size

Challenge Size your Images has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.

Please visit the Help Room if you need assistance with the challenge. Happy Coding!

@clement00 Thank you for reporting this issue, but your code is wrong, as @Manish-Giri has pointed out.
This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the "help" button on the challenge on Free Code Camp, which will take you to the help chatroom for that specific challenge. You can also view our full list of official chatrooms.
If you think I'm wrong in closing this issue, please reopen it and add further clarification. Thank you, and happy coding!


Not scale up if the image has small size than configuration

Like the title said, do we have option like that.

This is currently not supported. s3-uploader is using gm under the hood, aheckmann/gm#226 discusses this functionality.

I think your library can support that with some checking. I don't know coffee script, so I give some pseudo code in node as example.
var resizeWith = version.maxWidth;
var resizeHeight = version.maxHeight;
if (!version.force && self.meta && self.meta.imageSize) {
    if (version.maxWidth > self.meta.imageSize.width) {
        resizeWith = self.meta.imageSize.width;
    }
    if (version.maxHeight > self.meta.imageSize.height) {
        resizeHeight = self.meta.imageSize.height;
    }
}

var img = mpc.resize(resizeWith, resizeHeight, '^')
    .gravity('Center')
    .crop(resizeWith, resizeHeight)
    .quality(version.quality || self.config.opts.resizeQuality);

The version.force = true will indicate that user want to scale up if the image size was smaller than the configuration size. The '^' will make the image is resized while maintaining the aspect ratio of the image, but the resulting width or height are treated as minimum values rather than maximum values.

Not sure what you mean that GraphicsMagick doesn't support this. You'd only append a > at the end of the -resize argument, for example 400x400>.
Do you want a PR for this? It's a breaking change, but IMHO with the current API I would not expect it scaling up when passing maxWidth/Height arguments hence it's a bug that needs fixing rather than breaking current behavior.

The short answer is yes, I would want a PR for this.
The long answer is that this is outside of what I need from s3-uploader so I will not have the time to do this myself.
Since this issue first was opened we have refactored away from gm so most of the functionality would need to go in im-resize  package. Also aspectratio would need a corresponding change to calculate correct image size based on this new logic. It currently assumes that the image will be scaled up if it is smaller than the max width / height option.

@Starefossen: no worries, already did those changes locally for im-resize can do it for aspectratio too. Question is if you're willing to merge a breaking change. Replied here since there was no issue and very low activity in the im-resize repo.

By the way, wouldn't it be better to rely on inspect or similar than to get actual dimensions rather than precalculate them?

Yes, I am willing to merge this breaking change as long as the existing behavior can be enabled with an option.
It would be easier to use ImageMagics's identify command, but it will also be much much slower since it requires reading each image version from disk in order to return the size of it.

identify would be more accurate since rounding and resizing algorithms might differ between im-resize and Image/GraphicsMagick. Slower, sure, but in the context of manipulating images and sending them to S3 it's probably negligible unless you're at Facebook scale.
If you think aspectratio is the way to go I'll do it :-)

Yes, for the time being I think aspectratio is the right way to go. I welcome any PR for that :thy mbsup:


Can not find renderer for grammar HTML/CSS

First off, let me just say that I am new to web development and Atom.
When I open a preview tab I get a Previewing failed message and under it says  "Can not find renderer for grammar HTML." Then when I click on my CSS tab, it says the same thing except for CSS.  I want to get the preview package working for my projects that use HTML, CSS, and JavaScript (in different files but linked in the HTML file) but I have not gotten it working yet.

Same proble

Unfortunately, I no longer use Atom and am no longer maintaining this package.

Hey hello!
What are you using now?


Animesaga hindi not working

Source information
Animesaga.in
Source language
hindi
Steps to reproduce
Open any show and play any episode
Expected behavior
Play video
Actual behavior
no links found or error
Aniyomi version
v<IP_ADDRESS>
Android version
11
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

I am also facing the same issue


automation, Remove unneeded build repetitions

make bazel-build-images happens 4 times, even if all the times
succeeded, wasting resources.
Fix it by stopping when it first managed to finish successfully.
Signed-off-by: Or Shoval<EMAIL_ADDRESS>None

/cc @EdDev @qinqon

Addressed comments.

Addressed comments.

Asking myself, what will happen if we will remove it totally,
as cluster-up / cluster-sync is enough usually.
I will try that on other PR

Thanks Edy
(failing tests are unreleated)
/cc @enp0s3

/approve


engine compatibility error installing latest release

Installing a project with this package as a dependency and started getting this error.
 warning webpack-s3-plugin > cdnizer ><EMAIL_ADDRESS>Package no longer supported. Contact<EMAIL_ADDRESS>for more info.
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "^5.6.0".
error Found incompatible module
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
:buildNodeDest FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':buildNodeDest'.
> Process 'command '/var/lib/****/workspace/***/.gradle/yarn/yarn-v1.3.2/bin/yarn'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Pinning back to 1.0.12 fixed it, but based on recent commits, I'm not sure what would have triggered this?  🤔
$ node -v && npm -v && yarn -v
v8.11.2
5.6.0
1.7.0

@thescientist13 v1.0.14 has been published to fix this issue ^

Thanks @phuonghuynh !


Fix for figures in the Granger causality tutorial

Currently, the plots generated in the Granger causality tutorial have incorrect axis ranges. This was fixed by setting x- and y-axis bounds in both plots.

Coverage remained the same at 88.414% when pulling 0a80750ed1f4b7d4f1eb86e0290ec83586c25a5d on INM-6:fix/gc_tutorial_plot_correction into f5c3e1524731ddf07a3ca873a5d1fcbb529f2a47 on NeuralEnsemble:master.

Old version:

New version:


Dragging an event in the RTL month view calendar gets confused to the wrong side

Check that this is really a bug

[X] I confirm

Reproduction link
https://drive.google.com/file/d/1kKL80YCJLrz6q0Y1GJeWzlwNgkccJ-OA/view?usp=share_link
Bug description
Calendar Drag and Drop month view always drags event from most left column.
It is important to note that in the "week" & "day" view it works properly.
Expected Behavior
While dragging, I expect the event to hover over the date which I am selecting.
Actual Behavior
No response
react-big-calendar version
1.5.2
React version
18.2.0
Platform/Target and Browser Versions
chrome 107.0.5304.107 microsoft edge
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a react-big-calendar issue and not an implementation issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

Can you provide a reproduction link, your code or a video?

Can you provide a reproduction link, your code or a video?

Yes, hope that will be helpful:
https://www.veed.io/view/79e6c327-f18f-402c-bb22-874473027393?sharingWidget=true&panel=share

Can you provide a reproduction link, your code or a video?

I would greatly appreciate your help, I tried every option but unfortunately without any success.

That's probably a bug in the dragAndDrop add-on. It's probably just that no-one ever used it that way.
Maybe you can try to debug it. It should be somewhere near here: https://github.com/jquense/react-big-calendar/blob/master/src/addons/dragAndDrop/WeekWrapper.js#L62

That's probably a bug in the dragAndDrop add-on. It's probably just that no-one ever used it that way. Maybe you can try to debug it. It should be somewhere near here: https://github.com/jquense/react-big-calendar/blob/master/src/addons/dragAndDrop/WeekWrapper.js#L62

Thanks for you response!
how do i get access to that all events?

Don't understand your question. If you want to try to fix the bug, you could clone the repo locally, modify an existing Storybook story and then try to debug.

Don't understand your question. If you want to try to fix the bug, you could clone the repo locally, modify an existing Storybook story and then try to debug.

I was clone the repo, but still without any result to solve this.
Maybe is it possible to use an external library, to perform a drag? for example to use react-beautiful-dnd

That's probably a bug in the dragAndDrop add-on. It's probably just that no-one ever used it that way. Maybe you can try to debug it. It should be somewhere near here: https://github.com/jquense/react-big-calendar/blob/master/src/addons/dragAndDrop/WeekWrapper.js#L62

Thanks for you response! how do i get access to that all events?

That's probably a bug in the dragAndDrop add-on. It's probably just that no-one ever used it that way. Maybe you can try to debug it. It should be somewhere near here: https://github.com/jquense/react-big-calendar/blob/master/src/addons/dragAndDrop/WeekWrapper.js#L62

That's probably a bug in the dragAndDrop add-on. It's probably just that no-one ever used it that way. Maybe you can try to debug it. It should be somewhere near here: https://github.com/jquense/react-big-calendar/blob/master/src/addons/dragAndDrop/WeekWrapper.js#L62

Can you explain me exactly how to debug in this area with storybook ?
I was trying to debug there for hours, but I feel like I got a little lost there.

You can start a local storybook with
npm install
npm run storybook

or
yarn
yarn storybook

You can try to take an example with DnD, modify it directly or duplicate it, add the rtl props and then change the files (add console.log for example). Storybook should rebuild on saved files.

You can start a local storybook with
npm install
npm run storybook

or
yarn
yarn storybook

You can try to take an example with DnD, modify it directly or duplicate it, add the rtl props and then change the files (add console.log for example). Storybook should rebuild on saved files.

How can I change the files?

With a text editor?

With a text editor?

I mean
I tried to edit the source code through the node moduels but there was no effect.

That's not really a good way to do it. Try cloning this repository and making the changes in it until you find the problem.


hotkey: Give feedback when no unreads left in followed topics.

When navigating to the next unread followed topic using the Shift+N hotkey, we notify the user using feedback_widget when there are no more unread messages in followed topics.
Fixes: #27604
Screenshots and screen captures:
no-more-unread.webm

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Merged after making a small tweak in the string suggested by @alya. Thanks @prakhar1144!

BTW please include a screenshot of new UI even when also doing a video; it's a lot more convenient for certain parts of the review process.


Why is the framework named 'Starscream'?

Question
Why is it based on the decepticon, Starscream, from the Transformers comics / movies?
Environment:

OS/Version: [e.g. iOS/13.3]
Starscream Version [e.g. 4.0.4]
Xcode version [e.g. 11.5]

Because life is too short for lame library. Thought it was fun theme for the iOS libraries we created.


⚠ Bofrost.de has degraded performance

In b3b4f93, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 856 ms

Resolved: Bofrost.de performance has improved in efeb655 after 6 minutes.


Implement getters for ProblemContext

This PR fixes https://github.com/TietoEVRY/quarkus-resteasy-problem/issues/301. Without public access to ProblemContext data it's almost useless to implement custom ProblemPostProcessors. In addition, this PR did some reordering of modifiers as at a first glance it looked like the register and rest methods of PostProcessorsRegistry would also not be public.

@chberger thank you, I really appreciate your contribution. Before I merge this, let me think about how those processors are registered - I never planned to make it possible to implement custom processors, so ExceptionMapperBase.postProcessorsRegistry.register was kind of okey-ish as internal mechanism, but not very elegant for application developers to interact with.
I'll try to make it work with CDI, so that you can simply create a processor, annotate it with @ApplicationScoped and it would be picked up by the extension automagically.

@lwitkowski This sounds great! It's exactly what we're looking for (see https://github.com/TietoEVRY/quarkus-resteasy-problem/issues/301#issuecomment-1735805539). Please let me know if you need help, because we would need the possibility of custom post-processors urgently.

@chberger Please address one small comment, then I'll merge it.
I have a working prototype with CDI, nevertheless I will do it in a separate PR with code changes and documentation on how to use it and will ask you for a review. WDYT?

@lwitkowski Sure, I'd love to do a review - thank you!


App stops working after FCM registration

Hello, I am using this plugin on a project created with Apache Cordova CLI, not PhoneGap. The plugin is installed correctly, and the build is just fine. But a few seconds after I open the app (I guess it is after the plugin registration on FCM) on my Samsung Galaxy A7, the app stops responding. It just stucks on the screen, with no more reaction.
What could be the problem? Thank you for your help.
Cordova version : 9.0.0
Cordova Android version : 7.1.4
Phonegap Plugin Push version : 2.2.3
Installed plugins :
cordova-plugin-exit 1.0.3 "Exit"
cordova-plugin-file 6.0.2 "File"
cordova-plugin-whitelist 1.3.4 "Whitelist"
cordova-plugin-x-socialsharing 5.1.3 "SocialSharing"
cordova-support-google-services 1.1.0 "cordova-support-google-services"
es6-promise-plugin 4.2.2 "Promise"
phonegap-plugin-multidex 1.0.0 "Multidex"
phonegap-plugin-push 2.2.3 "PushPlugin"

Finally, I found a solution here:
I used the code given there, istead of the one given in the plugin's docs.


chore(release): v0.11.4 🎉

:robot: I have created a release beep boop
0.11.4 (2024-07-27)
Bug Fixes

audit: bump deps to fix audit (c98f4b0)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ehmpathy/declapract/releases/tag/v0.11.4 :sunflower:


Add missing source information for AdMob

Please provide information about the SDK
Platform: Android
Name (as on the CSV file): Google AdMob
Please add this official source URL for data types collected by AdMob: https://developers.google.com/admob/android/play-data-disclosure

Thanks @darek607 - This was a miss, updated. Closing this issue, feel free to add more issues and suggest improvements. Thanks.

@darek607 - We have launched a free Data Safety Generator tool based on our experience so far. Would you be kind enough to test it?
Link to tool: https://github.com/Privado-Inc/privado


[HTTP] Implement streaming decompression.

In this PR:

Adds a StreamPeerGZIP (currently exposed, but might need discussion on the API, so we could decide to skip registration for now).
HTTPRequest now decompress the body on the fly, this involves extra copying in some cases, and might result in higher memory footprint for small files, but will result in dramatically lower memory usage for bigger files since it does not require allocating the whole file in memory twice.
Some refactor to HTTPRequest to only use on SNAME.

Supersedes #55946 .
Draft status:

~Documentation if we decide to expose it.~
Documentation added, but let me know if we should unexpose it.

Stream test:
func _ready():
	var text = "TestTestTestTestTestTestTestTestTestTestTestTest"
	var bytes = text.to_utf8_buffer()
	var deflate = false
	var compression = File.COMPRESSION_DEFLATE if deflate else File.COMPRESSION_GZIP
	var compressor = StreamPeerGZIP.new()
	compressor.start_compression(deflate)
	# Add some
	print(compressor.put_data(bytes))
	# Add some more
	print(compressor.put_data(bytes))
	# Write end of stream
	print(compressor.finish())
	# Read all
	var buf = compressor.get_data(compressor.get_available_bytes())[1]
	# Compare
	var cmp = PackedByteArray(); cmp.append_array(bytes); cmp.append_array(bytes)
	assert(Array(buf) == Array(cmp.compress(compression)))

	# Write to file (check the content with an advanced editor like vim)
	var f = File.new()
	f.open("test.gz", File.WRITE)
	f.store_buffer(buf)
	f.close()

	# Decompress
	compressor.clear()
	compressor.start_decompression(deflate)
	print(buf.size())
	compressor.put_data(buf)
	var out = compressor.get_data(compressor.get_available_bytes())[1]
	print(out.get_string_from_utf8())

HTTP Test:
extends HTTPRequest

func _ready():
	download_file = "./index.html"
	request("https://www.wikipedia.org/")
	request_completed.connect(self._completed)

func _completed(status, code, headers, body):
	var f = File.new()
	f.open(download_file, File.READ)
	printt(get_downloaded_bytes(), f.get_length(), body.size())

Fixes #65635 .
Possible solution for #28999 (can open gzip and stream-decompress, though it does not really fix the open_compressed issue itself).

Sorry it's really picky :P
diff --git a/doc/classes/StreamPeerGZIP.xml b/doc/classes/StreamPeerGZIP.xml
index 663992d..71dd361 100644
--- a/doc/classes/StreamPeerGZIP.xml
+++ b/doc/classes/StreamPeerGZIP.xml
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8" ?>
-<class name="StreamPeerGZIP" inherits="StreamPeer" version="4.0" is_experimental="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../class.xsd">
+<class name="StreamPeerGZIP" inherits="StreamPeer" is_experimental="true" version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../class.xsd">
 	<brief_description>
 		Stream peer handling GZIP and deflate compression/decompresison.
 	</brief_description>

(Another argument for refactoring this so it's defined via a macro and not manually in the XML.)

Thanks!


pprof_rs: expose frame-pointer feature

Pyroscope is currently unusable with pprof-rs with the default stack unwinder: https://github.com/tikv/pprof-rs/issues/219
Frame-pointer seems to work, so let's expose it to end users

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

Could we get a release with the latest master code? there are some useful fixes

pushed pyroscope and pprofrs to crates


add get_std() to simulators

Added native implementation calculating the standard deviation to all simulators. Tried my best to support as large a scale as possible and avoid unnecessary duplicate computations.
Bonus: get_qaoa_objective() now can accept a sequence of strings as its objective (see https://github.com/jpmorganchase/jpmc-argonne-quantum-optimization/issues/169), so no more "expectation and overlap".
Also, #42 is addressed but has not been tested yet.

I did some simple tests; would appreciate unit tests to be added, as well as testing the mpi implementation.


timestamp timezone fix

Fix timestamp parsing.
Timestamp parsing previously suffered from two issues:

The timezone was replaced with UTC. This meant that any datetimes from other time zones were converted to incorrect times.
If fixed with using astimezone, then any timezone-naive timestamps assumed the local system timezone. This meant they were not only wrong, but wrong in different ways depending upon the time zone!

This now differentiates between three use cases:

The timezone is in the parsed datetime, and we expect that.
The timezone is not in the parsed datetime, and we explicitly say that it is UTC.
The format is user-supplied, and we can't be sure if it's aware or not. We will have to assume any timezone-aware datetimes are correct, and if they're naive, they are meant to be UTC.

There are also some small utilities / helpers for some miscellaneous use cases across the code base.
resolves #662

This wound up being a bigger change than I had hoped for. But incorrect timezone logic and brittle assumptions were prolific across the entire codebase. I think this is important to fix before MVR.

thanks @KevinMGranger taking it for a spin now

/retest

https://github.com/weshayutin/pelorus/commits/master
https://github.com/weshayutin/pelorus/issues
so far looks good..  let's review in the morning

locally I'm seeing unit tests fail..
XFAIL exporters/tests/test_deploytime.py::test_generate_reps_with_same_name
  Bug with different rep kinds with same name and namespace
FAILED exporters/tests/integration/test_committime.py::test_github_provider[setup_collector] - urllib3.exceptions.Ma...
FAILED exporters/tests/integration/test_committime.py::test_github_provider[setup_collector_from_env_loading] - urll...
PASSED exporters/tests/test_config.py::test_loading_simple_string
PASSED exporters/tests/test_config.py::test_default
PASSED exporters/tests/test_config.py::test_fallback_lookups
PASSED exporters/tests/test_config.py::test_load_collections
PASSED exporters/tests/test_config.py::test_loading_from_other
PASSED exporters/tests/test_config.py::test_logging
PASSED exporters/tests/test_datetime.py::test_parse_hard_utc
PASSED exporters/tests/test_datetime.py::test_parse_tz_aware
PASSED exporters/tests/test_datetime.py::test_parse_tz_aware_diff_timezones
PASSED exporters/tests/test_datetime.py::test_dynamic_parsing_aware
PASSED exporters/tests/test_datetime.py::test_dynamic_parsing_assumed
PASSED exporters/tests/test_datetime.py::test_github
PASSED exporters/tests/test_deploytime.py::test_generate_normal_case
PASSED exporters/tests/test_deploytime.py::test_image_sha
PASSED exporters/tests/test_exporters.py::test_commitmetric_initial[pytest]
PASSED exporters/tests/test_exporters.py::test_commitmetric_repos[https://dogs.git.foo/dogs/repo.git-https-dogs.git.foo-repo]
PASSED exporters/tests/test_exporters.py::test_commitmetric_repos[http://dogs.git.foo/dogs/repo.git-http-dogs.git.foo-repo]
PASSED exporters/tests/test_exporters.py::test_commitmetric_repos[http://noabank.git.foo/chase/git.git-http-noabank.git.foo-git]
PASSED exporters/tests/test_exporters.py::test_commitmetric_repos[ssh://git.moos.foo/maverick/tootsie.git-ssh-git.moos.foo-tootsie]
PASSED exporters/tests/test_exporters.py::test_commitmetric_repos[git@github.com:konveyor/pelorus.git-ssh-github.com-pelorus]
PASSED exporters/tests/test_exporters.py::test_commitmetric_repos[https://gitlab.com/firstgroup/secondgroup/myrepo.git-https-gitlab.com-myrepo]
PASSED exporters/tests/test_exporters.py::test_malformed_git_url[kmoos://myprotocol/buffy/noext/noext]
PASSED exporters/tests/test_exporters.py::test_malformed_git_url[notvalid://breakme/snoopy/gtist.git]
PASSED<EMAIL_ADDRESS>PASSED<EMAIL_ADDRESS>PASSED exporters/tests/test_failure_exporter.py::test_github_prometheus_register
PASSED exporters/tests/test_failure_exporter.py::test_github_search_issues
PASSED exporters/tests/test_failure_exporter.py::test_negative_github_search_issues
PASSED exporters/tests/test_failure_exporter.py::test_negative_label_github_search_issues
PASSED exporters/tests/test_failure_exporter.py::test_github_closed_issue_search_issues
PASSED<EMAIL_ADDRESS>PASSED<EMAIL_ADDRESS>PASSED<EMAIL_ADDRESS>PASSED<EMAIL_ADDRESS>PASSED<EMAIL_ADDRESS>PASSED exporters/tests/test_pelorus.py::test_get_app_label
PASSED exporters/tests/test_pelorus.py::test_get_prod_label
PASSED exporters/tests/test_pelorus.py::test_missing_configs
PASSED exporters/tests/test_pelorus.py::test_ugprade_legacy_vars[github_{user,token,api} work on their own-None-None-None-goodU-goodT-goodA-None-None]
PASSED exporters/tests/test_pelorus.py::test_ugprade_legacy_vars[git_{user,token,api} work on their own-goodU-goodT-goodA-None-None-None-None-None]
PASSED exporters/tests/test_pelorus.py::test_ugprade_legacy_vars[git_* takes precedence over github_*-goodU-goodT-goodA-badU-badT-badA-None-None]
PASSED exporters/tests/test_pelorus.py::test_ugprade_legacy_vars[api_user, token work on their own-None-None-goodA-None-None-None-goodU-goodT]
PASSED exporters/tests/test_pelorus.py::test_ugprade_legacy_vars[api_user, token have precedence over git_*-badU-badT-goodA-None-None-None-goodU-goodT]
PASSED exporters/tests/test_pelorus.py::test_ugprade_legacy_vars[api_user, token have precedence over github_*-None-None-goodA-badU-badT-None-goodU-goodT]
PASSED exporters/tests/test_utils.py::test_nested_lookup_default
PASSED exporters/tests/test_utils.py::test_nested_lookup_exception
PASSED exporters/tests/test_utils.py::test_nested_lookup_collect
PASSED exporters/tests/test_utils.py::test_env_var_default
PASSED exporters/tests/certs/test_custom_certs.py::test_custom_requests_certs
================================ 2 failed, 49 passed, 4 deselected, 1 xfailed in 1.44s ==

Overall looks great. I went and did verification an all but servicenow collections, with few small nits found. The full list of findings is attached.
verify_timestamp_work.txt

/retest

/retest

/lgtm


How can I change the font  ?

in General I solved it like this for my specific scenario,
<ng-select class="myFont"
[options]="foodUnits"
[noFilter]="10"
[ngStyle]="{'width': '190px'}">

.myFont>ng-select > div > div.single > div.value, ng-select > div > div.single > div.placeholder{
font-family: 'my font family here';
}
why did you specify font family btw? maybe better to inherit...

You could set it with CSS:
ng-select div, ng-select li {
  font-family: monospace;
}

Thanks for answering @Crevil. I hope that helps you out @rannaot. I will close the issue.


Minimum Images for Evaluation, question about dimensions

I have trained a GAN for generating sculptures and I have only 20 Images in my Testdataset. Can I use FID Metric for evaluation? So as I read the dimensionality decrease then automatically to 64. What does it mean when the dimension is smaller? Does it mean that there are used low level features (e.g edges and lines)and not high level feature classes?
What does dim 64, 192, 768, 2048 exactly mean?

@GiangHLe. I met a similar problem with @guitar9. I will explain what makes me confused.
If we have 200 number of images(or 2000) to train, and we need to compare the real images and generated images with FID metric. Then I have following problems:

Can we calculate the FID with dim 2048? As for this dim, they certainly conclude all features in the training dataset.
Are there some relationships between the number of training data set and feature dimension when we calculate the FID? Currently, I think the reason would be overfitting if we use the small data set. But I don't know whether it's right.

@GiangHLe is correct. I will explain the relationship between features dimension and number of images.
If you use features of dimensionality N, it is necessary that you use at least N images, otherwise the FID computation might not work. For more stable and accurate results, the authors recommend more images, like 50000. As an option, this package offers to use lower feature dimensionalities, which might be of use if less images are available. However, it is unclear if the resulting FID values are still a good metric for image quality. Definitely, they are not comparable to the standard FID on 2048-dim features.


Architecture Design

As title

I am working on it next week, planned to finish one version before next Friday. After that, maybe we can have a little meeting for it.


The Anti-Pitch

First I thought some guy called Anit had a particular opinion on Vivaldi, but then I realized this is a great opportunity for a very easy fix. Cheers :)

Thanks! Sorry this slipped my radar for a bit!


feat: chrome

:tada: This PR is included in version 0.110.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat(core): Identifier in NanoTDF ResourceLocator borrowed from Protocol

Add support for identifiers in ResourceLocator
Introduced an IdentifierType enum to categorize different identifier lengths. Updated ResourceLocator constructors to handle identifiers, including parsing and setting appropriate identifier types. Modified ByteBuffer constructor to extract identifier information from the protocol byte.
Issue: https://github.com/opentdf/platform/issues/1203
Specification: https://github.com/opentdf/spec/pull/40
ADR: https://github.com/opentdf/platform/issues/900

merged as https://github.com/opentdf/java-sdk/pull/112


Failure Does Not Fail The Build

Hey,
The misconfigured workflow will mark the build passed despite the step being failed. (example):

Maybe we can catch that and core.setFailed() && process.exit(1)? 🤔

Well this is not exactly a failure. The API just throws an error when we want to create a PR with no changes. The logging is there to debug another issue (#20) and I should probably reword the message or remove it.

Alright! Thanks!


WIP: full no_std support

Closes #62
Unresolved issues:

What to do about yasna? AFAIK it does not offer a std feature that can be disabled
What to do about the dev dependancy issues explored in #62

Thanks for the PR! You probably need to update .travis.yml to install the target as well.

Yeah, adding the target helps :). I've cherry picked these changes to the parent commit of the yasna merge, which almost compiles but I'm greeted with this:
error[E0512]: cannot transmute between types of different sizes, or dependently-sized types
   --> mbedtls/src/cipher/raw/serde.rs:301:5
    |
301 |     ::core::mem::transmute(ctx)
    |     ^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: source type: `mbedtls_sys::cipher_context_t` (544 bits)
    = note: target type: `[u8; 96]` (768 bits)

error[E0512]: cannot transmute between types of different sizes, or dependently-sized types
   --> mbedtls/src/cipher/raw/serde.rs:305:5
    |
305 |     ::core::mem::transmute(ctx)
    |     ^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: source type: `mbedtls_sys::aes_context` (2240 bits)
    = note: target type: `[u8; 288]` (2304 bits)

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0512`.
error: Could not compile `mbedtls`.

I can comment this out to make sure it does actually compile but that's not a good idea in the long run.
As far as I can see, the mbed source is tracked inside mbed-sys-auto so I'm guessing this isn't due to changes in the C api, and more likely and issue with compiling with an arm compiler. Any thoughts?
You can try it out in this branch.

Likely a combination of structure padding and also different pointer sizes. @jethrogb these sizes are checked because the cipher_context serialization code uses them, right? Can we switch serialization to using a generic format that doesn't rely on the layout of cipher_context_t? IIRC this was discussed on the RTE slack a while back.

Yeah RH did ask about that

@MabezDev we just merged a couple of PRs that should make getting this to work easier

Thanks, that helps alot! From master I now only need to change byteorder set use default-features = false for it compile.
Unfortunately using it in a project I run into https://github.com/rust-lang/cargo/issues/5730 . There seem to be a few work around, none of them particularly nice.

One being https://github.com/auxoncorp/cargo-5730.
The second solution I've seen it by forcing the user to have bindgen installed in their $PATH, hence removing the build dependencies all together and invoking bindgen manually.
Another 'solution' I've seen is forking all std enabled crates, disabling std and using cargo patch - but I don't think that would work here as std is required and quite frankly that is an insane solution.

With no clear fix to this cargo issue, would you be willing to accept one of these work arounds?

I kind of like the solution of https://github.com/auxoncorp/cargo-5730, but I think it's too complicated. I came up with the following:
Make all build dependencies optional, add a feature to enable then, and allow running the build script via cargo run:
# Cargo.toml
[package]
build = "build.rs"

[[bin]]
name = "build-script-build"
path = "build.rs"

[features]
build = ["dep"]

[build-dependencies]
dep = { ..., optional = true }

In the build script, if the feature isn't enabled, re-execute the build script:
// build.rs
#[cfg(not(feature = "build"))]
fn main() {
    let cargo = std::env::var_os("CARGO").unwrap()
    let args = [
        /* cargo, */ "run",
        "--bin", "build-script-build",
        "--features", "build",
        "--target-dir", /* $OUT_DIR/bindgen */
    ];
    let mut target_dir = std::path::PathBuf::from(std::env::var_os("OUT_DIR").unwrap());
    target_dir.push("bindgen");
    assert!(std::process::Command::new(&cargo).args(args).arg(&target_dir).status().unwrap().success())
}

#[cfg(feature = "build")]
fn main() {
    // normal build script
    // TODO: do nothing if this is invoked as a build script
}

Note, during a normal build, the build script gets executed 3 times: once as the original build script, then again as the build script with the feature enabled, then as the bin target for cargo run. Some logic should be added so the second execution does nothing.

That technique seems to work quite well, though I had to specify the optional build dependencies inside the normal dependacies too, but I think there is a way to avoid this.
Very close to being able to build code for arm, now failing at the linking stage with:
 = note: /usr/lib/gcc/arm-none-eabi/9.2.0/../../../../arm-none-eabi/bin/ld: error: no memory region specified for loadable section `.got'
          collect2: error: ld returned 1 exit status

error: aborting due to previous error

the got section indicates dynamic relocation (see: https://github.com/rust-embedded/cortex-m-rt/blob/master/link.x.in#L143), I'm guessing something isn't being built statically - just haven't figured out what yet.

Well that took longer than expected. Turned out cmake was injecting the -fPIC flag which allowed the compiler to create relocatable sections; cmake-rs currently doesn't support disabling PIC but a PR exists. I now have built mbedtls withing an thumbv7 project and have it running (yay!), though not actually doing anything with it yet.
I'll spend a bit of time cleaning up the changes I've made and submit them hopefully tomorrow. I'll probably close this and open a fresh PR when I do.

Closed in favour of #67


Can we setup a discord for live discussion?

It would make discussions less trackable. And not very inclusive for new contributors. Since it would be hard for them to catch up on topics. So I'm a little against it. But if we set one up, we should make sure the outcome and the rational is documented in guthub

I don't think discord implies moving all serious discussion to discord.  I think they'll still be plenty of traffic On github issues.
I just think sometimes it's nice to have a place to hang out and discuss some issues in real time.

There are a few of us in #base16 on Libera Chat, an IRC server. It's a bit of a dated technology, but it doesn't require us to set up and maintain a separate Discord server.
I'll add that information to the README.
If we outgrow that channel, I'd be happy to set up a Discord server.

One last thought then: I'd argue IRC isn't nearly as accessible to normal people as Discord - who are likely already using it for other chats anyways.  I think Discord is the new IRC - for non-geeks.
Food for thought.

Note that Libera Chat also has a Matrix Bridge. Matrix might be easier/more convenient for some users.


Add a way to price items through Backpack.tf Classifieds, instead of prices.tf

Is your feature request related to a problem? Please describe.
Sort of. Prices.tf sometimes messes up its prices and makes your bot pay WAY over buy orders for items, mostly unusuals (for instance, my bot ended up buying a Stormy Storm Brown Bomber for 28 Keys 58 Refined, when all other bot buy orders were at 20). Having a way to price your items through classifieds/match classified listings would partially fix this issue and would allow users to have reliable unusual bots without having to pay say 10 keys a month for a bot service. Granted, the issue would be risky and be subject to price manipulators, but is way safer than paying 8-10 keys over other buyers and getting screwed over on a hat.
Describe the feature you'd like
Have an option for your bot to price items based off of classified listings, like buy orders on unusuals, instead of relying entirely on prices.tf. Have it match the prices of the highest buyer/lowest seller. This would be a great option/alternative for people that use their bots to bank unusuals.
Describe alternatives you've considered
There are only 3 alternatives that I know of:

Manually price all unusuals: People have told me to do this but it's simply impossible to say manually price 300+ unusuals and expect it to keep up with other bots' listings, since they have overcut/undercut scripts.
Use prices.tf autopricing: As stated before, this can be extremely risky or just flat out screw you over. Most of the time the autopricer prices items way too high for what they are currently at, and it can buy way above other buyers and leave you with barely any profit or at a 1+ key loss.
Pay for a bot service: This is the only other option that I can think of for having a reliable unusual banking bot, but not everyone can afford the costs (for instance, gladiator.tf charges 10 keys a month for its bot with the overcut/undercut script).

Thanks for the suggestion.

There should be requirements to update the price (to avoid price manipulation):

there should be at least 3 listing with same price or price difference shouldn’t be more than 0.33 ref
these listings should have been staying there for 5-30 min

I agree with this, if there is someway to implement this into v4 that would be great. Can help with logic.


Tracking Issue - Actor improvements

Error handling
Error handling is currently based on the supervision tree in the runtime, where a failed actor will send a Report to its supervisor, which will choose how to handle it. This has created a few issues:

The supervisor is not guaranteed to handle the Report, as it may not be in its event loop for whatever reason (already exited, still stuck in init, etc). This means that critical errors could potentially not be handled or displayed in the logs.
Supervisors must always have intimate knowledge of their children actors' error types so that they can properly handle them.

I propose that actors should be able to define how they wish their own errors be handled. This can also unify supervised and unsupervised actors as their bounds would be defined by the Actor trait implementer. We may even be able to unify tasks this way.
Config control
Currently, supervisors can add an additional stream to a child actor, or specify that the Addr should not be registered, via the SpawnConfig. This puts the onus on the supervisor, rather than the actor that will use it, and relegates error handling to the supervisor when it should be done by the child. It would be better if the init fn could allow setting the SpawnConfig properties instead.

After further deliberation (between my various split personalities) I believe that some of this is easily fixable while some is more-or-less impossible.

Actors have access to their own thrown errors in the shutdown fn. This is guaranteed for thrown associated error types, but not panics or aborts (though in those cases there's not much to do anyway 🤷). Thus, if an error absolutely must be printed to the logs, it should be done there.
Actors unfortunately cannot have knowledge of their supervisor without introducing serious circular typing problems. Also, there is no simple way to bound a type so that it can be BOTH supervised or unsupervised in a generic way. Thus, the supervisor decides which it wants when it spawns the child and that knowledge stays in the scope of that created task. I cannot find a way around this while maintaining a relatively simple API.
The config issue is more-or-less solved by #284. I think it makes sense in some cases to allow supervisors to effectively have control over HOW events reach a particular actor without creating a pointless intermediary mapping actor and adding latency, but in most cases that logic can be handled by the child actor itself. As strange as it is to define an actor without explicitly defining anything to send it a message, actors are fundamentally not defined by the sources of their events, only by which events they process.


can you support code for swift 5

hello author. I think your repos is helpful. So I think you should update code for everyone.
Thank you very much.

I had to manually fix the code in the pod library files and push it to my repo git for this library. I don't need to do that now. thank you very much.

I had to manually fix the code in the pod library files and push it to my repo git for this library. I don't need to do that now. thank you very much.

@Pircate could you give me your twitter?

@Pircate could you give me your twitter?

I'm glad I can help you, but I'm sorry I don't have a twitter account number.

I'm glad I can help you, but I'm sorry I don't have a twitter account number.

@Pircate 我来自越南，我爱中国。
谢谢你的帮助。 我在日本工作。

@Pircate 我来自越南，我爱中国。
谢谢你的帮助。 我在日本工作。


Permission denied on wandb.init()

wandb --version && python --version && uname

Weights and Biases version: 0.9.1
Python version: 3.7.3
Operating System: Linux

Description
I am trying to use wandb on a computing cluster.
What I Did
I use this small script to see if I can login and log some arbitrary values.
Since I am unable to do wandb login, I am setting the api key.
os.environ["WANDB_API_KEY"] = '<my_key>'
os.environ['WANDB_MODE'] = 'dryrun'
os.environ['WANDB_ENTITY'] = '<my_wandb_name>'
os.environ['WANDB_PROJECT'] = 'cluster_test'
os.environ['WANDB_CONFIG_DIR'] = '/home/wallat/.config/wandb/'

wandb.init(dir='/home/wallat/wandb_mnist_test/')
wandb.log({'epoch': 2, 'loss': 0.5})

This is the output:
Traceback (most recent call last):
  File "/home/wallat/wandb_mnist_test/test_wandb.py", line 23, in <module>
    main()
  File "/home/wallat/wandb_mnist_test/test_wandb.py", line 16, in main
    wandb.init(dir='/home/wallat/wandb_mnist_test/')
  File "/home/wallat/.local/lib/python3.7/site-packages/wandb/__init__.py", line 1125, in init
    _init_headless(run)
  File "/home/wallat/.local/lib/python3.7/site-packages/wandb/__init__.py", line 286, in _init_headless
    headless_args)], env=environ, **popen_kwargs)
  File "/usr/lib/python3.7/subprocess.py", line 775, in __init__
    restore_signals, start_new_session)
  File "/usr/lib/python3.7/subprocess.py", line 1522, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
PermissionError: [Errno 13] Permission denied: ''

Can anyone tell me what might cause this problem? The error message is not quite enough to guess :)
Thanks

This looks like a file system permission error.  Are you sure /home/wallat/wandb_mnist_test/ exists and is writeble by the user you're running the script as?

There are likely more details in wandb/debug.log

Yes, it should not be an permission problem. Every run creates a new run-folder in /home/wallat/wandb_mnist_test/wandb/. The debug.log is empty though...
My guess was that the cluster's job manager is not letting me spawn more subprocesses, since it is crashing on that line. But I tried and spawning subprocesses seems not the be the problem either.

This is really strange.  If debug.log is empty that indicates we weren't able to write to that file.  What are the permissions on it?  ls -al wandb

I managed to figure out what was causing the problem. The job-manager of my cluster was starting the script from a private dir. This caused the os.getcwd() and sys.executable to direct to some dir like /var/lib/condor/execute/dir_25945 (the cluster is using ht condor).
When wandb.init() tried to open the subprocess like this:
subprocess.Popen([sys.executable, internal_cli_path, json.dumps(
        headless_args)], env=environ, **popen_kwargs)

it had no permission to access the executable in that folder.
A workaround was manually setting sys.executable = '/usr/bin/python3'. After doing so, it worked like a charm. Not sure if that might cause problems with my cluster configuration later on, though.
But the problem was entirely on my side, so I am closing this issue. Thanks for the help.

Good to know, we can provide a better error message in this case.


[BUG] Juicefsruntime-controller hanged and pod OOM

What is your environment(Kubernetes version, Fluid version, etc.)

k8s: v1.23.6
fluid: both 0.9.0 and 1.0.0 has this problem

Describe the bug

We have been using the fluid (v0.9.0) + juicefsruntime in the production as the data cache for a long time since last year. But today we find that we cannot successfully create the Dataset. We find the following phenomenon:

juicefsruntime-controller pods have a lot of restarts resulting from OOM;
The are no abnormal logs in juicefsruntime-controller pods;
juicefsruntime-controller logs will be hanged before it become OOM;

Hanging logs before OOM:

OOM as the memory limits:
During the hanging process, we can see the increase in memory use:

after a while， it triggers the OOM:

I have saved the last hanging dataset logs as follows:

2024-04-22T14:29:57.921+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/runtime_info.go:43      The current node selectors for worker   {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-61", "fuseName": "atms-mmt-10176-v1-2-61-fuse", "nodeSelector": {"fluid.io/f-ai-nlp-llm-test-atms-mmt-10176-v1-2-61":"true"}}
2024-04-22T14:29:57.921+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/runtime_info.go:43      The deprecated node selector doesn't exist      {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-61", "nodeselector": "data.fluid.io/storage-ai-nlp-llm-test-atms-mmt-10176-v1-2-61"}
2024-04-22T14:29:57.921+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/runtime_info.go:50      No deprecated PV found  {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-61", "pv name": "ai-nlp-llm-test-atms-mmt-10176-v1-2-61"}
2024-04-22T14:29:57.921+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/engine.go:76    Deprecation check finished      {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-61", "isLabelDeprecated": false, "isPVNameDeprecated": false}
2024-04-22T14:29:57.921+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/engine.go:76    Setup with dataset done {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-61", "exclusive": false}
2024-04-22T14:29:57.921+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/engine.go:82    Set the syncRetryDuration       {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-61", "engine": "juicefs", "id": "ai-nlp-llm-test-atms-mmt-10176-v1-2-61", "syncRetryDuration": 15}
2024-04-22T14:29:57.921+0800    INFO    juicefsctl.JuiceFSRuntime       controllers/runtime_controller.go:245   Setup the ddc engine    {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-61", "engine": "juicefs", "id": "ai-nlp-llm-test-atms-mmt-10176-v1-2-61", "runtime": {"apiVersion": "data.fluid.io/v1alpha1", "kind": "JuiceFSRuntime", "namespace": "ai-nlp-llm-test", "name": "atms-mmt-10176-v1-2-61"}}
2024-04-22T14:29:57.925+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/report.go:29    mountRoot       {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-61", "path": "/var/lib/docker/runtime-mnt/juicefs"}
2024-04-22T14:30:24.800+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/runtime_info.go:43      Fuses with deprecated label not found   {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62"}
2024-04-22T14:30:24.800+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/runtime_info.go:50      No deprecated PV found  {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62", "pv name": "ai-nlp-llm-test-atms-mmt-10176-v1-2-62"}
2024-04-22T14:30:24.800+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/engine.go:76    Deprecation check finished      {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62", "isLabelDeprecated": false, "isPVNameDeprecated": false}
2024-04-22T14:30:24.801+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/engine.go:76    Setup with dataset done {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62", "exclusive": false}
2024-04-22T14:30:24.801+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/engine.go:82    Set the syncRetryDuration       {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62", "engine": "juicefs", "id": "ai-nlp-llm-test-atms-mmt-10176-v1-2-62", "syncRetryDuration": 15}
2024-04-22T14:30:49.508+0800    INFO    juicefsctl.JuiceFSRuntime.AddFinalizerAndRequeue        controllers/runtime_controller.go:152   add finalizer and requeue       {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62", "Runtime": {"namespace": "ai-nlp-llm-test", "name": "atms-mmt-10176-v1-2-62"}}
2024-04-22T14:30:49.517+0800    INFO    juicefsctl.JuiceFSRuntime       controllers/runtime_controller.go:152   RequeueImmediatelyUnlessGenerationChanged       {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62", "prevGeneration": 1, "currentGeneration": 1}
2024-04-22T14:32:07.069+0800    INFO    juicefsctl.JuiceFSRuntime       controllers/runtime_controller.go:245   Setup the ddc engine    {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62", "engine": "juicefs", "id": "ai-nlp-llm-test-atms-mmt-10176-v1-2-62", "runtime": {"apiVersion": "data.fluid.io/v1alpha1", "kind": "JuiceFSRuntime", "namespace": "ai-nlp-llm-test", "name": "atms-mmt-10176-v1-2-62"}}
2024-04-22T14:32:08.170+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/transform_fuse.go:230   mountRoot       {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62", "path": "/var/lib/docker/runtime-mnt/juicefs"}
2024-04-22T14:32:08.170+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/transform_fuse.go:231   mountRoot       {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62", "path": "/var/lib/docker/runtime-mnt/juicefs"}
2024-04-22T14:32:08.170+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/transform_fuse.go:232   mountRoot       {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62", "path": "/var/lib/docker/runtime-mnt/juicefs"}
2024-04-22T14:32:08.170+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/master_internal.go:45   Generate values {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62", "value": {"fullnameOverride":"atms-mmt-10176-v1-2-62","edition":"enterprise","source":"ai-juicefs-datacenter","image":"hub-mirror.wps.cn/hpc-open/base_image/juicedata/juicefs-fuse","imageTag":"v1.0.4-4.9.2","imagePullPolicy":"IfNotPresent","imagePullSecrets":null,"user":0,"group":0,"fsGroup":0,"configs":{"name":"ai-juicefs-datacenter","accesskeySecret":"atms-juicefs-secret","accesskeySecretKey":"access-key","secretkeySecret":"atms-juicefs-secret","secretkeySecretKey":"secret-key","tokenSecret":"atms-juicefs-secret","tokenSecretKey":"token","formatCmd":"/usr/bin/juicefs auth --token=${TOKEN} --accesskey=${ACCESS_KEY} --secretkey=${SECRET_KEY} ai-juicefs-datacenter"},"fuse":{"privileged":true,"enabled":true,"image":"hub-mirror.wps.cn/hpc-open/base_image/juicedata/juicefs-fuse","nodeSelector":{"fluid.io/f-ai-nlp-llm-test-atms-mmt-10176-v1-2-62":"true"},"envs":[{"name":"BASE_URL","value":"http://<IP_ADDRESS>:8000/static"},{"name":"CFG_URL","value":"http://<IP_ADDRESS>:8000/volume/%s/mount"}],"imageTag":"v1.0.4-4.9.2","imagePullPolicy":"IfNotPresent","resources":{},"criticalPod":true,"volumeMounts":[{"name":"cache-dir-1","mountPath":"/data/jfs/cache2/mem/a8d349c0845306defa56547d2bb83910"}],"volumes":[{"name":"cache-dir-1","hostPath":{"path":"/data/jfs/cache2/mem/a8d349c0845306defa56547d2bb83910","type":"DirectoryOrCreate"}}],"hostNetwork":true,"subPath":"/kas-datacenter/model/8b5c6bcc-c04c-428d-98b6-a495085436d5","mountPath":"/var/lib/docker/runtime-mnt/juicefs/ai-nlp-llm-test/atms-mmt-10176-v1-2-62/juicefs-fuse","hostMountPath":"/var/lib/docker/runtime-mnt/juicefs/ai-nlp-llm-test/atms-mmt-10176-v1-2-62","command":"/sbin/mount.juicefs ai-juicefs-datacenter /var/lib/docker/runtime-mnt/juicefs/ai-nlp-llm-test/atms-mmt-10176-v1-2-62/juicefs-fuse -o no-sharing,cache-size=51200,cache-group=ai-nlp-llm-test-atms-mmt-10176-v1-2-62,cache-dir=/data/jfs/cache2/mem/a8d349c0845306defa56547d2bb83910,ro,attrcacheto=7200,entrycacheto=7200,foreground,subdir=/kas-datacenter/model/8b5c6bcc-c04c-428d-98b6-a495085436d5,free-space-ratio=0.1","statCmd":"stat -c %i /var/lib/docker/runtime-mnt/juicefs/ai-nlp-llm-test/atms-mmt-10176-v1-2-62/juicefs-fuse"},"worker":{"privileged":true,"resources":{},"envs":[{"name":"BASE_URL","value":"http://<IP_ADDRESS>:8000/static"},{"name":"CFG_URL","value":"http://<IP_ADDRESS>:8000/volume/%s/mount"}],"volumeMounts":[{"name":"cache-dir-1","mountPath":"/data/jfs/cache2/mem/a8d349c0845306defa56547d2bb83910"}],"volumes":[{"name":"cache-dir-1","hostPath":{"path":"/data/jfs/cache2/mem/a8d349c0845306defa56547d2bb83910","type":"DirectoryOrCreate"}}],"hostNetwork":true,"mountPath":"/var/lib/docker/runtime-mnt/juicefs/ai-nlp-llm-test/atms-mmt-10176-v1-2-62/juicefs-fuse","statCmd":"stat -c %i /var/lib/docker/runtime-mnt/juicefs/ai-nlp-llm-test/atms-mmt-10176-v1-2-62/juicefs-fuse","command":"/sbin/mount.juicefs ai-juicefs-datacenter /var/lib/docker/runtime-mnt/juicefs/ai-nlp-llm-test/atms-mmt-10176-v1-2-62/juicefs-fuse -o free-space-ratio=0.1,cache-dir=/data/jfs/cache2/mem/a8d349c0845306defa56547d2bb83910,ro,foreground,cache-group=ai-nlp-llm-test-atms-mmt-10176-v1-2-62,subdir=/kas-datacenter/model/8b5c6bcc-c04c-428d-98b6-a495085436d5,cache-size=51200"},"cacheDirs":{"1":{"path":"/data/jfs/cache2/mem/a8d349c0845306defa56547d2bb83910","type":"hostPath"}},"placement":"Shared","owner":{"enabled":true,"apiVersion":"data.fluid.io/v1alpha1","kind":"JuiceFSRuntime","name":"atms-mmt-10176-v1-2-62","uid":"37960ef3-6d5c-4c06-bac1-b3ba39bf3d77","controller":true,"blockOwnerDeletion":false},"runtimeIdentity":{"namespace":"ai-nlp-llm-test","name":"atms-mmt-10176-v1-2-62"}}}
2024-04-22T14:32:08.172+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/master_internal.go:45   Save the values file    {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62", "valueFile": "/tmp/atms-mmt-10176-v1-2-62-juicefs-values.yaml621051713"}
2024-04-22T14:32:08.456+0800    INFO    helm    helm/utils.go:59        Exec    {"command": "/usr/local/bin/ddc-helm install -f /tmp/atms-mmt-10176-v1-2-62-juicefs-values.yaml621051713 --namespace ai-nlp-llm-test atms-mmt-10176-v1-2-62 /charts/juicefs"}
2024-04-22T14:32:09.222+0800    INFO    helm    helm/utils.go:62        NAME: atms-mmt-10176-v1-2-62
2024-04-22T14:32:09.249+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/worker.go:47    workers are not ready   {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62", "phase": "NotReady"}
2024-04-22T14:32:09.253+0800    INFO    utils   utils/errors.go:28      Retry later when update operation violates with apiserver concurrency control.  {"error": "Operation cannot be fulfilled on juicefsruntimes.data.fluid.io \"atms-mmt-10176-v1-2-62\": the object has been modified; please apply your changes to the latest version and try again", "name": "atms-mmt-10176-v1-2-62", "namespace": "ai-nlp-llm-test"}
2024-04-22T14:32:09.265+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/worker.go:47    workers are not ready   {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62", "phase": "NotReady"}
2024-04-22T14:34:06.658+0800    INFO    juicefsctl.JuiceFSRuntime       controllers/runtime_controller.go:245   Setup the ddc engine    {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62", "engine": "juicefs", "id": "ai-nlp-llm-test-atms-mmt-10176-v1-2-62", "runtime": {"apiVersion": "data.fluid.io/v1alpha1", "kind": "JuiceFSRuntime", "namespace": "ai-nlp-llm-test", "name": "atms-mmt-10176-v1-2-62"}}
2024-04-22T14:34:06.671+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/report.go:29    mountRoot       {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62", "path": "/var/lib/docker/runtime-mnt/juicefs"}
2024-04-22T14:34:06.891+0800    INFO    juicefsctl.JuiceFSRuntime       operations/base.go:259  execute in time {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62", "command": ["cat", "/var/lib/docker/runtime-mnt/juicefs/ai-nlp-llm-test/atms-mmt-10176-v1-2-62/juicefs-fuse/.stats"]}
2024-04-22T14:34:06.892+0800    INFO    juicefsctl.JuiceFSRuntime       juicefs/ufs_internal.go:61      mountRoot       {"juicefsruntime": "ai-nlp-llm-test/atms-mmt-10176-v1-2-62", "path": "/var/lib/docker/runtime-mnt/juicefs"}

How to reproduce it

This problem appears today, I do not know why.

Additional Information

When I switch to development mode, I can see where it gets stuck. As shown below, it gets stuck during the process of executing commands to the worker container.

Enter this pod: ai-datasci-prod/atms-mmt-10418-v1-5-2, we can see the following process:

Running this command will cause the command line to hang: curl localhost:6060/debug/pprof/goroutine?debug=1

In another newly created hanging pod atms-mmt-10176-v1-2-65-worker-0，will see the same processes list. And for the command ls, it will also directly freeze the terminal:

@so2bin I guess that there are too many files in the directory.  @zwwhdls @Suave could you please take a look at this issue? And you can drop an email to me. my email address is<EMAIL_ADDRESS>

@cheyang I resolved this problem by upgrading the fluid version to 1.0.0 and useing the newest juicefs image like the following command:
helm upgrade fluid --namespace=fluid-system --version=1.0.0  fluid/fluid \
  --set runtime.juicefs.fuse.ceimage=juicedata/juicefs-fuse:ce-v1.1.2 \
  --set runtime.juicefs.fuse.eeimage=juicedata/juicefs-fuse:ee-5.0.17-f0c0890 \
  --set runtime.juicefs.controller.image=fluidcloudnative/juicefsruntime-controller:v1.0.0-31f5433


Object reference not set to an instance of an object

Maybe this is part of the key bind issue? Finally threw and error.
LogReport_24-07-02_21-14.zip

Mid game I got this object ref error. Hopefully the log helps you.
LogReport_24-07-03_21-53.zip

Do you have the option for extra debug logging enabled?

Not sure but I will ensure it is on here when I load up in about 5 mins.
I'll have Skyve just save the logs and send a follow up.

LogReport_24-07-05_23-18.zip
Got this on start up but the game also grabbed another updated mod and I think that is why this happened.

LogReport_24-07-06_21-22.zip
This is from my last build session with the MIT debugging on for Move It.

I am getting this issue on the Beta Version. "System update error during ToolUpdate ->MIT: System.Exception: Entity E578401.35 does not have MIT_ControlPoint component.
Hope this helps!
LogReport_24-07-18_11-36.zip

Is this still happening? Can you please give as much detail as you can about what you're doing at this time, and what objects you are doing it with. Is there a specific building that seems to cause this?

I flipped to the "release" version but yes it is occasionally happening.
If it helps I am still on Discord. I just don't want to flood you with stuff. Feel free to reach out if you need more info from me.
I captured these logs today. You'll see Move It and a No Pollution error going on. No Pollution just got an update so I am unsure if they are related.
When I got this particular are and sudden CTD I was messing with a building to get it in the right place. Right before that I was pulling apart some decals and billboards I had placed. Prior to that I was ironing out a highway exit.
I have noticed that sometimes the road markings the game draws come apart from the roadway surface. Usually letting the game run will update them.
As always keep up the amazing work. I appreciate you and I know the community does too.
LogReport_24-08-06_09-05.zip


Feature/dryad/python 3.5

@felliott ,
As promised, the python 3.5 version of the Dryad addon. This passes Travis on my fork, so I'm hoping it works on the main repo. Based off the latest conversations, this should be the final iteration or close to it...

@felliott
That last commit just replaced the path verifcation with calls to WaterButlerPath. Hopefully it should be a bit more readable.

Minor:  can you add a /docs/provider.dryad.rst and add it to /docs/providers.rst?  That'll make it easier to see the Dryad docs on readthedocs.  If you want to preview your docs:
$ pip install -r doc-requirements.txt
$ cd docs
$ make html
$ open _build/html/index.html

@felliott . Done and done. How does it look to you? More detail in the docs?

Thanks, @kwierman! The detail is good.  Can you add some markup to the class docstring to set off the code and non-code bits?  The docstring for WaterButlerPath (rendered) uses inline and block code markup, as an example.

@felliott , Sure thing. I did notice something earlier when trying to cross reference functions in the doc strings. In the WaterButlerPath module, if you try and reference :func:WaterButlerPath.path (I left out the backticks because we're inside github flavoured markdown) from elsewhere inside the same module, it would create a link to the method documentation. However, inside the dryad.provider module, I need to use more verbose references. For instance, inside the class docstring, I need to use :func:waterbutler.providers.dryad.provider.DryadProvider.validate_path whereas I thought I should be able to use :func:DryadProvider.validate_path or even :func:.validate_path. I'm guessing this is because the build directory is not the same as the module directory.
Obviously, it's not a huge deal to verbosely reference other methods, but you'll see in the source code that I'm running over the 80 character line limit every time. If you know a better way to clean it up, I'd like to know. Otherwise, the documentation itself is looking pretty good...

Sorry, this was closed automatically when the feature/python-3.5 branch was deleted.  feature/python-3.5 has been merged into master and develop.  Can you reopen this against develop?

Woops! Sure thing. I need to take off in a few minutes, but I'll get to this when I get back tonight or tomorrow morning.


Add InfluxDbWriteable procedural derive macro

Fixes https://github.com/Empty2k12/influxdb-rust/issues/19

The InfluxDbWriteable macro should now be working. I don't know if a InfluxDbReadable macro makes sense and what the use case would be? Maybe someone could give an example how they'd like to use it

CI is failing with

README.md out of date. Run "cargo readme > README.md" and commit again.

@Empty2k12 I've fixed the readme. Kcov is still failing with an error message I cannot understand. Do you have an idea how to fix kcov?

I would guess this is due to you changing the folder structure, resulting in a different folder structure inside the target folder which the kcov command relies on.

As code coverage is inherently broken in Rust, even more so when using macros, I'd suggest removing code coverage in this PR and opening an issue to open it back up when better code coverage tools emerge or if a working solution has been found.
What do you think @msrd0 ?

#23

Keeping this up to date with master is getting annoying. What exactly is bloking this PR atm?
cc @Empty2k12

Tests and CI will need to be looked at again.
I would suggest the following to get this merged soon:

Make any existing tests pass
remove code coverage step in this PR: it's quite broken for rust and does not work with your monorepo approach for the two crates.
document usage of the macro, as well as integrating a mention to this new documentation into the README.md (via app.rs and cargo-readme)

It might make sense to merge this before #41 so #41 can support writing Chrono dates as the timestamp.

create a different PR which changes CI to Github Actions

It might make sense to merge this before #41 so #41 can support writing Chrono dates as the timestamp.

#41 implements From<DateTime<Utc>> for Timestamp, so that should integrate without any issues.

From my PoV, this PR is ready to be merged. Releasing will go just like you said ... release the derive crate first, wait a minute to give crates.io time to process the new/updated crate, and then release the main crate which has the derive crate as its dependency. However, note that there is no need to update the derive crate if no changes were made, just don't update the version either. It might be a good idea to keep major/minor versions in sync, at least that's what bigger libraries like diesel seem to be doing.

Before releasing I will probably fix #54 to improve behavior on embedded platforms.


RPM build jobs failing

The RPM jobs are failing due to a bad refactoring of the various documentation transformations I pushed in the last documentation and site update commit.
In an attempt to keep the documentation source DRY I wanted to include the manpage content in all the other products so there would only be one source file to update. Unfortunately, the manpage source has to be in exactly the format it expects (spacing and section naming conventions) or it will fail while the other formats (HTML, PDF and EPUB) are much more forgiving.
The proposed solution will be to run a sed preprocessing operation on source before running the man page transformation so it can get the exact format it expects which can be escaped from evaluation in the other formats.

Does #262 fix this?

Fixed with #262


Rebuild

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

I am a bit confused that https://github.com/conda-forge/xtb-python-feedstock/pull/11 failed, so I just wanted to see if the tests work if nothing is changed.

>       assert approx(atomic_result.properties.scf_dipole_moment, abs=thr) == dipole_moment
E       assert approx([0.33451151977076465 ± 1.0e-07, -1.0701017905608206 ± 1.0e-07, -1.229921234359929 ± 1.0e-07]) == array([ 0.3345064 , -1.07009252, -1.22991954])
E         +approx([0.33451151977076465 ± 1.0e-07, -1.0701017905608206 ± 1.0e-07, -1.229921234359929 ± 1.0e-07])
E         -array([ 0.3345064 , -1.07009252, -1.22991954])

../_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_place/lib/python3.9/site-packages/xtb/qcschema/test_qcschema.py:73: AssertionError
=========================== short test summary info ============================
FAILED qcschema/test_qcschema.py::test_gfn2xtb_energy - assert approx([0.3345...
======================== 1 failed, 29 passed in 10.16s =========================

@conda-forge-admin, please rerender


Delete Set

[ x ] Delete set from back end
[ x ] Delete set from front end
[ ] Delete exercise if set array is empty
[ ] Only able to delete very last set (pop)

[ ] While deleting exercises from workout if there are no exercises left the workout will be destroyed