reset_default_graph awkwardly breaks graph nesting.

System information

Linux Ubuntu 16.04:
TF version 1.1.0, though it should still be present in master:

Bug
Running this:
import tensorflow as tf

g = tf.Graph()
with g.as_default():
  tf.reset_default_graph()
  # Build something...
  a = tf.constant(1.0)
  b = tf.constant(1.0)
  c = a + b
  # Bug happens on exit of the with statement

Causes this
---------------------------------------------------------------------------
IndexError                                Traceback (most recent call last)
<ipython-input-1-af7c5ed96704> in <module>()
      7   a = tf.constant(1.0)
      8   b = tf.constant(1.0)
----> 9   c = a + b

/usr/lib/python3.5/contextlib.py in __exit__(self, type, value, traceback)
     64         if type is None:
     65             try:
---> 66                 next(self.gen)
     67             except StopIteration:
     68                 return

/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/ops.py in get_controller(self, default)
   3626     finally:
   3627       if self._enforce_nesting:
-> 3628         if self.stack[-1] is not default:
   3629           raise AssertionError(
   3630               "Nesting violated for default stack of %s objects"

IndexError: list index out of range

This bug causes a confusing error message. The stack should either include the new default graph created by reset_default_graph or a warning/error message should happen when you reset the default within nested graphs.

The default graph is a property of the current thread. tf.reset_default_graph() function applies only to the current thread. Calling this function while a tf.Session or tf.InteractiveSession is active will result in undefined behavior. Using any previously created tf.Operation or tf.Tensor objects after calling this function will result in undefined behavior.
import tensorflow as tf
g = tf.Graph()
with g.as_default():
  a = tf.constant(1.0)
  b = tf.constant(1.0)
  c = a + b

Right, but you don't need an active session or any previously created ops/tensors to cause the error. Just calling reset_default_graph within nested graphs causes a confusing error.
Just this:
import tensorflow as tf

g = tf.Graph()
with g.as_default():
  tf.reset_default_graph()

Also breaks with the same error.
---------------------------------------------------------------------------
IndexError                                Traceback (most recent call last)
<ipython-input-1-8377d035bd16> in <module>()
      3 g = tf.Graph()
      4 with g.as_default():
----> 5   tf.reset_default_graph()

/usr/lib/python3.5/contextlib.py in __exit__(self, type, value, traceback)
     64         if type is None:
     65             try:
---> 66                 next(self.gen)
     67             except StopIteration:
     68                 return

/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/ops.py in get_controller(self, default)
   3813     finally:
   3814       if self._enforce_nesting:
-> 3815         if self.stack[-1] is not default:
   3816           raise AssertionError(
   3817               "Nesting violated for default stack of %s objects"

IndexError: list index out of range

I think it would be better if it actually threw the AssertionError rather than break on an index error. I'll see if I can make a PR for the fix tonight.

For historical context, tf.reset_default_graph() was never designed to be used with with g.as_default(): context managers. I think the proper fix here is to make tf.reset_default_graph() fail with an informative error message when used inside a with g.as_default(): context. I think this could be done by checking that ops._default_graph_stack is empty before resetting.

@mrry You are right. Many errors in tensorflow should be written in human friendly manner so that they don't have to research so hard for its cause.

I agree we should fail with a more informative error message. @Thenerdstation @printdhruv would either of you be willing to create a PR for this?

@skye It would be so easy for author of that specific code do this. I don't have specific guidelines but let me see how can I approach this?

@skye Ill gladly make the PR tonight

Great, thank you @Thenerdstation! I realize getting started with TensorFlow development is non-trivial, and  there are many small issues like this that collectively would take up a lot of the team's time, so we really appreciate external contributions!
As Derek said, you can detect if you're in a default graph context by checking if _default_graph_stack is empty. This will probably involve adding a new method to the _DefaultGraph class. Don't forget to add a unit test :)

@skye Let me try in your direction. I am enjoying this work!

As far as I understand graph.as_default adds graph on the top of stack and tf.reset_default_graph resets whole stack. Is it non-unintuitively? Would it be better to make tf.reset_default_graph remove graph from top of stack? So that it would work with nested graphs. @mrry


Flask Migrate can't find other models aside from roles and users

using the latest version and python 3.5

forgot to import model in my views

I have this same issue at the moment. Can you explain further what you did to fix this?


IE11 issue when deleting all accounts

This issue is imported from pivotal - Originaly created at Apr 15, 2021 by Koen Cornelis
When deleting all accounts, the switch to the "normal" wayf does not work and the buttons on screen appear to become unresponsive (specifically the use another account button and the edit button).  This works again after a while, but takes too long for the average user.
Note from @arnout: there may be a delay because IE tries to find all non-findable logo's.

This issue turned out not to be reproducable locally or on the test2 environment. It's also not reproducable via browserstack.  As such, after conferring with Arnout we decided to close this issue for now.  (Koen Cornelis - Apr 15, 2021)


Allows preprocess_weights_for_loading() to consider layers wrapped in TimeDistributed or Bidirectional

Currently layers with a Bidirectional or TimeDistributed wrapper are not considered by preprocess_weights_for_loading() as only the layer.class.name property is examined. This would fix that. Alternatively it could be addressed within preprocess_weights_for_loading()

Please add unit tests.

Since this mainly concerns reading weight files from Keras 1, I am not 100% sure what can helpfully be covered in the Keras 2 unit tests, any thoughts? I also didn't see any unit tests for the general reading and writing of weights, is it permissible to write files within the unit tests?

Currently, how was correctness tested? Do you have a test script and test files that you used?

Any update?

Sorry, PhD work built up and then I totally forgot about this! So I had tested it for myself by having a weight file (.hdf5) saved from an older version and then loading it in and testing that the weights in each layer had been modified, but that requires lugging around an old weights file. Perhaps it would make more sense to move the fix into preprocess_weights_for_loading() then unit tests could just work with weight tensors that are constructed in the old style?

Agreed, preprocess_weights_for_loading is where this step belongs.
One note on style: use e.g. num_weights instead of nb_weights.

I have refactored preprocess_weights_for_loading to handle the cases from TimeDistributed and Bidirectional wrappers. I have added unit tests that construct a TimeDistributed and a Bidirectional wrapped layer and construct weight tensors that need preprocessing via preprocess_weights_for_loading. I assert that the input tensors and the layer weights are equal after preprocessing and batch applying them.

LGTM, thanks

great, should this be submitted to tf.contrib.keras also?


update notebooks

Hi I want to note that although the tests passes here it doesnt on the other PR here https://github.com/theislab/moscot/actions/runs/9513260069/job/26222972253#step:5:153 It's just one notebook remaining. Writing so that it won't also fail in the future.


'ms' instead of 'ms-cli'

Hi,
why isn't the bin command ms? That would be even faster to type.

Well, I was mainly concerned about possible collisions, hence the prefixed version


Support for Arduino Uno R3?

I recently purchased an NHD-3.12-25664UCW2 and found this repository for controlling it with an Arduino Mega. I'm trying to modify it to work with my Arduino Uno R3 (changing the SCK and MOSI ports appropriately) but haven't had success yet. Do you know if it is possible to control the screen with an Uno? If so, do you have any tips or would you be willing to help me troubleshoot?

Hello Jacob,
I apologize for the delayed response.
To start, I would recommend not only changing SCK and MOSI, but the other control signals as well.
To something like this:
#define OLED_DC    3    // Register select signal
#define OLED_RESET 4    // Reset signal
#define OLED_CS    5    // Chip select signal
#define OLED_CLK   6    // Serial clock signal
#define OLED_MOSI  7    // Serial data signal

Additionally, make sure you are using 3.3V signals to talk to the display. Arduino Uno boards typically use 5V signals, so you may need to use a voltage shifting circuit or an Arduino board that runs on 3.3V.

It's been a while, but I believe I solved this issue by getting the right logic shifting set up as you eventually suggested. The support team (Zach and Mayra) at NHD helped me solve this issue. Since then, I've moved on to using an Arduino Due instead, which runs at 3.3V. This code was great for setting up the initially IO/testing out the look of the display, but for further programming, I've been using the u8g2 library.


Should we switch the llvm package to ollvm?

Look at this https://github.com/OCamlPro/ollvm

Prof. advises us to opt for more mature package


Duplicate named routes definition

Versions

nuxt: v2.14.8
node: 14.15.1

Reproduction

Additional Details

downgrade node to 10.23.0

downgrade node to 10.23.0


Added a whole bunch of translation keys and created head titles for the pages that doesn't have them!

#2171

Did this right before I'm going to sleep. Don't expect response or fixes.


Is there any way to avoid calling a dtd url from response when using XmlBodyMatcher?

I am using XML in body request and response, so I am using XmlBodyMatcher.
My request and response contain some urls for a dtd, which I think are called when the request is made and also when the response is verified with XmlBodyMatcher. For the request I have managed to avoid checking the dtd by setting some features on the DocumentBuilderFactory, like this:
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
factory.setValidating(false);
factory.setNamespaceAware(true);
factory.setFeature("http://xml.org/sax/features/namespaces", false);
factory.setFeature("http://xml.org/sax/features/validation", false);
factory.setFeature("http://apache.org/xml/features/nonvalidating/load-dtd-grammar", false);
factory.setFeature("http://apache.org/xml/features/nonvalidating/load-external-dtd", false);
DocumentBuilder builder = factory.newDocumentBuilder();

But for the response I don't know how to instruct XmlBodyMatcher to not call my dtd. I need this because otherwise I get a connection timeout error, because that url is not available from my network.
I think it tries to validate that dtd when the XML is parsed by the XmlBodyMatcher. Do you have any ideas how can I ignore the verification of the dtd?
Thanks!

I've added the pact.matching.xml.validating system property, which if set to false will set the validating value on the document builder factory to false.

4.0.3 has been released with this fix

@uglyog I've just tested this using 4.0.3 and it seems that even if I use -Dpact.matching.xml.validating=false it will still try to access the dtd url.

Hi @uglyog. In order to completely ignore the dtd url, I think you should set also the following on the document builder factory:
factory.setFeature("http://apache.org/xml/features/nonvalidating/load-dtd-grammar", false);
factory.setFeature("http://apache.org/xml/features/nonvalidating/load-external-dtd", false);

Thanks


CIV-6669 Rename tab name

Before creating a pull request make sure that:

[x] commit messages are meaningful and follow good commit message guidelines
[x] README and other documentation has been updated / added (if needed)
[x] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-6669
Change description
Change Application "Summary" tab name to "Application"
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No


False positives in Imported Function Recognizers

Version and Platform (required):

Binary Ninja Version: 3.5.4377-dev Personal (24869472)
OS: Windows
OS Version: 10.0.25375.1
CPU Architecture: x64

Bug Description:
Some functions are being marked as import thunks despite clearly doing more than that.
No amount of messing around with symbols and data vars in the API seems to make BN stop marking them as such.
Steps To Reproduce:

Open this BNDB.
Navigate to these functions: Sleep, InitializeSListHead, RaiseException, SetUnhandledExceptionFilter

Expected Behavior:
These 4 functions should not be marked as import thunks.
Screenshots:

This I assume is one of our function recognizer being overly broad.

Thanks for the report this should be fixed in 3.5.4391

@plafosse maybe I'm missing something, but this doesn't appear to be fixed on my end. I updated to 3.5.4392-dev Personal (f9a3e2ad) and navigated to the misidentified InitializeSListHead. I first undefined the function and then the kernel32:InitializeSListHead variable. Then I recreated the function, and it's once again identified as InitializeSListHead and marked as a library function. The same happens for SetUnhandledExceptionFilter and Sleep. It's a bit harder to tell with RaiseException because undefining it causes BN to consider it as an extension of FOutputDeviceWindowsError::method_001 (0x7ff69a9399d0).

For me it looks like this:

Could you try re-opening the original binary?

Also for SetUnhandledExceptionFilter all the calls to it seem to be un-named

Same with InitializeSListHead

I really believe I fixed the underlying issue here as I had to update our unit tests to remove one of the false positives that was showing up.

Could you try re-opening the original binary?

Hmm, it does seem to work as it should when creating a new BNDB.
Is there any way to fix it for my existing BNDB? At this time, Import From BNDB doesn't carry over enough of my analysis progress for it to be a realistic option.

Is there any way to fix it for my existing BNDB?

After messing around with the API a bit, I managed to get rid of the stale ImportedFunctionSymbols for good:

ok great!


Trigger click event on treenode

Hi,
after initialize the tree in my component I want to select a determinate treenode with an Id and trigger the click event. This is what I have:
ngOnInit() {
    setTimeout(() => {
      let nodeToShowFirst = this.tree.treeModel.getNodeById('evAt');
      let event = new MouseEvent('click');
      if(nodeToShowFirst !== undefined){
        nodeToShowFirst.elementRef.nativeElement.dispatchEvent(event);
      }
    }, 0);
  }

but I receve the Error: "Element Ref is no longer supported since introducing virtual scroll
You may use a template to obtain a reference to the element"
It happen because of the call to elementRef() on the ITreeNode,
but if the list of treenodes is generated dinamically I can't use ViewChild. So, how can I obtain the elementRef to the node and dispatch click event?

Hi,
you can use the API to find the node and select it:
treeModel.getNodeById(id).setIsActive(true)


Automate NPM deployment

Setup Github action for NPM deployment

Can I take this up?

Sure! @aneeshrelan

Is the NPM_AUTH_TOKEN added to the repo settings? @karlmarxlopez

Wait I'll add it @aneeshrelan

Done @aneeshrelan

Thanks! @karlmarxlopez . Please excuse me this is my first time trying my hands on Github actions. Putting something up soon!

@aneeshrelan No worries! Goodluck!


hpcg: init at 3.1

Motivation for this change
HPCG is a benchmarking suite that aims at complementing linpack  (HPL).
Things done

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

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

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

Result of nixpkgs-review pr 86132 1

1 package built:
- hpcg


UVAtlasTool on linux

I've successfully build and run UVAtlas on Ubuntu22.04. The results are shown below:

The code is quit simple and every option is hardcoded currently. I am considering wrapping it into a pypi package, say pyUVAtlas, for linux users. Any suggestions from the community?
For those interested in building on Linux, I used vcpkg to install all the dependencies. I am wondering if it's possible to use vcpkg to install dependencies when building a PyPI package? Even if it is possible, users would still need to install vcpkg first and then use it to install DirectXMesh, DirectXMath, etc., before finally configuring pyUVAtlas. Is there a more elegant way to streamline this process?

I've successfully build and run UVAtlas on Ubuntu22.04. The results are shown as below:   The code is quit simple and every option is hardcoded currently. I am considering wrapping it into a pypi package for linux users. Any suggestions from the community?

For those interested in building on Linux, I used vcpkg to install all the dependencies. I am wondering if it's possible to use vcpkg to install dependencies when building a PyPI package?

Here is the python wrapper repo pyatlas

I noticed that the helper functions related to gutters are missing in the current library, which prevents me from creating a texture atlas with gutters. Could the developers please kindly add this feature to the library?


the 'InnerHandler' property must be null. 'DelegatingHandler' instances provided to 'HttpMessageHandlerBuilder' must not be reused or cached

remove the code on line 21 in DispatcherDelegatingHandler.cs
.net core will do it for you.

not required, just made a override


osx: Implement clear recent documents

Fixes #3932

cc  @https://github.com/Microsoft/vscode/issues/1662

Thanks!

Nice thanks!


SA1009,1111,1114,1115 trigger when using compiler directives in method signatures

Unfortunately due to Microsoft renaming a bunch of interfaces, we had to use compiler directives to pick the right interface for the version being compiled.
It would be great if Stylecop would ignore compiler directive lines and not treat them as whitespace.
#pragma warning disable SA1111, SA1115, SA1114, SA1009
        public EventNotificationStatus ProcessEvent(
#if TFS20151
            IVssRequestContext requestContext,
#else
            TeamFoundationRequestContext context,
#endif
            NotificationType notificationType,
            object notificationEventArgs,
            out int statusCode,
            out string statusMessage,
            out ExceptionPropertyCollection properties)
#pragma warning restore SA1111, SA1115, SA1114, SA1009
        {

And:
private Uri GetCollectionUriFromContext(
+#if TFS20151
+            IVssRequestContext requestContext
+#else
+            TeamFoundationRequestContext requestContext
+#endif
+            )
         {

@jessehouwing Thanks for reporting this issue.
I agree that said rules should not report diagnostics in this case.

Grabbing this

@jessehouwing why did you disable SA1009? Its seems to me that there would be no need for that.
The only reason I can think of is:
    public void TestMethod(
#if SOMEEVENT
        IInterface1 instance
#else
        IInterface2 instance
#endif
        )
    {
    }

but that construction is incorrect in my opinion and should be written as:
    public void TestMethod(
#if SOMEEVENT
        IInterface1 instance)
#else
        IInterface2 instance)
#endif
    {
    }

The observation above probably also holds true for SA1111.

That would work, though I prefer to have the the least amount possible between my compiler directives. Adding a new parameter at the end would require me to update both compiler directive parts.
I can see how your layout would work as well.
I ended up finding a better solution anyway, using:
#if TFS2015u1
using IVssRequestContext = Microsoft.TeamFoundation.Framework.Server.IVssRequestContext;
#else
using IVssRequestContext = Microsoft.TeamFoundation.Framework.Server.TeamFoundationRequestContext;
#endif

Because the interface was simply renamed, that results in cleaner code overall.

OK, thanks for the feedback. Your new solution is preferable indeed :+1:
I'll still fix this for SA1114 and SA1115, since that still is a valid use case.

Thanks!


Missing breaking change note for look-around regexes/patterns

Initial Checks

[X] I confirm that I'm using Pydantic V2 installed directly from the main branch, or equivalent

Description
Look-around regexes/patterns (e.g. ^(?!_)(?!.*__)[a-z_]{1,64}(?<!_)$) have been supported in v1, but fail with the following error in v2:
pydantic_core._pydantic_core.SchemaError: Error building "model" validator:
  SchemaError: Error building "model-fields" validator:
  SchemaError: Field "value":
  SchemaError: Error building "dict" validator:
  SchemaError: Error building "str" validator:
  SchemaError: regex parse error:
    ^(?!_)(?!.*__)[a-z_]{1,64}(?<!_)$
     ^^^
error: look-around, including look-ahead and look-behind, is not supported

I didn't see this noted as a breaking change (or I overlooked it!).
Is this something that's planned to be supported again?
(pydantic v2 is looking very cool so far! 🎉)
Example Code
import pydantic

class Model(pydantic.BaseModel):
    x: pydantic.constr(pattern=r"^(?!_)(?!.*__)[a-z_]{1,64}(?<!_)$")

Python, Pydantic & OS Version
             pydantic version: 2.0
        pydantic-core version: 2.0.1 release build profile
                 install path: /Users/empicano/Library/Caches/pypoetry/virtualenvs/server-W6QUvoSE-py3.11/lib/python3.11/site-packages/pydantic
               python version: 3.11.0 (main, Dec 15 2022, 21:05:29) [Clang 14.0.0 (clang-14<IP_ADDRESS>)]
                     platform: macOS-12.6-x86_64-i386-64bit
     optional deps. installed: ['typing-extensions']

Selected Assignee: @adriangb

On the off chance that anyone looking at this used a similar regex to mine: I solved this in the end by rewriting the regex without look-arounds to pydantic.constr(pattern=r"^[a-z](_?[a-z])*$", max_length=64). It effectively does the same thing.
Thanks again for the work on this, Adrian! 🔥


ERROR: localization network cannot detect the region of interest. Please check image quality

ERROR: localization network cannot detect the region of interest. Please check image quality

Hello @Maahi129 which images are you using? Which resolution? are they defaced?

I am using resolution of 0.7, could you send me your mail id so that i can send sample image.

<EMAIL_ADDRESS>

sent, please do check. If its not there, please do check spam too, Thank you.

103818.nii.gz
https://drive.google.com/file/d/1G7JRDC44yGczgZdr9H1V8By0FJmus3GO/view?usp=drive_web
On Mon, 15 Jul 2024 at 16:13, Santiago Estrada @.***>
wrote:

@.***
—
Reply to this email directly, view it on GitHub
https://github.com/Deep-MI/olf-bulb-segmentation/issues/3#issuecomment-2228203390,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWH5P3QWTVOTXRTJ6BDZ3XDZMORW3AVCNFSM6AAAAABK4HF756VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRYGIYDGMZZGA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Internal use of unwrap

Currently, the code is littered with calls to unwrap an option.
In every case, what we really mean is that we are expecting a resolved value and not having one is an Error.
These panicking code paths should instead Err and we should have a "resolution error" field of DemesError.
Related: #136

Closing. We have done what we can until #161 is implemented.


[Linux] Add a flutter run console output test

Adds a test to verify the console output of flutter run --debug and flutter run --release on Linux.
Test run using led: https://ci.chromium.org/swarming/task/5fbc7d5d48ad1c10?server=chromium-swarm.appspot.com
Part of: https://github.com/flutter/flutter/issues/111577
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Still LGTM


Fix Numba Cache Error

What does this PR do?
Fix for an error I received while trying to utilize the intel GPU TGI image.
Fixes
2024-08-21T22:35:19.551153Z  INFO download: text_generation_launcher: Starting check and download process for Intel/neural-chat-7b-v3-3
Error: DownloadError
2024-08-21T22:35:24.217869Z ERROR download: text_generation_launcher: Download encountered an error:
/usr/local/lib/python3.10/dist-packages/torchvision/io/image.py:13: UserWarning: Failed to load image Python extension: 'libpng16.so.16: cannot open shared object file: No such file or directory'If you don't plan on using image functionality from `torchvision.io`, you can ignore this warning. Otherwise, there might be something wrong with your environment. Did you have `libjpeg` or `libpng` installed before building `torchvision` from source?
  warn(
2024-08-21 22:35:23.250 | INFO     | text_generation_server.utils.import_utils:<module>:75 - Detected system ipex
Traceback (most recent call last):
  File "/usr/local/bin/text-generation-server", line 5, in <module>
    from text_generation_server.cli import app
  File "/usr/local/lib/python3.10/dist-packages/text_generation_server/cli.py", line 10, in <module>
    from text_generation_server.utils.adapter import parse_lora_adapters
  File "/usr/local/lib/python3.10/dist-packages/text_generation_server/utils/__init__.py", line 13, in <module>
    from text_generation_server.utils.tokens import (
  File "/usr/local/lib/python3.10/dist-packages/text_generation_server/utils/tokens.py", line 7, in <module>
    from text_generation_server.utils.logits_process import (
  File "/usr/local/lib/python3.10/dist-packages/text_generation_server/utils/logits_process.py", line 8, in <module>
    from outlines.fsm.fsm import RegexFSM
  File "/usr/local/lib/python3.10/dist-packages/outlines/__init__.py", line 2, in <module>
    import outlines.generate
  File "/usr/local/lib/python3.10/dist-packages/outlines/generate/__init__.py", line 1, in <module>
    from .api import SequenceGenerator
  File "/usr/local/lib/python3.10/dist-packages/outlines/generate/api.py", line 5, in <module>
    from outlines.fsm.fsm import FSMState
  File "/usr/local/lib/python3.10/dist-packages/outlines/fsm/fsm.py", line 9, in <module>
    from outlines.fsm.regex import create_fsm_index_tokenizer, make_deterministic_fsm
  File "/usr/local/lib/python3.10/dist-packages/outlines/fsm/regex.py", line 96, in <module>
    def create_fsm_info(
  File "/usr/local/lib/python3.10/dist-packages/numba/core/decorators.py", line 225, in wrapper
    disp.enable_caching()
  File "/usr/local/lib/python3.10/dist-packages/numba/core/dispatcher.py", line 808, in enable_caching
    self._cache = FunctionCache(self.py_func)
  File "/usr/local/lib/python3.10/dist-packages/numba/core/caching.py", line 601, in __init__
    self._impl = self._impl_class(py_func)
  File "/usr/local/lib/python3.10/dist-packages/numba/core/caching.py", line 337, in __init__
    raise RuntimeError("cannot cache function %r: no locator available "
RuntimeError: cannot cache function 'create_fsm_info': no locator available for file '/usr/local/lib/python3.10/dist-packages/outlines/fsm/regex.py'

Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
@OlivierDehaene
@Narsil

no, I use https://github.com/huggingface/text-generation-inference/pull/2439 based branch, and have not seen such issue

Closing this for now. Feel free to reopen.


crash with "Illegal instruction" when build release on linux

I have built the library https://github.com/aous72/OpenJPH with cc and use Bindgen to generate FFI, on Mac Os working fine when running release and debug, for Linux it's running well with debug mode, release mode  it builds success but  crashes with "Illegal instruction" when I running.
this is my Repo: https://github.com/ngoclinh93qt/openjph-ffi

Thanks for the report but this isn't particularly actionable, do you have more information such as debug logs, system configuration, etc?


cpanm AI::MXNetCAPI fails: error: mxnet_wrap.o: No such file or directory

Description
installing AI::MXNetCAPI fails
Error Message
cpanm AI::MXNetCAPI fails
To Reproduce
type: sudo cpanm -v AI::MXNetCAPI
Environment
debian 10 stable, 64 bit
sudo cpanm -v AI::MXNetCAPI
cpanm (App::cpanminus) 1.7044 on perl 5.028001 built for x86_64-linux-gnu-thread-multi
Work directory is /root/.cpanm/work/1586466130.25207
You have make /usr/bin/make
You have LWP 6.36
You have /usr/bin/tar: tar (GNU tar) 1.30
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://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.

Written by John Gilmore and Jay Fenlason.
You have /usr/bin/unzip
Searching AI::MXNetCAPI () on cpanmetadb ...
--> Working on AI::MXNetCAPI
Fetching http://www.cpan.org/authors/id/S/SK/SKOLYCHEV/AI-MXNetCAPI-1.5.tar.gz ... OK
Unpacking AI-MXNetCAPI-1.5.tar.gz
AI-MXNetCAPI-1.5/
AI-MXNetCAPI-1.5/README
AI-MXNetCAPI-1.5/mxnet.i
AI-MXNetCAPI-1.5/lib/
AI-MXNetCAPI-1.5/lib/AI/
AI-MXNetCAPI-1.5/lib/AI/MXNetCAPI.pm
AI-MXNetCAPI-1.5/Makefile.PL
AI-MXNetCAPI-1.5/META.yml
AI-MXNetCAPI-1.5/Changes
AI-MXNetCAPI-1.5/mxnet_typemaps.i
AI-MXNetCAPI-1.5/META.json
AI-MXNetCAPI-1.5/MANIFEST
AI-MXNetCAPI-1.5/t/
AI-MXNetCAPI-1.5/t/AI-MXNetCAPI.t
Entering AI-MXNetCAPI-1.5
Checking configure dependencies from META.json
Checking if you have ExtUtils::MakeMaker 6.58 ... Yes (7.34)
Running Makefile.PL
Configuring AI-MXNetCAPI-1.5 ... Checking if your kit is complete...
Looks good
Warning (mostly harmless): No library found for -lmxnet
Generating a Unix-style Makefile
Writing Makefile for AI::MXNetCAPI
Writing MYMETA.yml and MYMETA.json
OK
Checking dependencies from MYMETA.json ...
Checking if you have ExtUtils::MakeMaker 0 ... Yes (7.34)
Checking if you have Test::More 0 ... Yes (1.302170)
Building and testing AI-MXNetCAPI-1.5 ... cp lib/AI/MXNetCAPI.pm blib/lib/AI/MXNetCAPI.pm
Running Mkbootstrap for MXNetCAPI ()
chmod 644 "MXNetCAPI.bs"
"/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- MXNetCAPI.bs blib/arch/auto/AI/MXNetCAPI/MXNetCAPI.bs 644
rm -f blib/arch/auto/AI/MXNetCAPI/MXNetCAPI.so
x86_64-linux-gnu-gcc  -shared -L/usr/local/lib -fstack-protector-strong  mxnet_wrap.o  -o blib/arch/auto/AI/MXNetCAPI/MXNetCAPI.so  \
      \

x86_64-linux-gnu-gcc: error: mxnet_wrap.o: No such file or directory
x86_64-linux-gnu-gcc: fatal error: no input files
compilation terminated.
make: *** [Makefile:479: blib/arch/auto/AI/MXNetCAPI/MXNetCAPI.so] Error 1
FAIL
! Installing AI::MXNetCAPI failed. See /root/.cpanm/work/1586466130.25207/build.log for details. Retry with --force to force install it.

It doesn't seem solved yet.

I still get this error when I compile in Ubuntu 20.04.02

@navoj Try "apt install swig"


Rebrand and prepare documentation notebooks

I find the tutorial documentation so confusing? In part it's aimed at me preparing the tutorial, in part at participants, and in part referring to outdated things (.ipynb), downloading notebooks, etc. :sweat_smile:

I find the tutorial documentation so confusing? In part it's aimed at me preparing the tutorial, in part at participants, and in part referring to outdated things (.ipynb), downloading notebooks, etc. 😅

@lagru sorry about that, we probably should have given you more context about the source here, which is a workshop template so that people making workshops have all of the infra (jupyter book, gh-actions) set up already. But yeah, all of the instructions for instructors should be gone before we launch, and only the notebooks that we intend to use should remain. (I would remove the old ones rather than just remove them from the TOC.)
At any rate the book building on actions is broken right now... 😭 so we might not be getting all that much value out of the template. 😭
Immediately after this merge @lagru we should use jupytext to convert the relevant notebooks from the skimage tutorial to md and then commit those. But I think it's a good idea to do that in a follow-up PR.

At any rate the book building on actions is broken right now...

Oh? So we shouldn't try to fix our CI for this repo? Is there no way to circumvent that by replacing the action with manual instructions?

Ready from my side. @jni, if you want to do the honor? Otherwise I'll merge in a few hours from now.

Re https://github.com/scipy-2023-image-analysis/tutorial/pull/5#issuecomment-1617575032, at the worst we can maybe push our local build to the pages manually?

Sure! But I don't consider it a priority. The book/site is very valuable if you have a jupyter-lite built and they can run it online or whatever. But for an interactive tutorial, the most important thing is that they can download the repo and run some cool notebooks interactively with the class, and do the exercises. A fancy online website as an artifact at the end is cool but "icing on the cake," so to speak. First we should bake a cake! 😂


Add contributing guide

Updates #168.
/cc @KodrAus

I'm merging this as is, any improvements can be made later.


fix: stage format name

fix for #1911

Test Plan

[x ] acceptance tests

References
#1911

We will redesign the stage as part of https://github.com/Snowflake-Labs/terraform-provider-snowflake/blob/main/ROADMAP.md#preparing-essential-ga-objects-for-the-provider-v1. We will take this PR into consideration then.


Cursor jumps into floating window of function signature help

My testing minimal init.vim
call plug#begin('~/.vim/bundle')
    Plug 'neovim/nvim-lspconfig'
    Plug 'nvim-lua/completion-nvim'
call plug#end()
inoremap <expr> <Tab>   pumvisible() ? "\<C-n>" : "\<Tab>"
inoremap <expr> <S-Tab> pumvisible() ? "\<C-p>" : "\<S-Tab>"
lua require'lspconfig'.tsserver.setup{on_attach=require'completion'.on_attach}
au Filetype javascript setl omnifunc=v:lua.vim.lsp.omnifunc
set completeopt=menuone,noinsert,noselect

How to reproduce

Get the function signature help to pop up by typing some params in a function call site.
Sometimes cursor will window jump into the floating window. for me its >50% of the time so it makes function signature help unusable.
Can try to brute force trigger by holding , or holding delete on a long string of ,

Expected behavior
The cursor should not jump into the floating window of the function signature help.

Closing as this seems to be a neovim issue.

This is not a neovim issue, but a completion.nvim issue

I'm having the same issue


Pay for the exchange rates api

Would be $100 per year
We could perform more requests (currently 250/m are free, we request 2 a day per service ... so we would need to lower this, new limit would be 10k)
More recent exchange rate (free is daily, basic is hourly, so we could also try to fetch more often than twice a day)
https support

https://exchangeratesapi.io/pricing/ will allow us to have hourly updated prices. Should we reduce the cache duration of this information to 1 hour?
We will continue the free usage with staging. Meaning that https will only be able for production. We are ok with this?

This requires only a change in the env var EXCHANGE_API_BASE_URL to https://api.exchangeratesapi.io/latest. I left a comment in the next milestone to remind of that: https://github.com/gnosis/safe-client-gateway/milestone/17


[BUG] cog not signing commits with gitsign

cog not signing commits   when using  with gitsign

signing commits with normal commits works

This should work when #192 is merged. I plan to work on cocogitto again around september. Thanks for your patience :)

This is now in main branch and needs to be tested before releasing.
@xmlking If you wish you can install latest upstream with the following :
cargo install --git https://github.com/cocogitto/cocogitto

Just released  5.2.0. Signed commit should be considered unstable but i'd be glad to have your feedback.

Thank you very much @oknozor
Cog is helping my team do consistent commits , change logs and Version bumps.

I am getting the following error:

How to reproduce
brew install sigstore/tap/gitsign
cd /path/to/my/repository
git config --local commit.gpgsign true  # Sign all commits
git config --local tag.gpgsign true  # Sign all tags
git config --local gpg.x509.program gitsign  # Use gitsign for signing
git config --local gpg.format x509  # gitsign expects x509 args

My error message:
❯ cog commit feat "add one"
gpg: no default secret key: No secret key
gpg: signing failed: No secret key
Error: failed to sign commit

cause:

Seeing the same as @bdarcus with Cog 5.3.1

@bdarcus @cas-- I have this line which sets the default key ID in my ~/.gnupg/gpg.conf file which seems to be working for me:
default-key  MY_KEY_ID

You should be able to specify the key ID you have specified for user.signingkey in your global git configuration instead of MY_KEY_ID in the snippet above. Hope it helps.

Hey @xmlking, I finally had time to dive into this.
gitsign will be supported in the next release.


Readme updates

PR Description 📜
Fixed grammatical errors and reworded sentences for clarity. Added links to the website of games and discord for visibility.
Fixes # #2907
Completed Tasks:

[x ] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x ] I have performed a self-review of my own code or work.
[x ] My changes generates no new warnings.

Thank you @a-sommer ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Thank you  @a-sommer , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Break down mega-README into bite size articles under /docs

Description
The README has sort of just grown organically over time and I think its high time it gets broken down into more focused documents under something like a /docs folder. We can link to that folder form the README so the information is still easily discoverable, but keep the copy in the README a tighter narrative about what Fulcio does. The focus here would be leaning towards contributors primarily as the end-user documentation lives at https://docs.sigstore.dev which lives over here https://github.com/sigstore/sigstore-website.

Big +1 to this! For GitHub "SEO" it's usually good to have a small blurb/diagram/picture targeted to end-users "above the fold" in the README, but the rest of the end-user stuff should move to the docs website and this can stay contributor focused.

Yes absolutely!

Ok so first step is breaking down the README, then I'll start moving things around.

Readme is a lot more reasonable now. Closing this


User Story: SurveyResults displays users's style title and image

As a user in the survey results page, I should see the title and image of my calculated style


vulkaninfo: Meet extension version dependencies

Fixes error when VK_KHR_surface_protected_capabilities
is enabled with Vulkan 1.0

@charles-lunarg It will not be added, because driver that does not support the version must not report the extension.

Ah I had it backwards then. I had made a similar fix the other day in a unpublished branch were I used the solution above, because at the time I was hesitant to change the apiVersion in VkAplicationInfo. However thinking it through, using the version queried is a better solution overall, as you very rightly point out that on a 1.0 platform, that extension should not be reported.

Right. It should be mostly safe to use the queried version. Only things I can think of

From time to time, there might be contra-dependencies. So far only VK_AMD_negative_viewport I think.
Newer version disables implicit layers that do not support it. No harm done I think; they are either drivers, in which case they should be always updated, or they should not change the info anyway.
Malicious driver could report different info for different versions. More of a theoretical concern. And no harm done; we do not know anyway for which version the user wants to know the info.

Definitely worthwhile to think about the consequences, but none of those seem likely or needing to be handled. Negative viewport was obsoleted by the VK_KHR_maintenance1, disabling implicit layers shouldn't impact vulkaninfo due to it not enabling any layers in the first place (or rather, no behavior it reports should depend on implicit layers), and worrying about malicious drivers feels like the ultimate form of defensive coding.
Also, one of the vulkaininfo alterations made for the 1.2 release was for the autogen to support reporting the correct struct names depending on the version or available extensions. That should make sure we report the 'most' correct info possible.

obsoleted by the VK_KHR_maintenance1

Technically, "deprecated" which means the app must not try to enable it. Should be straightforward to handle, just needs to be kept in mind if Khronos decides to do more of those in future.

NVM, I see you already only enabling Swapchain and Device Group extensions on vkCreateDevice, so that is non-issue.

Now just waiting for CI to complete...


Make compatible with Django 1.8

In Django 1.8, DiscoverRunner.option_list is replaced with the classmethod DiscoverRunner.add_arguments()

Could someone consider merging this?

Yes, is this project still being maintained? This is a very straightforward compatibility change (maintaining backwards compatibility) and without it the app does not run in django 1.8.

@camilonova, if you don't have time to work on this anymore I'd be glad to get the contributor rights and maintain it.

@fdintino Thank you.
@charettes Thank you, please add yourself to jazzband and start right away. Welcome on board.

@camilonova just did, thanks!

@charettes will be great if you take a look into automated tests and readthedocs, for sure the integrations are outdated.

Will try to have a look today.


skpm install failed

skpm/node_modules/keytar/node_modules/.bin:/usr/local/lib/node_modules/skpm/node_modules/.bin:/usr/local/lib/node_modules/.bin:/Users/didi/CRClientTools/arcanist/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
6446 verbose lifecycle<EMAIL_ADDRESS>CWD: /usr/local/lib/node_modules/skpm/node_modules/keytar
6447 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'node-gyp rebuild' ]
6448 silly lifecycle<EMAIL_ADDRESS>Returned: code: 134  signal: null
6449 info lifecycle<EMAIL_ADDRESS>Failed to exec install script
6450 verbose unlock done using /Users/didi/.npm/_locks/staging-3a08f0df5026584d.lock for /usr/local/lib/node_modules/.staging
6451 verbose stack Error<EMAIL_ADDRESS>install: node-gyp rebuild
6451 verbose stack Exit status 134
6451 verbose stack     at EventEmitter. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:280:16)
6451 verbose stack     at emitTwo (events.js:106:13)
6451 verbose stack     at EventEmitter.emit (events.js:191:7)
6451 verbose stack     at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
6451 verbose stack     at emitTwo (events.js:106:13)
6451 verbose stack     at ChildProcess.emit (events.js:191:7)
6451 verbose stack     at maybeClose (internal/child_process.js:877:16)
6451 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
6452 verbose pkgid<EMAIL_ADDRESS>6453 verbose cwd /Users/didi
6454 verbose Darwin 17.0.0
6455 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "skpm"
6456 verbose node v6.9.1
6457 verbose npm  v5.5.1
6458 error code ELIFECYCLE
6459 error errno 134
6460 error<EMAIL_ADDRESS>install: node-gyp rebuild
6460 error Exit status 134
6461 error Failed at the<EMAIL_ADDRESS>install script.
6461 error This is probably not a problem with npm. There is likely additional logging output above.
6463 verbose exit [ 134, true ]

I install skpm failed,it report upon errors,i don't know how to resolve!

hum what version of node are you using? It's an issue about keytar if that helps

node version is v6.9.1,npm version is 5.5.1,Thank you!

Have same problem :( Node v: 8.9.0 NPM v: 5.5.1

install failed. above image is the npm error report.
Runtime: node -v9.2.0 npm -v5.5.1
Anyone can help? THKS

Same problem, node verion: v8.9.0
The issue happens after I upgraded my mac os system to High Sierra 10.13.2

You have to always make sure that x-code is installed and command line tools are enabled. I found that after installing, skpm installed properly.

Oh good catch. @zhixunqiu @nichenqin @danielwi can you make sure you have a command line tools installed (http://osxdaily.com/2014/02/12/install-command-line-tools-mac-os-x/)?
If it works afterwards, I'll add a not in the readme about it

@mathieudutour It works for me! But there is still error when I tried to install through npm, I successfully installed it through yarn

Cool, I added a note in the readme


chore: update theme

What :computer:

Update to latest theme

Why :hand:

Updates that occur in the theme template repo don't automatically get updated in the projects using it.
A build needs to occur to pull the latest changes from the template repo.

At some point the better process is to track this with a versioning process of downloading the template via NPM

Build is not correct 👇


ERROR: No matching distribution found for groundingdinoPlease read & provide the following

Instructions To Reproduce the 🐛 Bug:
When I want to get the environment installed, I meet the error:
ERROR: Could not find a version that satisfies the requirement groundingdino (from versions: none)
ERROR: No matching distribution found for groundingdino
how can I fix this

My problem turned out to be mentioned on installation guide for groundingdino.

Pip subprocess error: ERROR: Ignored the following versions that require a different python version: 1.2.0 Requires-Python >=3.9 ERROR: Could not find a version that satisfies the requirement groundingdino==0.1.0 (from versions: none) ERROR: No matching distribution found for groundingdino==0.1.0
I meet the same problem .
it seems  groundingdino version 0.1.0 not exists ?  and groundingdino  version 1.2.0 require python 3.9 ?

Branch: main
Commit: f4ca2960a97cb73aff2c459a9d0f06c7674452e4
ERROR: Ignored the following versions that require a different python version: 1.2.0 Requires-Python >=3.9 ERROR: Could not find a version that satisfies the requirement lang-sam==0.1.0 (from versions: none) ERROR: No matching distribution found for lang-sam==0.1.0
package lang-sam==0.1.0  not in pipy or conda-forge source  ?

I successfully installed it with the following command.
Installation:
1.Clone the GroundingDINO repository from GitHub.
git clone https://github.com/IDEA-Research/GroundingDINO.git
Change the current directory to the GroundingDINO folder.
cd GroundingDINO/
Install the required dependencies in the current directory.
pip install -e .

But In lang_sam.py file, I detect that the model = build_model(args) command of the load_model_hf function cannot be executed. why?thank you

You can try pip install nw-groundingdino, this works for me.

I also encounter the same issue. It seems that the conda env use python 3.8, but some of the required packages do not support python 3.8 anymore.


Support for @Health annotations

Includes support for security realms
NOTE: Requires https://github.com/wildfly-swarm/wildfly-swarm-spi/pull/1 to be merged first

Does the spi module.xml in /container need to be updated to have a dependency on jandex module? Now that the spi has a provided dependency for it?

Yes, the Map IDM is not needed anymore

@kenfinnigan please keep this on hold. I still need to tweak the authentication bits a little bit

No problem, wasn't planning to merge just yet

Cleaned up and squashed everything into one commit. From my point of view this is good to go. I'd suggest to move any further into dedicated branches (i.e. @kenfinnigan thoughts on the RuntimeDeployer)

My vote on merging this one: +1
@kenfinnigan ?

The latest commit fixes a typo and squashes everything into one again

Looks good :+1:

Just a quickie on RuntimeDeployer. Would we envisage that something like https://github.com/wildfly-swarm/wildfly-swarm-swagger/blob/master/adapter/runtime/src/main/java/org/wildfly/swarm/swagger/runtime/SwaggerConfiguration.java#L63 is replaced with using the index or not?

Looks like I broke the security with one of my latest commits. I'll need to enhance the test coverage for this and fix it, before we can move on.

Re: Swagger. Yes, that's one of the intended use cases.

Given that, we will need to prepare the index before calling prepareArchive() but also pass the index into that method, which is an SPI change.
Is there an alternative I haven't thought of?

@kenfinnigan we can still shuffle things around later, but I would suggest not to make all possible use cases (i.e. swagger) a pre-requisite for merging what we have so far.

Squashed everything again and fixed the JAXRSArquillianTest


0.8.x bug fixes sync

Some conflicts now exist. I updated shxparser to deal with the potential crashes. It shouldn't crash even if the files are gibberish now.


Re-design help templates

[x] Integrate extraDocs
[x] Re-design tables for arguments
[x] More information about arguments

Closed by #263. More information about the arguments will be solved by #264 and other issues...


Improve sorting of enum autocompletion

Closes godotengine/godot-proposals#7913
The enum constants will now appear before methods. Also they are sorted in their declaration order and not alphabetical.

can this be merged to 4.2 also

I don't see why this can't be cherrypicked for 4.2, yeah.

Thanks!

Cherry-picked for 4.2.2.


Feature/life tables

Adding meadow step for "Life Tables" by Human Mortality Database.

(Just a quick tip if you don't want to go nuts from walden conflicts - instead of adding files using e.g. git add -A :/ add them with git add -- . ':!vendor')


Bulk renaming script issue

I wrote a script for adding suffix\prefix to selected in CB assets, but it works strange- some part of the assets were renamed correctly, and for the other the names stayed the same.
I'm using source control ( Perforce), and before running the script i didn't CheckOut ( but this operation is automatic, when some changes are being made to asset). I've ran this script on ~10k texture assets, some were renamed correctly but some weren't, thought the uasset package name it seems was changed because i couldn't run this script again after reloading project - Error was somthing - asset with this name already exists.
I'm using rename_asset() because it renames also the uasset package what is very handy.
So why does this happened, does it source control fault, or maybe some old redirectors?
On another test project ( 200 materials without source control) rename asset() works as expected even without cleaning redirectors
import unreal_engine as ue

assets = ue.get_selected_assets()

suffics = '_T'
prefix = ''
loading_class = 'Texture2D'

for asset in assets:
		old_name = asset.get_name()

		full_name = asset.get_full_name()  #Type Path.Name of selected asset
		full_path = full_name.split(' ', 1)[1]  #clean full path with name
		asset_path = full_path.split('.', 1)[0]  #clean full path without name

		#loading asset into memory
		asset_class = ue.find_class(loading_class)
		load_selected_asset = ue.load_object(asset_class, asset_path)

		new_name = prefix + old_name + suffics

		#rename and save ( the package .uasset also will be renamed to amth the asset)
		ue.rename_asset(full_path, new_name)

		# asset.set_name(new_name)  #run if rename_ass bugsout

		asset.save_package()

Yeah, already tried this.

Creat new project ( no source control)
import this set of folders with textures (dnd the folder in to the CB window),
run script
The result in my case: some files were renamed, some were not ....
here are this folders with files to reproduse
https://drive.google.com/open?id=1oP5W-qmrr8biT0YidQo21Lr7ABZEszcm

Maybe some asset is incorrect and failing the whole process- becouse a this messege shows up - File name '_25' resolves to 'None' and cannot be used
Yeah, this was the issue. After this asset all files retained their original names

Did the script generated some kind of error ? it would be cool to signal this kind of issues

Yeah there was an error, sorry missed it in the middle of the night ))


Need some explaination

What is trailing names? Please give me some example. Thank you.

Chi tiết tài liệu
⚠ Không chỉnh sửa phần này. Điều này là bắt buộc cho docs.microsoft.com ➟ Vấn đề khi liên kết GitHub.

ID: 11269278-125b-a9b8-19eb-b52aa94d2389
Version Independent ID: 15369254-5b5e-75b0-0ef0-6015dde04648
Content: Bug Check 0xF9 DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN - Windows drivers
Content Source: windows-driver-docs-pr/debugger/bug-check-0xf9--driver-returned-status-reparse-for-volume-open.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @DOMARS
Microsoft Alias: domars

@zeltrax00 - I added additional links to this bug code to point to the related driver docs for IFS drivers including the design guide - File systems driver design guide and the IRP_MJ_CREATE - IRP_MJ_CREATE (IFS).
You may be able to use the debugger !irp extension to display information about an I/O request packet (IRP) in question.
For additional questions about working with file system drivers, the OSR forum is a great resource for developers. For example this thread discussed Status_Reparse.
https://community.osr.com/discussion/6623/status-reparse
Good luck in solving your stop code issue.


Don't drop .rb suffix for formula names

Fixes #1718

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

Thanks @vladshablinsky for the fix and @jasonkarns for the report (and apologies for overestimating the complexity and edge-cases here).

Thanks @vladshablinsky!! And no worries @MikeMcQuaid. I don't begrudge your maintainership (and thank you!)


Get a dev job up and running

The Jenkins job should sync with the dev-owi.usgs.gov-website S3 bucket for now. It should be viewable at dev-owi.usgs.gov-website.s3-website-us-west-2.amazonaws.com/vizlab/water-use-15
In a couple of weeks we will be switching to the S3 bucket named dev-owi.usgs.gov, but that has to wait on an RFC.

@wdwatkins this is done, right? How long did it take?

Yes.  5 hours was probably about right, although it shouldn't normally take that long if we aren't introducing new system dependencies that have to be installed.


deferred data returning a DeferredData object with useLoaderData

What version of Remix are you using?
1.11.1
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce
I haven't been able to reproduce it with fresh boilerplate.
I am using a custom express server with the remix adapter instead of the built-in remix dev server. The route handler is exactly as done in the boiler plates and in the documentation.
EDIT: Here's a discord thread that was created by someone who's facing the same issue as me https://discord.com/channels/770287896669978684/1071639409100857384/1071639409100857384.
Expected Behavior
Expected useLoaderData to work the same way when defer isn't used.
Actual Behavior
useLoaderData returns the DeferredData object type.
This is the output of console.log(useLoaderData()):
DeferredData {
  pendingKeysSet: Set(0) {},
  subscribers: Set(0) {},
  deferredKeys: [],
  abortPromise: Promise { <pending> },
  controller: AbortController { signal: AbortSignal { aborted: false } },
  unlistenAbortSignal: [Function (anonymous)],
  data: { // The data is nested in here
    modules: [
      [Object], [Object],
      [Object], [Object],
      [Object], [Object],
      [Object], [Object],
      [Object], [Object],
      [Object], [Object]
    ]
  },
  init: {}
}

Just to be clear, you can't expect to pass a promise without defer({}) and have it work?
This is the expected behaviour when you return a promise in json(), you just won't be able to get the resolved value once it's complete
You might need to explain a little more if this isn't what you are doing

Just to be clear, you can't expect to pass a promise without defer({}) and have it work?
This is the expected behaviour when you return a promise in json(), you just won't be able to get the resolved value once it's complete
You might need to explain a little more if this isn't what you are doing

A code example will probably clear this up. I've done it several different ways and the result is always the same.
export const loader = async () => {
  return defer({
    foo: await getFoo(),
    bar: getFoo()
  });
}

I've attempted it with all promises resolved (so, nothing deferred) and with no promises resolved (all data deferred).

Updated original post with a link to discord of another user facing the same issue. https://discord.com/channels/770287896669978684/1071639409100857384/1071639409100857384

I had a similar problem and it was because one of my packages @remix-run wasn't updated in package.json
specifically for me, it was "@remix-run/dev": "1.12.0"
make sure all your remix packages are on the same version that support defer a.k.a ^1.11.1

I had a similar problem and it was because one of my packages @remix-run wasn't updated in package.json
specifically for me, it was "@remix-run/dev": "1.12.0"
make sure all your remix packages are on the same version that support defer a.k.a ^1.11.1

That was my initial suspicion, but, all my dependencies are on the same version (^1.12.0).


Inconsistent behavior when disabling future dates after selecting a date

Describe the bug
When attempting to disable future dates, the functionality works properly until a date is selected. After selecting a date, the disabled dates are no longer functioning as expected.
To Reproduce
Steps to reproduce the behavior:

Navigate to the date picker functionality.
Disable all future dates.
Select a date from the date picker.
Attempt to select a future date

Expected behavior
The functionality should consistently disable all dates beyond the selected date, maintaining the initial restriction on future dates.
Screenshots

Desktop & mobile (please complete the following information):

Browser: Chrome
Library version: 1.6.1

Hey,
Kindly asking if there are any chances this can be fixed in the next releases?
Love the component, but this issue is a blocker for the production usage.
Many thanks in advance!

Hey, I dug into the code and found something called disableInRange. It's not in the docs, but adding it to the component did the trick.

i describe this bug here https://github.com/elreco/vue-tailwind-datepicker/issues/114#issuecomment-1962407529

Hey, I dug into the code and found something called disableInRange. It's not in the docs, but adding it to the component did the trick.

i confirm this is working


expect null as zero

i got an js error like:

Uncaught TypeError: Cannot read property 'toString' of null

use like this numeral("").divide(100)
so how can i set the value as 0 when is null like
numeral("")
numeral(null)

Hi,
I have added this on pr #781


Biosample sample characteristics

This PR addresses the need for a different structure and naming of the Biosample.disease attribute:

there has been consensus in the metadata task team that an attribute name of disease is misleading in the context of Biosample and should be reserved for the individual object level
a Biosample can use a number of ontologies, e.g. for patho-histology, anatomic location, tissue type ...; see also the discussion at https://github.com/ga4gh/schemas/issues/707

The renaming to sample_characteristics is in line with the use e.g. at GEO; however, the sample_ prefix may not be strictly necessary. Alternatives welcome.

This makes sense to have a tag-bag field that strictly represents Ontology Terms, although the semantic context of those terms can be lost if no name is provided.
Please also consider the approach of allowing tagging via Ontology Term (and others) in a generic attributes field by upgrading the info field. This would allow a data curator to define named tag bags on a biosample with some more context without adding new named fields to the message. This replaces the info field and both approaches are not exclusive. PR for this feature here.
I'm +1 for this approach as it solves the immediate issue of specifying tissue type for TCGA data.

Closed & moved to https://github.com/ga4gh/schemas/issues/711 (clean up).


Click closes the wrong open editor

Type: Bug
In VSCode OSX "Open Editors" sidebar clicking on a close button closes the selected tab, not the one you click on ... i.e. the wrong tab is closed
VS Code version: Code 1.82.2 (Universal) (abd2f3db4bdb28f9e95536dfa84d8479f1eb312d, 2023-09-14T05:59:47.790Z)
OS version: Darwin x64 22.6.0
Modes:
Remote OS version: Linux x64 5.15.49-linuxkit-pr

/duplicate of #193574

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Unable to correct problems, you have held broken packages.

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/MinaProtocol/mina/issues
[X] This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/MinaProtocol/mina/discussions

Description
cryptofather@Minerrig:~$ sudo apt-get install -y curl unzip mina-mainnet=1.2.2-feee67c
Reading package lists... Done
Building dependency tree
Reading state information... Done
unzip is already the newest version (6.0-25ubuntu1).
unzip set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
mina-mainnet : Depends: libffi6 but it is not installable
Depends: libjemalloc1 but it is not installable
E: Unable to correct problems, you have held broken packages.
Steps to Reproduce
follow installment instructions provided : https://docs.minaprotocol.com/en/getting-started
Expected Result
i assume mina should have been installed and ready to go
Actual Result
the above pasted problem:
cryptofather@Minerrig:~$ sudo apt-get install -y curl unzip mina-mainnet=1.2.2-feee67c
Reading package lists... Done
Building dependency tree
Reading state information... Done
unzip is already the newest version (6.0-25ubuntu1).
unzip set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
mina-mainnet : Depends: libffi6 but it is not installable
Depends: libjemalloc1 but it is not installable
E: Unable to correct problems, you have held broken packages.
How frequently do you see this issue?
Always
What is the impact of this issue on your ability to run a node?
Blocker
Status
cryptofather@Minerrig:~$ mina client status
mina aborted!
Don't know how to build task 'client' (See the list of available tasks with `mina --tasks`)
/usr/bin/mina:53:in `block (2 levels) in <main>'
/usr/bin/mina:26:in `block in <main>'
/usr/bin/mina:25:in `instance_eval'
/usr/bin/mina:25:in `<main>'
(See full trace by running task with --trace)

Additional information
No response

Hey @mediumjack1 please try it with the version described in updated docs here. It works on Ubuntu 18.04 / Debian 9


Problems with Diarization - Rest API

Hello Guys!
I'm implementing Speech-to-text in an app. But I'm facing some problems with some audio files.
What I'm trying to do is create a transcription and get the Speech as Text, with the "speakers" differentiation.  But the response only appear "Speaker":  1. The audio file is a conversation between two people. Nothing extraordinary.
The file is: https://drive.google.com/file/d/15saVNxnlZ8chSs07ggkgKUptmgW6284m/view?usp=sharing
The request body is:
{   "contentUrls": [     "****"   ],   "properties": {     "diarizationEnabled": true,     "wordLevelTimestampsEnabled": true,     "punctuationMode": "Automatic",     "profanityFilterMode": "masked"   },   "locale": "pt-BR",   "displayName": "Esta é uma transcrição de teste" }
A good observation is: I've tried with another audio with < 30 seconds and get the same problem.
Thank you!!

@murilomendes , we have a new set of diarization models that should address this issue (will be in public preview some time by February). Currently they are in private preview only, you can ping me directly at eldak at microsoft.com if you want to have early access. Thanks!

@murilomendes Did you try early access to new models and if yes, did they work better?
@eldakms Is the public preview of new models still due in Feb? Is there any work item or doc page that we could track for status?

@eldakms Please update with status.

Closing the item since no more updates from either side. Please open a new issue if more support is needed.


Performance issue Find with more than 500 records

Steps to reproduce
When calling find action with a resulting dataset of more than 500 records, it takes 15 seconds to update the store.
Expected behavior
Faster store update
Actual behavior
takes 15 sec.
System configuration
Tell us about the applicable parts of your setup.
Module versions (especially the part that's not working): "@feathersjs/vuex": "^4.0.1-pre.16",
NodeJS version: v14.16.1
Operating System: Ubuntu
Browser Version: chrome
I traced it to the addItems function in service-module-mutations
I think these statements are causing the performance issue.
state.ids.push(id);
state.keyedById[id] = item;
Somehow it takes a lot of time, maybe because of vue/vuex reactivity.  Don't know exactly why.
A possible solution hereunder takes it to less then a second:
function addItems(state, items) {
       const keyedById = {}
       const stateIds = []
       const { serverAlias, idField, tempIdField, modelName } = state;
       const Model = _get(models, [serverAlias, modelName]);
       const BaseModel = _get(models, [serverAlias, 'BaseModel']);
       for (let item of items) {
           console.log ("item " + item._id)
           const id = getId(item, idField);
           const isTemp = id === null || id === undefined;
           // If the response contains a real id, remove isTemp
           if (id != null) {
               delete item.__isTemp;
           }
           if (Model && !(item instanceof BaseModel) && !(item instanceof Model)) {
               item = new Model(item, { commit: false });
           }
           if (isTemp) {
               let tempId = item[tempIdField];
               if (tempId == null) {
                   tempId = assignTempId(state, item);
               }
               item.__isTemp = true;
               state.tempsById[tempId] = item;
           }
           else {
               // Only add the id if it's not already in the `ids` list.
               if (!state.ids.includes(id) && !stateIds.includes(id)) {
                   stateIds.push(id)
                   //state.ids.push(id);
               }
               keyedById[id]=item
               //state.keyedById[id] = item;

           }

       }
       state.keyedById = {...state.keyedById,...keyedById}
       state.ids = state.ids.concat(stateIds)

   }

This is interesting, could you verify that the items added to the store this way are still reactive ?
I'll send a PR with the fix and it might be good idea to add a benchmark, to see the perf improvement.
What do tou think @marshallswain ?

I'm surprised that it's still doing mutations one at a time.  I thought we addressed that.  If not then we definitely need to get this in place.  Thanks for the catch.

@marshallswain I think we talked about it bu never realy implemented it.
It should stay reactive as the keyedById and ids properties are reassigned instead of adding properties on them.

When I add a new record via Postman, I see it appearing on my frontend
So it is still e2e reactive.

The only thing is that when adding or updating one record it is less optimal now (for javascript), but is not noticable.
I wonder if completely re-assigning state.keyedById triggers more reactive updates compared to adding one extra property.

I don't know why the spread is faster than the Object.assign.

Spread has been optimized in browser engines and should be at least as fast as Object.assign

The only thing is that when adding or updating one record it is less optimal now , but is not noticeable.

A workaround could be to detect if there is only one item in the response and update the state accordingly.

I do wonder if completely re-assigning state.keyedById triggers more reactive updates compared to adding only one new property.

This is a possibility, it depends if Vue is smart enough to detect that the items didn't change but if not, it might trigger components re-rendering.

UPDATE -> not a good solution, because it kills reactivity

I think we should apply the same logic for the updateItems mutation, once the new item has been merged with the original one, store it in a keyedByIds object and then reassign the state.keyedByIds state ptoperty, like in the addItems.
Same logic can be applied to the removeItems mutation too.

We could also squeeze a bit more performance when checking for existing items.
We could check if the id has an item in the keyedByIds object instead of using includes on the ids Array, unless there is a case where an item it's in the ids array but not in keyedByIds @marshallswain ?

You are correct. That would be a good improvement, although I believe
chromium internally optimizes that code to use a map, I’ve not read
anything like that about other browsers.
On August 12, 2021, GitHub @.***> wrote:

We could also squeeze a bit more performance when checking for
existing items.
 We could check if the id has an item in the keyedByIds object instead
of using includes on the ids Array, unless there is a case where an
item it's in the ids array but not in keyedByIds @marshallswain
https://github.com/marshallswain ?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/feathersjs-ecosystem/feathers-
vuex/issues/609#issuecomment-897677435>, or unsubscribe
<https://github.com/notifications/unsubscribe-
auth/AAA7OWPPXUON7SKDLFYELZDT4PJULANCNFSM5B6KMSBQ>.

That would be a good improvement, although I believe
chromium internally optimizes that code to use a map, I’ve not read
anything like that about other browsers.

I knew that Sets ans Maps used a hash map internally in V8 but I was not aware of this being the case for Arrays and I didn't find anything on that...

So it might improve everywhere.  Let’s do it
On August 12, 2021, GitHub @.***> wrote:

That would be a good improvement, although I believe
 chromium internally optimizes that code to use a map, I’ve not read
 anything like that about other browsers.

I knew that Sets ans Maps used a hash map internally in V8 but I was
not aware of this being the case for Arrays and I didn't find anything
on that...

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/feathersjs-ecosystem/feathers-
vuex/issues/609#issuecomment-897700012>, or unsubscribe
<https://github.com/notifications/unsubscribe-
auth/AAA7OWJ5EIYHNREWY6PJTRDT4PM4BANCNFSM5B6KMSBQ>.

There is one problem, the tests  it('correctly emits events for new... fails if we don't use the updateOriginal method.
This is because the tests watch a property that is undefined and that is added after the watcher has been setup.
But this is because the properties added has not been initialized.
I have always initialized my items properties because if some properties are manually added without the Vue.set method, it doesn't works either (e.g. in forms input)
So there is 2 workaround for this:

Define properties in advance.
For the watch api, watch the whole item instead of the property with the deep: true option

I think we could propose a different behavior as it is due to how Vue 2 reactivity works.
Vue 2 can't detect if new properties are added if it's not done with Vue.set that add all the reactivity stuff.
Iterating on all the properties of all the items added is hurting performance and is only needed in Vue 2 as Vue 3 Proxies handle property addition.
And for the updateOriginal function to handle nested properties it should iterate the items recursively.
But the one big disadvantage is when you don't know all the properties of the items you receive in advance, you can't predefine them and you loose reactivity on updates.
So it could be an option, maybe off by default, in order to not introduce breaking change, that could be turned on globally or per service which would not use the updateOriginal for the updateItems mutation.
Are you ok with that @marshallswain ?

+1. I've also performance issues on slow machines.
The solution sounds nice! Your code is for vue3, right?

I do wonder if completely re-assigning state.keyedById triggers more reactive updates compared to adding only one new property.

I also wonder if that would make a difference for vue2: Vue.set(state, 'keyedById', {...state.keyedById,...keyedById}).

The only thing is that when adding or updating one record it is less optimal now , but is not noticable.

We definitely should add performance tests for that with 1k items or something. We could also catch if it's just one item.

Any idea when this can be solved?

I've been on vacation in the mean time.
I'll try to look into it in the next days but we need to agree on the way we handle this, as mentioned in my last comment


GET http://<IP_ADDRESS>:8080/undefined net::ERR_TOO_MANY_REDIRECTS

I tested the app with my own firebase credentials and whenever I click on the new link(shortened), it always gives the following error in the console-
GET http://<IP_ADDRESS>:8080/undefined net::ERR_TOO_MANY_REDIRECTS
and the URL automatically changes to <IP_ADDRESS>:8080/undefined.
Did you face any such issue, or do you have any solution to it?

Hey @shreyansh26 I have resolved this issue and updated the repository.
Thanks!


feat: adds python27-flask-buildtools template with build tool support

I'm not sure if you want to maintain this variant? I used it for a function that needed pycrypto, which needs a c complier to install. I expect it will be generally useful.

Unfortunately it is a little less than DRY, as it copies everything except the Dockerfile. Perhaps it would be nice to have the ability of one template to extend another -- by being copied into same place, say.

I realize this is a zombie PR, but the need for additional build-tools might be addressed with the addition of the debian based templates.  There aren't debian based templates for python27, but those could be done instead of this PR. @alexellis WDYT?

Python 2.7 is EOL, it is no longer supported by the PSF. https://www.python.org/doc/sunset-python-2/
Can you elaborate on what these build tools are? I see that no issue was raised as per the contribution guide to explain what this change is, why it's needed and what it does?

Closing, feel free to raise an issue with what you need.


Fix issues obtaining the JWT

Couple things have broken/changed on SC's end.

LoginComplete now 500s on a null being sent as the ReturnUrl. Send a valid value.
LoginComplete now returns a 302 on success. Cookies are only returned by aiohttp for the last request that was followed, so we need to disable following redirects.

I confirmed that error handling for invalid username/password still works as expected.
Resolves https://github.com/Southern-Company-HA/southern-company-hacs/issues/80
cc @Lash-L @dcsim0n

Thanks @rixth I'll try this out sometime tomorrow!

From a quick test - it seems to run, thanks!
Can you change all of the instances of 200 in the tests to 302? Otherwise it wont output a release

@rixth, let me know if you can't get around to finishing the PR, I can try and jump in.

@Lash-L good to go!

Thank you @rixth

@rixth If you have time, please investigate it still not working properly on the hacs integration. I have not done much with it, but I did bump the version and do some other 'chores' on the repo

Please ignore - I should have it fixed in the latest update


Reformat with black

OK by you @martindurant?

Sure, why not - seems to be getting everywhere

Closed by #194


Object reference not set to an instance of an object notification.

When I open playnite I always get a notification saying "Object reference not set to an instance of an object."
The program seems to run correctly other than that so not really sure why it is happening. I took a playnite backup and restored on a different OS which is where I am getting this error so maybe that is why it is happening?
Either way I have added the logs that are created when I click on the notification in the hopes it will help figure out the issue.
I have also tried uninstalling and reinstalling the extension but it continued to happen after that too.
Thanks for looking into it!
extensions.log
playnite.log

https://github.com/Lacro59/playnite-plugincommon/commit/796c76a0d576453cad3f641242b35b6c826cb065

I have the same issue i don't know that to do...


I forced updated the theme for 19.20 beta and now it shows a blank white page!

There must be a bug on this latest issue i just updated it and got a blank white page with nothing on it. How can I fix this?! Please help!

Any possible workaround from the shell would help!

Hi,
Here is what'll do for the next release. I will stop showing update notice for releases  that have incompatibly issue.
To work-around the problem, go to the theme directory and run:
./theme-update.sh -release

isn't it better to wait for the Webmin update? I know that's slow...eg. here on CentOS (don't know why) but maybe worth the wait...
or also, could Jamie or you create a beta update by click instead of that manual command?
Thanks 👍

We're actually in sync with Jamie. But I have to go first, as he includes the theme into the main package and not visa versa.
I will make a patch tonight/tomorrow to make sure that notifications for new releases are not shown, in case there is incompatibly issue.

I don't see a themes directory in my /usr/share/webmin or is it somewhere else? I just confused why there isn't a directory called themes anywhere!

Ops! found it as the name of the authentic-theme. shouldn't webmin make it so it is as separate in a directory for all themes like all usual software does?! a bit confusing thou!


Magritte: descriptions should keep defining methods

We can see where field descriptions are defined:

Same for actions:


Bug Fixes

What's New?

Fix bug where inputs would blur when state is broadcast.
Fix bug where phantom FarmEvents would appear on the calendar.

Coverage decreased (-0.07%) to 81.255% when pulling c6aa3407454e2275c16c82ff739b9df900ea8506 on RickCarlino:dropdown_bug into 2d00cca23a0337b5b4dc44b9512017d00c3707ca on FarmBot:staging.

Coverage decreased (-0.1%) to 81.202% when pulling 74629b1b033b2f6a13859f82f2acacb8260b079f on RickCarlino:dropdown_bug into 2d00cca23a0337b5b4dc44b9512017d00c3707ca on FarmBot:staging.


[2024-11-25] - Sync main with main-apache

I had to do it manually this time duo to the high number of commits.

PLEASE DO NOT SQUASH MERGE.


Bugfix/unr 3405 unrealed workflow problem

Description
Fixed a bug where enabling autogenerate config to run a Load Balanced PIE deployment, then later disabling it, results in deployments still having multiple servers.
Release note
Added a bugfix note to changelog.md.
Tests
Verified the problem described no longer occurs with this change.
STRONGLY SUGGESTED: How can this be verified by QA?
Follow the repro steps on UNR-3405 and observe the problem no longer happens.
Documentation
Release note.
Primary reviewers
If your change will take a long time to review, you can name at most two primary reviewers who are ultimately responsible for reviewing this request. @ mention them.

Closing as Nic has fixed this here:
https://github.com/spatialos/UnrealGDK/commit/886575342179f019eef3375ad5f52f1b284af8f3


[TRACKING] End-to-End Test Contribution Proposal

Motivation
As consumers of libs, we have developed a comprehensive set of end-to-end tests that have proven valuable in ensuring the reliability and functionality of falcosecurity/libs, particularly in conjunction with various drivers. Recognizing the benefits of community collaboration, we aim to upstream these tests to the falcosecurity/libs repository.
Feature
We propose the contribution of a set of private end-to-end tests specifically designed to validate the behaviour of libsinsp together with the associated drivers. These tests aim to cover critical scenarios, ensuring that the library performs optimally in various environments.
Additional Context
The proposed end-to-end tests cover a spectrum of scenarios, including but not limited to:

Interaction of libsinsp with various drivers.
Comprehensive coverage of edge cases and error scenarios.

These tests cover various areas of libsinsp interest, like:

[x] processes
[x] syscalls
[x] cgroups
[ ] container runtimes
[x] networking

To facilitate this process, we are creating this tracking issue to serve as a central point for discussion and coordination with the maintainers of falcosecurity/libs.

Amazing @therealbobo, thanks for taking the lead on tracking this!
Re container runtimes cross-linking to https://github.com/falcosecurity/libs/issues/1298. Looking forward to seeing e2e tests expansions!

/assign

@therealbobo what's the status of this one? Can you update the body?
Anyway, moving to 0.17.0 because the effort is not over yet!
/milestone 0.17.0

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

what is missing here @therealbobo ?

There's only a PR left (which is already open) but I was asked to fix the flaky tests first. I looked into them but didn't find a solution yet.

I don't think we will make it for 0.18, let's move this to 0.19!
/milestone 0.19.0

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

This last PR https://github.com/falcosecurity/libs/pull/1958 ends this contribution. :)


ValueError: size of reduced grid does not match number of data values

hi,
running the following for a specific ECMWF forecast data file:
    for grb in grbs:
        print(grb)
        print(grb.gridType)
        print(grb.gaussianGridName)
        print(grb.values)

I'm getting the following output and traceback:
1:Sea ice area fraction:(0 - 1) (instant):reduced_gg:surface:level 0:fcst time 4 hrs:from<PHONE_NUMBER>00
reduced_gg
O1280

Traceback (most recent call last):
  File "/home/srepmub/s4l2-processors-st/modeldata/plot_ecmwf.py", line 17, in <module>
    print(grb.values)
  File "src/pygrib/_pygrib.pyx", line 766, in pygrib._pygrib.gribmessage.__getattr__
  File "src/pygrib/_pygrib.pyx", line 1172, in pygrib._pygrib.gribmessage.__getitem__
  File "src/pygrib/_pygrib.pyx", line 1279, in pygrib._pygrib.gribmessage._reshape_mask
  File "src/pygrib/_pygrib.pyx", line 32, in pygrib._pygrib._redtoreg
ValueError: size of reduced grid does not match number of data values

when using the eccodes bindings directly, I can get 'values' out no problem.
could this be an indication there is something wrong with the data file, or of a bug in pygrib..?

oooh.. using grb.expand_grid(False) avoids the issue. perhaps the valueerror could hint a bit at this? (TBH I haven't even checked the documentation, so possibly just my bad..)


Better error handling for errors caused due to hallucinations.

Hallucination in AI refers to the generation of outputs that may sound plausible but are either factually incorrect or unrelated to the given context. It may assume file paths and commands that do not exist. So we need better error handling mechanism for this.

Example: It never created such file but assumed that it did


The New SeqView foundation

Do this in the develop branch in current location for SeqView class (i.e. core.sequence).
An abstract base class foundation for the different types of view. Core attributes for SliceRecordABC are.
("start", "stop", "step", "_offset", "_seq_len")

Needs the following as concrete methods:

[x] absolute_position
[x] relative_position
[x] ALL methods involved with __getitem__

[x]  __getitem__
[x] all related methods

Needs concrete properties for:

[x] is_reversed (just renaming the reverse property)
[x] parent_start
[x] parent_stop

All attributes beginning with _ need a corresponding concrete setter / getter properties without the _.

[x] _offset setter and getter
[x] _seq_len setter only at this point

Misc:

[x] ensure wording in docstring remains consistent with the abstraction
[ ] abstract methods for value...?

Updating current SeqView
Inherits from SliceRecordABC, deleting methods that are in the ABC but retaining special attributes and methods.
This issue is finished when all current tests pass!

@GavinHuttley
In SeqView we do not provide a setter for _len_seq, instead relying on setting the length,self._seq_len = seq_len or len(self.seq), in the constructor.
Do we want to provide a setter in the ABC, or only allow _seq_len to be set in the constructor of inheriting classes?

@GavinHuttley in SeqView should I deprecate the reverse property (change it to calling self.is_reversed and add the deprecation warning, changing other internal usages to self.is_reversed )
or just remove it and change all internal usages?

@GavinHuttley in SeqView should I deprecate the reverse property (it callsself.is_reversed and decorate with the deprecation warning, changing other internal usages to self.is_reversed )
or just remove it and change all internal usages?

just remove and replace all internal usage

I've noticed that cogent3.core.location.Span uses reverse in the same way. Should we change it (for consistency?)

@GavinHuttley  __getitem__ and related methods (as they are currently used in SeqView) require all the arguments to construct another instance. This includes attributes like seqid, which we do not require for inheriting classes.
I started hacking this by having SeqView.__getitem__ call super().__getitem__ and provide the seqid, and then in the ABC a pass on the kwargs.
    def __getitem__(self, segment, **kwargs):
        if _is_int(segment):
            start, stop, step = self._get_index(segment)
            return self.__class__(
                self.seq,
                start=start,
                stop=stop,
                step=step,
                offset=self.offset,
                seq_len=self.seq_len,
                **kwargs,
            )

However, a better solution might be to not implement __getitem__ in the ABC. Instead, move the logic into something like a _get_start_stop_step function, which then returns those attributes, and the inheriting class is responsible for implementing a __getitem__ which populates an instance with all required attributes.

@GavinHuttley question above about design choices for the __getitem__ method in the base class. Since it return a new instance, and this might have different arguments in the inheriting class - what is the best way to approach this?

@GavinHuttley with this approach, we will need to ensure that all subclasses have a positional argument self.seq. This makes me think it might be better to be called data


Concordance scripts for ADAM/GATK pipeline

We chatted about this a while back, but didn't assign this to anyone. We're close to the point where we'll need to evaluate concordance between ADAM and GATK VCFs, as well as GRCh38 vs. HG19. I think there are two items here:

[ ] Code for lifting GRCh38 VCFs to HG19 (or vice versa, but I've chosen GRCh38 -> HG19 since GIAB data is HG19)
[ ] Code for performing concordance evaluation between four VCFs (HG19/GRCh38 on one axis, ADAM/GATK on second axis)

I've tagged @heuermh as the owner for this, but @heuermh please split this task with either @jpdna or @almussel as is needed.

Also, here is @beaunorgeot's old concordance code.

@heuermh What is the status of this ticket?

Needs to be refactored after library code was added, will update it this week.


executeCallbacks() loop error

I kept getting an error saying "Cannot read property 'execute' of undefined" until I changed this line:
for (var i = 0, length = taskCallbacks.length; i < length; i++)
int this:
for (var i = 0; i < taskCallbacks.length; i++)
In Abstract.prototype.executeCallbacks, /dist/task-runner.js, line 261
Please look into this.

Need repro steps. This looks like insufficient info.


node_modules installation error

Describe the bug
During the setup im getting this error

How to Reproduce
clone the repo and npm install

Screenshots
Link to GitHub repository with project that has issues
Files that can help reproduce the issue, like your AsyncAPI file, either paste inside the issue in a code block or in a sharable gist

Expected behavior
Should install all the dependencies

Is it because of my node version or any dependency issue??

I'm on node 16.13 and npm 8.1 and fresh installation works like a charm. What version or node and npm you're using?

I'm on node 16.13 and npm 8.1 and fresh installation works like a charm. What version or node and npm you're using?

I was using 18.17 then i used 20 using nvm and now back to 18.17 and it works fine dont know why!! Just engineer things :laughing:


postnet parameters

I noticed that the postnet filter size is 32, which makes the output have different shapes than the input. Also, the dropout rate is so high that it's not learning anything meaningful. Is that supposed to be like this?

@capavrulus I strictly following paper details here, although you can change dropout here as it's not mentioned in paper explicitly.

I have the same issue that after each layer of Postnet, the sequence length decrease, this lead to the y_g_hat have difference size and miss match with the ground truth ones.

hello @v-nhandt21, did you change the padding in every layer of the postnet model from padding=(n_filts - 1) // 2, to padding=same ?
Thank you

hello @v-nhandt21, did you change the padding in every layer of the postnet model from padding=(n_filts - 1) // 2, to padding=same ? Thank you

Hi, bro:
Have you tried this successfully? I also encountered the same problem, the dimensions are not correct

@SupreethRao99 @velonica0  I can not remember exactly what I have done with my code, I have cleaned it
But you can check the padding in this ConvNorm class:
https://www.tutorialexample.com/keeping-the-shape-of-input-and-output-same-in-pytorch-conv1d-pytorch-tutorial/

we could try this to keep the same shape:
https://pytorch.org/docs/stable/generated/torch.nn.Conv1d.html

hello @v-nhandt21, did you change the padding in every layer of the postnet model from padding=(n_filts - 1) // 2, to padding=same ? Thank you

Hi, bro:
Have you tried this successfully? I also encountered the same problem, the dimensions are not correct

Yes , I think i was able to get past the issue , but the model performance was horrible to say the least even after training with the full dataset on multiple GPU's for the full 1Million training steps , the models performance didn't improve, which is why I moved on

@SupreethRao99 @velonica0  I can not remember exactly what I have done with my code, I have cleaned it
But you can check the padding in this ConvNorm class:
https://www.tutorialexample.com/keeping-the-shape-of-input-and-output-same-in-pytorch-conv1d-pytorch-tutorial/

we could try this to keep the same shape:
https://pytorch.org/docs/stable/generated/torch.nn.Conv1d.html

Hi, thanks. I resorted to using 'padding = same' to overcome the issue in PyTorch 1.12

@v-nhandt21 @SupreethRao99
Thank you for your help. I now use my own Raman spectrum data to train for one million steps, and the Gen Loss Total is 4.7. How can I reduce the loss?
In addition, is there any related paper code that uses GAN for one-dimensional data denoising or restoration? I want to learn it, thank you very much.


07/09/2018 03:53 : Create Pull Request for branch master -> prTesting1_2018070903

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.