[Bug] On clicking AdvanceMarker to open  InfoWindow, goes into an Infinite loop of rendering on setting  markerRef(marker) manually

Description
I am using the Cluster example the docs with MarkerWithInfoWindow, however there is nothing much i changed for cluster or infowindow from the docs... onClick on the marker should have open the infowindow, but instead to goes in an infinite loop.
Please note that i am setting the markerRef(marker); on the ref of AdvanceMarker manually because i want to support Cluster along with it... it appears to be a standard way to me to set ref to multiple places for marker... however it crashes
const MarkerWithInfoWindow = forwardRef<
  AdvancedMarkerRef,
  AdvancedMarkerProps & {
    point: Point;
    setMarkerRef: (marker: Marker | null, key: number) => void;
  }
>(({ point, setMarkerRef, ...props }, ref) => {
  let [markerRef, marker] = useAdvancedMarkerRef();
  const [infoWindowOpen, setInfoWindowOpen] = useState(false);

  return (
    <>
      <AdvancedMarker
        ref={(marker1) => {
          markerRef(marker1);
          setMarkerRef(marker1, point.key);
        }}
        onClick={(e) => {
          setInfoWindowOpen(true);
        }}
        position={point}
        title={point.name}
        zIndex={50}
        {...props}
      />
      {infoWindowOpen && (
        <InfoWindow anchor={marker} maxWidth={200} onCloseClick={() => setInfoWindowOpen(false)}>
          <AdvancedMarker /> combined with an
          Infowindow.
        </InfoWindow>
      )}
    </>
  );
});

Steps to Reproduce
I am using next 14, and this is a client component.

Click on the marker and it goes on an infinite loop and hence the app crashes.

Environment

Library version<EMAIL_ADDRESS>"^1.0.2",
Google maps version: 3.57.3a
Browser and Version: Chrome 125.0.6422.141 (Official Build) (64-bit)
OS: Linux ( Ubuntu )

Logs

I think I have an Idea whats happening:

rendering this component will eventually invoke the ref-callback of the AdvancedMarker
via markerRef() this will update the marker state-variable, causing the component to re-render
when re-rendering, the ref- and onClick- props of the AdvancedMarker are changed, so the AM needs to re-render as well
this causes the ref to be updated, so we're back at step 1.

To mitigate, it should be enough to memoize the two callbacks you're passing to AdvancedMarker, which is a good practice anyway...
const MarkerWithInfoWindow = forwardRef<
  AdvancedMarkerRef,
  AdvancedMarkerProps & {
    point: Point;
    setMarkerRef: (marker: Marker | null, key: number) => void;
  }
>(({ point, setMarkerRef, ...props }, ref) => {
  let [markerRef, marker] = useAdvancedMarkerRef();
  const [infoWindowOpen, setInfoWindowOpen] = useState(false);

  const refCallback = useCallback((marker1) => {
    markerRef(marker1);
    setMarkerRef(marker1, point.key);
  }, [setMarkerRef, point.key]);

  const handleClick = useCallback((e) => {
    setInfoWindowOpen(true);
  }, []);

  return (
    <>
      <AdvancedMarker
        ref={refCallback}
        onClick={handleClick}
        position={point}
        title={point.name}
        zIndex={50}
        {...props}
      />
      {infoWindowOpen && (
        <InfoWindow anchor={marker} maxWidth={200} onCloseClick={() => setInfoWindowOpen(false)}>
          <AdvancedMarker /> combined with an
          Infowindow.
        </InfoWindow>
      )}
    </>
  );
});

handleClick

Great, i will check on it.. however its a bit of confusion that a ref update can cause re-render, since in react, refs are global to the component lifecycle and updating it should not re-render the component.
Let me know if there misunderstanding on implementation of ref or how it should work ?

This case is slightly different – since we need to react to changing of the ref (update the anchor of the infowindow when the marker API-element is available), useAdvancedMarkerRef uses the ref-callback format together with a state-variable signalling changing of the property and triggering a re-render. Normally this isn't a problem since the callback is memoized and doesn't trigger a re-render by itself. In your case, when the ref-callback isn't memoized, you'll potentially run into problems.
I'm always open to suggestions how to architect this differently, but as far as I am aware this is the best solution we have available to build the connection of the  marker to the infowindow.

This case is slightly different – since we need to react to changing of the ref (update the anchor of the infowindow when the marker API-element is available), useAdvancedMarkerRef uses the ref-callback format together with a state-variable signalling changing of the property and triggering a re-render. Normally this isn't a problem since the callback is memoized and doesn't trigger a re-render by itself. In your case, when the ref-callback isn't memoized, you'll potentially run into problems.
I'm always open to suggestions how to architect this differently, but as far as I am aware this is the best solution we have available to build the connection of the marker to the infowindow.

ah i see...
This code  is not directly related with ref.. it's just saving into state so that can be reused for infowindow anchor:
export function useAdvancedMarkerRef() {
  const [marker, setMarker] =
    useState<google.maps.marker.AdvancedMarkerElement | null>(null);

  const refCallback = useCallback((m: AdvancedMarkerRef | null) => {
    setMarker(m);
  }, []);

  return [refCallback, marker] as const;
}

the term ref in useAdvancedMarkerRef was a confusion, as i was in assumption that its using useRef or createRef underneath to store the marker which is exposed to infowindow.. However, to update the infowindow it needs useState to re-render.
Just my few cents:
Can we store marker in useRef and useState for open and close states... it's simple and reflect the terminology used.
const markerRef = useRef<google.maps.marker.AdvancedMarkerElement | null>(null);
const [infoWindowOpen, setInfoWindowOpen] = useState(false);

const refCallback = useCallback((marker) => {
  markerRef.current = marker;
  setMarkerRef(marker, point.key);
}, [setMarkerRef, point.key]);

const handleClick = useCallback((e) => {
  setInfoWindowOpen(true);
}, []);

return (
  <>
    <AdvancedMarker
      ref={refCallback}
      onClick={handleClick}
      position={point}
      title={point.name}
      zIndex={50}
      {...props}
    />
    {infoWindowOpen && markerRef.current && (
      <InfoWindow anchor={markerRef.current} maxWidth={200} onCloseClick={() => setInfoWindowOpen(false)}>
        <AdvancedMarker /> combined with an
        Infowindow.
      </InfoWindow>
    )}
  </>
)

if you want to open the marker by default then use the useEffect for mount (with no deps) , to update   setInfoWindowOpen(true); .    🤔

That's interesting to read and I understand the confusion. Originally, React only had the CallbackRef style refs, iirc the newer style (mutable object ref) that we now know as 'ref' was introduced together with hooks in 16.8, probably precisely because of the problems the callbacks can have. Still, both are valid formats for a ref.
Your suggestion will probably work as well, but you the component will not notice when the ref'd object (the google.maps.marker.AdvancedMarkerElement) is set. It will only work because you trigger a re-render by setting the infoWindowOpen state after the marker is already rendered (and thus the ref.current having a value). If, for whatever reason, this wasn't the case, the infowindow would have no anchor.
Also let me note that the documentation is pretty clear about not using ref.current during rendering:

Do not write or read ref.current during rendering.
React expects that the body of your component behaves like a pure function:

If the inputs (props, state, and context) are the same, it should return exactly the same JSX.
Calling it in a different order or with different arguments should not affect the results of other calls.

Reading or writing a ref during rendering breaks these expectations.

Ah great explanation, thanks for pointing out the best practice. 🙏🏼

If, for whatever reason, this wasn't the case, the infowindow would have no anchor.
however, this was a bit ambiguous to understand, usually it always works or in my experience on mounted there's DOM available.

just that: if the internal marker object in markerRef.current has – for whatever reason – not yet been created when this condition is evaluated:
{infoWindowOpen && markerRef.current && ( ... ) }

There'll be no re-render once it is available, so no way to recover from that.

I'll convert this to a discussion, it doesn't look like theres an actual bug in our library here.


Making subscriptions comment more clear

Just a quick clarification. Thanks so much for publishing this @rtfeldman !

I dig it. Thanks @jasondew!


[terraform] Try to workaround instance type change issue

When the instance type is changed the instance boots with the same EBS
root value on a clean machine. This means that the instance store is
empty, but still referenced in fstab, causing a boot error. This adds
nofail to the fstab entry to allow boot to continue.

Tested on a fresh workspace, initial format and mount still works.

@bors-libra r=andll

:pushpin: Commit 8907fbc has been approved by andll

:hourglass: Testing commit 8907fbcb2043ca72ca1cf74f30a60283bec1b74b with merge e3327b5cd1e625f7f062c1055330f7209e5f402d...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: andll
Pushing e3327b5cd1e625f7f062c1055330f7209e5f402d to master...


bottle.rb: add workaround to make gcc have cellar :any

…LINKS

[ ] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ ] 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.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

This is a followup to https://github.com/Homebrew/linuxbrew-core/pull/23361.  I followed the suggestion from @iMichka to add a regex to exclude the nonrelocatable strings inside the GCC formulae.  For many years :any was manually added to the GCC cellar block on Linux so we know it works.  This should guarantee this happens from now on.

Review period will end on 2021-08-24 at 00:00:00 UTC.

ALLOWABLE_HOMEBREW_REPOSITORY_LINKS is purely about exceptions to the HOMEBREW_REPOSITORY rule, which hard blocks rather than simply mark as non-relocatable.

Okay, what's the best place to add this exception?  Perhaps in the ignores regex:
ignores = [%r{/include/|\.(c|cc|cpp|h|hpp)$}]

I was able to change that to
ignores = [%r{/include/|\.(c|cc|cpp|h|hpp)$|#{cellar}/gcc}]

and it also made the gcc bottles relocatable.

Something like that, yes.
Can you clarify here what the references are? We don't have the issue on macOS so I'm interested what might be different.

Oh sorry, we do have the issue on macOS. Someone just changed the macOS line in the PR you linked.

Yeah, let me post the strings below.  I'm happy to explore other solutions even outside of bottle.rb - this was just a starting point.
Warning: String '/home/linuxbrew/.linuxbrew/Cellar' still exists in these files:
<EMAIL_ADDRESS> --> match<EMAIL_ADDRESS>at offset 0x12160
 --> match<EMAIL_ADDRESS>at offset 0x121a0
 --> match<EMAIL_ADDRESS>at offset 0x121e0
<EMAIL_ADDRESS> --> match<EMAIL_ADDRESS>at offset 0x12160
 --> match<EMAIL_ADDRESS>at offset 0x121a0
 --> match<EMAIL_ADDRESS>at offset 0x121e0
<EMAIL_ADDRESS> --> match<EMAIL_ADDRESS>at offset 0x7aef8
 --> match<EMAIL_ADDRESS>at offset 0x7af38
 --> match<EMAIL_ADDRESS>at offset 0x7af78
 --> match<EMAIL_ADDRESS>at offset 0x82f90
<EMAIL_ADDRESS> --> match<EMAIL_ADDRESS>at offset 0x12160
 --> match<EMAIL_ADDRESS>at offset 0x121a0
 --> match<EMAIL_ADDRESS>at offset 0x121e0
<EMAIL_ADDRESS> --> match<EMAIL_ADDRESS>at offset 0x79ef8
 --> match<EMAIL_ADDRESS>at offset 0x79f38
 --> match<EMAIL_ADDRESS>at offset 0x79f78
 --> match<EMAIL_ADDRESS>at offset 0x81f50
<EMAIL_ADDRESS> --> match<EMAIL_ADDRESS>at offset 0x7aef8
 --> match<EMAIL_ADDRESS>at offset 0x7af38
 --> match<EMAIL_ADDRESS>at offset 0x7af78
 --> match<EMAIL_ADDRESS>at offset 0x83110
<EMAIL_ADDRESS> --> match<EMAIL_ADDRESS>at offset 0x7aef8
 --> match<EMAIL_ADDRESS>at offset 0x7af38
 --> match<EMAIL_ADDRESS>at offset 0x7af78
 --> match<EMAIL_ADDRESS>at offset 0x82ff0
<EMAIL_ADDRESS> --> match<EMAIL_ADDRESS>at offset 0x112c380
 --> match<EMAIL_ADDRESS>at offset 0x112c3e0
 --> match<EMAIL_ADDRESS>at offset 0x112c420
 --> match<EMAIL_ADDRESS>at offset 0x112c778
 --> match<EMAIL_ADDRESS>at offset 0x112c7e0
 --> match<EMAIL_ADDRESS>at offset 0x112c818
 --> match<EMAIL_ADDRESS>at offset 0x1140300
<EMAIL_ADDRESS> --> match<EMAIL_ADDRESS>at offset 0xde1540
 --> match<EMAIL_ADDRESS>at offset 0xde15a0
 --> match<EMAIL_ADDRESS>at offset 0xde15e0
 --> match<EMAIL_ADDRESS>at offset 0xde1938
 --> match<EMAIL_ADDRESS>at offset 0xde19a0
 --> match<EMAIL_ADDRESS>at offset 0xde19d8
 --> match<EMAIL_ADDRESS>at offset 0x11988e0
<EMAIL_ADDRESS> --> match<EMAIL_ADDRESS>at offset 0xd041a0
 --> match<EMAIL_ADDRESS>at offset 0xd04200
 --> match<EMAIL_ADDRESS>at offset 0xd04240
 --> match<EMAIL_ADDRESS>at offset 0xd04598
 --> match<EMAIL_ADDRESS>at offset 0xd04600
 --> match<EMAIL_ADDRESS>at offset 0xd04638
 --> match<EMAIL_ADDRESS>at offset 0x10bb6c0
<EMAIL_ADDRESS> --> match<EMAIL_ADDRESS>at offset 0xcd8b40
 --> match<EMAIL_ADDRESS>at offset 0xcd8ba0
 --> match<EMAIL_ADDRESS>at offset 0xcd8be0
 --> match<EMAIL_ADDRESS>at offset 0xcd8f38
 --> match<EMAIL_ADDRESS>at offset 0xcd8fa0
 --> match<EMAIL_ADDRESS>at offset 0xcd8fd8
 --> match<EMAIL_ADDRESS>at offset 0x1090080
<EMAIL_ADDRESS> --> match<EMAIL_ADDRESS>at offset 0xe0da20
 --> match<EMAIL_ADDRESS>at offset 0xe0da80
 --> match<EMAIL_ADDRESS>at offset 0xe0dac0
 --> match<EMAIL_ADDRESS>at offset 0xe0de18
 --> match<EMAIL_ADDRESS>at offset 0xe0de80
 --> match<EMAIL_ADDRESS>at offset 0xe0deb8
 --> match<EMAIL_ADDRESS>at offset 0x11c4da0

Oh sorry, we do have the issue on macOS. Someone must have manually changed the macOS line in the PR you linked.

Interesting.  Anyway, GCC is designed to be portable so these strings should be ignored regardless of OS.

I pushed a change to add something to the ignore regex that I know will work for GCC.  Hopefully this is a better solution.

GCC is designed to be portable

Everyone says so, but is this officially documented upstream?
Looking at the long list of /home/linuxbrew/.linuxbrew/Cellar/ paths in the binaries, somethings tells me that stuff might still break in unexpected fashion (and hard to debug maybe) in non-default prefixes?

The documentation of GCC_EXEC_PREFIX somewhat describes a behaviour where the full include paths (e.g<EMAIL_ADDRESS>have the "configured prefix" (which should be<EMAIL_ADDRESS>swapped with the value of that env (the env itself is determined automatically if not specified).
That's about as far as I know regarding the matter.

I pushed a change to add something to the ignore regex that I know will work for GCC

Maybe we should actually limit this to the GCC formulae so that a potential dependent that includes GCC prefixes is still flagged.

Review period ended.

Thanks for the additional feedback.  A few more thoughts:

I think @Bo98 is right that GCC figures out the right prefix automatically at run time.  This thread on the GCC mailing list also says clearly that a GCC installation can be moved so long as the whole directory tree is moved together (which we are doing here): https://gcc-help.gcc.gnu.narkive.com/GnwuCA7l/moving-gcc-from-the-installation-path-is-it-allowed.  I'd also like to hear from @sjackman on this when he has a chance to reply, as he has a lot of knowledge on GCC.

I would definitely like to restrict this to GCC formulae.  If anyone has suggestions on the best way to do this I'm happy to change it accordingly.  I would rather avoid even messing with ignores and just having a hard override for GCC on Linux here.  GCC is special on Linux because pretty much everything depends on it, so making it specific is reasonable.

I think the ultimate long term solution for this is https://github.com/Homebrew/brew/issues/10846 and I'm almost certain that would work for GCC as it's already used by Anaconda, but I want to wait for the core merge to finish before putting serious work into that.  For now I'm just hoping we can find a safe, simple workaround because GCC is a critical dependency and a large percentage of the Linux user base has to use non-default prefixes.  We get a lot of support issues right now from users who are needlessly strugglingly to build GCC from source when it can be used as a bottle.

I think @Bo98 is right that GCC figures out the right prefix automatically at run time.  This thread on the GCC mailing list also says clearly that a GCC installation can be moved so long as the whole directory tree is moved together (which we are doing here): https://gcc-help.gcc.gnu.narkive.com/GnwuCA7l/moving-gcc-from-the-installation-path-is-it-allowed.  I'd also like to hear from @sjackman on this when he has a chance to reply, as he has a lot of knowledge on GCC.

Cool, this is exactly what I'd like to see as a comment in the source.

I would definitely like to restrict this to GCC formulae.  If anyone has suggestions on the best way to do this I'm happy to change it accordingly.  I would rather avoid even messing with ignores and just having a hard override for GCC on Linux here.  GCC is special on Linux because pretty much everything depends on it, so making it specific is reasonable.

I'd still like to see some sort of "ignores" just in case we accidentally add a hardcoded path through our formula changes and don't notice.

3. I think the ultimate long term solution for this is Use binary patching to improve relocatability of bottles #10846 and I'm almost certain that would work for GCC as it's already used by Anaconda, but I want to wait for the core merge to finish before putting serious work into that.  For now I'm just hoping we can find a safe, simple workaround because GCC is a critical dependency and a large percentage of the Linux user base has to use non-default prefixes.  We get a lot of support issues right now from users who are needlessly strugglingly to build GCC from source when it can be used as a bottle.

I agree that could be a good long-term solution. I'm more optimistic it will be for these sorts of cases where we know they are already working on Anaconda than globally.

Your understanding is correct. Also true for binutils, which is currently flagged as non-relocatable, but is in fact similarly relocatable. Having formulae in the compiler toolchain flagged as relocatable is particularly helpful to the user experience of bootstrapping a new Homebrew on Linux installation.

I'm fine with us adding more and more of these formula-specific tweaks to bottling logic and then reverting them on user complaints. We may want to move them to a dedicated file i.e. bottle_formula_tweaks.rb or something.

Apologies for lapsing on this, I got everything fixed and I'm going to push a new version.

I made a few changes here to pass brew style, and to deal with the fact that Formula.versioned_formulae wasn't behaving as expected.  Now I've used Version.formula_optionally_versioned_regex to do a regex match to the formula name that should handle versions properly.  I had to move a lot of the logic into a new method in order to pass the AbcSize audit, but I tested gcc and binutils and it works like it did before.

Looks great, thanks @danielnachun and sorry for all the back and forth!


Fix ops on different frames for multi-index columns support.

Codecov Report

Merging #713 into master will decrease coverage by 2.38%.
The diff coverage is 98.64%.

@@            Coverage Diff             @@
##           master     #713      +/-   ##
==========================================
- Coverage   94.01%   91.63%   -2.39%
==========================================
  Files          32       32
  Lines        5548     5557       +9
==========================================
- Hits         5216     5092     -124
- Misses        332      465     +133

Impacted Files
Coverage Δ

databricks/koalas/indexing.py
92.51% <100%> (+0.08%)
:arrow_up:

databricks/koalas/utils.py
97.24% <100%> (-0.75%)
:arrow_down:

databricks/koalas/frame.py
93.2% <96.15%> (-1.63%)
:arrow_down:

databricks/koalas/usage_logging/__init__.py
23.14% <0%> (-74.08%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
50% <0%> (-50%)
:arrow_down:

databricks/koalas/__init__.py
76.92% <0%> (-7.7%)
:arrow_down:

databricks/conftest.py
90.69% <0%> (-6.98%)
:arrow_down:

databricks/koalas/namespace.py
88.62% <0%> (-1.57%)
:arrow_down:

databricks/koalas/plot.py
93.64% <0%> (-1.16%)
:arrow_down:

... and 4 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8b62fcc...36387c4. Read the comment docs.

Nice!


Add support for Windows Server domain user

Add support for Windows Server domain users over windows policies.
A user need interactive rights.

Please, check again

why close, I just reopend that PR

Sorry, wrong button.


forget password page

#fixes(issue-200)
I have made a forget password page

@kumarishalini6 please share a video with forget password working!

Ok

I am not good at backend , I have tried but not working


i do the same steps but didnt work no transltion

i do the same steps but didn't work any translation
i try it on other server and work
but on new vps  host it isn't worked

Hi,

Please follow this instruction: https://github.com/mageplaza/magento-2-french-language-pack#2-how-to-install-french-language-pack to install this. We have translated 56%(this current time).

ok , thanks , it is working now


package.json repository attribute

The NPM page for this code doesn't have a link to its source repository.
https://www.npmjs.com/package/next-intercom
I think if you add the repository attribute to package.json it would help developers discover and review the source code or file issues.
Thanks

@grempe thanks for the issue. This should be fixed now https://github.com/j-mendez/next-intercom/commit/0badb0e9425ddcd21730122244a742ebad279b4b.


ddev import-db - misleading error

What happened (or feature request):
I've created configuration file manually.
I've run command ddev import-db --src=typo3.sql
This command resulted in an red error like:
Failed to import database for typo3-core-master: failed to write settings file for typo3-core-master: Failed to get Typo3 AdditionalConfiguration.php file path: settings files already exist and are being managed by the user

I've checked the DB and all data is in there, so the dump went through successfully.
It's also quite surprising that ddev import-db is trying to create a config for me. I would expect that this happens when calling ddev configure or ddev start.
What you expected to happen:
I would expect a success message, maybe with a warning that config file is managed manually.
How to reproduce this:
Version: Please include the output of ddev version, docker version and the project's .ddev/config.yaml.
ddev version
cli   	v0.12.0
web   	drud/nginx-php-fpm-local:v0.9.1
db    	drud/mariadb-local:v0.7.1
dba   	drud/phpmyadmin:v0.2.0
router	drud/ddev-router:v0.5.0
commit	v0.12.0
domain	ddev.local
Anything else do we need to know:
Related source links or issues:
Please use a complexity rating of 1-5 (5 is high) for a feature request. (High complexity implies more PR planning)

I'm quite sure this is a duplicate of https://github.com/drud/ddev/issues/451

Right, havent seen the other one. Lets close this one then.


Common: Fix broken compilation for trees without the PISTACHE_USE_SSL option

Due to a brain-lag on my end, I've introduced a regression in commit
44e40478d604746963b898efd463a541ebbea824, because a SSL utility function
was compiling whether or not the SSL was enabled. It is now fixed,
apologies.
Pull Request: https://github.com/oktal/pistache/pull/623
Fixes: https://github.com/oktal/pistache/issues/621
Fixes: https://github.com/oktal/pistache/issues/622
Fork: Fork: https://git.mobley.ne02ptzero.me/~louis/pistache
Signed-off-by: Louis Solofrizzo<EMAIL_ADDRESS>

Codecov Report

Merging #623 into master will increase coverage by 0.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #623      +/-   ##
==========================================
+ Coverage   70.46%   70.57%   +0.11%
==========================================
  Files          50       50
  Lines        7008     7008
==========================================
+ Hits         4938     4946       +8
+ Misses       2070     2062       -8

Impacted Files
Coverage Δ

src/common/utils.cc
6.66% <ø> (ø)
:arrow_up:

src/client/client.cc
78.81% <0%> (+1.52%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dd5e155...e27e02d. Read the comment docs.

Pushed to unstable PPA.


Bug in PreserveTitleAndBody configuration?

Hi,
First of all thanks for this great tool! I really appreciate it.
I think there is bug in the PreserveTitleAndBody feature. In your PR (https://github.com/ejoffe/spr/commit/e643a7908e5d8a9a732e64b9dd8ff5393418e330) you modify client.go to set the title and Body to nil. But if we look at the latest version of client.go on master it looks like this code has been removed, which cause a bug if PreserveTitleAndBody is true. I'd love to open a PR for this but I'm not sure how to test my fix works properly. I'd love to do it if you have those instructions (can be useful for others PRs as well)
Thanks!

Not sure how this happened. Pull requests always welcome!
To test it out you can build your own binaries.
Either using the method stated in the readme, or you can install goreleaser and use make bin (my preferred approach).
Personally I create aliases to the built binaries in the dist directory, instead of call them git-spr and git-amend, I just call them spr and amend.
Then instead of running git spr, I just run spr to make sure I'm using my own built binaries instead of the installed ones.
Hope that helps, let me know if you have any questions.

Thanks I'll have a PR soon then! Looks like it was removed in this PR

@ejoffe Would be super-cool if, despite preserveTitleAndBody=true, the tool updated the "Stack:" block in the end of PR description. I think this block needs to be up to date in all cases, no matter whether the user wants to overwrite the description or not.


AnnotationProperty -- has alternate label category

From<EMAIL_ADDRESS>on February 01, 2011 12:05:46
Please indicate the label for the new term has alternate label category Please provide a textual definition a property that links an alternate label annotation assertion axiom to an individual of the class alternate label category. Example: AnnotationAssertion( Annotation('has alternate label category' iao:taxonomic name) 'alternate label' Taxon:1234 "wibblius wibblii") Please add an example of usage for that term Please provide any additional information below. (e.g., proposed position in the IAO hierarchy) xref: obo-format:synonym-type
Original issue: http://code.google.com/p/information-artifact-ontology/issues/detail?id=99

From<EMAIL_ADDRESS>on May 25, 2011 14:21:49
We decided to use instead specific annotation properties. See for example definition and usage of "OBO community label" in the file https://code.google.com/p/information-artifact-ontology/source/browse/trunk/src/ontology/obo2owlconversion.owl
Status: WontFix

This issue was moved to information-artifact-ontology/ontology-metadata#13


Background color of selected date area, is not changing while disabled the datepicker

Issue
In selected date showing area, background color is not working when it is disabled.
Is there any other way to make it done?
Expected Behavior
Code
<DatePicker
       disabled= {isDisabled} //Boolean Val of isDisable
       style={{ backgroundColor: '#e0ffbc'}}
/>

Environment

react-native -v: 0.67.2
node -v:16.14.2
npm -v:8.17.0
yarn --version:
target platform: Android | iOS
operating system: windows 10

Solution :Need to use customStyles props and then use disable tag to make necessary design changes when it is in disable mode.

Hi @PrantikMon can you share the code, i am unable to change background color while making disabled.
Here is my code:-

<DatePicker
{...props}
customStyles={{
placeholderText: { fontSize: 15, color: 'white', top: 10 },
dateText: { fontSize: 15, color: 'black', top: 10, backgroundColor: 'white' },
dateIcon: { position: 'absolute', right: 0, top: 15, marginLeft: 0 },
dateInput: { borderWidth: 0, left: 10, position: 'absolute', }
}}
/>


Missing .gz support

I troubleshooted this plugin because it didn't do anything and didn't log anything at all (even with debug output)
          if logfile_suffix !~ /\.log\z/ or logfile_datetime <= (timestamp - @buffer_sec)
            next
          end

It turned out there's no .gz support and it's just ignoring all files ending instead.

Sorry for late.
I added support for .gz.
Please try v0.3.7

Sorry
v0.3.7 has a bug.
try 0.4.1


⚠ Bofrost.lu has degraded performance

In 8782cac, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1076 ms

Resolved: Bofrost.lu performance has improved in b920076 after 11 minutes.


deposit Query Resolver

TODO

Scaffold resolver to match generated types
Implement resolver
Test resolver

Blockers

No corresponding service implementation

blocked by #202


Use coroutines to shorten synthesis time

https://kotlinlang.org/docs/tutorials/coroutines/coroutines-basic-jvm.html
https://github.com/SeanShubin/kotlin-tryme/blob/5a390a36701dda00e8598154ab655ec1a0f642a3/src/jvmMain/kotlin/com/seanshubin/kotlin/tryme/jvm/process/ListExtensions.kt#L13

https://jivimberg.io/blog/2018/05/04/parallel-map-in-kotlin/

From initial experiments from February, coroutines didn't give the boost I would expect. It's probably because the parallelization was done on a level of a single sample. Maybe processing samples in batches would give better result, to reduce parallelization overhead.

I decided not to use coroutines for now. They wouldn't give anything for JS version anyway since there's no possibility to process stuff in parallel.


[BUG] VM stuck in Restoring state

Describe the bug
Restoring snapshot to the (existing) VM, it will stuck in Restoring state if the VM was stopped by shell command.

To Reproduce
Steps to reproduce the behavior:

Install Harvester with any nodes
Create an Image for VM creation
Create VM vm1 and write some data
Take snapshot vm1-s for vm1
Stop vm1 by executing command sudo shutdown now
Restore snapshot vm1-s to existing

Expected behavior
VM should restored and started successfully
Environment:

Harvester ISO version: v1.2.0-rc4
ui-source Option: Auto
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): Baremetal DL360 3 nodes

Additional context

The bug could be resolved by restart the Restoring VM
Cluster was upgraded from v1.1.2

Provide test result on v1.3.0-dev-20231222, close as fixed.
Environment

Harvester

Version: v1.3.0-dev-20231222
Profile: QEMU/KVM, 2 nodes (8C/16G/500G)
ui-source: Auto

Test Steps

 Create an Image for VM creation

focal-server-cloudimg-amd64.img

 Create VM vm1 and write some data

 Take snapshot vm1-s for vm1

 Stop vm1 by executing command sudo shutdown now

 Restore snapshot vm1-s to existing

 VM should restored and started successfully, and data should still valid

Note

 Can reproduce in v1.1.2, vm1 Restoring over 10 mins.


Pull request for project review

Project requirements:

[x]  Build a Rails application ensuring that:

The models, associations, controllers, and views are working as expected
Sign-up, log-in and log-out methods within the app sessions behavior work successfully
Models' special associations and scopes work properly
Users can create, view, edit and destroy events
Users can assist events

Further information is available at The Odin Project Associations

PR for code review: Lint errors fixed

Required changes completed


[BUG] Unable to upgrade to any version from 0.17.0 to 0.21.0 using google cloud PostgreSQL sql: ERROR: type "xid8" does not exist (SQLSTATE 427040)

Describe the bug
Error and crash the application during startup
To Reproduce
Trying to upgrade from 0.15.2 to 0.21.0
Logs
time="2024-02-02T10:13:08Z" level=warning msg=".env file not found or unable to load. This warning can be ignored if Zep is run using docker compose with env_file defined or you are passing ENV variables."
time="2024-02-02T10:13:08Z" level=info msg="Starting Zep server version 0.17.3-88d7882 (2023-11-01T22:47:29+0000)"
time="2024-02-02T10:13:08Z" level=info msg="Log level set to: info"
time="2024-02-02T10:13:09Z" level=error msg="error updating pgvector extension: ERROR: must be owner of extension vector (SQLSTATE=42501). this may happen if running on a managed service without rights to update extensions."
time="2024-02-02T10:13:09Z" level=info msg="vector extension version is >= 0.5.0. hnsw indexing available"
time="2024-02-02T10:13:09Z" level=info msg="there are no new migrations to run (database is up to date)"
time="2024-02-02T10:13:09Z" level=warning msg="summary embedding dimensions are 1536, expected 0.\n migrating summary embedding column width to 0. this may result in loss of existing embedding vectors"
time="2024-02-02T10:13:09Z" level=info msg="creating hnsw index on message_embedding.embedding if it does not exist"
time="2024-02-02T10:13:09Z" level=info msg="created hnsw index successfully on message_embedding.embedding if it did not exist"
time="2024-02-02T10:13:09Z" level=info msg="creating hnsw index on summary_embedding.embedding if it does not exist"
time="2024-02-02T10:13:09Z" level=info msg="created hnsw index successfully on summary_embedding.embedding if it did not exist"
time="2024-02-02T10:13:09Z" level=info msg="Using memory store: postgres"
time="2024-02-02T10:13:09Z" level=info msg="Initializing tasks"
time="2024-02-02T10:13:09Z" level=info msg="Adding handler" handler_name=message_summarizer topic=message_summarizer
time="2024-02-02T10:13:09Z" level=info msg="message_summarizer task added to task router"
time="2024-02-02T10:13:09Z" level=info msg="Adding handler" handler_name=message_token_count topic=message_token_count
time="2024-02-02T10:13:09Z" level=info msg="message_token_count task added to task router"
time="2024-02-02T10:13:09Z" level=info msg="Adding handler" handler_name=document_embedder topic=document_embedder
time="2024-02-02T10:13:09Z" level=info msg="document_embedder task added to task router"
time="2024-02-02T10:13:09Z" level=info msg="running task router"
time="2024-02-02T10:13:09Z" level=info msg="Running router handlers" count=3
time="2024-02-02T10:13:09Z" level=info msg="Initializing subscriber schema" query="[ \n\t\tCREATE TABLE IF NOT EXISTS "watermill_message_summarizer" (\n\t\t\t"offset" SERIAL,\n\t\t\t"uuid" VARCHAR(36) NOT NULL,\n\t\t\t"created_at" TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP,\n\t\t\t"payload" JSON DEFAULT NULL,\n\t\t\t"metadata" JSON DEFAULT NULL,\n\t\t\t"transaction_id" xid8 NOT NULL,\n\t\t\tPRIMARY KEY ("transaction_id", "offset")\n\t\t);\n\t \n\t\tCREATE TABLE IF NOT EXISTS "watermill_offsets_message_summarizer" (\n\t\tconsumer_group VARCHAR(255) NOT NULL,\n\t\toffset_acked BIGINT,\n\t\tlast_processed_transaction_id xid8 NOT NULL,\n\t\tPRIMARY KEY(consumer_group)\n\t)]" subscriber_id=01HNMMXMA2JEYKDSWAMAGTSCEG
time="2024-02-02T10:13:09Z" level=info msg="Starting purge delete processor. Purging every 1m0s"
time="2024-02-02T10:13:09Z" level=info msg="Web interface enabled"
time="2024-02-02T10:13:09Z" level=info msg="Listening on: <IP_ADDRESS>:8000"
time="2024-02-02T10:13:09Z" level=info msg="Web UI available at: <IP_ADDRESS>:8000/admin"
time="2024-02-02T10:13:09Z" level=fatal msg="failed to run task router cannot subscribe topic message_summarizer: cound not initialize schema: ERROR: type "xid8" does not exist (SQLSTATE 42704)"
dfEnvironment (please complete the following information):

Zep version: 0.21.0 (from  ghcr.io/getzep/zep)
Deployment: Google cloud kubernetes, using google cloud PostgreSQL (latest version POSTGRES_12_16.R20230830.01_07)

Hi @koldoon,  Zep requires Postgres 15.4 or later. The xid type was introduced in Postgres 13.


Refactor Data-Files class into Data-Teams class

It makes more sense since we have moved quite far from the original use of this class to manage files

Another option is to keep this as a 'File Storage' api and add an Data-Team class that exposes team like functionality (like the Data-Project does at the moment)

The use of file in these apis was driving me crazy, so I made these changes yesterday (on a train journey)
https://github.com/OWASP/Maturity-Models-API/commit/3e95459e096811dedcdc5f721dd26a5242bf543f
it is now called Data_Team and all methods use team instead of file


Support aggregation function name with underscore inside

Description
Support aggregation function name with underscore inside

I think the current version works, but has some inefficiency.
Should we just change ST_UNION to STUNION and always remove underscore if exists? The logic will be much simpler. Sorry to go back and forth on this.

I think the current version works, but has some inefficiency.
Should we just change ST_UNION to STUNION and always remove underscore if exists? The logic will be much simpler. Sorry to go back and forth on this.

I actually prefer to this way before we have two functions with same name after removing all "_" :)


Reorganize json-gen and slow-odgi into two packages

[ ] The json-generation code should stand alone in its own package.
[ ] It should just borrow mygfa (and maybe preprocess) from slow-odgi, or, better yet, mygfa (+preprocess) should be lifted above these two separate packages.
[ ] Separate the testing infrastructure
[ ] Separate the argparse-ers

Originally posted by @anshumanmohan in https://github.com/cucapra/pollen/issues/25#issuecomment-1524065092

Nice. I like the idea of factoring things out so that we have top-level Python modules that can be shared among multiple tools. Logistically, there are two options for doing this in Python:

One giant Python package (called pollen or something), with one pyproject.toml and one top-level source directory, where everything is a module nested within that package. So there would be Python modules named pollen.mygfa, pollen.slow_odgi, etc.
The "monorepo" approach, with several directories containing separate Python packages, each accompanied with their own pyproject.toml. The Python package names would be just plain mygfa and slow_odgi and such. This post illustrates this directory structure.

Option 1's advantage is that there are no questions about which ones are installed on someone's machine; they're all installed at once. Its disadvantage, however, is that they only have one set of dependencies—so people using our imagined "PanoBench" can't install slow_odgi without getting all our other stuff, which might depend on Calyx or whatever. I'd probably lean toward Option 2 unless it's super inconvenient.

Super, Option 2 was my plan, and this is better motivation than ever


can you help me  the NC-LS model code mentioned in this article

Dear expert, I am sorry to bother you. The NC-LS model is mentioned in this article. Can you provide the code for this model? I reversed myself and found that the result of the run was not the result of your original text.

Dear expert, I am sorry to bother you. The NC-LS model is mentioned in this article. Can you provide the code for this model? I reversed myself and found that the result of the run was not the result of your original text.

Many thanks for your interests in our paper. for the NC-LS, you can just replace the bilateral filter in our code with the NC version of the domain transform filter. The same applies to the AMF-LS. The code of transform filter can be downloaded here: https://www.inf.ufrgs.br/~eslgastal/DomainTransform/ . Hope my reply could be useful to you.

Dear expert, I am sorry to bother you. I have replaced the bilateral filter with the NC function. When I re-emerge the code, I use the parameters mentioned in the article and I don't get the same results as in the article.
So I still have some questions as list:

How are the parameters of the NC set? Is it set to the same sigma_s and sigma_r as the initial input? How do NC iteration parameters be set?
How do I set the parameters for rolling guidance NC-LS?
If it's convenient for you to upload these codes?


social icon can't show

why not the icon displayed,in my html source code,Here already exists

like above ,but the icon width and height are all 0*0,and if I miss something?

Which browser and version?

Google chrome 54.0.2840.98 (64-bit),btw excited to receive your reply

I just try to create a new application,it works,and I don't know why,sorry for my odd error and thanks for the gem,it's useful for me!


TransitionSpring elements don't leave and enter when replaced, unique keys not working

I have a TransitionSpring wrapping a list, whose elements get replaced using redux. I gave elements unique keys, and still elements only enter or leave to accommodate for a change in their numbers. That is, if there were two elements before, and now there are three, the third element will enter, but the other two will just get their contents replaced instead of the prior ones leaving and the new ones entering. This is important because I need the animation to trigger.
In chrome's inspector I can actually see the keys change (the data-reactid attribute in the contained li element) instead of the whole tag being replaced with a new one.
Also, I do get a

Warning: Each child in an array or iterator should have a unique "key" prop. Check the render method of TransitionSpring. See https://fb.me/react-warning-keys for more information.

in the console, which I don't understand, since I see the keys.
Below is the problematic render code.
render: function () {
	var p = this.props;
	return (
		<TransitionSpring
			endValue={this.getEndValue()}
			willEnter={this.willEnter}
			willLeave={this.willLeave}
		>
		{function (motionVals) {
			return (
				<ol className="potential">
					{Object.keys(motionVals).map(function (ind, garbage) {
						return (
							<Heir
								name={motionVals[ind].text}
								onGo={p.onGo}
								opacity={motionVals[ind].opacity.val}
								leftTrans={motionVals[ind].leftTrans.val}
								key={motionVals[ind].text} // Unique keys.
							/>
						);
					})}
				</ol>
			);
		}}
		</TransitionSpring>
	);
}

What does your getEndValue look like? Also, see here: https://github.com/chenglou/react-motion#little-extras. Don't use numbers as your keys.

getEndValue: function () {
		// Have to convert to object for compliance with
		// react-motion. The `heirs` property holds a list of strings.
		var endVals = {};
		this.props.heirs.map(function (str, i) {
			return {
				opacity: {val: 1, config: presets.stiff},
				leftTrans: {val: 0, config: presets.stiff},
				text: str
			};
		}).forEach(function (obj, i) {
			endVals[i] = obj;
		});
		return endVals;
	}

Also, I just use the text property for the id, which aren't numbers...

Somehow works now. Since this post I've made a change in my app to ImmutableJS that broke some functionality, among which was changing all the element keys to true. After I fixed it so the id's are back to normal, the problem disappeared. Still don't know why it works though... Will update if I find out - for now I'm closing the issue.
Thanks!


Redesigning the Mapping Pipeline

The New pipeline is located here:
https://github.com/EBISPOT/gwas-data-services


Zero-G turning head doesn't turn player orientation (messing up forward/back/left/right movement controls)

First of all, thank you for creating what is my favorite VR experience to date, hands down. It's absolutely incredible and I can't wait to get my headset on again for another run.
Now, I think I might be playing in a way that wasn't anticipated: I stand in the middle of a room and turn my whole body to face whatever direction I want to go (playing on a Quest with ReViveVR,  so no wires). I didn't even realize the right hand thumbstick did anything until my third or fourth loop (made piloting the spaceship fun). Which meant that, to take the least spoilery example possible, when I'm in the zero-g cave on timber hearth, if I physically turn myself 90 degrees to the left, pressing forward on the left stick moves me to my right, pressing left moves me forward etc. I have to keep looking down at the feet decals to figure out which way the game thinks I'm facing. This isn't an issue for environments where I'm walking, the game seems to track which way I'm facing just fine.

This is a technical limitation with how the player physics behave in zero G vs while standing on a planet. Too much work to fix.

That seems totally fair. Would it be worth considering adding a input to in zero g (and spaceflight) for "right stick- turn" or similar? I think there's something there for grip+right stick - roll already, perhaps that could just be modified to include right and left turning?

@JpTiger not sure what you mean. Right and left turning already works in Zero G. It's just always relative to the character's "forward" direction. To know the forward direction in zero-g, either look at the compass present in the helmet HUD (there's a longer line pointing forward), or look at the player's footprints.

Sorry I wasn't clear, when I said "input" I meant a visual HUD prompt when in zero-g next to the right hand indicating that the right stick can rotate the player.

Fixed in #391, available now in update 1.1.1


Use column number in Maven error format

Hello,
Here is a patch that should fix Maven error format output (#342). Patched worked in local environment running on Linux and with Maven 3.3.9.

Hmmm...I am currently using Maven 3.3.9 + maven-compiler-plugin 3.3 and I only seem to get line numbers for my errors as you can see here:
[ERROR] /home/brcolow/code/core/Main.java:[65] q cannot be resolved to a type
I am not sure why we get different results =(

Given that both results are possible, can we simply include both variations of the errorformat?

Hm very interesting indeed that you are not getting column number in your output. Idk if it helps but my javac version is 1.8.0_73. Also I had the same issue on OSX env.
Made the new patch there and tested it too. Seems to be working with both outputs now.

I think I figured out why there is a difference. I am actually using the eclipse compiler by using the following configuration for maven-compiler-plugin:
<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-compiler-plugin</artifactId>
    <version>3.3</version>
    <configuration>
        <source>1.8</source>
        <target>1.8</target>
        <compilerId>eclipse</compilerId>
    </configuration>
    <dependencies>
        <dependency>
            <groupId>org.codehaus.plexus</groupId>
            <artifactId>plexus-compiler-eclipse</artifactId>
            <version>2.5</version>
        </dependency>
    </dependencies>
</plugin>

@brcolow, nice that you found out what caused the difference for us. I think it would be good to have both errorformats still in.

@rasmusx
Yes.
Can you do this, please?

@blueyed, yes I could look into it over the weekend.

Hello again,
Finally I had some time to work on this. I have fixed Maven error format to accept lines in various different formats. Most use cases should be handled.
I have also created one new feature to remove duplicates from job output. I created it due to Maven sending duplicate lines. Could you please take a look at this feature and let me know what you think. It could be useful in future too. Code wise it might not be the best, I don't write vimscript.
Waiting for feedback :)

This branch/PR has conflicts, please rebase it.

Hi again,
I have rebased the branch with some minor edits. Tests are also passing.
Altough I am not sure why the previous test failed actually. There was just vimlint missing (env setup issue?).

Hi,
Are we going forward with this one? :)

Are we going forward with this one? :)

Yeah!
Can you please rebase it against master?

Hi again!
Sorry for long reply, I was on a vacation :).
Anyway I have rebased it against master once more. Also fixed some function style errors that were not using abort attribute.

I am sorry, but it needs to be rebased again.
Please ping me when done.

@blueyed , rebased against master with very small change. Please let me know if there is any problems.

Couldn't the removal of duplicate lines also be done via postprocess?

There are also quite a lot CI / test failures.

@blueyed, made new implementation using postprocess as you suggested. Everything seems to work, including the tests. Let me know if you have questions.

@rasmusx
ping

I am using maven-compiler-plugin 3.5.1 and I can confirm that it is too also reporting line and column numbers in format [%l\,%c]

@deathbeam
Thanks for the confirmation, but for me the actionable on this PR is still unclear.

Any love for scala? Also any way to easily use mvn compile instead of mvn install?
The mvn version I work with uses:
[ERROR] /home/dpc/lab/myproject/src/java/Somefile.scala:1401: error: illegal start of declaration (possible cause: missing `=' in front of current method body)
[ERROR]     return ""
[ERROR]

@rasmusx
I hope you've not given up on it?
Would anybody like to pick it up and finish it otherwise?

No update since a while, so I am closing this.
Feel free to pick this up though, of course (anybody!).


Breakpoint doesn't switch if cols are the same

In my case I just want to provide a different layout with the same number of cols, but onWidthChange checks that newState.cols !== this.state.cols before switching the breakpoint.

Fixed in 0.10.2.


White browser window appears when running testcafe in headless mode

What is your Scenario?
I run tests in headless mode using flag chrome:headless
What is the Current behavior?
when i run testcafe in headless mode opens up new browser and hangs with white screen until i close it manually
What is the Expected behavior?
on previous week no screens appeared
What is the public URL of the test page? (attach your complete example)
this doesnt matter, any public page in healdess mode
What is your TestCafe test code?
fixture`test`.page('https://github.com/DevExpress/testcafe');

test('test', async (t) => {
    t.request('https://github.com/DevExpress/testcafe');
});

Your complete configuration file
no config files used
Your complete test report
No response
Screenshots

Steps to Reproduce

Run test in headless mode with command  npx testcafe chrome:headless .\PATH_TO_TEST_FILE

TestCafe version
3.6.2
Node.js version
v20.14.0
Command-line arguments
npx testcafe chrome:headless .\PATH_TO_TEST_FILE
Browser name(s) and version(s)
Chrome 129.0.6668.59
Platform(s) and version(s)
Windows 11 Pro
Other
No response

Hello @silkdemon,
This issue is related to ChromeDriver and is not specific to TestCafe. It was also reported in the ChromeDriver issue tracker.
As a workaround, you can use the --headless=old flag to run Chrome in the old headless mode or hide the window (set the position off-screen with the --window-position=-2400,-2400 flag for this purpose).
npx testcafe 'chrome --headless=old' .\PATH_TO_TEST_FILE

npx testcafe 'chrome "--window-position=-2400,-2400"' .\PATH_TO_TEST_FILE


Add an option/table to find/log the "reward accounting issues" per epoch when using the snapshots on Mainnet

OS
Linux
Run method
Sync db-sync state on Mainnet from a snapshot.
Additional context
At this moment the "reward accounting issues" (like https://github.com/input-output-hk/cardano-db-sync/issues/947) are visible only when syncing from a clean state (not using a snapshot) but this is extremely slow on Mainnet.
It would be useful to be able to spot the "reward accounting issues" also when db-sync state is fully synced (from snapshot = much faster, and the recommending way of doing this).
Idea: we can have a new table with 3 columns:

epoch_no
expected rewards
effective rewards
That way we would be able to compare the values of the last 2 columns in order to validate the rewards per epoch.

When db-sync is restored from a snapshot, this bug WILL NOT BE TRIGGERED because the buggy code is never executed.

There is no way to do this other than by implementing a test with the test framewrok we are working on.
Closing.

Considering that there is a way to automate this check through a test, it would be useful to keep this ticket open (for tracking purposes) until the test is implemented otherwise there is a high risk of losing it.
cc @vhulchenko-iohk , @vfrsilva

https://github.com/input-output-hk/cardano-db-sync/issues/959


Message: ignored auto-triggered completion, preceding char did not match

Clangd Version
clangd version 8.0.1-svn360950-1~exp1~20190517004233.70 (branches/release_80)
Clangd Output
https://gist.github.com/mihaelartz/b5074b05dcb497aedcb9e97ffe9cc8e5

@ilya-biryukov I guess this is https://reviews.llvm.org/D55994. Do we need to return an error instead of [] in this case?

We do return an error in that case, with an UnknownErrorCode (-32001).
The intention was always to return RequestCancelled code, I'll send a patch to do so.
Looking at coc.nvim source code, this should fix the issue.

Sent out D6299 for review, it should fix this.

@ilya-biryukov Same problem appear in vscode, with vscode-clangd extension.

We don't expect users to see those logs.
But actually, it turned out returning empty completion list does not show a completion window in VSCode, that looks like the best fix so far

Landed a fix in r362811, could you please check the problem is gone after it?

@ilya-biryukov First release build on Ubuntu repository. Compile takes a long time.

We don't manage the ubuntu packages on our own, so I'm afraid you'll have to wait for the new LLVM release to get the fix.
Alternatively, you could grab a fresh build from https://apt.llvm.org/


Keyboard manager is not working

Microsoft PowerToys version
0.86.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
Keyboard Manager
Steps to reproduce
I use Dvorak keyboard layout. So, I map Ctrl-J to Ctrl-C  and Ctrl-K to Ctrl-V.
It would work half of the time and half of other time it just not doing anything.
✔ Expected Behavior
It should always work. And when I pressed Ctrl-J it should do the copy to clipboard as Ctrl-C would
❌ Actual Behavior
Ctrl-J still acting like Ctrl-J
Other Software
Vivaldi | 7.0.3495.26 (Stable channel) (64-bit)

/bugreport

Here they are.
PowerToysReport_2024-12-17-10-50-53.zip

Looking through the logs nothing stands out. I suspect this should be joined with main issue related to how keyboard manager stops working sometimes.
What model and brand is your keyboard? /needinfo


replace icons

Currently it's the default Yeoman one. https://github.com/arthurvr/timeline-url/blob/master/app/images/icon-128.png
Let's find something more creative :p

Fixed. Thanks @paulirish!


[Question] Sample Controller is listing from cluster scope

Hello,
I am trying to play with sample controller without a cluster role. I saw a bunch of error messages like this:
E0128 22:32:08.533076       1 reflector.go:123] pkg/mod/k8s.io/client-go@v0.0.0-20190831074946-3fe2abece89e/tools/cache/reflector.go:96: Failed to list *v1.StatefulSet: statefulsets.apps is forbidden: User "system:serviceaccount:test:default" cannot list resource "statefulsets" in API group "apps" at the cluster scope

Is there a way to ask the sample controller only list from certain namespace? Or is it by design that most of the CRD operator need to have the permission to list CRDs in all namespaces? Thanks in advance.
Regards,
Shuo

All the client-go functions support passing in Namespace name in their CRUD calls. The sample-controller code is already written to parse and use namespace field from input YAMLs. So yes, you can restrict your code to make calls for objects in a particular namespace. If you pass the namespace field as "" (empty string) in a list call, then that call goes out to all namespaces.
Regarding above error, it is showing up in the reflector which is the entity in client-go that behind the scene tries to retrieve objects from API server and cache them locally. The sample-controller then works with these cached objects. Access of client-go's reflector to the API server is also controlled by same RBAC rules as any other entity that is trying to make calls to the API server. To solve above error you will have to define RBAC policies in your cluster. Generally you will deploy your controller as a Pod and define RBAC rules for that Pod's 'serviceAccount'. If you are just trying out sample controller I would recommend enabling cluster admin permissions  for your kubeconfig context user. If you are using minikube then you will have these permissions already. If not, you can follow these steps. They are bit involved -- create a ServiceAccount, grant it cluster admin permissions, get that SA's token, update your kubeconfig context to use that SA, and then try running sample-controller. Using minikube might be simpler option if these steps seem complicated.


Unable to install the nginx-kubernetes-gateway successfully

Dear team,
We are getting following error while installing the gateway class on the rancher cluster(rke4). Could anyone help us to install the gateway?
Status:
Conditions:
Last Transition Time:  1970-01-01T00:00:00Z
Message:               Waiting for controller
Reason:                NotReconciled
Status:                Unknown
Type:                  Scheduled
Events:

Hi @tgkumarmca
The GatewayClass resource is not yet supported. So that's why the GatewayClass is not reconciled.  So NGINX Gateway doesn't require it -- you can deploy the Gateway resource and HTTPRoutes without the GatewayClass.
However, soon we will add support for GatewayClass, once https://github.com/nginxinc/nginx-kubernetes-gateway/pull/136 is merged.

Hi @tgkumarmca
The GatewayClass is supported now - if you rebuild the image from the latest main branch.

But, weight based routing is not happening correctly. I can still see the traffic is being sent to the instance which has the weight is set to 0.

we don't support weights yet - only a single destination.
The project is very early in the development. However, we're adding more and more features.
We will publish the first v0.1.0 in August with some additional documentation explaining which Gateway API resources and which features (fields) of those resources are supported.

@tgkumarmca Have you had a chance to try again?
Traffic Splitting is now supported  https://github.com/nginxinc/nginx-kubernetes-gateway/pull/261


Publish to PyPI

We would love to be able to pull this package from PyPI rather than as a git dependency. Are there any plans for or blockers to publishing this to PyPI?
Thanks!

@dbluhm here you go!


Axon4 Saga Store

Hi there, I have a quick question.
Due the production considerations
Should I configure saga store or axon server already do that job ?
A question is, on the default configuration (spring boot + axon server autoconfiguration) if saga already started and the service was shut down while saga still active. and when server start again. I wanna know what will happened ? will I lose that saga state or it will continue their job ?

case closed
after trying to dig into axon source code, I understand all about this.
You should configure SagaStore if you want your saga to continue thier job (and configure TokenStore as well)
If you're using jdbc or jpa. don't worry, axon already have JpaAutoconfigure and JdbcAutoconfigure which will configure that for you.
Buf if not, you should configure it yourself.

Happy to see you found a resolution to your problem @mapkuff.
Nonetheless, I'd like to point out that the GitHub issue tracker is not intended for usage questions.
Instead in the future, you can drop a question on StackOverflow, using the axon tag, or place a question on the Axon User Group.


docs: update stories featuring bootstrap

Bootstrap 4 has been released.
npm install bootstrap --save installs Bootstrap 4 instead of Bootstrap 3.
To install Boostrap 3, we should do npm install bootsrap@3

I signed it!

@markgoho or @rafaelss95,
Is there any action I can take to improve this PR so that it can be merged ?
Thanks

Heya, this pr is superseded by https://github.com/angular/angular-cli/pull/10541.


[Storage] Update typing for blob_service_client

This is the first of many PRs to begin updating type hints for all of Storage's public facing types. This PR updates typing for _blob_service_client and _blob_service_client_async.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-storage-blob

/azp run python - storage - ci


[RFC] Making new Versions Available

Code is now updated to work with spring-platform-1.1.2 (#197). I'm a bit frustrated with the delays (see #199) - a lightadmin-1.1.0 could have been already close to release.
Has anyone experience with setting up a distribution on maven-central? so he can guide me a bit, thus I don't loose too much time setting it up?
This way, I can make a new (compatible) version available on maven-central, which can be used until this project becomes alive again.
(users would just change the reference in the POM)

http://central.sonatype.org/pages/apache-maven.html

@lazaridis-com There is no way, we'll release an unstable version to users. Have you ran selenium tests on PR?

So, I wait 4 days for a respons of the "Master of the Buttons" (= repo owner) to just have to deal again with his paranoia? How do you conclude "releasing unstable versions to users"?
For now: please just act, and merge the garbage form #197, and if for any reason you don't want to user master as main development branch, then go ahead and create a branch platform-1.1.2 and merge it there.
The test framework does not work on my side, and I did not dig into it. Leaving testing to others for now (the integration work is difficult enough). I'll myself test later, after revising the test-system a bit to work against the new system.
(Note to readers: I wanted to invest a fulltime week into this, which is nearly gone. So, if you want furter results, please keep me active by responding. Although I start to think that nobody uses lightadmin in a serious project.)

@lazaridis-com Next time, instead of waiting 4 days, please prepare your Pull Request properly.

There will be no "next time", as it's obvious that your ego is far greater than your technical ability (and you refuse even to clean up a bit #199).
How confused can you be to start posting video links; You don't really expect me to follow them and to reply? Find some open-source beggar which treats you like the big master. They like usually playing with youtube.

@Readers: I finally understand that this here is a dead project. 2 years for an unstable POC? And the repo owner blocks efforts to get things

.


[Technical] DynamicTableViewController improvements

This PR improves the technical implementation of the DynamicTableViewController regarding its predefined cell types.
Cell types have been refactored from an enum type to a struct with static function defining the actually types. Support for the standard typography configurations as specified by the design guides has been added. The previous dynamic type cell type have been deprecated and will be removed after all view controllers have been migrated.
Furthermore a section shortcut for a navigation subtitle has been added as required by the most recent design updates regarding navigation bar titles and subtitles.
The risk legend has been modified to adopt these changes already, including some minor pixel spacing and color adjustments.

Sorry, for the open/close bonfire. Something was wrong with the diff. Needed to convince GitHub to refresh it.


Secrets should be stored in a java.security.KeyStore

Original issue 158 created by<EMAIL_ADDRESS>on 2012-03-28T23:27:19.000Z:
Instead of storing the secrets in the SQLite database, the SQLite database should store the alias of the SecretKey in a java.security.KeyStore. This will allow migration to more secure methods of storage in the future.
Note that you'll have to use a JCEKS instead of the default JKS.

Any update on this? I've got a Lollipop device that has no room to install on the internal storage, and can't encrypt the SD card.

No update, aside from that I'm moving this to the android repo.
https://github.com/google/google-authenticator-android/issues/48


getkeys

Here's one I've found useful - is this already implemented somehow or would you like a PR?
julia> function getkeys(nt::NamedTuple, ks)
           namedtuple(ks)((nt[k] for k in ks)...)
       end
getkeys (generic function with 1 method)

julia> nt = (a=1,b=2,c=3,d=4)
(a = 1, b = 2, c = 3, d = 4)

julia> getkeys(nt, (:a,:c))
(a = 1, c = 3)

ahh get a subset of the keys -- sure PR it

thank you

call it fromkeys or bykeys or ?? because getkeys is misleading

getkeys is misleading

Yeah I wasn't sure what to call it, so this was analolgous to getindex. But getkey returns a key so yeah that's confusing.
I think the "right" way to do this is with getindex, so you could write nt[[:a,:c]]. But, type piracy and all... :)

yes -- I already ran into piracy and had to rewrite much of this -- so do not go down that path
.. I had a way to do this ..

here it is (just the opposite logic)

julia> nt
(a = 5, b = 6, c = 7, d = 8)

julia> delete(nt, (:a, :c))
(b = 6, d = 8)

select(nt, (:b, :d)) == delete(nt, (:a, :c))
and there is setdiff so ? copy the nt do the setdiff on the keys and delete those keys (shorthand)

Are you suggesting calling it select? That sounds good to me

yes


Issue/log user

Pull Request
Description
Log user and url every time a route is called
TODO, gets new session everytime
Fixes #206
How Has This Been Tested?

CI test

added tests

[ ] Yes

Checklist:

[ ] My code follows OCF's coding style guidelines
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked my code and corrected any misspellings

Aside from the improvement you've already spotted looks like it'll do the job for now

thanks, ill see what I can do, about not making a new session every time


STAKE_POOLS_ESTIMATE_FEE negative tests for 40x responses

Issue Number
#1096
Overview

[ ] I have added few more tests  for 40x responses

Comments

bors r+

bors r+


RISC-V: Add WCH/QingKe XW extension

This PR adds support for the WCH/QingKe "XW" extension, closing issue #6385
This only includes support for the "XW" extension and not any of the other QingKe-specific functionality (i.e. the ARM Cortex-inspired SysTick and interrupt controller)
As part of this, I had to make a duplicate of the existing .cspec file, as some issues seem to arise with it if the core supports only single-precision floating point but not double-precision floating point. I don't know whether this .cspec is actually correct or not, especially for the QingKe-V2 core which only implements RV32ECXW.
I don't know how to make Ghidra correctly pick the correct variant based on .riscv.attributes.
The XW opcode disassembly was tested by feeding all possible opcodes (as far as I can tell) through the vendor toolchain, opening the resulting .o into Ghidra, and then visually scanning the results.

One thing sticking out are the insn names conflicting with ratified Zcb instructions.
Naming them like xw.c.lbu has a higher chance of getting upstreamed to compilers (and reduce overall mess), though won't compile back through their proprietary gcc.

To fix build error:
diff --git a/Ghidra/Processors/RISCV/certification.manifest b/Ghidra/Processors/RISCV/certification.manifest
index 07cddb0454..9e40a0da46 100644
--- a/Ghidra/Processors/RISCV/certification.manifest
+++ b/Ghidra/Processors/RISCV/certification.manifest
@@ -5,6 +5,7 @@ data/languages/RV32G.pspec||GHIDRA||||END|
 data/languages/RV32GC.pspec||GHIDRA||||END|
 data/languages/RV32I.pspec||GHIDRA||||END|
 data/languages/RV32IC.pspec||GHIDRA||||END|
+data/languages/RV32IMACFX.pspec||GHIDRA||||END|
 data/languages/RV32IMC.pspec||GHIDRA||||END|
 data/languages/RV64G.pspec||GHIDRA||||END|
 data/languages/RV64GC.pspec||GHIDRA||||END|
@@ -16,6 +17,7 @@ data/languages/riscv.ilp32d.slaspec||GHIDRA||||END|
 data/languages/riscv.ilp32d_thead.slaspec||GHIDRA||||END|
 data/languages/riscv.instr.sinc||GHIDRA||||END|
 data/languages/riscv.ldefs||GHIDRA||||END|
+data/languages/riscv.lp32qingke.slaspec||GHIDRA||||END|
 data/languages/riscv.lp64d.slaspec||GHIDRA||||END|
 data/languages/riscv.lp64d_thead.slaspec||GHIDRA||||END|
 data/languages/riscv.opinion||GHIDRA||||END|
@@ -30,6 +32,7 @@ data/languages/riscv.rv32k.sinc||GHIDRA||||END|
 data/languages/riscv.rv32m.sinc||GHIDRA||||END|
 data/languages/riscv.rv32p.sinc||GHIDRA||||END|
 data/languages/riscv.rv32q.sinc||GHIDRA||||END|
+data/languages/riscv.rv32xw.sinc||GHIDRA||||END|
 data/languages/riscv.rv64a.sinc||GHIDRA||||END|
 data/languages/riscv.rv64b.sinc||GHIDRA||||END|
 data/languages/riscv.rv64d.sinc||GHIDRA||||END|
@@ -56,6 +59,7 @@ data/languages/riscv.zvbc.sinc||GHIDRA||||END|
 data/languages/riscv.zvkng.sinc||GHIDRA||||END|
 data/languages/riscv.zvksg.sinc||GHIDRA||||END|
 data/languages/riscv32-fp.cspec||GHIDRA||||END|
+data/languages/riscv32-fp32.cspec||GHIDRA||||END|
 data/languages/riscv32.cspec||GHIDRA||||END|
 data/languages/riscv32.dwarf||GHIDRA||||END|
 data/languages/riscv64-fp.cspec||GHIDRA||||END|

re https://github.com/NationalSecurityAgency/ghidra/pull/6390#issuecomment-2043412222: to be honest I have no idea what this actually does (running sleigh manually works without doing this), but I've added it as a separate commit
re https://github.com/NationalSecurityAgency/ghidra/pull/6390#issuecomment-2043952241:
i am attaching the files that I used to visually smoke-test this PR (as well as the quick hack script that generated them): wch-xw.zip
the opcodes are definitely found in the bootroms of the ch32v003/ch32v203/ch32v208 chips, but i do not want to be responsible for publicly distributing those. i've also been able to make vendor gcc emit them for ad-hoc specially-contrived test functions. the disassembly makes sense when skimming these cases.
as to your questions:

the vendor gcc's version command reports riscv-none-elf-gcc (xPack GNU RISC-V Embedded GCC x86_64) 12.2.0
no idea, i am not affiliated with the vendor, and I haven't found anything from google searching the english-language internet
all vendor documentation (including a quick skim of the chinese-language documentation) seems to just call it XW
i am only aware of a single version of this extension (specifying rv32ecxw (for QingKe V2) vs rv32ima{f}cxw (for QingKe V4) doesn't change the opcodes). I don't know anything about future vendor cores.

Thanks for the exemplars and the contextual metadata.  I'll see about getting them into my exemplars repo.
The certification.manifest file @jobermayr added is needed for building and distributing Ghidra, not for using sleigh to locally support a new processor spec or instruction set extension.   It may amount to a public assertion that the contents of your new file are free of other proprietary or licensing claims and can be freely redistributed within Ghidra's  Apache license.
If anyone knows how to triage intellectual property rights and licensing from reverse-engineered binaries we could have a fun discussion here.  I've only been subpoenaed for a deposition on that topic once, which was enough for me.

If anyone knows how to triage intellectual property rights and licensing from reverse-engineered binaries we could have a fun discussion here.

GCC is GPL licensed

@jnk0le: gcc and binutils are both safe.  The thead, ventana, and sifive vendor extensions contributed to binutils are probably equally safe.  I'm unsure about the others.

As someone who has contributed to other projects that involve reverse engineering, I can assure you that the reverse-engineering processes that was done in order to create this specific PR is, to the best of my knowledge (IANAL), completely safe. As you can see from the script included in the zip file posted earlier, I performed the entire process by running controlled inputs through the vendor toolchain and observing the bytes that come out. In no case did I ever load vendor tools themselves into Ghidra or any other disassembler. The bit patterns and pcode in this PR describe only facts and information (and are my own expression of such, not the vendor's), so I do not believe the vendor can make any copyright claims to it. I am less familiar with patent law and did not read any patents while doing this work, but, as this PR doesn't involve implementing a RISC-V core itself, I find it unlikely that there is a legitimate patent claim to... decoding some opcodes for a disassembler.
In any case, I believe this discussion is far off-topic and out of scope when it comes to discussing this PR in question.

Does anyone have suggestions on how to name this extension and the processor/language variant within the Ghidra RISCV directory?  The wch toolchain provided by @ArcaneNibble names it xw2p2.  That implies version 2.2 of the w vendor-specific (x) extension set.  The pull request calls the processor/language variant RV32_QingKe - but not all QingKe processors support this versioned extension.
The Ghidra design questions here are well over my head.  They get worse when Ghidra opens a linux-next RISCV-64 kernel, which determines the supported extensions at load time then patches its own executable code to optimize things like bit manipulation and encrypted file system support.

There are build errors together with #5778 (conflicting changes):
Compiling ./data/languages/riscv.lp32qingke.slaspec:
line 1:9 no viable alternative at input '<EOF>'
3 NOP constructors found
Use -n switch to list each individually
riscv.table.sinc:149: Size restriction error in table 'instruction' in constructor at riscv.zfh.sinc:232
  Problem with 'frd' and 'frs1H' in 'Copy(=)' operator
  Input and output sizes must match; {type=handle value_real=0x0 spaceid=null} != {type=handle value_real=0x0 spaceid=null}
riscv.table.sinc:149: Size restriction error in table 'instruction' in constructor at riscv.zfh.sinc:236
  Problem with 'frd' and 'frs1H' in 'Copy(=)' operator
  Input and output sizes must match; {type=handle value_real=0x0 spaceid=null} != {type=handle value_real=0x0 spaceid=null}
riscv.table.sinc:149: Size restriction error in table 'instruction' in constructor at riscv.zfh.sinc:240
  Problem with 'frd' and 'frs1H' in 'Copy(=)' operator
  Input and output sizes must match; {type=handle value_real=0x0 spaceid=null} != {type=handle value_real=0x0 spaceid=null}
riscv.table.sinc:149: Size restriction error in table 'instruction' in constructor at riscv.zfh.sinc:244
  Problem with 'frd' and 'frs1H' in 'Copy(=)' operator
  Input and output sizes must match; {type=handle value_real=0x0 spaceid=null} != {type=handle value_real=0x0 spaceid=null}
riscv.table.sinc:149: Size restriction error in table 'instruction' in constructor at riscv.zfh.sinc:252
  Problem with 'frd' and 'frs1H' in 'Copy(=)' operator
  Input and output sizes must match; {type=handle value_real=0x0 spaceid=null} != {type=handle value_real=0x0 spaceid=null}
No output produced

Is there an easy way to fix it?

A quick fix is to force the lengths to match with this patch.  Floating point width conversion doesn't really work this way, so the Ghidra emulator will fail to give anything useful.  The decompiler window should be OK, if you pretend there is some C compiler that can implicitly convert 16 bit floating point values to 32 bit floating point values.
$ git diff riscv.table.sinc
diff --git a/Ghidra/Processors/RISCV/data/languages/riscv.table.sinc b/Ghidra/Processors/RISCV/data/languages/riscv.table.sinc
index 05def9e30b..2e93bf8ada 100644
--- a/Ghidra/Processors/RISCV/data/languages/riscv.table.sinc
+++ b/Ghidra/Processors/RISCV/data/languages/riscv.table.sinc
@@ -94,7 +94,7 @@ frs3D: fr2731 is fr2731 { local tmp = fr2731:$(DFLEN); export tmp; }

 macro fassignS(dest, src) {
 @if FPSIZE == "32"
-       dest = src;
+       dest = zext(src);
 @else
        dest = zext(src);
 @endif

That's not the correct way to resize floats. You should use float2float

float2float isn't defined when converting the 16 bit floats supported in
riscv.zfh.sinc.  I can use it anyway, if that's more consistent with your
roadmap.
On Wed, Jun 12, 2024 at 2:25 PM GhidorahRex @.***>
wrote:

That's not the correct way to resize floats. You should use float2float
—
Reply to this email directly, view it on GitHub
https://github.com/NationalSecurityAgency/ghidra/pull/6390#issuecomment-2163657735,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXFNMDMJBEOHKJ2LLEAXG23ZHCHB3AVCNFSM6AAAAABF3QOAW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRTGY2TONZTGU
.
You are receiving this because you commented.Message ID:
@.***>


Make the vs code fluent

hi developers i just wanted to request you guys to add fluent design for the vs code exactly like in this video because it's awesome in this video that i wish if vs code is like this for real
https://youtu.be/HrlNTIbo9o4?si=q6lWKgahUhRq9iwm

VS Code team doesnt want to enable smooth scrolling by default. And you talk about new design 😆

Duplicate of #133372 and many other that were marked as duplicate of #115641

damn i didn't see that there is a duplicated requests like mine XD
i am just sad because they made the extension fluent vscode disabled and now we can't enable it so i am asking them to make it fluent by defualt


collectives are not taking the currency of the host

Describe the bug
collectiveId=21190 was set to USD when the host (id=21188) was in AUD
collectiveId=21738 was set to USD when the host (id=21739) was in EUR
I manually changed both.
Expected behavior
For the collective to automatically take the currency of the host (this used to happen)
Additional Context
Run this query
SELECT
  count(*) as count, max(hc.slug) as "host", max(hc.id) as "HostCollectiveId",
  max(hc.currency) as "host.currency",
  max(c.slug) as "collective", max(c.currency) as "collective.currency",
  max(t.currency) as "transaction.currency",
  max(t."hostCurrency") as "transaction.hostCurrency",
  upper(t.data -> 'balanceTransaction' ->> 'currency') as "stripe.currency",
  min(t."createdAt") as "firstTransactionAt",
  max(t."createdAt") as "lastTransactionAt"
FROM "Transactions" t
LEFT JOIN "Collectives" hc ON hc.id=t."HostCollectiveId"
LEFT JOIN "Collectives" c ON c.id=t."CollectiveId"
WHERE t."hostCurrency" != hc.currency
  AND t."deletedAt" IS NULL
GROUP BY t."HostCollectiveId", t."CollectiveId", "stripe.currency"
ORDER BY count DESC

And only 5 collectives are mismatched with the host which we already knew about (and some are on purpose). So we should check the code in the self-serve flow to avoid this happening again.

@xdamman can you have a look?


Add some features to the CLI

Feature Request

pnpx wxt@latest init <project-name> --with-src

pnpx wxt@latest init <project-name> --entry=options,test.contents

pnpx wxt@latest create --entry=options,test.contents

Explanation
pnpx wxt@latest init <project-name> --with-src
When creating a project, use src as the root directory.
Currently, the process requires manual steps, which are cumbersome:

Create the src directory.
In the wxt.config.ts file, add srcDir: "src".
Move the assets, components, entrypoints, and public files to the src directory.

pnpx wxt@latest init <project-name> --entry=options,test.contents
When creating a project, it should automatically generate contents, popup, and options pages.
Currently, the generated project defaults to only having a popup page. Creating contents and options pages requires manual intervention:

Create the src directory.
Manually create the contents page. If the content of the contents page is not remembered, users need to open the https://wxt.dev webpage, check the documentation, and copy the content to the contents page.

pnpx wxt@latest create --entry=options,test.contents
If the project already exists, use the command line to create the options page and test contents page.

The init changes you recommend are a duplicate of #187, but in combination with your new create command, it's interesting.
It is definitely annoying to have to refer to the docs to add an entrypoint, and a code-gen tool would be useful, but that makes me think of Rails and I cringe on the inside 🫣
I don't want to maintain a code gen tool, TBH. Entrypoint boilerplate shouldn't be complicated enough that they need to be generated. For how rarely people create new projects, I don't think it's worth the extra work and continued maintenance.
Couple alternative solutions to the problems you're having:

Create your own project template based on your preferences. I'd love to add community templates to the init section
Create snippets for VSCode for creating entrypoint definitions. I'll probably create some of these and publish them at some point, this would be really useful

I really appreciate how much effort you put into this issue! I feel bad saying no, but since this project doesn't have any consistent contributors I can rely on yet, I have to decide what I'm willing to spend my time in 😓


Implement missing cdf/lcdf/lccdf functions for distributions

Description
This is a checklist of all _cdf, _lcdf and _lccdf functions that are not implemented for their _lpdf and _lpmf counterparts.
I am not sure all of them make sense or are even something we would want to implement, I am just listing all of the theoretically missing. If someone has insight, please comment and we can remove any of them.

[ ] bernoulli_logit_glm_cdf, bernoulli_logit_glm_cdf_lcdf, bernoulli_logit_glm_cdf_lccdf
[ ] bernoulli_logit_cdf, bernoulli_logit_lcdf, bernoulli_logit_lccdf
[ ] beta_proportion_cdf
[ ] binomial_logit_cdf, binomial_logit_lcdf, binomial_logit_lccdf
[ ] categorical_logit_glm_cdf, categorical_logit_glm_lcdf, categorical_logit_glm_lccdf
[ ] categorical_logit_cdf, categorical_logit_lcdf, categorical_logit_lccdf
[ ] categorical_cdf, categorical_lccdf, categorical_lccdf
[ ] dirichlet_cdf, dirichlet_lcdf, dirichlet_lccdf
[ ] gaussian_dlm_obs_cdf, gaussian_dlm_obs_lcdf, gaussian_dlm_obs_lcccdf
[ ] hypergeometric_cdf, hypergeometric_lcdf, hypergeometric_lccdf
[ ] inv_wishart_cdf, inv_wishart_lcdf, inv_wishart_lccdf
[ ] lkj_corr_cholesky_cdf, lkj_corr_cholesky_lcdf, lkj_corr_cholesky_lccdf
[ ] lkj_corr_cdf, lkj_corr_lcdf, lkj_corr_lccdf
[ ] loglogistic_lcdf, loglogistic_lccdf
[ ] neg_binomial_2_log_glm_cdf, neg_binomial_2_log_glm_lcdf, neg_binomial_2_log_glm_lccdf
[ ] neg_binomial_2_log_cdf, neg_binomial_2_log_lcdf, neg_binomial_2_log_lccdf
[ ] normal_id_glm_cdf, normal_id_glm_lcdf, normal_id_glm_lccdf
[ ] ordered_logistic_glm_cdf, ordered_logistic_glm_lcdf, ordered_logistic_glm_lccdf
[ ] ordered_logistic_cdf, ordered_logistic_lcdf, ordered_logistic_lccdf
[ ] ordered_probit_cdf, ordered_probit_lcdf, ordered_probit_lccdf
[ ] poisson_log_glm_cdf, poisson_log_glm_lcdf, poisson_log_glm_lccdf
[ ] poisson_log_cdf, poisson_log_lcdf, poisson_log_clcdf
[ ] wiener_cdf, wiener_lcdf, wiener_lccdf
[ ] wishart_cdf, wishart_lcdf, wishart_lccdf

loglogistic and beta_proportion are the only two where cdfs are partially supported, the rest of them have no cdf functions implemented.
Current Version:
v4.2.1

FYI, some of these are really difficult...like multi normal and involve integrating the pdf.

Thanks, updated the list, if there are any other that are difficult, just remove them from the list. I think having a list of missing but doable cdf functions would be helpful.

Would appreciate it if categorical and/or multinomial CDFs could be added to the math library. It looks like folks have had success using truncated Poisson variables to generate at least the multinomial CDF, relying on an article by Bruce Levin.  https://cran.r-project.org/web/packages/pmultinom/pmultinom.pdf; https://github.com/fennerm/pmultinom.  The latter is already in C++.

I note this suggestion on the Discourse of a multinomial probit implementation that might be worth pursuing: https://discourse.mc-stan.org/t/multinomial-probit-in-stan/17583

Any chance that loglogistic lccdf will be implemented soon?


How to run local linux script as actions ?

Is there a provision in articulate for running local unix scripts directly  as an action ?
For ex:
bash runscripts.sh my_script_name
Say I will create a script folder and and a script 'runscripts.sh', which will run one script file from that folder based on script name provided as argument.
I am building a personal desktop assistance for self help in my day to day job, which I will gradually extends to support my entire family. Say like personal assistance for my home.
If there would have been provisions to run linux/unix scripts directly as an action, I can quickly create many actions. I do not need to create webservices for them.
I can plugin many already build services and apps by running them via scripts.

Articulate only communicates web hooks, so you would need to wrap your scripts in some sort of web service or modify Articulate code to be able to run your scripts directly.


Twitter Login failing on Parse Server, working on Parse Endpoint.

Hi,
We are running Parse Server (node.js), AWS, MongoDB or Mlab and attempting a Twitter Oauth. When connecting to Parse Server instance on AWS we get the following:
[;g153,102,51;2016-08-17 18:21:14:251 1moment debug development[main] D OMLoginViewController.m:189 | signed in as r1moment
[;2016-08-17 18:21:14.605 1moment debug development[3650:1359145] [Error]: Twitter auth is invalid for this user. (Code: 101, Version: 1.14.0)
g255,0,0;2016-08-17 18:21:14:662 1moment debug development[main] E OMLoginViewController.m:205 | error: Twitter auth is invalid for this user.
So Twitter returned a valid session, no error, but when that auth is passed to Parse, it fails. If we run the same code, but set the end point back to Parse.com server it works fine.
Please advise.
Thanks.
KB.

Can you provide the parse-server logs running with VERBOSE=1? Do

Yes, we are working on this - please standby.

Hi,
I'm working on "after login" issue in my proj, so I'm logging in few times in a minute.
I did login 5 times, than got 3-4 times error described here.
In few minutes everything started working again.

@batkov can you provide the logs when running with VERBOSE=1 on Parse-server?

Ours is working now...if @batkov is okay you can close this one.

@JustK2 how did you resolve your issue?

We had a space in our config file. :/
On Sat, Sep 17, 2016 at 2:47 PM, Florent Vilmart<EMAIL_ADDRESS>wrote:

@JustK2 https://github.com/JustK2 how did you resolve your issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ParsePlatform/parse-server/issues/2542#issuecomment-247810091,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKFsrNOINhxc55eyk6SUAdXkMVkXA9aTks5qrF_egaJpZM4JnEDO
.


[🐞] Bun adapter breaks / hangs build

Which component is affected?
Starters / CLI
Describe the bug
I am running the cli to add bun, but when I try to build and run the server it breaks / hangs on the build.
This happens because TS errors on the entry.bun.ts file, since Bun is not defined there.
The bun docs are also lacking one property that needs to be added in the tsconfig.json, bun-types inside
"compilerOptions" : { "types": ["node", "vite/client", "bun-types"]  }

I would like to make a PR for this issue.
Reproduction
https://github.com/Twiggeh/qwik-report
Steps to reproduce
nix develop
bun run install
bun run build // crashes / hangs => ctrl + c
bun run serve // 404 index.html missing
System Info
System:
    OS: Linux 6.6 NixOS 24.05 (Uakari) 24.05 (Uakari)
    CPU: (16) x64 AMD Ryzen 9 5900HX with Radeon Graphics
    Memory: 17.73 GB / 30.78 GB
    Container: Yes
    Shell: 5.2.26 - /run/current-system/sw/bin/bash
  Binaries:
    Node: 20.11.1 - /run/current-system/sw/bin/node
    npm: 10.2.4 - /run/current-system/sw/bin/npm
    bun: 1.0.29 - /nix/store/jk432rp4sfm9y912yy071cxdx30bbhvm-bun-1.0.29/bin/bun
  Browsers:
    Brave Browser: <IP_ADDRESS>
  npmPackages:
    @builder.io/qwik: ^1.5.1 => 1.5.1
    @builder.io/qwik-city: ^1.5.1 => 1.5.1
    undici: * => 6.10.2
    vite: ^5.1.4 => 5.2.6

Additional Information
No response

I tested and it's working fine with the latest version.
This PR https://github.com/QwikDev/qwik/pull/6185 solved the issue I think.
Feel free to re-open it if it's still an issue for you.


Inconsistent handling of command-line key/value arguments separated by =

Imagine a crate with two optional features, named "first" and "second".
This is how cargo handles different command line arguments:

cargo build --features="first" - compiles the "first" feature, as expected
cargo build --features "first" - compiles the "first" feature, as expected
cargo build --features "first second" - compiles both features, as expected
cargo build --features="first second" - returns invalid arguments
cargo test --features "first second" - compiles and correctly runs the tests
cargo test --features="first second" - compiles the source ignoring both features and then passes the --features="first second" bit to the executable, which causes it to panic since it's not a recognized option

To summarize, when the value is a space separated (but still quoted) string and the key/value argument is specified as a single command-line argument (where the key and value are separated by a =), the build command says that the arguments are invalid, while the test completely fizzles out. When the value is a single string (with no spaces), then both styles work identically.
In my opinion, cargo should properly handle = separated option-value arguments, which means that the result should be the same as when the value is a separate command-line argument in all cases.
If, however, this style is not to be supported by cargo, then it should at least always cause the invalid arguments message when used, otherwise it leads to inconsistencies such as the build command failing, but test working (and failing very unexpectedly), while given the same set of command line arguments.

cc @BurntSushi, is this perhaps a bug in docopt?

Even if there is an underlying bug in docopt, it still seems at best strange that cargo build and cargo test work so differently when given the same args, doesn't it?

@mlalic see https://github.com/docopt/docopt.rs/issues/129

This was indeed a bug in Docopt, and it should be fixed on crates.io in 0.6.67. Nice find!
@mlalic The bug explains all of the behavior you observed. The underlying issue was that --feature="a b" wasn't detected as a long flag because of the space character. As a result, it was thrown into the catch all <args> ... for cargo test. The "Invalid arguments" on cargo build was because the cargo build usage didn't have a <args> ..., so Docopt the extra arguments didn't match any usage pattern, and thus, an error was reported.

@BurntSushi Thanks for the quick fix and the extra context there!


Copy binary to net50 directory

See https://github.com/RicoSuter/NSwag/pull/3115/files#r523072120

Sorry didn't mean to open the PR here


Make futharki a proper REPL

futharki is currently broken, and just spits out an infinite list of error messages.
However, even pre-breakage, it was not very useful.  It would be nice to have a proper REPL for Futhark.  This can be done without much knowledge of the compiler as a whole, if anyone is interested.

It does work as a (bad) REPL now.


Zombie detector

From time to time, there is a buggy http server which silently drops requests without response or disconnect.
This PR starts a timer (interval configurable by max_inactive) to detect for how long the connection had been inactive after the last request had been expired.
If the it's inactive for longer than the configured max_inactive option, then the connection is restarted.

shall socket opt: send_timeout_close help?

send_timeout_close

it's not that the socket is blocked, it's the server which blackholes requests.


Store binary data as HEX or OCT

Test if it is better to store binary data using hex representation \x0D of the octal representation \015
Note that google Protocol Buffer seems to use octal representation instead of hex

From https://stackoverflow.com/questions/10220401/rules-for-c-string-literals-escape-character
Octal might be preferred: In the case of \x, the hex digits will be read 'greedily' until the first non-hex digit (that is, not limited to 2 as you might expect)


Updated doc with support for multiple results

I have just written a draft for the update README. Some docs on readthedocs will follow in a few days.
@DenisCarriere, as I am not a native english speaker, please feel free to correct me and push the corrections on the branch

I am a native english speaker, but that doesn't mean I can write good english 🤓
Looks great! Piece by piece, this is a big library, but once we figure out the "core" parts and mechanism, the rest of the modules just need to follow that same format and we are good to go.


copr: vectorize md5

Signed-off-by: koushiro<EMAIL_ADDRESS>PCP #5751
What have you changed?
Vectorize md5
What is the type of the changes?

Improvement (a change which is an improvement to an existing feature)

How is the PR tested?

Unit test
Integration test

Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No
Does this PR affect tidb-ansible?
No

@sre-bot /run-integration-copr-test copr-test=pr/95

/run-integration-copr-test copr-test=pr/95

/test

Please make clippy happy. Rest LGTM

Rest LGTM

/test

/test

/run-integration-copr-test copr-test=pr/95

/merge

/merge


PSP Menu link is missing

Hello
In ROPI 4.2 is in the gamelist from PSP the PPSSPP-Menu link missing.
I cant start PPSSPP without a game to configure the emulator!
please fix it or make a batch/script to fix this
"+start PPSSPPSDL.sh"
best regards fredy

closed, publisher not interested to  fix it


[error] Error: EPERM: operation not permitted after upgrade from 8 to 9

I have just upgrade my project from 8 to 9 but it throught an exception
can't build my project, please help me resolve this issue

my dependencies

Thank you so much.

@jindovu, as @petebacondarwin mentioned, it seems that the current user doesn't have permissions to read angular.json.
Can you please verify your the permissions settings?

I follow this guidline link, But when run it's throw exception and I don't know why, I try to run project angular 8 it's still working fine

 I gant permission for project, it's working fine now

Thanks both of you.


Abdelski's contributions

Added jacoco plugin into our project
Added code coverage report
Extended test suits to improve code coverage
Extended documentation.

We have conflict with two files namely RDFMapper and documentation.md . I think we should either store all documentations in one folder or add them all to the root folder but different name(anyway we need different name as they are conclicting).

We have conflict with two files namely RDFMapper and documentation.md . I think we should either store all documentations in one folder or add them all to the root folder but different name(anyway we need different name as they are conflicting).

I think we can just resolve the merge conflict, I will resolve it, just someone needs to add more tests, hence increase the code coverage

We have conflict with two files namely RDFMapper and documentation.md . I think we should either store all documentations in one folder or add them all to the root folder but different name(anyway we need different name as they are conflicting).

I think we can just resolve the merge conflict, I will resolve it, just someone needs to add more tests, hence increase the code coverage

For RDFMapper yes we can solve but for documentation name should be changed

We have conflict with two files namely RDFMapper and documentation.md . I think we should either store all documentations in one folder or add them all to the root folder but different name(anyway we need different name as they are conflicting).

I think we can just resolve the merge conflict, I will resolve it, just someone needs to add more tests, hence increase the code coverage

For RDFMapper yes we can solve but for documentation name should be changed
what do you mean by changing a name? I think resolving a conflict in documentation is easy, and will not take much time to resolve it


pull request for e2e test at 01/13/2017 20:15:08

:white_check_mark: Validation status: passed
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.


Pattern arguments in commands executed with Exec#commandLine are processed as literal strings

Expected Behavior
Pattern arguments in commands executed with Exec#commandLine should be processed as patterns. For example:
Given:

Directory structure:
dir_1
|_ foo.bar
|_ dir_2
  |_ bar.baz

Task:
tasks.register("removeServers2") {
  doLast {
    exec {
      commandLine ("find", "/dir1" , "-type", "d", "-name", """'dir*'""", "-delete")

      /**
       * Or any of these alternatives:
       * commandLine ("find", "/dir1" , "-type", "d", "-name", """'dir*'""", "-delete")
       * commandLine ("find", "/dir1" , "-type", "d", "-name", """'dir*'""", "-delete")
       * commandLine ("find", "/dir1" , "-type", "d", "-name", """'dir*'""", "-delete")
      */

      // Or alternative #1: commandLine ("find", "/dir1" , "-type", "d", "-name", """'dir*'""", "-delete")
    }
  }
}

Current Behavior

Context

Steps to Reproduce

Your Environment

Build scan URL:

Prematurely submitted this. Will update

Updated. Will reopen now.


Fix XML Declaration + ES6 rewrite (partially)

Changes

Bugfix: XML declaration moved to top.
Gruntfile.js: Rewritten with ES6, reduced footprint.

Suggestions:

Due to ES6, this will break compatibility in build for some, so move to v3.0.0

If we merge this it should be as 3.0.0 according to semver 2.0.0 due to ES6.

@lefoy take a look at this one =)

I can't really test this PR tonight but I'll take a look at it tomorrow. I'm sure you already tested it but I just want to be sure nothing breaks. Thanks for all your work !

@lefoy yeah, that I understand =)
Btw, since postcss was added, when and if we merge this, we should also release as 3.0.0 and update sidebar icons.

Yeah I'll release both at the same time as 3.0.0

Released ;) Thanks again!