Always drop reference annotations in managed resources

How to categorize this PR?

/area usability
/kind enhancement
What this PR does / why we need it:
In https://github.com/gardener/gardener/pull/5056 we have observed that existing reference annotations on objects remain and never get deleted in case

managed resources are migrated from one ManagedResource to another.
in the same change new reference annotations get computed.

With this PR, the ManagedResource reconciler in GRM is enhanced to always drop such 'reference' annotations from the old object (since there is anyways no reasonable scenario in which they should be kept if they are not part of the desired object).
Special notes for your reviewer:
/cc @shafeeqes
Release note:

NONE

Can confirm that the old annotations are getting deleted now when the vpnshoot resource gets migrated and also when the new reference are getting computed (triggered by enabling and disabling ReversedVPN in this case).

Thanks for trying it out, @shafeeqes!

Works fine with node-local-dns removes the old reference annotations in managed resources, therefore leads to cleanup of old unused configMaps.

/cc @timuthy :-)


Support Flarum 0.1.0-beta.14

https://discuss.flarum.org/d/25181-flarum-010-beta14-released

seconded, this is a must have extension for me!


#11 onboarding button

created onboarding button as mentioned in issue

@Shubham0812 you can review this PR as I have tried to create onboarding button and let me now what to change if required

There's a conflict @Yashraj49

There's a conflict @Yashraj49

can you tell what needs to be resolved

There's a conflict in the pbxProject files. You should be able to resolve it using GitHub Editor itself

@Shubham0812 I have resolved the conflict you may review it.


[SUGGESTION] Improve highlights appearence

Thank you for this so beautiful and simple theme!
I noticed that highlights are not so readable because there is not enough padding around the highlighted text. Moreover, the dark theme show highlights in an "ugly" dark green color (i think it should be yellow).
Anyway it may be very useful to have additional options to customize highlights.
Kind regards.
Bart.

Hi @bdalia I've added some padding around highlighted text. Are seeing a green highlight experience on your end? Mind sending a screenshot?
Here is how it is displaying now for me, pictured amongst other colors for reference:

Hi @colineckert and thank you for the reply. Now is more readable with a little padding.
On the yellow matter i mean the color seems not so yellowish, i photoshopped your image with an example of what i mean (html code is #99802 and i make text full white to increase readability).

Kind regards.

Hey, @bdalia I just published a new version (2.1.3) that adds the ability to set custom highlight colors (light and dark mode) via the Style Settings plugin. Hopefully, that resolves this issue for you by allowing you to easily set whatever colors you'd like. Let me know if this works and if so, just close this issue. Thanks!


Names of relations that something is part of are not displayed

URL
No response
How to reproduce the issue?
Navigate to https://www.openstreetmap.org/#map=20/52.51881/-2.07390
Edit in iD
Note that the top route name isn't displayed.
There appears to be no action that I can take to display it.
I need to know the full name because iD hides useful information about the relation (it's object iD) so when adding other things to it (such as to fill in the gap here) I need to use a "best guess" based on other attributes that iD does let me see, such as the name.
Unfortunately the name is truncated.
Screenshot(s) or anything else?

Which deployed environments do you see the issue in?
Released version at openstreetmap.org/edit
What version numbers does this issue effect?
2.27.3
Which browsers are you seeing this problem on?
Firefox

Note that the top route name isn't displayed.

Can you clarify? Are you referring to the line that reads, “National Cycle Network National…”? This sounds a lot like #8313. You can resize the sidebar to see more of the relation’s label, though there really should be a tooltip here so you don’t have to.
Each of the bus route labels seen here would be cleaner if its network were to match a name-suggestion-index entry. Then it would say just “West Midlands Bus 11A”. osmlab/name-suggestion-index#4768 tracks adding highway route networks to NSI; cycling route networks would probably be a part of that effort.

Re the comment here, just to confirm, there is no tooltip showing details of relations.  There is no visual indicator showing that the panes on the screen can be dragged left and right, and if I do drag the window far enough to the right to see the full name (a) there's not much of the rest of the screen left and (b) it's still a bit esoteric because iD refuses to show the relation iD.

Noted. I’m considering tagging this issue as a duplicate of #8313, since it covers the same usability issue. At a glance, I would expect implementing a tooltip to be quite straightforward, and it could even contain a relation ID for disambiguation purposes.
Meanwhile, getting this and other local bus companies into NSI would be another good next step, with benefits besides disambiguation. Someone with more local knowledge about how the various bus companies in this region are branded and structured would be in a good position to file an issue in that repository.

duplicate of https://github.com/openstreetmap/iD/issues/8313,

Yes, it sounds like the same basic issue.
A tooltop would be better than nothing (why not just optionally display the relation number on screen?)  If iD is supposed to be useful beyond "someone's first three weeks in OSM" it seems essential to introduce them to object iDs - using the browse pages on the main site requires that.

why not just optionally display the relation number on screen?

As I mentioned in https://github.com/openstreetmap/iD/issues/9349#issuecomment-1769114994, it would be great if the membership editor would show the relation IDs when two relations have otherwise identical labels, as the dropdown menu already does. The case above, where the relation is only labeled by its preset, would be another reasonable opportunity to show relation IDs.
Showing relation IDs more generally would be problematic for a couple reasons. One is what you just pointed out: that labels already easily get cut off when the sidebar is at a reasonable width, so it doesn’t necessarily solve any problems that a tooltip wouldn’t solve.
Another reason is that relation IDs these days tend to be rather long. It can result in information overload in conjunction with all the other information that can already go into the label. Unlike the relation ID is selectable in the History or Measurement panel or a openstreetmap-website relation page, the relation label isn’t selectable, so the only purpose is to cross-reference it with something in another tab, which makes glanceability pretty important. If we do end up displaying relation IDs in general here, I would even go so far as to suggest formatting the numbers with digit grouping characters for readability.
Anyways, #9349 is already tracking showing the relation IDs, so we should continue that discussion there.

Duplicate of #8313


PRs welcome for home page links

Please feel free to add any specific links that we are missing

This will be ongoing activity


Add more marshaler options for ProtoJson converter

What was changed

I added options to be passed to marshaler code for Proto/JSON.
Why?

Automatic OCaml deserialization of JSON-encoded Protobuf does not work if empty (nil) fields are not present.
Checklist

Closes

How was this tested:

I observed in my own code the expected result, i.e. JSON-encoded Protobuf now contains nil fields.

Any docs updates needed?

 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.

 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.

Thanks for the contribution!


[CCB-3174] Add test script for defect

ATF Test Scripts to check issue 3174 (https://github.com/smartdevicelink/sdl_core/issues)
This PR is [ready / not ready] for review.
Summary
Add test script for defect 3174
Changelog

Added test script for defect 3174

CLA

[X] I have signed the CLA

All comments are processed.


[Bug] Managed Identity App should not throw when User Assigned MI is specified for Azure Cloud shell, Arc and Service Fabric platforms.

Library version used
14.4.2-beta
Java version
JDK 17
Scenario
ManagedIdentityClient - managed identity
Is this a new or an existing app?
None
Issue description and reproduction steps
###Context
Currently, Msal throws exceptions in client/resouce id is specified when running against Azure Arc, cloud shell or Service Fabric.
We should not throw exceptions, rather log a warning message similar to Azure Identity SDK except Service Fabric as they now support User Assigned MI.
Reasoning
Throwing Exceptions in this case ties the SDK behavior to service impl details which can break in future when these services support User Assigned MI.
Relevant code snippets
No response
Expected behavior
No response
Identity provider
Microsoft Entra ID (Work and School accounts and Personal Microsoft accounts)
Regression
No response
Solution and workarounds
No response

Confirmed in other discussions that an exception should still be thrown for Azure Arc.

Behavior fixed in msal4j 1.15.0


Implement cupy.argpartition

Merge #288 first.
This PR implements cupy.argpartition.
It uses naive cupy.argsort in its implementation, which leads worse performance than ideal one with a proper algorithm but at least satisfies cupy.argpartition's specification.

Cloud you rebase or merge master?

jenkins test this please

Check a comment.

jenkins test this please

jenkins test this please

jenkins test this please

Please review again after CI will have passed.

LGTM


Maybe add datasette --get --actor option - or datasette client get --actor

I experimented with a prototype of this here:

https://github.com/simonw/datasette/issues/2102#issuecomment-1691037971_

Which lets me run requests as if they belonged to a specific actor like this:
datasette fixtures.db --get '/fixtures/facetable.json' --actor '{
    "_r": {
        "r": {
            "fixtures": {
                "facetable": [
                    "vt"
                ]
            }
        }
    },
    "a": "user"
}'

Really useful for testing actors an _r options. Is this worth adding as a feature?

Building that "_r" array is the main reason this would be useful, but it's also fiddly to get right.
datasette create-token has a design for that already: https://docs.datasette.io/en/1.0a4/authentication.html#datasette-create-token
datasette create-token root \
    --secret mysecret \
    --all view-instance \
    --all view-table \
    --database docs view-query \
    --resource docs documents insert-row \
    --resource docs documents update-row \

Adding imitations of those options to datasette serve would add a LOT of extra options, but it would also make it really convenient to attempt a request with a specific set of restrictions. Not sure if that would be worth the extra --help output or not.

Another option: implement this as a plugin, providing a new command like datasette get ...
Or implement datasette client get ... as core commands or a plugin - except that clashes with the datasette client command that https://github.com/simonw/dclient adds (which is a tool for hitting remote Datasette instances, not running simulated queries through a local one).

Annoying that datasette client ... makes a great name both for a plugin that executes simulated queries against a local database (thanks to its similarity to the existing datasette.client Python API) but is also the ideal name for a command for running commands as a client of an external Datasette instance!

datasette serve currently only has a --get - for this to be really useful it needs to grow --post and maybe other verbs too.
Which is a good argument for moving this functionality to datasette client get ... instead.

Documentation:

https://docs.datasette.io/en/latest/cli-reference.html#datasette-get


Titles and fixed space between categories

First of all...I love DIM! :+1: With this PR I would like to propose a slight different items layout.
With the same space between categories and the title I think that is a little bit clearer.
Only the Vault still doesn't convince me...

I'll hold off on this until we're ready for the options page that we'll use
to toggle features like this.  I wouldn't want to enable this by default.
Thanks for the effort, we'll take it in the future.
On Wed, May 13, 2015 at 1:22 AM Luca Simone<EMAIL_ADDRESS>wrote:

First of all...I love DIM! [image: :+1:] With this PR I would like to
propose a slight different items layout.
With the same space between categories and the title I think that is a
little bit clearer.
Only the Vault still doesn't convince me...
[image: ca2b2992-f8b5-11e4-83ca-5b60cde7daee]
https://cloud.githubusercontent.com/assets/28878/7604849/f949e05e-f948-11e4-97e3-51aafffc4eb6.png
You can view, comment on, or merge this pull request online at:
https://github.com/kyleshay/DIM/pull/110
Commit Summary

Fixed space between items

File Changes

M app/scripts/store/dimStoreItems.directive.js
https://github.com/kyleshay/DIM/pull/110/files#diff-0 (3)
M app/styles/main.css
https://github.com/kyleshay/DIM/pull/110/files#diff-1 (12)

Patch Links:

https://github.com/kyleshay/DIM/pull/110.patch
https://github.com/kyleshay/DIM/pull/110.diff

—
Reply to this email directly or view it on GitHub
https://github.com/kyleshay/DIM/pull/110.


Lexus IS 2023 [vehicle is not recognized and is in dashcam mode]

Describe the bug
Installed Comma 3 with Toyota harness into 2023 Lexus IS, vehicle is not recognized.
Which car does this affect?
Lexus IS 2023
Provide a route where the issue occurs
649bf2997ada6e3a|2023-08-04--22-20-47
openpilot version
0.9.5
Additional info
Attempted to fingerprint myself but I could only get as far as "openpilot unavailable; waiting for controls to start."

looking into it


500 Image size cannot be determined. Please provide the width and height of the image

🐛 The bug
I have a projet Nuxt 3 SSR. I tried to use og-image-nuxt but I have a problem when it's on production mode in my dev server.
The image URL give me error 500 Image size cannot be determined. Please provide the width and height of the image.
Environement
My dev server run with a node docker.
Node.js Version: 18.20.4
npm Version: 10.7.0

My packages versions
    "nuxt": "3.12.4",
     "nuxt-og-image": "3.0.0-rc.64",
     "@nuxt/devtools": "1.3.9",
     "typescript": "5.5.4"

Explanations
I have my page invitation-[id].vue. I load data with useLazyAsyncData and I use these for generate an image in defineOgImageComponent.
I already try to play with defineOgImageComponent  options but nothing change.

My ogImage component : event.vue
It's a simple component who just take two parameters and display a string and an image.
I already try with a simpler version (no background, no image, fixed sizes defined).
<template>

      <NuxtImg v-if="picture" class="size-40 rounded-full mb-6" alt="user profile picture" :src="picture" />

        {{ userName }} t'invite à sortir

      <NuxtImg src="https://henoo.fr/logo/logo_text.png" class="h-12" />

</template>

Config OG Image Nuxt
export default defineNuxtConfig({
 ogImage: {
    debug: true,
  },
})

In dev.env => NUXT_PUBLIC_SITE_URL=https://web-dev.henoo.fr
🛠 To reproduce
https://nuxtseo.com/og-image/getting-started/stackblitz
🌈 Expected behavior
When I run the project in localhost with NuxtDevTools I have a good result in OG Image part.

But when I run it on deploy mode on my serveur with a docker I have this adress in my og:image balise : https://web-dev.henoo.fr/__og-image__/image/event/invitation-ab3f0601-eb9c-41ad-946f-13f151234955/og.png
The format seem to be in the same format in localhost but here I have the following result :

500 Image size cannot be determined. Please provide the width and height of the image.

 I already try to create a new Nuxt project just for try this module but in localhost it's working fine...

Okay I find something !
I changed my OG image template and I define width height and sizes in nuxtImg
<template>

      <NuxtImg
        v-if="picture"
        class="size-40 rounded-full mb-6"
        alt="user profile picture"
        :src="picture"
        width="150"
        height="150"
        sizes="xs:200px sm:210px md:220px lg:230px xl:240px xxl:250px '2xl':260px"
      />

        {{ userName }} t'invite à sortir

      <NuxtImg src="https://henoo.fr/logo/logo_text.png" class="h-12" />

</template>

Know I don't have the 500 error. But unfortunately the image whose tag I've modified doesn't appear in the final image.
I looked at my server logs and I have :
Can't load image http://web-dev.henoo.fr/_ipx/s_500x500/https://filesdev.henoo.fr/user/16616_1721310762248?1722417805412: fetch failed
If I load the full link in my browser I get the image. That's all that's left. The server-side module can't get the image.

Please just use an img tag, I think NuxtImg has issues

Yeah it's what I tried it's working fine now 👍
It's weird because the second  works properly.
In any case, thank you very much for this package 🩵
**Final code**

<template>

      <div class="text-3xl text-center !font-semibold my-6" v-text="`${userName} t'invite à sortir`" />

      <NuxtImg src="https://henoo.fr/logo/logo_text.png" class="h-12" />

</template>


Debug Test is massively slow - 40 secs waiting for promp & it always ask for a Debug Launch Configuration

Brief Issue Summary

Click on the Debug Test & Select my unit test.

Starts build the test, even with   "cmake.buildBeforeRun": false"?

Takes ~30-40 secs to show the promp to select a Debug configuration.

It's not a Hello-world or simple project, but a production & enterprise one.
So:

How could I speed this up?
How can I avoid to select each time the same debug configuration from a list? Is not possible to let the Debug Test to choose the already selected option? This is really annoying.

Thanks.
CMake Tools Diagnostics
Snippet with censored info (NDA/private company data)

[build] Generating changeset header for repo /home/mf/repos/PROJECT/
[build] [111/131] Automatic MOC for target whatever
[build] [112/129] Automatic MOC for target whatever
[build] [113/127] Automatic MOC for target whatever
[build] [114/125] Automatic MOC for target whatever
[build] [115/123] Automatic MOC for target whatever
[build] [116/121] Automatic MOC for target whatever
[build] [117/119] Automatic MOC for target whatever
[driver] Build completed: 00:00:03.953

After this, it shows [cmakefileapi-parser] Read reply folder: /home/borjamf/repos/asdasd/build/asdasd/Debug/.cmake/api/v1/reply
[cmakefileapi-parser] Found index files: <a bunch of files.json>

[build] Build finished with exit code 0
[cache] Reading CMake cache file /home/borjamf/repos/whatever/build/asdasd/Debug/CMakeCache.txt
[cache] Parsing CMake cache string
[cache] Reading CMake cache file /home/borjamf/repos/acds_shell3/build/rasdasd/Debug/CMakeCache.txt
[cache] Parsing CMake cache string

Debug Log
No response
Additional Information
No response

Slowness could be workaround disabling compileCommnands in settings.json, it has improved significantly.
"cmake.loadCompileCommands": false,

However, I still don't get why it's "configuring" test each time, for example. It's ignoring the     "cmake.buildBeforeRun": false.
Besides that, as I mentioned, perhaps would be really useful to map somehow the Launch&Ddebug configuration instead of prompting each time when running from the panel.
I have found one thread talking about this last point: #2999 using cmake.debugConfig could be nice, but it's being ignored for me.


pbTests: Build bisheng as a test for RISC-V

Bisheng is a hotspot variant that builds natively on the platform for RISC-V, so select that if we're going a hotspot build test in qemuPlaybookCheck

Checklist

[ ] commit message has one of the standard prefixes
[ ] FAQ.md updated if appropriate
[ ] other documentation is changed or added (if applicable)
[ ] playbook changes run through VPC or QPC (if you have access) J9/ppc64le and hs/s390x (RISC-V QPC doesn't fully work yet)
[ ] for inventory.yml changes, bastillion/nagios/jenkins updated accordingly

Do you have any documentation on Bisheng so I can read up? :-)

It's Huawei's port and was added via this issue: https://github.com/AdoptOpenJDK/openjdk-build/issues/2420

Assigning Will as co-owner of this since it can be used to fully test the RISC-V QPC support

Ah okay- in that case, this PR is blocked by #2123 - I'll get on that now

Ah okay- in that case, this PR is blocked by #2123 - I'll get on that now

Yep that's pretty much why I've kept it in draft for now - awaiting the QPC test so we can verify it :-) Feel fre to take it out of draft as and when it's useful to do so

@sxa Will need a rebase

I'm going to cancel this since Temurin now builds natively for JDK17+


Impossible to add any ring to structure

Greetings and thank you for your work.
Have a problem with ketcher: I use it in a modal window and everything works fine except rings panel (at the bottom). Every time I'm trying to add, for example, benzene ring to existing structure, the modal being closed as editor doesn't let me to draw any ring from that panel. If the editor is empty or I'm adding a ring separately, the problem doesn't appear. I don't know how to provide a code example though since there are a few files and it won't be that compact, but here is my component where I use ketcher:
  const handleOnInit = async (ketcher: Ketcher) => {
      (window as any).ketcher = ketcher;

      await loadMolecule(ketcher);
      ketcher.editor.subscribe('change', operations => {updateMolecule()})
      window.parent.postMessage({
          eventType: 'init',
      }, '*');
  };

  const loadMolecule = async (ketcherInstance: Ketcher) => {
      try {
          await ketcherInstance.setMolecule(props.smilesStr);
      } catch (error) {
          console.error("Error loading molecule:", error);
          setErrorMessage("Failed to load molecule");
      }
  };

   const updateMolecule = async () => {
      try {
          const ketcherInstance: Ketcher = (window as any).ketcher;

          const smiles = await ketcherInstance.getSmiles();
          props.setInputValue(smiles);
          props.setCurrentOptions({...props.currentOptions, smiles: smiles})
      } catch (error) {
          console.error("Error updating molecule:", error);
          setErrorMessage("Failed to update molecule");
      }
  };

  return (
      <>
          <div className="ketcher-container">
              <Editor
                  staticResourcesUrl={""}
                  structServiceProvider={structServiceProvider}
                  errorHandler={(message: string) => {
                      setErrorMessage(message);
                  }}
                  onInit={handleOnInit}
              />
          </div>
      </>
  );

Have you ever seen such issue? Please let me know if you do, because I'd be glad having a possibility to solve it asap

Also have a question how can I aromatize molecule via any method before output the structure? Kekule benzene's not displayed well in my case so I have to aromatize before using in next step? I've found ketcherInstance.indigo.aromatize but not sure it's the thing


Fix synthentic (incl. forwarded) responses not getting processed by repsonse plugins

In case one of the request plugins creates a synthetic response, (e.g. forwarding plugin)
the response plugins wouldn't be called at all. This means that
such responses would not be processed by the nxlog, block_ip(v6)
and cache response plugins. In the case of block plugins the response simply wouldn't be blocked. Due to the cache response plugin not being called none of the responses generated by the forwarding plugin are cached.
Note: with this PR as it is now, the cache response plugin will also be called for responses generated by the cache plugin, which I suppose isn't desirable.

Hi Ferdinand,
This is the expected behavior. A synthetic response is something that should be delivered to the client.
These shouldn't be cached, as a synthetic response can depend on properties that are not included in the cache key.
Forwarding is typically done to access local, trusted domains, so I'm not sure that applying blocking rules is desirable.
Maybe we need to introduce new states, to differentiate synthetic responses from forwarded/cloaked responses. But I'd rather keep synthetic responses as final responses that bypass other filters.

Forwarding is typically done to access local, trusted domains, so I'm not sure that applying blocking rules is desirable.

Sure, didn't think of that. Personally, I'm using it also for some non-local domains, so it made sense to me.
Cheers/f


Ensure shell expansions are quoted in docs workflows.

Two improvements:

Ensure that shell command arguments that use env var expansion are always quoted if they are intended to be one argument. Otherwise they may expand to multiple arguments, and become a vector for shell injection attacks.
Avoid using GitHub Actions templating (${{ ... }}) in shell commands, and use env vars instead. Such templating cannot be escaped against injection attacks since it runs before the shell sees the command, so it's always better to stick the templated data in an env var and use shell expansion instead.

I don't believe the current workflows were exploitable as currently written, but security is hard and it's always better to be safe than sorry.

Got it, thanks!


MAMP syntax error, unexpected 'ENDPATH' (T_STRING) (View: /bagisto/resources/themes/velocity/views/home/index.blade.php)

Bug Report
Issue Description
after installation on home page MAMP we get
syntax error, unexpected 'ENDPATH' (T_STRING) (View: /bagisto/resources/themes/velocity/views/home/index.blade.php)
Preconditions

Bagisto Version
1.3.2

hi @ghena
can you please elaborate?

@ghena
I guess there is some issue with your instance.

of course, I close it.
Sorry.


⚠ SolarOscp has degraded performance

In 23d706b, SolarOscp ($SOLAROSCP_URL) experienced degraded performance:

HTTP code: 200
Response time: 257 ms

Resolved: SolarOscp performance has improved in 516b00b after 11 minutes.


LGBM sometimes strongly extrapolates in a regression problem with huge feature set

Hey all,
currently, I am using LGBM in a project where I am facing a quite remarkable problem.
It is a regression problem with a large featureset (partially due to 70 one-hot features). The total amount of features is ~ 200.
The situation I am facing is, that I have a feature that is outside of the typical bounds seen in the training data.
The trained model goes crazy and more or less based on judging the loss directly overfits. When predicting, in a normal situation typical MAPE values are at max 100% or so. But in this case the model extrapolates very strongly and predicts almost 800% or even more. So really far away and exceed actually any value seen as a target in the training dataset.
The validation loss shoots up more or less from the first boosting round onwards and keeps increasing.
Played around with the hyperparameters a bit but could no mitigate the problem.
Hence I would like to ask if such problems are common and if somebody knows a good mitigation strategy.
An ideal Early Stopping for example would stop at boosting round 1 which does not seem like a right mitigation at all.
More generally: Is it known when LGBM gets problems with extrapolation? My hope was more thinking from a bagging perspective that extrapolation for a tree based model should happen only in extreme rare cases. But now I would like to understand why I see this on multiple occasions in my problem right now.
Any insights would be very valuable for me. Thanks a lot already!
Best regards!

Thanks for using LightGBM. Are you able to provide the details asked for in the template that was shown when you clicked "create issue", like:

version of LightGBM you are using and how you are building it
a reproducible example (code + publicly-available data) demonstrating the issue

Without information like that, you are asking maintainers here to just guess at what's going on, and I don't think that guessing is likely to lead you to a resolution.

Based on the information you've provided so far, the only thing I can say is that the MAPE objective in general (not just in LightGBM) can be unstable if you have target values that are less than 0 in absolute value. We try to account for that (see the discussion in #3608) but it can still present challenges.
Do you see issues with "extrapolating strongly" if you use a metric like regression_l1 (MAE) or regression_l2 (RMSE)?

Hello @jameslamb,
thanks a lot for your quick response. I am sorry, that I left a lot of uncertainty in my initial phrasing of the questions and hence would like to address the open points and clarify further so that the maintainers/developers of LGBM can get the bigger picture here. See therefore my description below according to the templates.
Description
As stated in the original first post, we are talking about a regression problem with a large featureset (partially due to 70 one-hot features). The total amount of features is ~ 200.
The situation we are facing is, that one of the total of 200 features shows the problematic behavior. We identified the feature by using SHAP value analysis.
I will try to give you two concrete numeric example here:

Example:
During training, the respective feature sees the values: 1.29 up to 1.95. (these values are included in the training set).
During validation/testing, the respective feature for the first time sees the value: 1.99
The model completely goes crazy in its output and overestimated heavily and the SHAP values, that the respective feature is driving the output almost entirely alone to those high values.

Example:
During training, the respective feature sees only one value: 0.49
During validation/testing, the respective feature for the first time sees the value: 0.59
This situation is actually quite remarkable as I would hope that the feature itself has no meaning and information gain for the model, but yet again the model completely goes crazy in the output. The SHAP values again indicate, that this is only due to this one feature mainly.

Some hypothesis:
Clearly, having data outside of the training regime in such high dimensional space is risky. Our current best guess is that the respective feature sort of compensates/offsets the whole prediction.
The question remaining, did you experience something like this? Is it common or even expected behavior and are there any tips/leads to mitigate the problem? It maybe isn't a bug I could imagine. Don't get me hence wrong here, I am not expecting any definitive answer, just maybe some interesting leads or explanations that might or might not support the hypothesis stated above.
Reproducible example
Unfortunately, in the project I am working in, LGBM is just one part of a huge architecture. The data is not publicly available and hence I cannot create an reproducible example here. I am sorry for that.
Environment info
Currently version 2.3.1 is used on the Azure Cloud. Docker and K8s is used. We are planning to soon bump the version but believe, that this is (hopefully) not the root-cause of the issue and that it may likely persist also with the newer versions. But that remains to be seen.
Additional Comments
My initial description regarding the configuration/loss was too unspecific. Actually we are using RMSE (regression_l2) as the loss function during training.
We are using also the standard set of hyperparameters, besides the following that were changed from the default values:
objective: regression
boosting: gbdt
learning_rate: 0.01
max_depth: 5
bagging_fraction: 0.5
feature_fraction: 0.4
metric: RMSE
num_threads: os.environ["NTHREAD"]
num_leaves: 250
min_data_in_leaf: 5
bagging_freq: 5
num_boost_round: 1500
We played around with regularization and some other parameters to prevent overfitting, but our problems was not mitigated by this as it rather looks like an extrapolation issues due to the clear differences on train and test set (where a feature might reach out of the boundaries ever seen in the test set, see above description).

Just a quick sidenote: The newest stable release of LGBM was also tried out but did not mitigate the above stated issue.

@shiyu1994
thanks a lot for taking your time and answering!
Here are the answers to your two questions:

During training, the situation is fine, hence the train loss decreased nicely and monotonic. It is just the validation loss that increases from boosting round 1 onwards.
I'll give you some examples we are seeing:
Normal Target Label -> Crazy Output of Model
~200 -> 3000-3400
~500-1000 -> 5500-6500

There are various more showing the same pattern with different increases that reach clearly out of the range of typical label values. All have in common that the validation loss goes up from round 1 onwards and in validation or test there are values for the respective feature outside of the typical range and hence unseen in training yet.

@shiyu1994 thanks for your take. We don't use distributed training.
I am a bit unsure if I will be able to send you the tree and some validation set examples unfortunately.
But maybe you can outline some steps you would conduct for your analysis.
A potential would maybe using the new explainability functionality as outline here:
https://towardsdatascience.com/lightgbm-algorithm-an-end-to-end-review-on-the-trees-to-dataframe-method-13e8c4b74027
Hence using the trees_to_dataframe() and create_tree_digraph() methods to see how those high predictions are created could be a good option.
Would you also do your analysis like this? What additional/different steps would you undertake?
Thanks a lot and best regards!


Version 2.0

Q
A

Bug fix?
yes

New feature?
yes

BC breaks?
no

Deprecations?
no

Fixed tickets
no

Update this line in phpstan:
    - %currentWorkingDirectory%/DependencyInjection/Configuration.php

To add the /src subfolder

96% coverage 👍


CLIENT ID and blocking XREAD in cluster

I didn't see anything in the API that would help us with our situation and wanted to make sure I wasn't missing something. We have a Redis cluster where we want to issue a XREAD BLOCK 0 command. At some later point we will want to issue a CLIENT UNBLOCK to break the infinite block. The Redis documentation suggests running CLIENT ID before the blocking XREAD will allow you to know what ID to pass to CLIENT UNBLOCK. However it seems ioredis is using the stream key passed to XREAD to determine a slot and node in the cluster it should connect to. If the CLIENT ID happens on execute on a different node than the XREAD we have no way of knowing the correct CLIENT ID to issue the CLIENT UNBLOCK on.
Below is some sample DEBUG output showing the node hopping (for testing purposes I'm not blocking):
  ioredis:redis write command[<IP_ADDRESS>:7000]: 0 -> client([ 'id' ]) +2ms
  ioredis:redis status[<IP_ADDRESS>:7002]: wait -> connecting +6ms
  ioredis:redis queue command[<IP_ADDRESS>:7002]: 0 -> xread([ 'STREAMS', 'a', '$' ]) +1ms
  ioredis:redis status[<IP_ADDRESS>:7002]: connecting -> connect +1ms
  ioredis:redis write command[<IP_ADDRESS>:7002]: 0 -> info([]) +0ms
  ioredis:redis status[<IP_ADDRESS>:7002]: connect -> ready +1ms
  ioredis:connection send 1 commands in offline queue +11ms
  ioredis:redis write command[<IP_ADDRESS>:7002]: 0 -> xread([ 'STREAMS', 'a', '$' ]) +0ms
  ioredis:redis write command[<IP_ADDRESS>:7002]: 0 -> client([ 'id' ]) +1ms
  ioredis:redis status[<IP_ADDRESS>:7001]: wait -> connecting +2ms
  ioredis:redis queue command[<IP_ADDRESS>:7001]: 0 -> xread([ 'STREAMS', 'c', '$' ]) +0ms
  ioredis:redis status[<IP_ADDRESS>:7001]: connecting -> connect +1ms
  ioredis:redis write command[<IP_ADDRESS>:7001]: 0 -> info([]) +0ms
  ioredis:redis status[<IP_ADDRESS>:7001]: connect -> ready +1ms
  ioredis:connection send 1 commands in offline queue +5ms
  ioredis:redis write command[<IP_ADDRESS>:7001]: 0 -> xread([ 'STREAMS', 'c', '$' ]) +0ms

You can see the first client id takes place on 7000 while the xread takes place on 7002.
Are there any facilities to know which node a command will be run on so that we can capture the correct client id and also issue the client unblock to the correct node?

I added Redis Stream Classes. Maybe they help you
https://github.com/luin/ioredis/pull/1376

I added Redis Stream Classes. Maybe they help you

That's not relevant at all
Regarding the issue. There's a slot table:
https://github.com/luin/ioredis/blob/88b8a3125cd039afdac928c529a1b9958009979c/test/functional/cluster/transaction.ts#L9-L12
https://github.com/luin/ioredis/blob/88b8a3125cd039afdac928c529a1b9958009979c/lib/cluster/index.ts#L850
And some way to calculate it for a key: https://github.com/luin/ioredis/blob/88b8a3125cd039afdac928c529a1b9958009979c/test/functional/cluster/transaction.ts#L1


fix: set default log level to warn

Fixes #82

As we discussed, this does not meet all the rules listed in #82?

Updated to meet all conditions of #82.
Specifically, added a logging statement at the error level if the configuration cannot be initialized and switched the default log level to 2 (the warning level).


[AMBARI-24106] - Upgrade History Model Changes

What changes were proposed in this pull request?
Upgrade History must be tied to MPacks/Service Groups/Service IDs. The following changes (in bulk) need to be performed:

Removing {{RepositoryVersionEntity}} from upgrade history
Associating history with a specific service group
-- Associating that service group with to/from mpack versions
Exposing upgrade summary information for
-- Service Groups
-- Modules
-- Module Components
Removal of desired stack movement and replacement with mpack adjustment for service groups
Removal of orchestration type as this was based off of the repository and no longer can be

How was this patch tested?
Simple deploy to make sure I didn't break anything fundamental.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2715/
Test FAILed.
Test FAILured.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2718/
Test FAILed.
Test FAILured.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2717/
Test FAILed.
Test FAILured.


VSCode extension strategy

I'm not yet sure if we'll be able to adopt Gobo in our work, but if we can do it we'll want it as a VSCode extension. In that case I'd love to help out.
There are a few ways we could approach that, so this Issue is for discussion on the topic.
At a high level I see three options, in best-guess preference order:

A VSCode extension is added in a subfolder of this very repo, so that everything is in the same place and you maintain full ownership. I would contribute through PRs.
A new Pizzandy repo just for the extension is created. I personally prefer monorepos, but I can definitely see wanting to separate concerns (especially since the tech stacks for Gobo and a VSCode extension are basically non-overlapping). I would contribute through PRs or directly on main.
I add Gobo into Stitch for VSCode. On the one hand I wouldn't use Gobo without Stitch, so this would be convenient. But I think it's better to keep them decoupled so that you have full project ownership, and so that people could use it with other VSCode GML extensions, and since it's very unlikely we'd be editing Gobo on our side (the tech stack is very much outside my wheelhouse!).

What do you think? I've put a few VSCode extensions together at this point so I can help get the initial setup and publishing stuff figured out in any case.

I agree with the ranking of these options. Putting the VSCode extension in a top-level Gobo.VSCode folder should work.


Hotfix

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@4c1dd72). Click here to learn what that means.
Patch has no changes to coverable lines.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #56   +/-   ##
=======================================
  Coverage        ?   98.05%
=======================================
  Files           ?        3
  Lines           ?      513
  Branches        ?        0
=======================================
  Hits            ?      503
  Misses          ?       10
  Partials        ?        0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[GSProcessing] Allow re-partitioning to run on the Spark leader

Issue #, if available:
Description of changes:
With this change we allow the re-partition step to run on the leader instance, removing the need to run a separate job for it. If no files need re-partitioning, and only Parquet modification is needed for labels/masks we always apply that on the leader.
To accomplish this we make the following changes:

Add new --repartition-on-leader argument
Refactor repartition_files.py to allow separate execution of just Parquet metadata modification, and full repartition that runs both the row count alignment and the Parquet metadata modification.

As part of this refactoring we also split the previously verbose main function into multiple smaller functions to allow easier maintenance. Each step is now performed by a separate function, namely _repartition_edge_files, _repartition_node_files and modify_flat_array_metadata. A combined public function repartition_files calls these three functions as needed in sequence. All functions take the graph metadata dict as input, and a ParquetRepartitioner instance.

Introduce checks for node data and Parquet metadata modification in our unit tests. Test coverage for repartition_files.py is now increased to 89% (from 81%).

Testing
Unit testing, and ran jobs on SageMaker and EMR-S with ml25M. For large-scale random 100M-edges-10M-nodes graph, the repartition step completed successfully on SageMaker (large memory instances) and failed (gracefully) on EMR-S. When the repart step fails we print an error in the logs to indicate to the user they'll need to run the additional gs-repartition job separately.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@jalencato changed the user-facing argument (sagemaker launch) to --do-repartition, let me know if you think I should change the internal script as well (distributed_executor.py arguments)


.NET Framework 4.7.2 sdk  download page issues

I am a  .net Chinese developer . When I downloaded the SDK(4.7.2 dev pack) package on the official website with  Chrome explorer, the page was redirected(http302) to download the language pack only, not the "really" dev pack.
download pages :
https://github.com/dotnet/docs/blob/master/docs/framework/install/guide-for-developers.md
https://www.microsoft.com/net/download/thank-you/net472-developer-pack

@preetikr @vivmishra can you check the links for the dev pack? Thanks!

@xLabel can you confirm which of the links are you clicking on? The one for the 4.7.2 dev pack on the topic (http://go.microsoft.com/fwlink/?LinkId=863261) seems to be working fine.

@mairaw
i click this link address (http://go.microsoft.com/fwlink/?LinkId=863261) will be redirect to this
download address(https://download.microsoft.com/download/5/7/7/57703C9C-1027-4533-A69D-2393314A32D1/NDP472-DevPack-CHS.exe), this dev pack is about 13.45MB, only the lanageuage pack ? not the "really" dev pack
when i use fiddler simulation web browser to httpget the link address (http://go.microsoft.com/fwlink/?LinkId=863261), will be redirect to this
(https://download.microsoft.com/download/5/F/E/5FE505D0-E753-4F1A-B8D6-D9E73C0C28C7/NDP472-DevPack-ENU.exe), this pack about 90+MB

@mairaw
here is the http request header, "Accept-Language" is a key point.
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36
Upgrade-Insecure-Requests: 1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,/;q=0.8
Accept-Encoding: gzip, deflate, br
Accept-Language: zh-CN,zh;q=0.9

Thanks @xLabel. Our engineering team investigated the issue and managed to repro the problem. They're currently working on a fix. We'll let you know once the fix is in place. We appreciate for letting us know about this.

@mairaw : )

@mairaw hi,  download link is wrong again, it has become download NDP472-DevPack-CHS.exe  and NDP472-KB4054530-x86-x64-AllOS-CHS.exe.
.NET Framework 4.7.2  Offline Installer  :  Developer Pack &  Runtime

@yhnbgfd I just pushed a change to https://www.microsoft.com/net/download/windows that should fix the issue for you. Can you confirm.

@rowanmiller All download links are now correct


Setup swarm

https://github.com/docker/swarm/

Will be replaced by https://docs.docker.com/engine/swarm/ in Docker 1.12. ;)

Yep :)
Closing this


Fix mix of formal and informal addressing

[ ] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

@AltheaE Thank you for  creating this PR.  However, since it was created, the underlying document has changed.  Can you please review and resolve the current merge conflicts?  It could be the changes to the underlying document are so significant that your changes are no longer relevant.  If the latter is the case, it might be easier to just close this PR and create a new PR with any changes you still feel are important to make.
If you need any assistance or have questions about resolving the merge conflicts, please reply back or contact someone in the Contributors Room on Gitter.
Thank you

We are restructuring a lot of the code and learning resources referenced in your pull request, so for now I am going to go ahead and close this pull request. Thanks again for opening this pull request and for contributing to the community.


Module for admin-provided munki conditions

resolve #627 from @flammable.
resolve #835 from @flammable.
Please let me know if you have any suggestions.
For one, I didn't know how to get the location of ManagedInstallReport.plist from prefs so it is hardcoded in the client script.
Second, all values are truncated and stored as 255 character strings. Would it be preferred to utilize BLOB so that JSON could be used to store arrays?
Munki Conditions Module
Provides the results of munki conditions, allowing admins to easily generate their own reportable datapoints without creating custom MunkiReport modules. Condition scripts are even easier to create using munki-facts.
Admin-Provided Condition scripts are found in /usr/local/munki/conditions.
The results of these scripts are stored in the 'Conditions' dictionary in /Library/Managed Installs/ManagedInstallReport.plist.
Both keys and values are truncated to 255 characters.
The following information is stored in the munki_conditions table:

serial_number
condition_key
condition_value

This module is mostly based on work by clburlison, erikng, bochoven and more.

The munkireport module grabs the Munki installation dir this way:
managed_install_dir = CoreFoundation.CFPreferencesCopyAppValue(     "ManagedInstallDir", "ManagedInstalls")

Thanks, I made some adjustments to the script to use the munki prefs, with a fallback to a default path if the pref doesn't work.

Hmm, I need to chase down a bug where the condition data is overwriting other data in the client tabs.

@tuxudo suggests that the values be stored as BLOB instead of VARCHAR255. I will work on that next.

Sorry for the late reaction. This looks great. Just one nitpick: could you rename the module to munki_facts? Although they are used as conditions, I think they should be treated as facts.


Disable Warning

Hello I netbox have virtual machines entered by hand, and for some reason in the synchronization is constantly warping, can you disable it how?
2023-04-05 09:48:38,208 - WARNING: Unable to determine second key 'cluster' for virtual machine 'FVF-MON-02', got: None
2023-04-05 09:48:38,208 - WARNING: This could cause serious errors and lead to wrongly assigned object relations!!!

Hi,
did you try addind a cluster to the VM as stated in the log message?

Hi,
did you try addind a cluster to the VM as stated in the log message?

I created a cluster and bound it to these vm, it no longer frowns in the logs


chore: missing typing for AC

Codecov Report
Attention: Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.

Project coverage is 6.36%. Comparing base (e3753db) to head (2a1e605).
Report is 16 commits behind head on main.

Files
Patch %
Lines

midealocal/devices/ac/__init__.py
0.00%
4 Missing :warning:

Additional details and impacted files
@@           Coverage Diff            @@
##            main     #85      +/-   ##
========================================
- Coverage   6.38%   6.36%   -0.03%
========================================
  Files         77      77
  Lines       6605    6626      +21
========================================
  Hits         422     422
- Misses      6183    6204      +21

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


Rewrites Not Working as Expected

It appears that rewrites are not functioning as expected. Here's my vercel.json configuration:
{
  "rewrites": [
    {
      "source": "/(.*)",
      "destination": "/api"
    }
  ],
  "functions": {
    "api/**/*.rs": {
      "runtime"<EMAIL_ADDRESS>    }
  }
}

Additionally, when I navigate to an API route, I receive the following error when running vc dev:
❯ vc dev
Vercel CLI 32.2.0
> Ready! Available at http://localhost:3000
> Building vercel-rust@4.0.6:api/simple.rs
> Built vercel-rust@4.0.6:api/simple.rs [2s]
Error: spawn /home/rajput-hemant/.cache/com.vercel.fun/runtimes/provided/bootstrap EACCES
    at Process.ChildProcess._handle.onexit (node:internal/child_process:286:19)
    at onErrorNT (node:internal/child_process:484:16)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
Error: An unexpected error occurred!
Error: spawn /home/rajput-hemant/.cache/com.vercel.fun/runtimes/provided/bootstrap EACCES
    at Process.ChildProcess._handle.onexit (node:internal/child_process:286:19)
    at onErrorNT (node:internal/child_process:484:16)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)

I managed to rewrite the path with the following vercel.json configuration for example/simple:
{
	"rewrites": [
		{ "source": "/simple", "destination": "/api/simple.rs" },
		{ "source": "/complex", "destination": "/api/complex.rs" },
		{ "source": "/user/:id", "destination": "/api/user/[id].rs" }
	],
	"functions": {
		"api/**/*.rs": {
			"runtime"<EMAIL_ADDRESS>		}
	}
}

However, this doesn't seem to work for the Experimental bundling API. Here is my vercel.json configuration, using the bundled_api macro for example/route-merge:
{
	"rewrites": [{ "source": "/(.*)", "destination": "/api/main.rs" }],
	"functions": {
		"api/main.rs": {
			"runtime"<EMAIL_ADDRESS>		}
	}
}

With this configuration, when I navigate to the route /foo, i.e., without /api as the base path, I get the usual 404: NOT_FOUND, and when I navigate to the route /api/foo, I get 502: BAD_GATEWAY and see this panic log in the terminal:
❯ vc dev
Vercel CLI 32.2.0
> Ready! Available at http://localhost:3000
> Building vercel-rust@4.0.6:api/main.rs
> Built vercel-rust@4.0.6:api/main.rs [4s]
thread 'main' panicked at 'internal error: entered unreachable code', examples/route-merge/api/main.rs:8:1
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
TypeError: Object prototype may only be an Object or null: undefined
    at Function.setPrototypeOf (<anonymous>)
    at new LambdaError (/home/rajput-hemant/.bun/install/global/node_modules/vercel/dist/index.js:13136:16)
    at Lambda.<anonymous> (/home/rajput-hemant/.bun/install/global/node_modules/vercel/dist/index.js:13269:27)
    at Generator.next (<anonymous>)
    at fulfilled (/home/rajput-hemant/.bun/install/global/node_modules/vercel/dist/index.js:13183:58)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

@dglsparsons Thanks for your quick response and for looking into this. I'm hopeful that this issue can be fixed, as having both rewrites and function bundling would be a valuable addition.


Use TryLock instead of RwLock/Mutex for uncontended locks

We use RwLock and Mutex in some places where we only use the .try_*() methods, as there's no actual contention, and we're doing it just for the borrow checker. However, RwLock and Mutex are fairly large and even their .try_*() methods are not small, so we should use a lightweight alternative like TryLock, whose only overhead is an AtomicBool and atomic swaps for locking and unlocking.

It seems like parking_lot::Mutex's .try_lock() is about as efficient as TryLock, so this isn't worth it anymore now that we're using parking_lot.


Feature request- CAF Terraform Module for Private DNS Resolver

Is there an existing issue for this?

[X] I have searched the existing issues

Community Note

Please vote on this issue by adding a :thumbsup: reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description
I can see currently hashicorp is in process of releasing the module for private DNS resolver looking forward to add that feature into CAF.
New or Affected Resource(s
azurerm_private_resolver
Potential Configuration file
No response
References
No response

Closing as merged and will be part of 5.7.0


Add a package flag to cryptonite

Suggestion from: https://github.com/DanielG/ghc-mod/issues/762
Addresses: #636
I do not fully understand the implications of this change, but it fixed the problem for me (once I forced stack to rebuild cryptonite)

Does not fully solve the problem; trying to render diagrams leads to an unhandled elf relocation in libHSglib-<IP_ADDRESS>.


Disable pyvelox wheels build in macos temporarily.

We are seeing pyvelox wheel builds fail on MacOS ( see issue 8635 ). This PR disables these builds while we investigate a fix.

I am investigating in #8627 after removing the fbthrift build a ccache error surfaces which I haven't had the time to check yet. So disabeling it makes sense.


base class, public/private parameter

Only a warning, but.._.

Marking the parameter as protected will help you.
I think the code analyzer should suggest to mark the parameter as protected instead of private.

There is a code snippet to create parameters, so you won't get this issue in the future:
para > tab > tab

Thanks for the answers!

Thanks!


[backport] Improve FunctionNode upgrade guide

Backport of #5527

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 50ff3141f16f277cf0bbe17c56c915a457cbbb88, target branch v5) succeeded!


[BUG] [2.4.0] Failed to process project graph. Run "nx reset" to fix this.

Current Behavior
After upgrading to @nx-dotnet/core to 2.4.0, I get the following error when running any nx command

Failed to process project graph. Run "nx reset" to fix this. Please report the issue if you keep seeing it.
An error occurred while processing files for the @nx-dotnet/core plugin.
- Plugin worker @nx-dotnet/core exited unexpectedly with code 0
Error: Plugin worker @nx-dotnet/core exited unexpectedly with code 0
at ChildProcess. (D:\DigitaalMeten\node_modules\nx\src\project-graph\plugins\isolation\plugin-pool.js:178:37)
at ChildProcess.emit (node:events:519:28)
at ChildProcess._handle.onexit (node:internal/child_process:294:12)
The "@nx-dotnet/core" plugin threw an error while creating dependencies:
Error: Plugin worker timed out when processing message @nx-dotnet/core30304:createDependencies:1
at Timeout. (D:\DigitaalMeten\node_modules\nx\src\project-graph\plugins\isolation\plugin-pool.js:201:17)
at listOnTimeout (node:internal/timers:581:17)
at process.processTimers (node:internal/timers:519:7)

Expected Behavior
to run nx commands properly
Github Repo
No response
Steps to Reproduce

update the @nx-dotnet/core package from 2.2.0 to 2.4.0
run nx run-many -t build
the error will show

Nx Report
**NOTE**: had to reduce the `@nx-dotnet/core` package to produce this report
---

NX   Report complete - copy this into the issue template

Node   : 20.16.0
OS     : win32-x64
npm    : 10.8.2

nx (global)        : 19.5.0
nx                 : 19.5.3
@nx/js             : 19.5.3
@nx/jest           : 19.5.3
@nx/linter         : 19.5.3
@nx/eslint         : 19.5.3
@nx/workspace      : 19.5.3
@nx/angular        : 19.5.3
@nx/devkit         : 19.5.3
@nx/eslint-plugin  : 19.5.3
@nx/playwright     : 19.5.3
@nx/plugin         : 19.5.3
@nrwl/tao          : 19.5.3
@nx/web            : 19.5.3
@nx/webpack        : 19.5.3
typescript         : 5.5.4
---------------------------------------
Registered Plugins:
@nx/eslint/plugin
@nx-dotnet/core
@nx/jest/plugin
---------------------------------------
Community plugins:
@fortawesome/angular-fontawesome : 0.15.0
@ngrx/component                  : 18.0.1
@ngrx/component-store            : 18.0.1
@ngrx/effects                    : 18.0.1
@ngrx/entity                     : 18.0.1
@ngrx/router-store               : 18.0.1
@ngrx/schematics                 : 18.0.1
@ngrx/store                      : 18.0.1
@ngrx/store-devtools             : 18.0.1
@nx-dotnet/core                  : 2.4.0
---------------------------------------

nx.json
{
	"tasksRunnerOptions": {
		"default": {
			"runner": "nx-remotecache-azure",
			"options": {}
		}
	},
	"workspaceLayout": {
		"appsDir": "apps",
		"libsDir": "libs"
	},
	"plugins": [
		{
			"plugin": "@nx/eslint/plugin",
			"options": {},
			"inferredTargets": {
				"lint": "lint",
				"lint-fix": "lint-fix"
			}
		},
		{
			"plugin": "@nx-dotnet/core",
			"options": {
				"solutionFile": "Ibis.DigitaalMeten.sln",
				"inferProjects": true,
				"nugetPackages": {},
				"inferredTargets": {
					"build": {
						"inputs": [
							"production",
							"^production",
							"!{workspaceRoot}/packag*.*",
							"!{workspaceRoot}/**/packag*.*",
							"!{workspaceRoot}/package.json",
							"!{workspaceRoot}/package-lock.json"
						],
						"targetName": "build",
						"configurations": {
							"production": {
								"runtime": "linux-x64",
								"configuration": "Release",
								"noDependencies": false
							}
						}
					},
					"lint": "lint",
					"serve": "serve",
					"test": {
						"inputs": [
							"default",
							"^production",
							"!{workspaceRoot}/packag*.*",
							"!{workspaceRoot}/**/packag*.*",
							"!{workspaceRoot}/package.json",
							"!{workspaceRoot}/package-lock.json"
						],
						"targetName": "test",
						"cache": true,
						"configurations": {
							"ci": {
								"blame": false,
								"blameCrash": false,
								"logger": "trx"
							}
						}
					}
				},
				"ignorePaths": [],
				"tags": ["nx-dotnet"]
			}
		},
		{
			"plugin": "@nx/jest/plugin",
			"options": {
				"targetName": "test"
			}
		}
	],
	"generators": {
		"@nx/angular:application": {
			"style": "scss",
			"linter": "eslint",
			"unitTestRunner": "jest",
			"e2eTestRunner": "playwright"
		},
		"@nx/angular:library": {
			"linter": "eslint",
			"unitTestRunner": "jest",
			"changeDetection": "OnPush",
			"style": "scss",
			"standalone": true,
			"strict": true
		},
		"@nx/angular:component": {
			"style": "scss",
			"changeDetection": "OnPush"
		}
	},
	"$schema": "./node_modules/nx/schemas/nx-schema.json",
	"cli": {
		"cache": {
			"enabled": true
		}
	},
	"targetDefaults": {
		"build": {
			"dependsOn": ["^build"],
			"inputs": ["production", "^production"],
			"cache": true
		},
		"lint": {
			"inputs": [
				"default",
				"{workspaceRoot}/.eslintrc.json",
				"{workspaceRoot}/tools/eslint-rules/**/*"
			],
			"cache": true
		},
		"lint-fix": {
			"inputs": ["default", "{workspaceRoot}/.eslintrc.json"],
			"options": {
				"fix": true
			}
		},
		"serve": {
			"dependsOn": ["^build"]
		},
		"e2e": {
			"cache": true
		},
		"test": {
			"inputs": [
				"default",
				"^production",
				"{workspaceRoot}/jest.preset.js"
			],
			"executor": "@nx/jest:jest",
			"cache": true,
			"options": {
				"passWithNoTests": true,
				"jestConfig": "{projectRoot}/jest.config.ts"
			},
			"configurations": {
				"ci": {
					"ci": false,
					"coverageReporters": ["json"],
					"outputDirectory": "coverage/{projectRoot}",
					"coverageDirectory": "coverage/{projectRoot}"
				}
			}
		},
		"@nx/eslint:lint": {
			"cache": true,
			"inputs": [
				"default",
				"{workspaceRoot}/.eslintrc.json",
				"{workspaceRoot}/tools/eslint-rules/**/*"
			]
		}
	},
	"namedInputs": {
		"default": ["{projectRoot}/**/*", "sharedGlobals"],
		"sharedGlobals": [],
		"production": [
			"default",
			"!{projectRoot}/**/?(*.)+(spec|test).[jt]s?(x)?(.snap)",
			"!{projectRoot}/tsconfig.spec.json",
			"!{projectRoot}/jest.config.[jt]s",
			"!{projectRoot}/.eslintrc.json",
			"!{projectRoot}/src/test-setup.[jt]s"
		]
	},
	"parallel": 6,
	"cacheDirectory": ".cache/nx",
	"defaultBase": "origin/master",
	"pluginsConfig": {
		"@nx/js": {
			"projectsAffectedByDependencyUpdates": "auto"
		}
	}
}

Failure Logs
Failed to process project graph. Run "nx reset" to fix this. Please report the issue if you keep seeing it.
An error occurred while processing files for the @nx-dotnet/core plugin.
- Plugin worker @nx-dotnet/core exited unexpectedly with code 0
Error: Plugin worker @nx-dotnet/core exited unexpectedly with code 0
at ChildProcess. (D:\DigitaalMeten\node_modules\nx\src\project-graph\plugins\isolation\plugin-pool.js:178:37)
at ChildProcess.emit (node:events:519:28)
at ChildProcess._handle.onexit (node:internal/child_process:294:12)
The "@nx-dotnet/core" plugin threw an error while creating dependencies:
Error: Plugin worker timed out when processing message @nx-dotnet/core30304:createDependencies:1
at Timeout. (D:\DigitaalMeten\node_modules\nx\src\project-graph\plugins\isolation\plugin-pool.js:201:17)
at listOnTimeout (node:internal/timers:581:17)
at process.processTimers (node:internal/timers:519:7)

Additional Information
I found that version 2.3.0 DOES work, so the issue started at 2.3.1

Did it hang for 5 minutes before dying? The max message timeout should be 5 minutes.
Does it work if you run with NX_ISOLATE_PLUGINS=false? If not, what does the error look like

Did it hang for 5 minutes before dying? The max message timeout should be 5 minutes.
Does it work if you run with NX_ISOLATE_PLUGINS=false? If not, what does the error look like

yes, it was a while (could be 5 minutes) for the timeout to trigger.
With the env set I got:
The "@nx-dotnet/core" plugin threw an error while creating dependencies:
    TypeError: dotnetClient.getProjectReferences is not a function
        at Object.createDependencies (D:\DigitaalMeten\node_modules\@nx-dotnet\core\src\graph\create-dependencies.js:21:49)
        at LoadedNxPlugin.createDependencies (D:\DigitaalMeten\node_modules\nx\src\project-graph\plugins\internal-api.js:60:59)
        at D:\DigitaalMeten\node_modules\nx\src\project-graph\build-project-graph.js:226:47
        at Array.map (<anonymous>)
        at updateProjectGraphWithPlugins (D:\DigitaalMeten\node_modules\nx\src\project-graph\build-project-graph.js:223:47)
        at buildProjectGraphUsingContext (D:\DigitaalMeten\node_modules\nx\src\project-graph\build-project-graph.js:135:30)
        at async buildProjectGraphUsingProjectFileMap (D:\DigitaalMeten\node_modules\nx\src\project-graph\build-project-graph.js:86:24)
        at async buildProjectGraphAndSourceMapsWithoutDaemon (D:\DigitaalMeten\node_modules\nx\src\project-graph\project-graph.js:101:30)
        at async createProjectGraphAndSourceMapsAsync (D:\DigitaalMeten\node_modules\nx\src\project-graph\project-graph.js:208:25)
        at async createProjectGraphAsync (D:\DigitaalMeten\node_modules\nx\src\project-graph\project-graph.js:198:39)

That's interesting, let me do some digging.

Can you run npm ls @nx-dotnet/dotnet? That feels like its pulling a different version as we added the dotnet client get project references call in 2.3.1

npm ls @nx-dotnet/dotnet

i ran it:
<EMAIL_ADDRESS>D:\DigitaalMeten
└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>

Ah, it looks like this broke when I swapped from some custom deploy scripts to nx release. I'll get it fixed up.
In the meantime you should be able to rm -rf node modules + package lock to get latest versions

This should be published now in 2.4.1, let me know if you still have issues

can verify this works now


To run the simple test case, run the following from this directory:

```bash
cd dakota/test/
dakota -i dakota_test.in -o dakota_test.out

Originally posted by @katyhuff in https://github.com/arfc/dcwrapper/pull/8

nvm


replace silently ignores parts of the version

If you try and replace a crate with a version more complex than x.y.z, the parts of the version other than x.y.z are ignored, which usually means the replace does not match any crates and has no effect (Cargo warns about this).
E.g., grpcio:0.5.0-alpha.3 will not match deps with version = "0.5.0-alpha.3"

Considering replace is mostly deprecated, I imagine it may be unlikely that effort will go into fixing this.  There are also several known issues with how pre-release versions are handled, which may be the root of this problem.
Can [patch] work for you instead?

As replace is deprecated and without further information in several years on if patch would instead work, I'm going to go ahead and close this.  If there is a reason to keep this open, let us know!


KeyError: "[E002] Can't find factory for 'pytt_wordpiecer'.

import en_pytt_bertbaseuncased_lg
nlp = en_pytt_bertbaseuncased_lg.load()

produces this error
KeyError: "[E002] Can't find factory for 'pytt_wordpiecer'. This usually happens when spaCy calls nlp.create_pipe with a component name that's not built in - for example, when constructing the pipeline from a model's meta.json. If you're using a custom component, you can write to Language.factories['pytt_wordpiecer'] or remove it from the model meta and add it via nlp.add_pipe instead."

Hi @Aya-S : this seems related to spaCy's en_pytt_bertbaseuncased_lg model rather than to the neuralcoref plugin?
I will close it here but feel free to open an issue on the spaCy issue tracker. When you do, make sure to include the details of your environment by pasting the output of python -m spacy info --markdown


I am currently using ssl certificates inside my configurations ('/ssl/fullchain.pem and /ssl/privkey.pem in http yaml section) and I don't want to push theses files in github. Such as secrets, I would like to mock theses files or I need to ignore somehow that they should exist. Do you have a way to that ?

 Just find the solution, one minute after writing this issue... For people in the same situation, you could just use the ssl path as a secret and change the path to dummy files using the fake secrets.yaml!

Took you just 4 minutes to figure out after creating the issue 😄
Glad you got it figured out m8!

Yes I was looking for a solution during more than a hour and then immediately after the issue, the idea came into my head.
Sorry for that, at least it may help some people in the future !


Issue 22: Add address validation

Verify that blockchain addresses are valid using coinaddrvalidation library

I though about calling the address validation just at the end of  tagpack.validate(), but the messages to the console were mixed together (those resulting of validating the schema/taxonomies and those of the address validation). Also, address validation will result in warning messages only (e.g. the tagpack validation won't fail if there are some invalid addresses), so the tagpack validation doesn't seem to strongly depend on address validation. Anyway, we can integrate address validation into tagpack validation if you think it's better that way.


build fails

./configure
make
make install

krishna, this doesn't work

/needsMoreInfo

@alexandrudima what info do you need? all steps are in snippet

user@pc ~ $ uname -a
Linux pc 5.3.6-arch1-1-ARCH #1 SMP PREEMPT Fri Oct 11 18:28:05 UTC 2019 x86_64 GNU/Linux
user@pc ~ $ make --version
GNU Make 4.2.1
Built for x86_64-pc-linux-gnu
Copyright (C) 1988-2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

@luntik2012 VS Code is not built with make. Here is a page describing how you can build VS Code and run it -- https://github.com/Microsoft/vscode/wiki/How-to-Contribute#build-and-run


Translation: Rational Priority

language code
zh-hans
Mod
https://steamcommunity.com/sharedfiles/filedetails/?id=2632758219
File
RationalPriority_zh.zip

Done in #27


Remove obsolete codes form batch (re)normalization

BatchRenormalizationFunction no longer has to support F.fixed_batch_renormalization (#4869).
Stop manually wrapping ndarray by Variable.

jenkins, test this please.

Jenkins CI test (for commit 3b8ed9cd4631ecc0c8cde63de6c94f69c6d0f6e5) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

LGTM!


[checkpoints] Introduce checkpoint timestamps

This PR adds CheckpointSummary::timestamp_ms field and populates it from the time of narwhal commit

Addressed feedback


running all tests on travis

Don't merge. Only doing this for investigatory purposes.

This could be merged if it passes CI.

This will be done in #1923


Add two new buttons to Soundsets Importer window

Changes:

Added a button to copy the ID of a mood to the clipboard
Added a button to create a macro to play a mood

https://github.com/frondeus/fvtt-syrin-control/assets/7666672/157cf228-358d-43a0-8d54-a4c37f7f840b

Looks good to me! Tested locally, buttons working as promised :)


contact.weixin showing openid; how do we get the "微信号"?

Aliyun
Run npm run doctor or wechaty run doctor(for docker user), paste output here
Starting Wechaty v0.13.41 with Node.js v9.4.0 ...

<EMAIL_ADDRESS>doctor /wechaty
npm run check-node-version && ts-node bin/doctor

<EMAIL_ADDRESS>check-node-version /wechaty
check-node-version --node ">= 7"

Wechaty Doctor

Wechaty version: #git[c8ce385]
Linux x64 version 3.10.0-514.26.2.el7.x86_64 memory 272/1839 MB
Docker: true
Node version: v9.4.0
Tcp IPC TEST: PASS

Expected behavior
contact.weixin suppose to get the weixin id for friends.
Actual behavior
contact.weixin printing out openid
Steps to reproduce the behavior (and fixes, if any)
docker run -ti --rm --volume="$(pwd)":/bot zixia/wechaty contact-bot.ts
Full Output Logs
$ WECHATY_LOG=silly npm run ts-node mybot.ts

# or

$ WECHATY_LOG=silly node dist/mybot.js

Show Logs

### Paste the full output logs here with `WECHATY_LOG=silly` set
# PASTE FULL LOG OUTPUT AT HERE:

This feature might be support by other Puppet.
See #1167


Nami swap

Hello I want to ask if the company of nami wallet had a swap like namiswap.io ??

@Limaseepro Talk to cardano Support on the Cardano Live Support so that your issue can be looked into.


Add support for Google Cloud Functions

Resource name: Google Cloud Functions
Pricing page: https://cloud.google.com/functions#section-15

Hello! Can I do this if nobody minds?

@ruanmartinelli we just released this in v0.7.20 🎉 (install docs), it would be great to hear your thoughts about how infracost handles usage-based resource such as Cloud Functions, e.g. using this.


Codes that Convert COLMAP Outputs to poses_bounds.npy

Hello, I would like to do the llff experiment with my own data and colmap poses. I found out that in data/llff.py, it read poses_bounds.npy instead of colmap outputs. I could not find the Python scripts that convert COLMAP outputs. I wrote one by using the functions provided by the LLFF dataset https://github.com/Fyusion/LLFF/tree/master/llff . The reconstruction quality was poor. I used other NeRF codes to learn a NeRF and the reconstruction were good. I am suspecting that there is something wrong with the poses_bounds.npy that was computed by the codes that I wrote. Could you tell me to how to create the poses_bounds.npy please? If there is already a file that does the job, could you point me to it please? Thanks!

Hi @XinhuaZhang, the pose_bounds.py files I have been using are all preprocessed and provided by the datasets. The gen_poses() function here is probably what you're looking for. Hope this helps!

I meet the same problem , have you fixed it? thanku


Popup is not showing up

Popup is not showing up.
This is my code:

				hep

Console tells me that jQuery is defined. No errors shown.

You need to specify autoopen: true in options to have the popup open right on creation.

Plain jquery (this is what you check with if (!jQuery)) is not enough for popups to work, you need to reference the jquery.popupoverlay script file in HTML.

When inserting code in messages, use the appropriate formatting (triple-backtick, see https://guides.github.com/features/mastering-markdown/ ), or else github garbles it, like it did with your code.

It was the autoopen: true, thanks.
Both 2 and 3 was okay all ready.


Fix a bug in star-tree filter operator which can incorrecly filter documents

This bug was introduced in #9667
When the predicate matches all the non-star nodes under a branch, we can use the star-node if it exists and the dimension is not included in the remaining predicate and group-by. In the existing code we update the global remaining predicate too late, and the branches before the update can mistakenly use the star-node even though the dimension is included in the remaining predicate.
This PR fixes that behavior by tracking whether we have added leaf node into the queue, so that we can update the global remaining predicate before traversing any child of that dimension.
Added a hard-coded query in StarTreeClusterIntegrationTest to test this behavior. Also print the random seed when test fails to make it much easier to reproduce.
This also fixes #9945

Codecov Report

Merging #10707 (92d8ab6) into master (ab79548) will decrease coverage by 56.44%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master   #10707       +/-   ##
=============================================
- Coverage     70.25%   13.81%   -56.44%
+ Complexity     6429      439     -5990
=============================================
  Files          2112     2058       -54
  Lines        113996   111518     -2478
  Branches      17219    16924      -295
=============================================
- Hits          80084    15411    -64673
- Misses        28312    94847    +66535
+ Partials       5600     1260     -4340

Flag
Coverage Δ

integration1
?

integration2
?

unittests1
?

unittests2
13.81% <0.00%> (-0.04%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...core/startree/operator/StarTreeFilterOperator.java
0.00% <0.00%> (-88.16%)
:arrow_down:

...cal/startree/v2/builder/BaseSingleTreeBuilder.java
0.00% <0.00%> (-90.00%)
:arrow_down:

... and 1666 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


mpl2: fix snap and avoid calling the track-grid unnecessarily

Fix #4868
We were not considering that it may exist cases, e. g. sky130hd, in which the distance between the pins and the origin in the master of a macro instance may not be a multiple of the track-grid. In such cases a small offset will need to be compensated.
Changes here:

Ensure that we take the mterm offset into account;
Avoid iterating layers after we already have the spacing parameters and with that avoiding calling the track-grid multiple times

Pins of a macro in sky130hd-microwatt with these changes:

Just a piece of commentary: it looks like this code snaps based on the first signal pin that it finds per layer. This works well assuming that the pins have a regular pitch that matches the routing grid, but won't help if the pitch is irregular.
I still think we need an IP checker to find these kinds of issues up front to ensure that a bad block isn't being passed. It would be a good project for a new-comer.

@rovinski would you open an issue with a write up for a new comer and label it?

@maliberty Now we compute the snap in DBU. I also went and refactored some things to remove variables that were not necessary.

macro_only (tcl) FAIL

secure CI?

@maliberty Secure-CI passed.


Pass github key as argument to script - Techzone

https://github.ibm.com/Developer-Playground/work-items/issues/658


Invalid value in tensor used for shape: -512

tensorflow-gpu ==2.3
keras == 2.3
wave_kern = 'db2'
inputs = Input(shape)
# x = wave(inputs)
wave0 = inputs
print(K.int_shape(inputs))
wave1 = WaveTFFactory.build(wave_kern,dim=2)(wave0)

inputs is (None, 512, 512, 1)
error is Invalid value in tensor used for shape: -512
why did this mistake happen

I want try to run mini_cnn
ValueError: Invalid value in tensor used for shape: -512

The same thing happened

I'll have a look and get back to you soon.

I've pushed  a fix (commit 4b38e23) that should solve the issue.
Let me know if it now works for you. Thanks.

It's usable. Thanks


multitiple files convert like query ?

big thx for this scripts
its a posible to start folder to transcode all files one to one with same name i try same variant bud i not get this sucess and the problem its thad the movie name will not same if you choose just folder the name of movie will the name of folder..
if its posible please need one example
kind regarts

@senkron24 I'm honestly not sure that I understand what you want to do. And for that I sincerely apologize because I know you're trying to write as clearly as possible.
If you want to transcode multiple files in a folder with a single command you cannot pass a path to that folder as an argument. That's because folder arguments are interpreted as DVD or Blu-ray disc image directories.
However, you can do something like this:
transcode-video /path/to/Folder/*.mkv

... and your shell should expand the * to all the MKV files in that folder.
Or, you could simple use a batch script. Which is what I do. Here's how to do that:
https://github.com/donmelton/video_transcoding#batch-control-for-transcode-video
I hope that helps.

ooo yes thad fine. exackly thad i mean with multi files with one comand
i will try this comand to do this
big thx for the help ..
Yasar Maymak
TvJoy Iptv Global Systems ..
Best Regarts
İyi Çalışmalar
mail<EMAIL_ADDRESS>mail<EMAIL_ADDRESS>Tel: +905427885669
2017-10-26 1:01 GMT+03:00 Don Melton<EMAIL_ADDRESS>
@senkron24 https://github.com/senkron24 I'm honestly not sure that I
understand what you want to do. And for that I sincerely apologize because
I know you're trying to write as clearly as possible.
If you want to transcode multiple files in a folder with a single command
you cannot pass a path to that folder as an argument. That's because folder
arguments are interpreted as DVD or Blu-ray disc image directories.
However, you can do something like this:
transcode-video /path/to/Folder/*.mkv
... and your shell should expand the * to all the MKV files in that
folder.
Or, you could simple use a batch script. Which is what I do. Here's how to
do that:
https://github.com/donmelton/video_transcoding#batch-
control-for-transcode-video
I hope that helps.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/donmelton/video_transcoding/issues/174#issuecomment-339485466,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AaKCQ4j4Y8m4HXJiZ7LrWB-865-g77SDks5sv6_KgaJpZM4QGo70
.

i just test like this comand line
root@tvjoy:/# transcode-video "/home/vip2/transc/.avi" -o "/home/vip2/Finish"
bud get a result like this
/usr/local/bin/transcode-video: No such file or directory - /home/vip2/transc/.avi
No such file or directory bud thare its video files exist with avi format
can help me to make its ..?

@senkron24 Sorry I took so long to reply.
The problem is that you're quoting the * in the input name as a literal string instead of allowing your shell to perform pathname expansion on it.
Try this instead:
transcode-video "/home/vip2/transc/"*.avi -o "/home/vip2/Finish"

Do you see the difference? Only the base pathname in the input is quoted. The *.avi is not.
I hope that helps.

no problem thank your for your nice support
oo yeah i see the difrens and its works very great ,now all its ok
Kind regarts

@senkron24 You are very welcome! I'm glad that worked.
I'll close this now but don't be afraid to open another issue if you run into a problem.


Add detection for SkyMake and SkyfallenSecureForms

Thank you, but this doesn't appear to meet the criterion of a widely used technology.
https://github.com/AliasIO/wappalyzer/blob/master/CONTRIBUTING.md#adding-a-new-technology


First pass

PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/variantannotation branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

self-merging, as this is a first pass that I deem acceptable enough


Support SpikeTrainList object in Elephant

Since Neo 0.10.0, there is a new SpikeTrainList object. While this new construct behaves like a list, there are a couple of instances where Elephant directly tests if an input is explicitly a list of SpikeTrains. This PR adds support for allowing SpikeTrainList objects as well as lists of SpikeTrains in these circumstances.
Fixes:

conversion.BinnedSpiketrain (wtih regression test, where SpikeTrainLists would lead to incorrect binned matrices)

This PR fixes #431.

Hello @mdenker! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file elephant/conversion.py:

Line 1247:10: E111 indentation is not a multiple of four
Line 1247:10: E117 over-indented
Line 1248:5: E722 do not use bare 'except'

In the file elephant/test/test_conversion.py:

Line 192:80: E501 line too long (115 > 79 characters)
Line 204:80: E501 line too long (87 > 79 characters)
Line 206:80: E501 line too long (89 > 79 characters)


Rename validate to appimagegpgvalidate

This is not a good idea for a binary name; it conflicts on my system.
I understand it started as an example program but when installed it no longer makes sense to call it just validate. However, I moved it back to the old name in the AppImage build. :-)
Supersedes #212.

AppImage tools are designed to run from within AppImages, not to be installed onto the host system with make install.

Closely related are linuxdeploy/linuxdeploy#229 (merged) which fixes make install for linuxdeploy and linuxdeploy/linuxdeploy#230 (rejected although I added a comment for @TheAssassin and might reopen it depending on their reply).

It would be easier to convince distributions to pack the AppImage tools if they installed to logical names

AppImage tools are intended to be used from the AppImages we provide, not from third-party (distribution) packages which may or may not be outdated and broken in subtle ways.

This doesn't break that or even change the name of the AppImage, or the name of the binary in the AppImage

This PR should just be closed without any further attention. It is anything but good style to basically open another PR with the exact same change that was already rejected, especially since you didn't even bother to wait for a reply for https://github.com/AppImageCommunity/AppImageUpdate/pull/212#issuecomment-1310560249.
We do not have a code of conduct currently, but these kinds of events make me think this might be a good idea.
Again, this project is not supposed to be installed on your system. We do not intend to fix this. Feel free to maintain a fork under a different name. It's still pointless from AppImage's perspective.
The name validate has a history. I could have explained it to you if you'd let me. I guess with a little effort, this could have been tracked down in the Git history even.
As mentioned in some other PR of yours, you should open issues before sending PRs, and wait for feedback. Sending PRs by one's own accord always means they might just be closed. This kind of interaction costs time I do not have to spend on other aspects of this project.

i would've been fine w/you just closing this
a CoC would not (normally) prevent PR's for as-yet-undiscussed changes
i mostly just open new PR's so i don't forget about the issue as i frequently do, or, if your feedback were positive, whenever it may arrive, then there's already a PR which does it, but i may not have time to open a new one when it does arrive
i think your post is a little dramatic.

Sorry @ctrlcctrlv. I appreciate your contributions. It's just that AppImageUpdate is supposed to run from within its AppImage, so the PR is kinda pointless, isn't it?

@probonopd I will open a meta issue later about that question as I think that if we want to see a world with more AppImages the basic tools should be installable through distro repositories, if only for CI. Once I get my thoughts together on that we can discuss whether make install-ed versions should print some kind of warning if run in an interactive terminal (this is for CI for certain pedantic projects that don't like to download binaries blah blah blah you should use the tools from the AppImages, this tool is @ <URL> etc)

Thing is, we don't want people use outdated versions of our tools shipped by distributions. But yes, let's talk about it.


[resotocore][feat] Allow custom commands

Description

To-Dos

[ ] Add test coverage for new or updated functionality
[ ] Lint and test with tox
[ ] Document new or updated functionality (someengineering/resoto.com#XXXX)

Issues Fixed

Fixes #XXXX

Code of Conduct
By submitting this pull request, I agree to follow the code of conduct.

Codecov Report
Base: 90.16% // Head: 89.73% // Decreases project coverage by -0.43% :warning:

Coverage data is based on head (988003c) compared to base (6af1e69).
Patch coverage: 59.23% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1182      +/-   ##
==========================================
- Coverage   90.16%   89.73%   -0.44%
==========================================
  Files          68       68
  Lines       10192    10290      +98
==========================================
+ Hits         9190     9234      +44
- Misses       1002     1056      +54

Flag
Coverage Δ

resotocore
89.73% <59.23%> (-0.44%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

resotocore/resotocore/web/api.py
71.79% <40.00%> (-1.19%)
:arrow_down:

resotocore/resotocore/cli/model.py
94.65% <56.25%> (-2.07%)
:arrow_down:

resotocore/resotocore/cli/command.py
86.04% <57.30%> (-1.82%)
:arrow_down:

resotocore/resotocore/query/model.py
93.80% <66.66%> (-0.12%)
:arrow_down:

resotocore/resotocore/cli/cli.py
92.52% <76.92%> (-0.77%)
:arrow_down:

resotocore/resotocore/core_config.py
95.63% <100.00%> (+0.02%)
:arrow_up:

resotocore/resotocore/types.py
100.00% <100.00%> (ø)

resotocore/resotocore/worker_task_queue.py
90.00% <100.00%> (ø)

resotocore/resotocore/db/entitydb.py
87.09% <0.00%> (+0.80%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Analysis Server doesn't notify clients when no analysis needs to be performed.

Usually the sequence follows:
SEND: {"id":"14900","method":"analysis.updateContent" ...
RECV: {"id":"14900","result":{}}
RECV: {"event":"server.status","params":{"analysis":{"isAnalyzing":false}}}
However, sometimes the server.status is never sent (example to follow by email).

Unclear if this is still a problem for the legacy protocol. But even if it is, this is a P4 issue.

Given that there have been no other reported problems with the protocol, I'm going to close this.


Docs: Describe the difference between "module": "ES2020" & "module": "ES2022"

Page URL: https://www.typescriptlang.org/tsconfig#module
Issue: The docs do not describe the difference between "module": "ES2020" & "module": "ES2022", it's not obvious what is different between them
Recommended Fix: Document the difference between them, the same as the difference between ES2015 and ES2020 is documented.

I imagine these are aliases for backwards compatability ( /cc @weswigham ? ) if so. I can add it


perf(sourcemap): elide bounds checks in VLQ encoding

#4583  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite


Code N Queens :infinity: in any programming language you like :computer:

Code N Queens :infinity: in the relevant language folder :file_folder: in the main branch.
if language folder doesn't exist you can make folder :file_folder: and add your program in it.
You can find new languages in this Programming Language List.
Give star :star: to this repository.

Hi @iParadocx , I can take this up. Kindly assign this to me.

hey @iParadocx can you assign this to me i can work on it


scalar: report error when we need to move decimal's zero point

dev=> select<PHONE_NUMBER>0000000000000000000 + 0.0000000000000000001::decimal;
           ?column?
-------------------------------
<PHONE_NUMBER>0000000000000000000

which means that we lost precision while computing decimal. This should not be allowed, and we should report an error.
cc @fuyufjh

Hi, any updates?

Hi, any updates?

Not yet, finding a solution for properly implementing BigDecimal turned out to be way more complex than I initially thought so I have paused this for now. However, I can Implement the report error and leave the implementation of BigDecimal to support larger precision for a later moment?

Not yet, finding a solution for properly implementing BigDecimal turned out to be way more complex than I initially thought so I have paused this for now. However, I can Implement the report error and leave the implementation of BigDecimal to support larger precision for a later moment?

Yes, IIUC a more powerful decimal is not necessary at least for now, since it's too complicated as discussed. But we should at least be correct, and reject errors e.g. in this issue 😄


multiple users on same system encounter permissions errors

Environment

OS: [Ubuntu 22.04]
Hardware (GPU, or instance type): no gpu

To reproduce
Steps to reproduce the behavior:

Create a StreamingDataset
Log in as a different user
Create a StreamingDataset
Encounter a permissions error on trying to write to tmp/streaming

A similar issue related to shared memory that only happens if your process crashes:

Create a StreamingDataset
Kill the process in an unclean way so that python doesn't have a chance to clean up shared memory (e.g. kill -9)
Delete /tmp/streaming to prevent the first issue.
Log in as a different user
Create a StreamingDataset
Encounter a permissions error on a shared memory resource (e.g. PermissionError: [Errno 13] Permission denied: '/000000_locals')

You can verify this with the following script:
from streaming import MDSWriter
from streaming import StreamingDataset
import tempfile
### generate a sample dataset...
# directory for a sample dataset
out_root = tempfile.TemporaryDirectory().name
local_root = tempfile.TemporaryDirectory().name
print("out_root: ",out_root)
# A dictionary of input fields to an Encoder/Decoder type
columns = {
    'anumber': 'int'
}

# some sample data
samples = [
    {
        'anumber': 123123
    }
    for _ in range(2)
]

# write out the sample data
print("writing data...")
with MDSWriter(out=out_root, columns=columns) as out:
    for sample in samples:
        out.write(sample)
### finished generating the sample dataset

print("creating dataset object...")
remote_dir = out_root
local_dir = local_root

dataset = StreamingDataset(remote=remote_dir, local=local_dir, split=None)
for x in enumerate(dataset):
    print(x)

input("wait for input (so you have a chance to kill the process in an unclean way)")

Expected behavior
No errors.

Additional context
StreamingDataset initialization will create a directory tmp/streaming if it does not exist yet, and so the first user will own that directory.
Subsequent users on the same system are now locked out unless the first user manually chmods the directory or system cleans up tmp/streaming.
A similar issue can happen with the SharedMemory objects in dev/shm.
Using the clean_stale_shared_memory function doesn't fix this because it encounters the same permissions error.

Hey! So we looked into this and weren't able to reproduce the first behavior, but we were able to reproduce the second (PermissionError: [Errno 13] Permission denied: '/000000_locals'). The reason this is happening is because we need to access each existing SharedMemory file to check for potential collisions between local directory names for different StreamingDatasets here -- without this, multiple StreamingDatasets could point to the same local directories, messing up the samples.
For this case, we would recommend making sure each user creating StreamingDatasets has the same permissions, or updating user permissions to make sure that /tmp/streaming and the SharedMemory files are accessible. Thanks for identifying the issue and submitting this PR!

Thanks for looking into it!
I'm confused how the first issue didn't replicate - my understanding of the issue was that this os.makedirs call made it so that /tmp/streaming is only writeable by the creating user.  Was it perhaps the case for you that /tmp/streaming/ was already present and globally writeable rather than being created for the first time? This would explain the difference since the shared memory is cleaned up when the process exits normally and so would actually have been created by the first process. In my scenario /tmp/streaming did not exist yet.
For my system (an academic cluster), it's not easy to ensure that /tmp/streaming is accessible since I don't have any special privileges. Right now I've told my students to just chmod /tmp/streaming as part of every job they launch in case they are the first to be scheduled on some node, but if any other group starts using streaming then we'll have problems again.

I just doublechecked again and the /tmp/streaming directory was not present when creating the first streaming dataset. Even when creating equally permissioned users, and not killing the process in an unclean way (it's still running when the second streaming dataset is created), I can only reproduce the Permission denied: '/00000_locals' error. And that's due to the local directory checking that's needed before initializing every streaming dataset. If possible, could you send over the stack trace with the error for /tmp/streaming? Would love to take a look.

closing the issue due to inactivity. Please feel free to re-open if you think this is still an issue.

@karan6181 Reopening this issue because I ran into the same issue on a university cluster. There is also an easy solution. Instead of hardcoding /tmp/streaming can we have it respect the TMPDIR env var instead so each user can set a custom location instead?

https://github.com/mosaicml/streaming/pull/570 is merged.

@knighton is it already in release?

@Oktai15 are you still seeing this with the latest version of streaming?