Not implemented stop reason (assuming exception): watchpoint-trigger

Using GDB 10.1, stepping and printing values works in general.
When I add a watch like the following *(char(*)[8])(0x7fd9166daa8a) I can directly see its current value and also see the value when GDB halts. But it seems to be more of a monitor as it does not stop when the variable changes. This may also be the reason
When I use the debugging console to manually add it watch *(char(*)[8])(0x7fd9166daa8a) then the program does stop as expected and also shows the old and new variant (as expected); but there is a notification and error message, which is bad.
Please catch the event and gracefully stop + update the value in the watch pane (or add it to the watch if it isn't included already).

Obviously there are more watchpoint related triggers:
  "watchpoint-trigger",
  "read-watchpoint-trigger",
  "access-watchpoint-trigger",
  "watchpoint-scope",

That should be added to the current list in the backend:
https://github.com/WebFreak001/code-debug/blob/c024e2cb0e942db259f8fda7e8ba5bf8e97c195d/src/backend/mi2/mi2.ts#L346-L365


COMP: UnaryFunctorImageFilter RLEImage support on Apple Clang

With:
❯ c++ --version
Apple clang version 15.0.0 (clang-15<IP_ADDRESS>)
Target: arm64-apple-darwin23.3.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
Addresses:
/Users/matt.mccormick/src/RLETest/RLEIteratorTest.cxx:15:35: error: no viable constructor or deduction guide for deduction of template arguments of 'ImageScanlineConstIterator'
  itk::ImageScanlineConstIterator it2(constRLE, constRLE->GetLargestPossibleRegion());
                                  ^
/Users/matt.mccormick/src/ITK/Modules/Core/Common/include/itkImageScanlineConstIterator.h:106:3: note: candidate template ignored: substitution failure [with TImage = itk::RLEImage<short>]: cannot reference member of primary template because deduced class template specialization 'ImageScanlineConstIterator<itk::RLEImage<short, 3, unsigned short>>' is instantiated from a partial specialization
  ImageScanlineConstIterator(const TImage * ptr, const RegionType & region)
  ^                                                    ~~~~~~~~~~
/Users/matt.mccormick/src/ITK/Modules/Core/Common/include/itkImageScanlineConstIterator.h:267:1: note: candidate template ignored: could not match 'SmartPointer<TImage>' against 'const itk::RLEImage<short, 3> *'
ImageScanlineConstIterator(SmartPointer<TImage>, const typename TImage::RegionType &)
^
/Users/matt.mccormick/src/ITK/Modules/Core/Common/include/itkImageScanlineConstIterator.h:119:3: note: candidate function template not viable: requires single argument 'it', but 2 arguments were provided
  ImageScanlineConstIterator(const ImageIterator<TImage> & it)
  ^
/Users/matt.mccormick/src/ITK/Modules/Core/Common/include/itkImageScanlineConstIterator.h:135:3: note: candidate function template not viable: requires single argument 'it', but 2 arguments were provided
  ImageScanlineConstIterator(const ImageConstIterator<TImage> & it)
  ^
/Users/matt.mccormick/src/ITK/Modules/Core/Common/include/itkImageScanlineConstIterator.h:64:27: note: candidate function template not viable: requires 1 argument, but 2 were provided
class ITK_TEMPLATE_EXPORT ImageScanlineConstIterator : public ImageConstIterator<TImage>
                          ^
/Users/matt.mccormick/src/ITK/Modules/Core/Common/include/itkImageScanlineConstIterator.h:97:3: note: candidate function template not viable: requires 0 arguments, but 2 were provided
  ImageScanlineConstIterator()
  ^

Closes #4537.

Thanks Matt, do I understand that this is just a quick-fix, to work around a compiler bug?
I still wonder:

Is this a known clang bug? And is it possibly fixed in a newer clang version?
Would it help to add "deduction guides" to the RLEImage specializations of ImageScanlineIterator and ImageScanlineConstIterator ? Just like in itkImageScanlineIterator.h https://github.com/InsightSoftwareConsortium/ITK/blob/a648bd5a40776f5e7575d3cd4c19976a7ea95d97/Modules/Core/Common/include/itkImageScanlineIterator.h#L100-L102 and itkImageScanlineConstIterator.h https://github.com/InsightSoftwareConsortium/ITK/blob/a648bd5a40776f5e7575d3cd4c19976a7ea95d97/Modules/Core/Common/include/itkImageScanlineConstIterator.h#L265-L268

work around a compiler bug?
possibly fixed in a newer clang version?

Well, this is for the compiler that comes with current XCode Clang (the default compiler on macOS), and we need to support it.

add "deduction guides" to the RLEImage specializations

Cool idea! Yes with a variation. Added here: https://github.com/KitwareMedical/ITKRLEImage/pull/63

Explicit template argument does not hurt, and it will allow compiling with older versions of RLEImage remote module. I vote to merge.

Explicit template argument does not hurt, and it will allow compiling with older versions of RLEImage remote module.

It would hurt me! We put a lot of effort into using CTAD in ITK. And it was a pain already to work around those warnings (-wctad-maybe-unsupported). Is UnaryFunctorImageFilter then expected to be the only case where CTAD (temporarily?) may not be used?

@thewtex If it is still found necessary to merge this PR, could you please add that four-letter-word (no pun intended 😸) "CTAD" somewhere in the subject of the commit?

Let's close in favor of https://github.com/KitwareMedical/ITKRLEImage/pull/63 to avoid additional warnings and bump the ITKRLEImage as @dzenanz suggested to improved compatibility #4555.


[retire] Summary QTY need more decimals on the tonnes

As an example, see https://www.carbonmark.com/retirements/0x6476edf98Bdc5EE62f9D4E4BF8932d69Ed685483 where we show the exact tonne quantity retired.
On the Retire page summary component, we are showing zero decimals so getting 0t values.

We should change the QTY to support:
If > 1 tonne, show up to 2 decimals
If < 1 tonne, show up to 3 decimals

@jabby09 the prod link above is showing a different page than the screenshot for me? Should I be seeing the page above?

@jabby09 the prod link above is showing a different page than the screenshot for me? Should I be seeing the page above?

sorry, the URL to the screenshot is https://www.carbonmark.com/retire (as a logged in user)
the link to https://www.carbonmark.com/retirements/0x6476edf98Bdc5EE62f9D4E4BF8932d69Ed685483 is a correct page, I shared as an example of showing actual retired amounts, instead of 0 on the /retire page.
Hopefully that cleared things up.

@jabby09 Ah, cool cool that makes sense. Thanks for the explanation 👍


haskellPackages: update stackage and hackage

This Merge
This PR is the regular merge of the haskell-updates branch into master.
This branch is being continually built and tested by hydra at https://hydra.nixos.org/jobset/nixpkgs/haskell-updates. You may be able to find an up-to-date Hydra build report at cdepillabout/nix-haskell-updates-status.
We roughly aim to merge these haskell-updates PRs at least once every two weeks. See the @NixOS/haskell team calendar for who is currently in charge of this branch.
haskellPackages Workflow Summary
Our workflow is currently described in pkgs/development/haskell-modules/HACKING.md.
The short version is this:

We regularly update the Stackage and Hackage pins on haskell-updates (normally at the beginning of a merge window).
The community fixes builds of Haskell packages on that branch.
We aim at at least one merge of haskell-updates into master every two weeks.
We only do the merge if the mergeable job is succeeding on hydra.
If a maintained package is still broken at the time of merge, we will only merge if the maintainer has been pinged 7 days in advance. (If you care about a Haskell package, become a maintainer!)

More information about Haskell packages in nixpkgs can be found in the nixpkgs manual.

This is the follow-up to #262645. Come to #haskell:nixos.org if you have any questions.

Branch off for 23.11 is in 10 days, November 20th. I hope we can finish this PR until then.

@libjared Looks like there is a problem in haskellPackages.sensei:

https://hydra.nixos.org/build/240435221
https://hydra.nixos.org/eval/1801598?filter=haskellPackages.sensei


Test immutability of shared objects, especially in XDS generation

For performance and simplicity, we pre-generate a lot of XDS objects, such as https://github.com/istio/istio/blob/e78224f921e0079871f40fdf1673adb7401f8368/pilot/pkg/security/model/authentication.go#L75.
This works well, unless we indirectly modify the shared object
shared := &xds.Object{foo: bar}
...
x.field = shared
x.field.foo=not-bar
...
y.field = shared
// Oops! y.field.foo is now "not-bar"!

Especially at risk is EnvoyFilter merges - we had a case where we merged into a shared object so every iteration we added the object again and again due to list append logic.
Naive proposal:

Introduce a new package, immutable, with a single function, say immutable.New(interface{}) interface{}
When -tags=test is passed, this function modifies the object to panic when mutated. Possibly using https://github.com/lukechampine/freeze or equivilent
When -tags=test is not passed, the function just returns the same object.
Wrap all suspicious variables with this

@howardjohn what's the priority of this? Merging EnvoyFilters makes me think this might be related to WASM?

not stale
On Mon, Mar 1, 2021 at 9:04 PM Istio Policy Bot<EMAIL_ADDRESS>wrote:

🧭 This issue or pull request has been automatically marked as stale
because it has not had activity from an Istio team member since 2020-12-01.
It will be closed on 2021-03-16 unless an Istio team member takes action.
Please see this wiki page
https://github.com/istio/istio/wiki/Issue-and-Pull-Request-Lifecycle-Manager
for more information. Thank you for your contributions.
Created by the issue and PR lifecycle manager.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/28947#issuecomment-788588582, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXNYVNQWGITW3J3FS2LTBRWW5ANCNFSM4TX5E7TA
.

not stale
On Mon, May 31, 2021 at 10:02 PM Istio Policy Bot @.***>
wrote:

🧭 This issue or pull request has been automatically marked as stale
because it has not had activity from an Istio team member since 2021-03-02.
It will be closed on 2021-06-15 unless an Istio team member takes action.
Please see this wiki page
https://github.com/istio/istio/wiki/Issue-and-Pull-Request-Lifecycle-Manager
for more information. Thank you for your contributions.
Created by the issue and PR lifecycle manager.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/28947#issuecomment-851806073, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXLPQMJVQHUBVLTP6FLTQRSWJANCNFSM4TX5E7TA
.

not stale
On Mon, Aug 30, 2021 at 10:02 PM Istio Policy Bot @.***>
wrote:

🧭 This issue or pull request has been automatically marked as stale
because it has not had activity from an Istio team member since 2021-06-01.
It will be closed on 2021-09-14 unless an Istio team member takes action.
Please see this wiki page
https://github.com/istio/istio/wiki/Issue-and-Pull-Request-Lifecycle-Manager
for more information. Thank you for your contributions.
Created by the issue and PR lifecycle manager.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/28947#issuecomment-908900253, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXNFAGC5ALS5SQYWRZLT7RO4RANCNFSM4TX5E7TA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

not stale
On Mon, Nov 29, 2021 at 9:01 PM Istio Policy Bot @.***>
wrote:

🧭 This issue or pull request has been automatically marked as stale
because it has not had activity from an Istio team member since 2021-08-31.
It will be closed on 2021-12-14 unless an Istio team member takes action.
Please see this wiki page
https://github.com/istio/istio/wiki/Issue-and-Pull-Request-Lifecycle-Manager
for more information. Thank you for your contributions.
Created by the issue and PR lifecycle manager.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/28947#issuecomment-982287270, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXMS46YGMPGJJLYFZ7LUORLEBANCNFSM4TX5E7TA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Not stale


retrieve output from leetcode for custom cases

For user provided test cases, the expected output can be left blank, we submit the code (must can be compiled) to leetcode to retrieve the output, and write it back to input.txt
ref: https://github.com/j178/leetgo/pull/90#issuecomment-1416735809

Do we need to sanitize this? What if a user provides a test case with the wrong output

Do we need to sanitize this? What if a user provides a test case with the wrong output

We can't tell, wrong output will get wrong result, user will recognize it.

do we need to sanitize the input to make sure it's legal

Not necessary I think, LeetCode will report an error if it's illegal, we just need to show the error to user.


rule initializers

please review

@bmmoore @cos please review

Jenkins: test this please

lgtm.

the branch doesn't merge cleanly now. @radumereuta helped fix things: https://github.com/kframework/k/commits/feature/ktest-tutorial2

Could you include some comments and unit tests?

ok, I'll retract the "lgtm". The configuration initializers are not the same as described on the wiki:
https://github.com/kframework/k/wiki/KAST-and-KORE
Instead of cleanly initializing the configuration, an Init Map (which contains the $PGM) is propagated through all initializers. I see why you went on this route. If you consider the $PGM as a special magic variable you need to somehow resolve it to the program at the end of initialization. Still, this is unnecessary if we consider the $PGM as a hooked function.
  rule =>(initTopCell(Init),<top>(initKCell(Init),initStateCell(Init))) requires #token(Bool,"true") ensures #token(Bool,"true") []
  rule =>(initStateCell(Init),<state>(_Map_())) requires #token(Bool,"true") ensures #token(Bool,"true") []
  rule =>(initKCell(Init),<k>(Map:lookup(Init,#token(KConfigVar,"$PGM")))) requires _andBool_(isK(Map:lookup(Init,#token(KConfigVar,"$PGM"))),isPgm(Map:lookup(Init,#token(KConfigVar,"$PGM")))) ensures #token(Bool,"true") []

Also, there's a bug in plugConfigVars. The empty map is initialized with .Map(), while the klabel for an empty map is _Map_. This breaks at least tiny. We should have some tests for this part of the pipeline.

plugConfigVars is correct. Map(.KList) is a badly typed term. You should fix your rewriter to obey the written syntax of maps, in which .Map is the unit. A production with two NonTerminals should always correspond to a KApply with two children in its klist. I have no idea why you are so interested in breaking this property, but it's an extremely valuable one.
As far as the initializers go, I like the idea you propose in theory but I'm not sure it works out in practice in a way that is particularly nice. In order to achieve the semantics you describe, it becomes necessary to decompose a hook string in some mysterious fashion into pieces that tell you that the hook corresponds to a configuration variable, and the name of the configuration variable. I would strongly prefer hook strings to remain opaque and statically fixed in each backend. As far as I can tell there isn't a way to do both of these, and I feel like the solution I went with is completely feasible and easy to understand. But I am willing to have discussion about how to proceed here; I just don't see a better solution yet based on the information I currently have.

Regarding .Map, Map is the current klabel in misc.k
The $PGM can be:
syntax ProgramVariable ::= "$" String [hook=....]
(sent from mobile phone)

On May 12, 2015, at 6:10 PM, dwightguth<EMAIL_ADDRESS>wrote:
plugConfigVars is correct. Map(.KList) is a badly typed term. You should fix your rewriter to obey the written syntax of maps, in which .Map is the unit. A production with two NonTerminals should always correspond to a KApply with two children in its klist. I have no idea why you are so interested in breaking this property, but it's an extremely valuable one.
As far as the initializers go, I like the idea you propose in theory but I'm not sure it works out in practice in a way that is particularly nice. In order to achieve the semantics you describe, it becomes necessary to decompose a hook string in some mysterious fashion into pieces that tell you that the hook corresponds to a configuration variable, and the name of the configuration variable. I would strongly prefer hook strings to remain opaque and statically fixed in each backend. As far as I can tell there isn't a way to do both of these, and I feel like the solution I went with is completely feasible and easy to understand. But I am willing to have discussion about how to proceed here; I just don't see a better solution yet based on the information I currently have.
—
Reply to this email directly or view it on GitHub.

misc.k is deprecated. I left it in place because I didn't want to spend time trying to fix your rewriter, but you should fix your code to be compatible with domains.k, which contains a much more accurate and complete prelude.

@bmmoore I added some comments, let me know if you want comments anywhere more specific as well. As far as testing goes, the functionality I am adding is tested by TstBackendOnKORE_IT... do you want more specific tests?

When I wrote https://github.com/kframework/k/wiki/KAST-and-KORE, what I had in mind for configuration variables was to regard them as constants with desugaring macros:
syntax KItem ::= "$PGM" | "$STATE"
rule $PGM => "int x; x =7;"
rule $STATE => "x |-> 0"
...
rule initKCell => <k> #parse($PGM, IMP-SYNTAX) </k>
...

I still believe that this is the ultimate, most general solution.  Recall that macros are meant to be like the anywhere rules, but they apply statically to the entire definition (and program).
However, I agree that this general solution would be inconvenient right now, because it will require to re-kompile the definition each time, which with our current kompile times is a problem.  Even if it took 10 seconds to kompile the entire C semantics, which is not even the case, it is still too much to pay when executing each program.  I believe Cosmin's solution is somewhat equivalent, passing the macros job to functions.  So I am OK with Dwight's solution for now.

For comments, I am concerned about documenting the translation strategy, especially now that it doesn't match what's documented on the wiki.
As for unit tests, I mean an example that tests just this pass, so we have at least a handful of test cases showing expected input and output of just this configuration desugaring pass.
I'm fine with the general implementation strategy. This approach may even be a bit better than macros, because I think we should continue enforcing that configuration variables are used only in the initial configuration, rather than letting them be used in any rule.
However, one detail needs to be improved - the treatment of cell initializers added in completion. It currently supplies an empty map which will lead to a runtime error if the cell references confiugration variables, when we could easily produce a static compilation error.
I suggest that cells not containing (transitively) configuration variables should get an initializer label that does not take any arguments (while continuing to pass a map into the ones that do need the variables). Then cell completion can revert to generate a simple no-argument label application for legal code, and more easily generate an appropriate error message otherwise. (I'd rather see the information explicitly represented, maybe modifying the existing ConfigurationInfo lookup methods, but if you insist on working by checking the arity, comments around the creation and check should document that you expect initializers to have those two arities, from which you infer additional semantics).

@bmmoore, what is the advantage of having configuration variables to be used only in the initial configuration? Furthermore, why do we need the concept of "configuration variable" in the first place? They can simply input streams to the definition:
syntax ConfigVar ::= "$" String [ hook(ReadNamedStreamInput) ]

Then:
rule initKCell => <k> #parse($PGM, IMP-SYNTAX) </k>

becomes, in (semi)labeled form:
rule initKCell => <k> #parse(`$`("PGM"), IMP-SYNTAX) </k>

where $ is just a function reading the entire stream named "PGM".
This approach gets rid of the concept of "configuration variable" and give us more flexibility. E.g., it allows us to easily write definitions that behave like continuous interpreters of input streams (e.g., a console).

The advantage of allowing configuration variables only in the initial state is that that makes them purely part of the initialization process, rather than the definition of the semantics.
Generalizing from simple named values to arbitrarily input streams is just unnecessary complexity. Do we really want to think about what happens if the contents of $PGM change halfway through parsing?!

Given that we already have a solution that meets our needs (which Brandon and I agree on and which is mostly implemented in this pull request with some minor alterations to follow soon), I would prefer that we close this discussion and move on, only re-evaluating the implementation if we can come up with some concrete use case justifying the need for things to behave differently than they already do. Is this going to be a problem?

Oh, is this still not closed?  I thought that it was over.  So yes, we do have a solution which works fine and does everything we were able to do before, so we are good for now.  Let us please not waste any more time with it.
Any re-design or change of this from here on should only happen after we discuss it in person.  All of us directly interested in this.  We have to look at all possible uses of the concept before proposing (or worse, implementing) any new design.  For example, we want to allow programs to contain variables, or even be just variables, and then do semantics-based program generation, like @yilongli used to do and like Tom (a new intern) will do soon.  In that light, $PGM is a variable, one which will be unified as rewriting takes place via narrowing.  So your solution, @cos, is not going to be general enough.  And I believe mine was not general enough either.
But let's not get into this, it is really not important now.  The bottom line: we have something which works with the new KORE and can do everything we wanted it to do so far, so we are fine.  Please merge asap and any other change of it should be bug fixes, not re-designs, unless we discuss and agree on a new design.  Same with configuration abstraction (which we also know that it is not as general as it can/should eventually be), please, no changes there either, except for bug fixes!  Let us first have everything work with KORE and the worry about making things as general as possible.

Ok, looks good now.


fixed the display of article content in italics and list

Has been tested.

I have used your code in there : https://github.com/shprink/wordpress-hybrid-client/commit/4009db8cb9c42f1dd72a0f0083658dfb5e89c48b#diff-116327492315fbe10e3f0d6a938e7d4aR4
Thanks for finding ul and ol had no style :)


How to use Pagination?

As phalcon-rest use Fractal in internals, how it is possible to use pagination feature from Fractals?
I've seen that an adapter has been implemented for Phalcon. But I still can't understand how to put everything together.
Thanks.

you can see this http://fractal.thephpleague.com/transformers/


Update README and project website

Update these documents to reflect changes made to value proposition

Codecov Report
Base: 60.70% // Head: 60.70% // No change to project coverage :thumbsup:

Coverage data is based on head (0b2dd0e) compared to base (e7df934).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #231   +/-   ##
=========================================
  Coverage     60.70%   60.70%
  Complexity      554      554
=========================================
  Files           103      103
  Lines          2059     2059
  Branches        211      211
=========================================
  Hits           1250     1250
  Misses          737      737
  Partials         72       72

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

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


How to install cython on windows?

I have tried to install MinGW - C compiler to compile .c files after doing the command on the setup file but it keeps giving an errors. I also tried to add MinGW to the environment variable, which didn't affect it all. After I'm doing the python setup.py build_ext --inplace command, it translates the .pyx to a .c, but when I try to compile the .c, it keeps showing me that there is no 'Python.h' file, and others. I tried to add the folder of the file to envv but didn't worked...

In general this issue tracker is for problems with cython. Since cython successfully generates the C file, your situation is better suited to a general forum for problems with setuptools/distutils.
Are you compiling without using distutils/setuptools? They query your version of Python to emit flags used to find the include path for Python.h via a call to values of sysconfig.get_config_vars('CC', 'CXX', 'OPT', 'BASECFLAGS','CCSHARED', 'LDSHARED'), which are fixed when compiling python, and the appropriate flags are added to the compile command.
When you report this in another forum, you will want to copy-paste the text (not a screen shot) of the exact calls you are making, including showing the compiler call with all flags to better help people reproduce your problem.

There's a bit of documentation about usage on Windows and also with MinGW available in the docs and the github wiki.
Closing, since it's not a bug or issue with Cython.

In general this issue tracker is for problems with cython. Since cython successfully generates the C file, your situation is better suited to a general forum for problems with setuptools/distutils.
Are you compiling without using distutils/setuptools? They query your version of Python to emit flags used to find the include path for Python.h via a call to values of sysconfig.get_config_vars('CC', 'CXX', 'OPT', 'BASECFLAGS','CCSHARED', 'LDSHARED'), which are fixed when compiling python, and the appropriate flags are added to the compile command.
When you report this in another forum, you will want to copy-paste the text (not a screen shot) of the exact calls you are making, including showing the compiler call with all flags to better help people reproduce your problem.

Thank you. I know this question is more suitable for forum website, but the biggest forum called 'StackOverflow', decides every once in a while to limit the amount of questions I can ask, if they'r not getting enough reputation or if the quality of them is "not enough".

And I don't want to go to Reddit or Quora, because those websites are not mainly concentrated in this target.
Can you recommend me some other forums?


Set up staging / dev / prod infra

Basic dev -> staging -> prod setup
~Need two setups for staging and prod -- one that continues to deploy to github pages as the "prototype" version and one that deploys to galago.czgenepi.org as the "production" version.~
~It would be particularly helpful if we could include feature flags (e.g., if (flags.prototype) {showBanner = true}), but I'm not sure how big of a lift this would be.~

@sidneymbell can we document the uses for dev, staging, and prod.
My understanding is...

dev = playground for development, not shared with others
staging = could have experimental features, not shared widely, but shared with collaborators for early feedback. contains big disclaimer
prod = what we link to from CZ GE; more rigorously vetted pushes; accessible to anyone

Per conversation with @vincent-czi --

No actual need for dev environments as easily run on a laptop / localhost and has no need for a server in order to demo
Need a "comp bio experimental space" which will remain on github pages -- keep the current deploy.sh to push to galago.chanzuckerberg.github.io. Consider changing the name to something like galago-experimental.chanzuckerberg.github.io
Need a "production / stable" version which will deploy to galago.czgenepi.org -- need to figure out where to host the static webpage

Discussed this with Jess as well, plan is to keep both the Prod and "dev/experimental/labs" version of the app both on github pages. That way deploy is consistent and we're already used to working with it from Sidney's prior work. Two repos: galago and galago-labs (forked). Most dev work will be done on galago-labs once everything is set up. Merging to its main branch will deploy the dev version of the site, while galago will be the prod version.

As part of this work, am also setting up basic CI/CD pipelines with GitHub Actions. Merge to main kicks off the deploy pipeline. We'll want to later come back and add some level of testing/linting in the Pipeline that applies to all PRs (all branch pushes?). See related #166 .


Fix GH-Actions workflow for pkgdown

https://github.com/2DegreesInvesting/r2dii.data/actions/runs/112715486
Until we fix this, I'll deploy with deploy_to_branch().

This fixed itself.


notion: groff -> mandoc & busybox -> which

bad name/version
whole busybox just for which
one of multiple groff -> mandoc test subjects

cc @jfb

fair warning: @joachifm has reservation agianst the mandoc stuff he has expressed in https://github.com/NixOS/nixpkgs/pull/18746

closed since it's not going anywhere.


material design color system  is added

Material design color system format is a widely used format in various CSS frameworks and libraries like tailwind CSS, emotion JS etc . Most developers are familiar with this format and easier for developers to adopt. Also Master CSS have less colors. So, I contributed a material design system format with more colors. Developers do not always want to use custom colors.

@elamandeep We've created a new color palette at v2.

We limited it to 1-99 for closer to brightness or even sensed brightness meaning.
Master CSS comes with a expertly-crafted color palette. In particular, a single color is more than just the 11 shades listed below; you can choose between 15, 20, 25 and even 32, 33, 34 values for better color rendering.
The v2.0 of the color has been prefixed with #.

Thanks for your contribution!

This is my first github contribution and I love to contribute to your project. You and your community are great.I will definitely contribute further to this project. Let's make it bigger.


x/tools/gopls: high memory usage with VS Code remote dev in github.com/cockroachdb/cockroach

Report on Slack:

huh, has anyone seen gopls taking 25+ 35 GiB of ram / getting OOMKilled?
strangely, it seems fine run locally on my laptop, where I only have 16gb total, but when I use VSCode’s remote dev feature, checking out the exact same codebase, but on a much bigger and beefier cloud VM, it gets OOMkilled a couple times a day with reported vm of 35GB. (edited)

Profiles:
gopls.30591-26GiB-goroutines.txt
gopls.30591-26GiB-heap.pb.gz
Local changes: https://github.com/cockroachdb/cockroach/compare/master...dt:gopls-oom?expand=1
/cc @heschik

This issue has been addressed: #38080
which seems to reduce RAM usage considerably.

Great!


Feature/umd support

Hey there! congratz for your library. Cool work here...
I thought it would be cool to have a AMD support, so I added a simple snippet to it. what do you think?
:)

@mauriciosoares really appreciate the pull request, but I'm going to close it because I'm planning on adding a wrapper that will support AMD and CommonJS (see issue #3)

@mauriciosoares UMD wrapper is now in place, AMD support should be included :+1:

Great!
:)


调用start时crash

版本1.1.0
手机 pixel 3XL
已开启悬浮窗权限
Caused by android.app.BackgroundServiceStartNotAllowedException
Not allowed to start service Intent { flg=0x10000000 cmp=com.hk.azal.live/top.shixinzhang.bitmapmonitor.ui.FloatWindowService }: app is in background uid UidRecord{8e253cc u0a217 TRNB idle change:uncached procs:0 seq(0,0,0)}

应该是一样的错误  java.lang.RuntimeException: Unable to create application com...Application: java.lang.IllegalStateException: Not allowed to start service Intent { flg=0x10000000 cmp=com../top.shixinzhang.bitmapmonitor.ui.FloatWindowService }: app is in background uid UidRecord{8e44a72 u0a241 TPSL idle change:idle|cached procs:1 seq(0,0,0)}


Feat: DFT

Implement DFT operator.

Can I do this ?

To implement this operator, I need complex numbers, I didn't find the implementation in any Cairo repo. Do I create an issue to add complex numbers in orion ? I'd love to implement that.

Yes that would be great! I thought to implement it, but didn't find the time yet to implement it. If you can implementing Complex numbers that would be great! Thanks!


Unexpected Delta Log caching

The following has been done in Azure Databricks 6.4 as well as with a Standalone Spark 3.0.0 (Scala 2.12.10) with Delta Core 2.12-0.7.0.
I have found some unexpected behaviour when working on the same Delta Table from multiple Spark sessions. It appears that, if an existing Delta Table (that has once been read by Spark Session B) is removed from the filesystem and recreated from Spark Session A, Spark Session B will not be able to read the Delta Table anymore since the Delta Log is stored somewhere in cache, even after unpersisting the Dataframe.
Steps to reproduce:

Start 2 Spark Sessions A (writing) and B (reading)
Let A write some Delta Table

val data = Seq(("a",1), ("b",2), ("c",3))
val df = spark.createDataFrame(data)
df.write.format("delta").save("/tmp/test")

Let B read and show the Delta Table

var df = spark.read.format("delta").load("/tmp/test")
df.show()

Remove the Delta Table from the filesystem and repeat step 2
Repeat step 3

At this point, Spark Session B will throw an exception stating that a Parquet file is missing and unpersisting the DF does not help.
org.apache.spark.SparkException: Job aborted due to stage failure: Task 0 in stage 18.0 failed 1 times, most recent failure: Lost task 0.0 in stage 18.0 (TID 308, 868fbeb950fc, executor driver): java.io.FileNotFoundException: File file:/tmp/test/part-00001-a6db7bc9-0dad-45c5-8f40-8413514e8e4e-c000.snappy.parquet does not exist
It is possible the underlying files have been updated. You can explicitly invalidate the cache in Spark by running 'REFRESH TABLE tableName' command in SQL or by recreating the Dataset/DataFrame involved.

Spark Session A, however, is able to read the Delta Table.
The actual content of the file system is correct and consistent at any point in time. So to me, it seems like the Delta Log is cached and not reloaded in Spark Session B, even after unpersisting the Dataframe.

Clarifying question: when you say two spark sessions, do you mean 2 sessions in the same driver/cluster, or in 2 different drivers/clusters?

The test on the standalone Spark was performed on the same cluster. On Databricks, I originally used two clusters in two notebooks since any other combination (same cluster in two notebooks or same notebook with two clusters) would not produce the issue.

Interesting. We generally recommend not to delete and recreate tables in this way, especially not with two different sessions, for a bunch of reasons - caching, as well as, S3 consistency issues. It's better to overwrite in those scenarios rather than delete the table directory along with the delta log.

I understand that this is not a regular scenario to encounter. However, sometimes you find yourself in a debugging situation where you do some iterative testing and need to examine the result of another job followed by cleaning up the Delta table and retrying. This can potentially cause spending a lot of time searching for errors in your own code. At least for me, this behaviour was unexpected.

However, sometimes you find yourself in a debugging situation where you do some iterative testing and need to examine the result of another job followed by cleaning up the Delta table and retrying.

@sbachstein You can try executing FSCK Repair before the reading part. It removes the entries from the transactional logs that can no longer be found.  With this, your previously mentioned steps will be as follows:

Start 2 Spark Sessions A (writing) and B (reading)
Let A write some Delta Tableval data = Seq(("a",1), ("b",2), ("c",3))
val df = spark.createDataFrame(data)
df.write.format("delta").save("/tmp/test")

Let B execute FSCK repair, read and show the Delta Tablespark.sql("FSCK REPAIR TABLE delta.`/tmp/test`")  // Newly added

var df = spark.read.format("delta").load("/tmp/test")
df.show()

Remove the Delta Table from the filesystem and repeat step 2 and 3 any number of times

It's good that you mention the FSCK REPAIR command. I have actually tried this already and I have encountered another problem, maybe even more serious:
When trying to repair the Delta table in Session B, it will actually use the cached Delta log as a basis for the repair and will leave you with an empty Delta table (since all of the Parquets referenced by the cached Delta log are gone), where the newly written Delta log, written by Session A, is actually overwritten by Session B.
Have you tried the steps? I would be very interested to hear if you encounter the same situation.

I notice this as well, reproducible in the following way

Create a folder on S3
Attempt to read from it to get the "path is not a Delta table" error
Write data into the folder to make it a Delta table
Attempt to read again

Result:

Still get the "path is not a Delta table" error even though the __delta_log folder is indeed there

Expected result:

Read works

I mostly see this in spark-shell when debugging and my workaround is to just restart spark-shell.


Example SCIM provider

This is the current state of my example SCIM provider WSGI application.

[x] Discovery endpoints (/v2/ServiceProviderConfig, /v2/ResourceTypes, /v2/Schemas)
[x] Create/Read/Update/Delete resources (POST, GET, PUT, DELETE)
[x] Searching & Filtering
[x] ETag support
[x] Evaluate unique Constraints
[x] PATCH (Add/Remove/Replace)
[ ] Sorting for Queries (WIP)
[ ] Bulk (TBD)

~While I think most of the code isn't too bad (though is definitely missing some comments), I am really struggling with the PATCH operation. I've started some experiments in utils.patch_resource, but the implementation is getting completely out of hand. Since you (@azmeuk) offered to take a look, maybe you have some ideas on how to improve that/add some useful helpers in scim2-models, to make it easier?~

Hi @ccoors
Thank you for your contribution! I will try to gather enough time to review your PR in the coming days/weeks.

I have managed to implement PATCH :) Now working on Sorting and will probably also do Bulk.

Hi. I still could not find much time for reviewing your work, but I don't lose hope!

I was thinking that maybe we could add your example server implementation in another repo.
To keep the codebase synchronized with scim2-models, we could then add it as a subrepository here.
 What do you think?

Yes, that sounds fine. Git submodules are a bit annoying to work with, but in this instance I guess it's okay.

Ok. I invited you on https://github.com/yaal-coop/scim2-server

@azmeuk I added the server in scim2-server and modified this PR, so that it uses it as a submodule. I'm not sure this will provide an 'easy' workflow for future changes in scim2-models, as you may have to synchronize changes across two repos. Maybe try it out for now?

Closing in favor of #71


Update Admin template

Css Admin login page
Css Admin template with custom.css
Redesign Product Edit page
Thank for Lanh Le with SCart

@namcyeon we will refer to your suggestions. Thanks very much :)


Change constrain to take any boolean expression

Currently the constrain construct includes a binary operator as part of its syntax: constrain <expr1> <binop> <expr2> where <binop> is a boolean operator like ==.  This seems to be a relic from before these operators where implemented elsewhere in the language.
Proposed change is to generalize to constrain <expr> where <expr> is any boolean-returning expression.

@jfecher can this be closed?

Indeed, this has been implemented in #236


Update dex dependencies

https://github.com/project-serum/serum-dex/blob/master/dex/Cargo.toml#L18
solana-program dependency version is pinned. When using that program as library it causes issues when having other libs in place that require newer versions of solana-program.

0x5245c0249e5eeb2a0838266800471fd32adb1089

Kindly open this live chat link to talk to the customer service directly on your issue  https://direct.lc.chat/14232768/


IE11 browser Issue: Facing issue with Forcetk.js(Rest toolkit), Parameter is incorrect

Hi,
I am using IE11 browser. I am using Forcetk.js to for file upload into content version. The script is working fine in Mozilla and Chrome.
But in IE11, I get the below error in Forcetk.js file. Please help if any one faced similar issue.

I have posted the same issue here:
http://salesforce.stackexchange.com/questions/111774/ie11-browser-issue-facing-issue-with-forcetk-jsrest-toolkit-parameter-is-inc?noredirect=1#comment154859_111774

Sending a blob has been supported in IE since version 10, so I'm a bit puzzled as to the problem. Can you put a breakpoint or a console.log in at that line and see what the value of blob is?

Please check the below screenshot for console log.

I'm stumped. I don't have a Windows machine with IE11 to try this on. Everything I can find says this should work on IE11. Is it possible to get more details on the exception?

Hi Patterson,
I too got stumped over debugging this issue!
I finally found the root cause of this issue. I was using "rerender" attribute in my visualforce page. It was due to this, I am getting this error.
I tried creating a new visualforce page without "rerender" attributes. Then the  file upload was working fine.
Thank you very much for the follow up.


Tile: Pile of ash

What should be done?
Pile of ash on sand and on grass

Ash pile will have a 5% chance to set player on fire when player walks over it.


Flashlight is drawing stuff when its off

Flashlight still draws things when it's off.

I don't get it, what do you mean "Flashlight is drawing stuff" ?

He probably means the shadow maps

I don't get it, what do you mean "Flashlight is drawing stuff" ?

 You can check it by r_light_debug 1.

If you mean the scene painted into s_GBufferFBO.s_hBackBufferTex, this is by-design.

Oh, i was thinking that it was a bug. Because when i turn off the flashlight effect using console (r_light_dynamic 0), fps suddenly goes up.


Cyrillic character ranges in regex

It is also possible to use \p{L} and p{Cyrillic} in unicode mode.  But this requires apparently minor changes to these expressions. But the letters work both in the search for posts and in the search for sub (and creation). ё added to posts search. I don't think she will meet in 'sub'.

I'm not sure this should be merged. Most instances certainly don't want to allow Cyrillic characters. This should be a config option (best would be to set the regex in the config file)


Mark cxf-soap as fully supported CEQ-6682

@jamesnetherton @ppalaga Could you please double check ?


[Code structure] Prefer C++20 modules over header files

Now that thprac is using C++20, I believe replacing most header files with import/export syntax would be a sensible change to make. Doing so would:

Remove the need for duplicate declarations between source and header files (and therefore also the possibility of forgetting to update one or the other)
Significantly reduce the number of files in the thprac/src/thprac directory
Possibly improve compile times for "hot" builds

I propose that thprac_locale_def be kept as a header/source pair for the time being, due to planned localization changes related to #90.
I am willing to work on this myself, but I felt that also opening an issue would be appropriate.

I guess that can come later. Right now I'm concerned with removing as much code as possible to narrow down the list of things to be turned into modules

Removing unused code first definitely makes sense, and may be worth creating another issue for. Another thing I'd like to address is the (in my opinion) excessive usage of macros throughout the codebase - especially in header files, as C++20 modules cannot export macros. (For this reason, I don't expect to be able to replace every header with module syntax.)
Could you clarify what you mean by "the last step"? Is there a list of priorities somewhere? (And if not, should we create one?)

Right now I'm concerned with removing as much code as possible [...]

Related: #107 (I forgot to mention this issue when opening the PR, sorry!)


Port otlp 4317 is not available in UI Service

Describe the bug
odigos-data-collectors are trying to send metrics to UI in grpc port 4317 but port is not configured in Service.
To Reproduce
Steps to reproduce the behavior:

Deploy helm chart
Configure source
Configure destination

Expected behavior
No error
Screenshots
Service ports for UI

Lack of metrics in UI

Additional context
UI Service Helm Template
apiVersion: v1
kind: Service
metadata:
  name: ui
  namespace: {{ .Release.Namespace }}
  labels:
    app.kubernetes.io/name: odigos-ui
spec:
  ports:
    - name: ui
      port: 3000
  selector:
    app: odigos-ui

Collectors errors (connecting to UI Ip)
2024-09-12T10:04:33.664Z    error    exporterhelper/queue_sender.go:92    Exporting failed. Dropping data. Try enabling retry_on_failure config option to retry on retryable errors.    {"kind": "exporter", "data_type": "metrics", "name": "otlp/odigos-own-telemetry-ui", "error": "rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dial tcp <IP_ADDRESS>:4317: connect: connection timed out\"", "dropped_items": 11
 go.opentelemetry.io/collector/exporter/exporterhelper.newQueueSender.func1
     go.opentelemetry.io/collector/exporter@v0.106.0/exporterhelper/queue_sender.go:92
 go.opentelemetry.io/collector/exporter/internal/queue.(*boundedMemoryQueue[...]).Consume
     go.opentelemetry.io/collector/exporter@v0.106.0/internal/queue/bounded_memory_queue.go:52
 go.opentelemetry.io/collector/exporter/internal/queue.(*Consumers[...]).Start.func1
     go.opentelemetry.io/collector/exporter@v0.106.0/internal/queue/consumers.go:43
2024-09-12T10:04:43.664Z    error    exporterhelper/queue_sender.go:92    Exporting failed. Dropping data. Try enabling retry_on_failure config option to retry on retryable errors.    {"kind": "exporter", "data_type": "metrics", "name": "otlp/odigos-own-telemetry-ui", "error": "rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dial tcp <IP_ADDRESS>:4317: connect: connection timed out\"", "dropped_items": 11
 go.opentelemetry.io/collector/exporter/exporterhelper.newQueueSender.func1
     go.opentelemetry.io/collector/exporter@v0.106.0/exporterhelper/queue_sender.go:92
 go.opentelemetry.io/collector/exporter/internal/queue.(*boundedMemoryQueue[...]).Consume
     go.opentelemetry.io/collector/exporter@v0.106.0/internal/queue/bounded_memory_queue.go:52
 go.opentelemetry.io/collector/exporter/internal/queue.(*Consumers[...]).Start.func1
     go.opentelemetry.io/collector/exporter@v0.106.0/internal/queue/consumers.go:43

FIX:
After add port in service everything works as expected. I’m happy to open a PR with this change

@narfeta Thanks for reporting this. I merged a fix for this and it should be resolved in the next release (which will be out in the next few days). Feel free to re-open this if the problem still occurs.


Gridsome does not load images dynamically into v-for

Description
I have an array of objects similar to the following:
[
  {
    name: 'js',
    title: 'Javascript Developer',
    logo: '~/assets/img/logos/javascript.png',
    description: 'js'
  },
  {
    name: 'php',
    title: 'PHP developer',
    logo: '~/assets/img/logos/php.png',
    description: 'php'
  }
]

I want to reuse a component using the v-for directive and load it with the data from the mentioned array. The problem is that the logo property throws a 404 error.
Steps to reproduce
Adding the logo dynamically in the :src property does not work.

  <g-image :src="skill.logo" class="rounded logo mr-2" align="left"/>

{{ skill.description }}

Expected result
Load the image dynamically.
Actual result
404 not found.
Environment
$ gridsome info

  System:
    OS: Linux 5.3 Ubuntu 18.04.4 LTS (Bionic Beaver)
    CPU: (4) x64 Quad-Core Processor (up to 1.4GHz)
  Binaries:
    Node: 10.18.1 - /usr/bin/node
    npm: 6.13.7 - /usr/bin/npm
  Browsers:
    Firefox: 72.0.2
  npmGlobalPackages:
    @gridsome/cli: 0.3.1

Hi @gregorip02,
with this, it should work.
Tested it locally and the images are shown as expected.
<template>
  <Layout>

      <g-image
        :src="require('!!assets-loader!~/assets/images/'+imageItem.image)"
        :title="imageItem.description"
        class="rounded logo mr-2" align="left"
      />

  </Layout>
</template>

Great @noxify  is working.
Is there any way to make this cleaner?

Is there any way to make this cleaner?

if you mean the docs, then yes :)
Alternative, you could use source-filesystem or so to load the entries into graphql,
then you're able to use <g-image :src="node.image"/> directly.
But this seems a bit over-engineered in your case.


add CORS support

I don't think CORS is enabled on this, which makes it impossible to request the API from Chrome? It looks like it was solved in the upstream repository: https://github.com/phalt/swapi/issues/60

I am also running into this issue when testing out this api.

Could you double-check that please, for me it seems to be working fine.


Refactor violations schema

Description

This refactors the schema of constraint violations to move data common to all violations of a given constraint into an outer object. Before, the results of a single constraint were represented as List<Violation>, where each violation contained metadata about the constraint, and its own list of gaps. Now they are stored in a single ConstraintResult object, which contains constraint metadata and gaps at the top level, and a list of Violations, each of which can contain a list of violating intervals and associated activities.
The reason for this is because we want to be able to associate multiple intervals with a single violation, or a single interval with multiple violations, without duplicating common data. This was not an issue before making a rolling window constraint node, which needs multiple intervals per violation.
Verification
A few AST tests broke and needed fixing.

[ ] I think there is still an e2e test that will fail. I'll fix it if it does, or add one if not. (edit: indeed)

Documentation

[ ] There is an example of the violation schema in the docs that needs to be updated.

Future work

[ ] This will require an update to the UI to account for the new schema. Also, currently the UI flattens the list of intervals in each violation into separate violations. This will need to be changed.

Created the UI ticket: https://github.com/NASA-AMMOS/aerie-ui/issues/797
Make sure we do not merge this until that ticket has an approved PR.

BEHOLD!
it builds

I'll do a quick retest of my ui branch, and lets try to get that approved too!


Deprecate epics.

Fix #424

:tada: This PR is included in version 1.0.2 :tada:
The release is available on:

1.0.2
GitHub release

Your semantic-release bot :package::rocket:


Unable to create an account

I keep getting the above error message when I try to create a new account

I am getting the same error message. The system is not connecting with Paypal.

NOTE: This solution is optional, You can use any other existing services to create an account. The primary requirement is to use public key retrieved from the device. Here is the list of other available services:
https://eostoolkit.io/account/create
https://www.zeos.co
https://eos-account-creator.com


Add multiple versions

Add tags for different rclone and ubuntu/alpine versions

Added a workflow that automatically builds a new image when a rclone update gets released


Unable to build remix while using absolute paths outside of the app directory with custom routes in vite.config.ts

Reproduction

Stackblitz: https://stackblitz.com/~/github.com/drewdecarme/remix-imports (I use yarn berry so you might have to clone the repo)
Github Repo: https://github.com/drewdecarme/remix-imports

System Info
System:
    OS: macOS 14.6.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 166.48 MB / 32.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 22.1.0 - ~/.nvm/versions/node/v22.1.0/bin/node
    Yarn: 4.5.0 - ~/.nvm/versions/node/v22.1.0/bin/yarn
    npm: 10.7.0 - ~/.nvm/versions/node/v22.1.0/bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 129.0.6668.58
    Safari: 17.6

Used Package Manager
yarn
Expected Behavior
I'm trying to build a Remix app by defining custom routes outside of the app directory. When I run it in DEV mode, things seem to be working fine, but when I try to build it I get some issues when the server manifest is trying to be built. I would expect if I define a route such as the below, that the absolute path would resolve correctly and the server bundle manifest would compile correctly.
Let's say I define an index route like the below:
export default defineConfig({
  plugins: [
    remix({
        future: {
          v3_fetcherPersist: true,
          v3_relativeSplatPath: true,
          v3_throwAbortReason: true
        },
        routes(defineRoutes) {
          return defineRoutes((route) => {
            route(
              "/",
              "/Users/user_name/absolute/path/to/route/file.tsx",
              {
                index: true
              }
            );
          });
        }
      })
  ]
})

Actual Behavior
Client building works fine, but when the ssr is true and vite attempts to build the server bundles, the asbolute of the routes are being prepended with the absolute app directory. I've done some tracing and found what I believe to be issue to be here:
https://github.com/remix-run/remix/blob/9d68bb37a26ebec92be819ba23e21332707a8bcc/packages/remix-dev/vite/plugin.ts#L873C11-L873C24
in the generateRemixManifestsForBuild of the vite plugin, the absolute file path is being joined to the app directory which results in a the route.file being incorrect.
 for (let [key, route] of Object.entries(ctx.remixConfig.routes)) {
      let routeFilePath = path.join(ctx.remixConfig.appDirectory, route.file);
      let sourceExports = routeManifestExports[key];
      let isRootRoute = route.parentId === undefined;

      let routeManifestEntry = {
        id: route.id,
        parentId: route.parentId,
        path: route.path,
        index: route.index,
        caseSensitive: route.caseSensitive,
        hasAction: sourceExports.includes("action"),
        hasLoader: sourceExports.includes("loader"),
        hasClientAction: sourceExports.includes("clientAction"),
        hasClientLoader: sourceExports.includes("clientLoader"),
        hasErrorBoundary: sourceExports.includes("ErrorBoundary"),
        ...getRemixManifestBuildAssets(
          ctx,
          viteManifest,
          routeFilePath,
          // If this is the root route, we also need to include assets from the
          // client entry file as this is a common way for consumers to import
          // global reset styles, etc.
          isRootRoute ? [ctx.entryClientFilePath] : []
        ),
      };

The route.file from the defineRoutes function is /Users/user_name/absolute/path/to/route/file, but when it's joined with the ctx.remixConfig.appDirectory, it then becomes /Users/user_name/absolute/path/to/route/file/app/Users/user_name/absolute/path/to/route/file.tsx.
This in turn then fails the lookup for the manifest since the manifest key is relative
{
"../../../../.rel/stuff/_index.tsx?__remix-build-client-route": {
    "file": "assets/_index-DDBvjPKe.js",
    "name": "_index",
    "src": "../../../../.relative/stuff/_index.tsx?__remix-build-client-route",
    "isEntry": true,
    "imports": [
      "_jsx-runtime-SuB_ucaY.js",
      "_classes-CfpolwFq.js"
    ],
    "css": [
      "assets/_index-2pbE-c8t.css"
    ]
  }
}

This then throws the No manifest entry found error since the absolute filepath doesn't match the relative key the manifest was created with.
My question is... does remix have a way around this or is this really a bug?

Have you tried using relative paths for your route files?
But I'm pretty sure that Remix/Vite doesn't really like route modules outside of the app folder. I had experimented before using workspaces to pull in shared routes, but kept running into issues.

i get this too trying to build remix when using mdx pages with plugins


improves docstrings in stages and operators

Copy what was done later on when interfacing Atlas Search. That is adding a description of the operator/stage

To improve enums docstrings => https://stackoverflow.com/questions/50473951/how-can-i-attach-documentation-to-members-of-a-python-enum

https://betterprogramming.pub/3-different-docstring-formats-for-python-d27be81e0d68

https://numpydoc.readthedocs.io/en/latest/format.html#documenting-classes

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

3. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share on Twitter

Winners: @alvail, @daerco22, @BillFoxUK, @oldhat2016, @weilhuiz, @abdul-maajid, @polzamango, @lingfan, @sahincetin, @olga2812

[ ] merge 59 dans 59 bis

In pipeline.py:

in replace_root and replace_with methods docstrings: "For more info on expressions, see Expressions." Where this should point to? There is no link atm but I think there should be one?
in all method docstrings: "Adds a ... stage to the current pipeline": should it be the monggregate stage or its MongoDB counterpart (when it exists) ? For instance, in search_meta: should it be "Adds a search_meta stage..." or "Adds a searchMeta stage..."  or "Adds a $searchMeta stage...".
Same question in set stage. Currently, it is a mix of both:

Adds a set stage to the current pipeline. Adds new fields to documents. $set outputs documents that contain all existing fields from the inputs documents and newly added fields. Both stages are equivalent to a $project stage that explicitly specifies all existing fields in the inputs documents and adds the new fields.

Made the following changes in pipeline.py:

In the Examples section of the pipeline class doctoring, changed

Examples
--------
You can instantiate a pipeline instance as follow:
    >>> pipeline = Pipeline(collection="listingsAndReviews") # collection is the only mandatory attribute
                                                            # [example using MongoDB AirBnB demo dataset](https://www.mongodb.com/docs/atlas/sample-data/sample-airbnb/#std-label-sample-airbnb)
and then add stages to the pipeline by calling its wrapper stages method as shown below:

to

Examples
--------
The following examples use the example using MongoDB AirBnB demo dataset.
You can instantiate a pipeline instance as follow:

    >>> pipeline = Pipeline(collection="listingsAndReviews") # collection is the only mandatory attribute

and then add stages to the pipeline by calling its wrapper stages method as shown below:

for a better rendering.

[ ] virer expression partout (pipeline et stages)
[ ] séparer dans la doc de pipeline les méthodes associées aux stages, et les autres. (les grouper ensemble)
[ ] mettre privé tout ce qui est décoré par pyd.validator (n'apparaîtra plus dans la doc)
[ ] faire une PR
[ ] quand la PR est validée, recréer une nouvelle branche à partir de l'issue.


Refactored retrieving of remote projects and added support for FTP, Mercurial and Subversion

@harrah Should I now inline these simple methods like retrieveRODir and downloadAndExtract?

Ok, I'll add another run method later this day. Thanks for help!

 What happens if there are changes on remote between the 1st and the 2nd calls to the resolver? The changes are not pulled in, are they?

Updating of remote projects is still not supported in sbt, and it is on wishlist (number 3 on https://github.com/harrah/xsbt/wiki/Opportunities). I was thinking on implementing it when i finish with this pull request. But, i will probably need some guidance with that implementation.

@vigdorchik i fixed !file.exists and added second run method. can you check the code now?

I see. Case class was indeed a bad suggestion. Looks good to me once you make the last commit we discussed.

But what about when URI is not a directory thing?

I don't feel strongly about it.

@vigdorchik thanks

Don't arbitrarily introduce a symbolic method.  A normal method toStdout(...) would be fine.
However, output should go to a logger and not standard output.
Calling lines and then printing it converts the byte stream to a Stream back to a byte stream.  Just redirect the output to a logger.

As for the two-step procedure, I think it is worth the benefit unless there are fundamental problems.  If the current issues are minor things to work through, then let's just work through them.  If the code needs to be made more understandable, let's do that.
@saserr, I can see how it is likely to save time and space, but I don't know the exact details.  Can you be precise about what git does with respect to network access and hardlinking files?  What about on Windows? (does hardlinking exist there?)
@vigdorchik can you summarize your problems with the two-step process?

@harrah My point is that the additional caching step introduces new bug possibilities. Right now I only see the problem with a new branch created on remote, which is not tracked on local. Maybe there are other problems too. So in the least the current code should account for new branches.

@harrah idea is very simple. before, when two projects required two different branches of same repository, the code would clone the remote repository twice. new idea is to have a clean copy of repository locally for HEAD branch and clone from it, thus reducing number of remote clonings. first, copying data over network and on filesystem is order of magnitude faster. furthermore, both git and mercurial use hardlinks for immutable data (basically almost everything under .git and .hg) when local cloning is used. only fat32 does not support hardlinks and there both of them fallback to pure copying, but still this is much faster then getting data from remote repository.
@vigdorchik i might have another solution that would not require code to manually track remote branches.

I think the two step will be worth it, but I see @vigdorchik's point that there are some things to think about.  I think we agree the other parts are not controversial and should go in for 0.12.0.  Then, @saserr should split the two-step pieces out into a separate pull request and the other parts can get merged now.

Sorry for the delay. I removed the optimization and tested the code. Everything works fine and I think that it can be merged in.
I will continue to work on the optimization + I want to added logging into the code so user have much better feedback on what sbt is doing. I will create a new pull request as soon as I have working code.

@vigdorchik, ok to merge now?

@saserr @harrah I'm afraid there are more problems, namely reload doesn't recompile if the build definition file changed. This can be reproduced both trying to test manually and with 'sbt "scripted actions/reload"'. I didn't examine the exact source of the problem.

@vigdorchik I don't understand your problem. How do you reproduce the problem?

@saserr publish-local your version, then in a test project try 'reload' after making a change to .sbt file. Nothing is recompiled.

The problem is that a writeable local directory is always copied now instead of the previous behavior that used the project right out of the original directory.  Source dependencies aren't updated automatically, so the change isn't seen.
I've merged the commits and made this fix.

Thanks for all the help and patience with me.
@harrah How should updating of remote projects work? Should resolver just try to update the code when it sees that there is already a directory in staging for that project?


Support Swift 5.0

This adds support for Swift 5.0 and fixes a bug with the iSO6081 date formatter.

We don't currently support SPM, do we?

Hey, wanna point out for the record: I can't merge this.


Why not use micros duration granularity with .poll()?

We do use microsecond precision if it's supported by the OS, but e.g. epoll only allows us to specify the timeout in milliseconds.

Is it possible to use epoll_pwait2()?

No that was added in 5.11, we support older kernels.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/459 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

Docs Build status updates of commit ec30a83:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-04-20-06-17-02 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-04-20-06-17-02

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.


Swag generate empty path

Describe the bug
generate empty path, but in v1.8.2, it's ok
To Reproduce
Steps to reproduce the behavior:

run command 'swag init -g ./internal/server/http/apiv1.go -dir ./ --parseInternal'

Screenshots
project tree:

handler comment:
:

Your swag version
1.16.3
Your go version
1.21.4
Desktop (please complete the following information):

OS: ubuntu
Version: 20.04

Same issue here!

I also have the same issue and make some deep digs. I found that if your code path is in $ROOT or the path prefix is $ROOT, will filter out the source code.


[SUPPORT] Deltastreamer errors ingesting kafka-streams topics (transactional / exactly_once producers)

Describe the problem you faced
Deltastreamer, when being run on a transactional topic (one being produced to by a transactional producer, like kafka-streams) is unable to be read.
Caused by: java.lang.IllegalArgumentException: requirement failed:
 Failed to get records for compacted spark-executor-hudi-deltastreamer-my-transactional-topic my-transactional-topic-0 after polling for 1000

 OR when using AllowNonConsecutiveOffsets=false..

Caused by: org.apache.spark.SparkException: Job aborted due to stage failure: Task 0 in stage 4.0 failed 1 times, most recent failure: Lost task 0.0 in stage 4.0 (TID 4) (<IP_ADDRESS> executor driver): java.lang.IllegalArgumentException: requirement failed: Failed to get records for spark-executor-hudi-deltastreamer-my-transactional-topic my-transactional-topic-0 5 after polling for 1000
        at scala.Predef$.require(Predef.scala:281)
        at org.apache.spark.streaming.kafka010.InternalKafkaConsumer.get(KafkaDataConsumer.scala:143)

Full stack traces will be linked below.
Our configuration is as follows:

Note: this works fine on non-transactional topics, and compacted topics (cleanup.policy=compact) when setting AllowNonConsecutiveOffsets=true
Note: This isn't a networking issue or timeout issue which we'll discuss below.

hoodie.datasource.write.recordkey.field=viewtime
hoodie.datasource.write.partitionpath.field=pageid
hoodie.deltastreamer.source.kafka.topic=${topic}
hoodie.deltastreamer.schemaprovider.registry.url=[http://localhost:8081/subjects/${topic}-value/versions/latest](http://localhost:8081/subjects/$%7Btopic%7D-value/versions/latest)
schema.registry.url=http://localhost:8081/
# Kafka Consumer props
bootstrap.servers=localhost:9092
auto.offset.reset=earliest
# Consumer Group
group.id=hudi-deltastreamer-${topic}
#isolation.level=read_committed <-- tried adjusting this with no effect
#enable.auto.commit=false <-- tried adjusting this with no effect

# spark.properties
spark.streaming.kafka.allowNonConsecutiveOffsets=true <--  so we use this by default as some of our topics are compacted
spark.streaming.kafka.consumer.poll.ms=1000 <-- To make it fail faster, from default of 120,000
spark.executor.cores=1

spark-submit \
  --master local[1] \
  --num-executors=1 \
  --executor-cores=1 \
  --class org.apache.hudi.utilities.deltastreamer.HoodieDeltaStreamer \
  --conf "spark.driver.extraJavaOptions=${LOG4J_SETTING}" \
  --conf "spark.executor.extraJavaOptions=${LOG4J_SETTING}" \
  --properties-file ~/Sandbox/spark-sandbox/src/main/resources/spark.properties \
 ~/Workspace/github.com/apache/hudi/target/hudi-utilities-bundle_2.12-0.12.1.jar \
 --op INSERT \
 --props /tmp/hoodie-conf-${topic}.properties \
 --schemaprovider-class org.apache.hudi.utilities.schema.SchemaRegistryProvider \
 --source-class org.apache.hudi.utilities.sources.AvroKafkaSource \
 --source-ordering-field viewtime  \
 --table-type COPY_ON_WRITE \
 --target-base-path file://${target_base_path} \
 --target-table $target_table

We've identified that this is because the get() / compactedNext() method used by the InternalKafkaDataConsumer is failing to poll records/batches for these transactional topics..
If we create a simple non-compacted topic that we'll be writing to non-transactionally, and one transactionally:
kafka-topics --bootstrap-server localhost:9092 --create --topic my-transactional-topic --partitions 5
kafka-topics --bootstrap-server localhost:9092 --create --pageviews --partitions 5

# Following messages can be consumed when produced **without** transactional producer, but not with..
[{:viewtime 100 :userid "User_0" :pageid "Page_0"}
               {:viewtime 101 :userid "User_1" :pageid "Page_1"}
               {:viewtime 102 :userid "User_2" :pageid "Page_2"}
               ...etc...
               {:viewtime 115 :userid "User_15" :pageid "Page_15"}]

Produced 16 message non-transactionally -- as you can see the end/"next available" offset is the one after the last offset containing data in each partition

Produced 16 message transactionally -- as you can see the end/"next available" offset is 2 more than the last offset containing data in each partition, because the end of that batch of write placed a commit marker/offset message in each partition

And we see the stack traces mentioned at the bottom:
hoodie-allow-consecutive-off-false.log
hoodie-allow-consecutive-off-true.log
Notably
Extra Information gathered from running this locally
Dive into our local example showing how we get the poll of [topic-partition] 5, followed by a poll of [] 0, followed by the crash when AllowNonConsecutiveOffsets=true
Interestingly, in the below, when setting AllowNonConsecutiveOffsets=False, we see that the initial poll for the partition 0 (which from the above screenshot, showed offset 0->4 being valid messages, offset 5 being the commit marker, has it poll those first 5 messages, then fail on the next poll.
23/03/21 12:48:57 INFO org.apache.spark.streaming.kafka010.KafkaRDD: Computing topic my-transactional-topic, partition 0 offsets 0 -> 6
23/03/21 12:48:57 DEBUG org.apache.spark.streaming.kafka010.KafkaDataConsumer: Not used cached consumer found, re-using it InternalKafkaConsumer(hash=511066e5, groupId=spark-executor-hudi-deltastreamer-my-transactional-topic, topicPartition=my-transactional-topic-0)
23/03/21 12:48:57 DEBUG org.apache.spark.streaming.kafka010.InternalKafkaConsumer: Get spark-executor-hudi-deltastreamer-my-transactional-topic my-transactional-topic-0 nextOffset 1 requested 0
23/03/21 12:48:57 INFO org.apache.spark.streaming.kafka010.InternalKafkaConsumer: Initial fetch for spark-executor-hudi-deltastreamer-my-transactional-topic my-transactional-topic-0 0
23/03/21 12:48:57 DEBUG org.apache.spark.streaming.kafka010.InternalKafkaConsumer: Seeking to my-transactional-topic-0 0
23/03/21 12:48:57 DEBUG org.apache.spark.streaming.kafka010.InternalKafkaConsumer: Polled [my-transactional-topic-0]  5
23/03/21 12:48:57 DEBUG org.apache.spark.streaming.kafka010.InternalKafkaConsumer: Get spark-executor-hudi-deltastreamer-my-transactional-topic my-transactional-topic-0 nextOffset 1 requested 1
23/03/21 12:48:57 DEBUG org.apache.spark.streaming.kafka010.InternalKafkaConsumer: Get spark-executor-hudi-deltastreamer-my-transactional-topic my-transactional-topic-0 nextOffset 2 requested 2
23/03/21 12:48:57 DEBUG org.apache.spark.streaming.kafka010.InternalKafkaConsumer: Get spark-executor-hudi-deltastreamer-my-transactional-topic my-transactional-topic-0 nextOffset 3 requested 3
23/03/21 12:48:57 DEBUG org.apache.spark.streaming.kafka010.InternalKafkaConsumer: Get spark-executor-hudi-deltastreamer-my-transactional-topic my-transactional-topic-0 nextOffset 4 requested 4
23/03/21 12:48:57 DEBUG org.apache.spark.streaming.kafka010.InternalKafkaConsumer: Get spark-executor-hudi-deltastreamer-my-transactional-topic my-transactional-topic-0 nextOffset 5 requested 5
23/03/21 12:48:58 DEBUG org.apache.spark.streaming.kafka010.InternalKafkaConsumer: Polled []  0
23/03/21 12:48:59 WARN org.apache.spark.storage.BlockManager: Putting block rdd_2_0 failed due to exception java.lang.IllegalArgumentException: requirement failed: Failed to get records for spark-executor-hudi-deltastreamer-my-transactional-topic my-transactional-topic-0 5 after polling for 1000.

If we create another topic with one partition and write a single batch of 16 records transactionally (so 0->15 is data, 16 is commit marker, end of topic is 17), we see similar behaviour.
my-transactional-topic-single-partition.log
If we remove the possibility that it might be crashing because the endOffset is the "invisible" marker that it can't read, by adding another 16 records (putting 17->32 as data, 33 as the marker and 34 as endOffset), we see a similar issue with the following:
requirement failed: Got wrong record for spark-executor-hudi-deltastreamer-my-transactional-topic-single-partition my-transactional-topic-single-partition-0 even after seeking to offset 16 got offset 17 instead. If this is a compacted topic, consider enabling spark.streaming.kafka.allowNonConsecutiveOffsets

my-transactional-topic-single-partition-32-msgs.log
Changing to AllowNonConsecutiveOffsets=true on the above topic yields the following:
23/03/21 13:24:10 INFO org.apache.spark.streaming.kafka010.KafkaRDD: Computing topic my-transactional-topic-single-partition, partition 0 offsets 0 -> 34
23/03/21 13:24:10 DEBUG org.apache.spark.streaming.kafka010.KafkaDataConsumer: Not used cached consumer found, re-using it InternalKafkaConsumer(hash=9903e40, groupId=spark-executor-hudi-deltastreamer-my-transactional-topic-single-partition, topicPartition=my-transactional-topic-single-partition-0)
23/03/21 13:24:10 DEBUG org.apache.spark.streaming.kafka010.InternalKafkaConsumer: compacted start spark-executor-hudi-deltastreamer-my-transactional-topic-single-partition my-transactional-topic-single-partition-0 starting 0
23/03/21 13:24:10 INFO org.apache.spark.streaming.kafka010.InternalKafkaConsumer: Initial fetch for compacted spark-executor-hudi-deltastreamer-my-transactional-topic-single-partition my-transactional-topic-single-partition-0 0
23/03/21 13:24:10 DEBUG org.apache.spark.streaming.kafka010.InternalKafkaConsumer: Seeking to my-transactional-topic-single-partition-0 0
23/03/21 13:24:10 DEBUG org.apache.spark.streaming.kafka010.InternalKafkaConsumer: Polled [my-transactional-topic-single-partition-0]  32
23/03/21 13:24:10 INFO org.apache.spark.storage.BlockManager: Removing RDD 6
23/03/21 13:24:11 DEBUG org.apache.spark.streaming.kafka010.InternalKafkaConsumer: Polled []  0
23/03/21 13:24:11 WARN org.apache.spark.storage.BlockManager: Putting block rdd_2_0 failed due to exception java.lang.IllegalArgumentException: requirement failed: Failed to get records for compacted spark-executor-hudi-deltastreamer-my-transactional-topic-single-partition my-transactional-topic-single-partition-0 after polling for 1000.
23/03/21 13:24:11 WARN org.apache.spark.storage.BlockManager: Block rdd_2_0 could not be removed as it was not found on disk or in memory
23/03/21 13:24:11 ERROR org.apache.spark.executor.Executor: Exception in task 0.0 in stage 4.0 (TID 4)
java.lang.IllegalArgumentException: requirement failed: Failed to get records for compacted spark-executor-hudi-deltastreamer-my-transactional-topic-single-partition my-transactional-topic-single-partition-0 after polling for 1000

Stack trace for the above:
my-transactional-topic-single-partition-allownonconsecutiveoffsetsTrue.log
Answers Required
So we know what the problem is, we are just unsure on how to fix.
We've taken this to the hudi office hours before and the host suggested to ask @yihua for advice.
Usual Environment in Production, but all of this has been reproduced locally
Hudi version : Deltastreamer on EMR 6.8.0 running Hudi 0.11.1-amzn-0
Spark version : 3.3.0
Hive version : 3.1.3
Hadoop version : Amazon 3.2.1
Storage (HDFS/S3/GCS..) : S3
Running on Docker? (yes/no) : No
Additional context
hudi 0.12.1 used for local testing
Can add more details if required.
Stacktrace
Stacktraces have been littered throughout but pasted here again:
my-transactional-topic-single-partition-32-msgs.log
my-transactional-topic-single-partition-allownonconsecutiveoffsetsTrue.log
hoodie-allow-consecutive-off-false.log
hoodie-allow-consecutive-off-true.log
my-transactional-topic-single-partition.log

I am able to reproduce your issue with HoodieDeltaStreamer. We are looking into this issue.
meanwhile you can use spark structured streaming to read the data from transactional topic and write to Hudi. I am not seeing any error while using the structured streaming. Below is the code you can refer.
`import io.confluent.kafka.schemaregistry.client.rest.RestService
import io.confluent.kafka.serializers.KafkaAvroDeserializer
import org.apache.avro.Schema
val schemaRegistryURL = "http://localhost:8081"
val topicName = "issue_8258_avro"
val subjectValueName = topicName + "-value"
//create RestService object
val restService = new RestService(schemaRegistryURL)
val valueRestResponseSchema = restService.getLatestVersion(subjectValueName)
//Use Avro parsing classes to get Avro Schema
val parser = new Schema.Parser
val topicValueAvroSchema: Schema = parser.parse(valueRestResponseSchema.getSchema)
//key schema is typically just string but you can do the same process for the key as the value
val keySchemaString = ""string""
val keySchema = parser.parse(keySchemaString)
//Create a map with the Schema registry url.
//This is the only Required configuration for Confluent's KafkaAvroDeserializer.
val props = Map("schema.registry.url" -> schemaRegistryURL)
//Declare SerDe vars before using Spark structured streaming map. Avoids non serializable class exception.
var keyDeserializer: KafkaAvroDeserializer = null
var valueDeserializer: KafkaAvroDeserializer = null
//Create structured streaming DF to read from the topic.
val rawTopicMessageDF = spark.readStream.format("kafka").option("kafka.bootstrap.servers", "localhost:9092").option("subscribe", topicName).option("startingOffsets", "earliest").option("maxOffsetsPerTrigger", 20).load()
import org.apache.hudi.QuickstartUtils._
import scala.collection.JavaConversions._
import org.apache.spark.sql.SaveMode._
import org.apache.hudi.DataSourceReadOptions._
import org.apache.hudi.DataSourceWriteOptions._
import org.apache.hudi.config.HoodieWriteConfig._
import org.apache.hudi.common.model.HoodieRecord
import org.apache.spark.sql.streaming.Trigger
rawTopicMessageDF.writeStream.format("hudi").
options(getQuickstartWriteConfigs).
option(PRECOMBINE_FIELD_OPT_KEY, "timestamp").
option(RECORDKEY_FIELD_OPT_KEY, "offset").
option(TABLE_NAME, topicName).
outputMode("append").
option("path", "file:///tmp/" + topicName).
option("checkpointLocation", "file:///tmp/ck_" + topicName).
trigger(Trigger.Once()).
start()
spark.read.format("hudi").load("file:///tmp/" + topicName).count()

`

Thanks @ad1happy2go
We are also leaning towards using either Spark Structured streaming or Batch processing as a workaround. We have some working examples for both cases now, thanks again for sharing your example code too
Could you confirm if we need to have a separate process for compaction when using Spark Structured streaming for writing to Hudi?

@WarFox
We can either use async compaction enable or offline compaction job.
With streaming, we normally don't use inline compaction job as that will increase the latency.

@danielfordfc JIRA created for the tracking the fix - https://issues.apache.org/jira/browse/HUDI-6297

@ad1happy2go @nsivabalan is this absolutely not going to happen anytime soon? It's preventing us from directly ingesting a large majority of our Kafka topics in our organisation and i'm very surprised it's not a more widely experienced issue, given its a common feature of topics produced through kafka-streams applications

Currently I didn't had any viable solution to fix this. Not sure if anybody is looking into it currently. So it is not going to happen anytime soon.
@bvaradar Do you have any insights how can we handle transactional topics? PR - https://github.com/apache/hudi/pull/9059


[bug] Failed to perform inference on the optimized distil-large-v3 using the test_transcription.py

I optimized the distil-large-v3 model using Olive:
Step 1:
python3 prepare_whisper_configs.py --model_name /share_model_zoo/LLM/distil-whisper/distil-large-v3/

Step 2:
python3 -m olive.workflows.run --config whisper_gpu_fp32.json --setup

Step 3:
python3 -m olive.workflows.run --config whisper_gpu_fp32.json 2> /dev/null

Then, I realized that the optimized model is still larger than 2GB. Since ONNX forcibly splits models larger than 2GB into two files: model_with_beam_search.onnx.data and model_with_beam_search.onnx,
I referred to the https://github.com/microsoft/Olive/blob/main/examples/whisper/test_transcription.py script to perform inference on the model, but encountered an error:
input_data = OnnxEvaluator.format_input(input_data, olive_model.get_io_config())
                                                        ^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'ONNXModelHandler' object has no attribute 'get_io_config'. Did you mean: '_io_config'?

Even after changing it to:
input_data = OnnxEvaluator.format_input(input_data, olive_model._io_config())

It still throws an error:
input_data = OnnxEvaluator.format_input(input_data, olive_model._io_config())
                                                        ^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not callable

How should I modify the test_transcription.py script to perform inference on the distil-whisper/distil-large-v3/ model optimized using the whisper_gpu_fp32.json configuration?

it needs to be olive_model.io_config https://github.com/microsoft/Olive/blob/064e9a60f5cedfdb5a6f1b7f9434d4ce5a8396fe/examples/whisper/test_transcription.py#L122
Can you try that change?

@jambayk
It still throws an error:
input_data = OnnxEvaluator.format_input(input_data, olive_model._io_config())

                                                        ^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not callable

@jambayk Have you encountered the following problems?  AttributeError: 'ONNXModelHandler' object has no attribute 'run_session'

@jambayk Have you encountered the following problems? AttributeError: 'ONNXModelHandler' object has no attribute 'run_session'

this is a weird bug @jambayk  . I have used some functions to test such as dir(olive_model) , ONNXModelHandler.__dict__. There is no run_session although run_session is implemeted inside ONNXModelHandler

Quick fix for @MrRace : just replace output = olive_model.run_session(session, input_data) to output = session.run(None, input_data)

The examples on the repo are updated to work with the latest code on main. Could you please pull the latest code and also install Olive from source https://microsoft.github.io/Olive/getstarted/installation.html#install-from-source
You could also checkout the tags for specific versions of Olive https://github.com/microsoft/Olive/tree/main/examples#important

The examples on the repo are updated to work with the latest code on main. Could you please pull the latest code and also install Olive from source https://microsoft.github.io/Olive/getstarted/installation.html#install-from-source
You could also checkout the tags for specific versions of Olive https://github.com/microsoft/Olive/tree/main/examples#important

Thanks a lot, it works


Upgrade to Laravel 9

Hi, I hope you are well
Since Laravel 9 has been released for almost two weeks, do you have any plans to upgrade to Laravel 9?

Hi @AmooAti
We will update bagisto  with Laravel-9

@jitendra-webkul
Thanks, now Laravel 9 upgraded. so I am closing this enhancement.