Question - How to force suggestion list to render on input focus

If this isn't the correct place to ask this type of question, please let me know.
I would like to know the suggested way of forcing the suggestion list to render when the input receives focus via tabbing. Right now, it appears that functionality only occurs when the input is actually clicked.
Thanks!

@imt-telliott you can use the should-render-suggestion to create a focus state.
Example:
https://codesandbox.io/s/vueautosuggest-171-22l6b
e.g.
 <vue-autosuggest
  ...
  @focus="isFocused = true"
  @blur="isFocused = false"
  :should-render-suggestions="(size, loading) => (size >= 0 && !loading) || isFocused"
>

I like this behavior!

Thanks so much for the quick reply, I was looking at the source and it never occurred to me to override this and instead I went the "hacky" way and updated loading to meet my needs.
This is much better.


Update geo-tools's jsdom dependency

Fix security warning

@aruniverse sorry another one to look at.


Address link does not open native maps app

My guess is there's still an issue with setting the mobile parameter. When I click on an address link from within the app, it opens up bing maps when it should open up apple maps
cc @nilnilnil @sdougbrown @bsstoner

@chrismorast when tapping on an address the app is getting the following URL load requests:
https://duckduckgo.com/l/?kh=-1&uddg=https%3A%2F%2Fbing.com%2Fmaps%2F%3Fobox%3D1%26q%3D135%2520George%2520Street%252C%2520Edinburgh%2520EH2%25204JH%252C%2520UK
https://bing.com/maps/?obox=1&q=135 George Street%2C Edinburgh EH2 4JH%2C UK
https://www.bing.com/maps/?obox=1&q=135 George Street%2C Edinburgh EH2 4JH%2C UK
https://login.live.com/login.srf?wa=wsignin1.0&rpsnv=12&ct=1445199174&rver=6.0.5286.0&wp=MBI&wreply=https:%2F%2Fwww.bing.com%2Fsecure%2FPassport.aspx%3Fpopup%3D1%26ssl%3D1&lc=2057&id=264960&checkda=1
https://www.bing.com/secure/Passport.aspx?popup=1&ssl=1
...etc.
I can't see into the javascript that is loaded from the DDG search results, but it doesn't seem like it's trying to open the Apple Maps URL.  Can the results use the user-agent to detect if it's talking to the iOS app and, if so, use the Apple Maps URL format defined at the link below?  https://developer.apple.com/library/ios/featuredarticles/iPhoneURLScheme_Reference/MapLinks/MapLinks.html
Would it be helpful if I just changed the user agent set for the client-side javascript to use the default (mobile safari) string with the DDG-iOS+version string appended to it?

Going to have to let @nilnilnil or @bsstoner make that call

No need to change user agent, we can fix this internally in the JS.

This conflicts directly with #128 from my understanding.

@bsstoner: @nilnilnil makes a great point there.  I think both tickets would be resolved if we simply append the DDG-iOS-version tag to the default (mobile safari) user agent.  Then servers/javascript that we don't control such as the imggur gifv stuff would treat us like mobile safari (which would be correct) and the DDG JS could still tell if it was running with the app as opposed to a normal browser.

Okay, we can do that. @nilnilnil Does that mean you're cool with changing the user agent? I wasn't sure what other implications there were aside from the device detection on the front-end.

There are web server changes we'll need to make. I expect the best thing to do in #128 is to use the DDG UA for DDG requests and The default for everything else.

@nilnilnil ok.  Although on the app's side we can set the UA at a fine-grained level for http(s) requests, but for the navigator.userAgent setting that is accessed in javascript we can't choose which string that returns for individual pages or hosts.

@thm This should now be fixed with the latest build!


Fix autocompletion of static methods in built-in types in GDScript

Added autocompletion for static functions of built-in types:

Fix https://github.com/godotengine/godot/issues/58826

The method should be inserted with (, like with normal method completion.

The method should be inserted with (, like with normal method completion.

@KoBeWi I think I'm done with it:

Thanks!


add linux and py36 build

Ping @Korijn

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

Perfect. Once my colleague returns from holiday we will follow up with manual OS X packages.
Are you still moving forward with GTK, by the way?

Are you still moving forward with GTK, by the way? I created #5 to track that work item.

Yes. That is the direction we should go. I'll try to end a PR to staged-recipes as soon as possible.


Make the navigation bar light grey in light mode

This would also look a lot nicer with the Android 10 gestures

@Poopooracoocoo it would be really helpful for us if you could include any screenshots (of the part we are talking about) to understand better your proposal. That component usually changes between different devices/brands and it would really nice to have a visual example of your scenario. Thanks!

@cmonfortep I'm talking about the Android system navigation bar at the bottom of the screen.
In apps like Settings, the navigation bar is translucent (I think they call it a scrim?) and in some fully transparent. I've heard some stuff about window insets and how you can make the navigation bar fully transparent (which looks great with apps that have bottom navigation).
In DDG Browser, the navigation bar is black in light and dark mode.

@Poopooracoocoo thanks for raising this! It's now fixed and will be out in the next release :shipit:


Treat number literals as generic numbers instead of specific representations like Int or Float

Currently we differentiate Int and Float literals in the IR:
https://github.com/finos/morphir-elm/blob/552d7d65682bdb48cbce9e80ea95022011bc1aed/src/Morphir/IR/Literal.elm#L39-L40
As it turns out this causes more harm than good because Elm treats Int literals as instances of the number type class which will be treated as Int or Float depending on the use-case.

That is Elm, but what about something like F#. I'd hate to cut the expressivity of Morphir for a single front-end.

That is Elm, but what about something like F#. I'd hate to cut the expressivity of Morphir for a single front-end.

That is Elm, but what about something like F#. I'd hate to cut the expressivity of Morphir for a single front-end.

The wording on the issue is a bit confusing so I changed it.
The type of whole number literals being number is not an Elm thing. Haskell uses the same approach because just writing down 1 should not mean that you want an Int. 1 could mean a lot of things from various integer types through float to decimal or even rational. So the fundamental issue is that the text representation is ambiguous.
What makes things even more difficult is that we use literals both as a way to represent constants that are part of the business logic and as a way to work with data. For constants in the business logic we want to be a bit more abstract so a float makes little sense there while in the data it's more desirable to have specific representation formats like that.
So keeping all that in mind I suggest we keep the existing IntLiteral and FloatLiteral representations as they align nicely with existing technologies but we make it easier to deal with them consistently.
The biggest issue we have currently is in the Interpreter where we have to allow IntLiteral in place of any FloatLiteral since 1 is actually a valid Float. The first issue we have is that we cannot match on "number literals" so we end up having to cover a baunch of specific cases: https://github.com/finos/morphir-elm/blob/2e198f3ea0c7d0cff1ffff750adc22dc44693487/src/Morphir/IR/SDK/Basics.elm#L413-L423
We also have to convert Ints to Floats in many specific cases. We can solve both issues by introducing a new NumberLiteral abstraction to replace this: https://github.com/finos/morphir-elm/blob/2e198f3ea0c7d0cff1ffff750adc22dc44693487/src/Morphir/IR/Literal.elm#L35-L40
With something like this:
type Literal
    = BoolLiteral Bool
    | CharLiteral Char
    | StringLiteral String
    | NumberLiteral Number

type Number
    = Int Int
    | Float Float

The interpreter issue that motivated this suggestion was fixed by changing IntLiteral into FloatLiteral when the type inference decides that the literal should be of float type. The name IntLiteral is still slightly confusing since it doesn't necessarily mean a value of type Int. The ideal solution would be to rename it to WholeNumberLiteral so will close this and open a new issue for that.

Created #399 based on the above


The add_license_url DAG keeps timing out

Description

This DAG keeps timing out for unknown reasons when the number of items to modify is relatively high (>500k). Instead, it was verified that the batched_update DAG can handle this kind of updates for loads of millions of row. It was tested to back fill the license (by-nc-sa, 2.0) and it updated 11,090,909 records successfully.
However, continuous executions have resulted in the reappearance of licenses in the group of rows missing the field, so there could be ingestion flows that are not filling in this data or some other problem (#4318). I'd like to update the add_license_url DAG to use the batched_update and automate this process until we make sure all rows are complete.
Additional context

Related to #3885 and #4318.

Is this sufficient enough reason to switch to the batched update dag for these purposes? I know that has been suggested a few times now. What do you think?


Map layout version 123 is not supported

When I try to set up the integration I get:
2024-11-27 18:32:38.586 ERROR (MainThread) [custom_components.tuya_vacuum_maps.config_flow] Error occurred while validating: Map layout version 123 is not supported.

I'm working on adding diagnostics #5 so I can fix this issue.

Kabum 700 gave me this error:
2024-12-16 17:43:40.003 WARNING (MainThread) [tuya_vacuum.vacuum] Unknown map type: 3 2024-12-16 17:43:40.031 ERROR (MainThread) [custom_components.tuya_vacuum_maps.config_flow] Error occurred while validating: 'utf-8' codec can't decode byte 0x84 in position 0: invalid start byte


Pass suggestions-element to the slot composer

@mmandlis writes
to properly create suggestions (similar to the change:
PolymerLabs/arcs@95a1c94#diff-bb5f1da3491bde37be05eb33223c488e)
Originally filed as https://github.com/PolymerLabs/arcs-cdn/issues/80.

This was earlier fixed by https://github.com/PolymerLabs/arcs-cdn/pull/127


Menu accent color issue

When you load a config with different menu accent, the gradient bars (image below) doesn't change until you load the config twice

Happens to me aswell. It's not terrible but it's not nice to look at either.


Don't use a submodule for secrets

We're having lots of problems with using submodules for the secrets. Im just gonna copy what we are doing in iOS and clone it straight up...

@mbrandonw Actually, looks like CI is failing on secrets-related things.


Disable passive mode

Hello,
I find myself running behind a firewall where only ports 20-21 are available.
I am using pyftpdlib 1.5.6 and python ftplib as the client.
Attempting to send data to the server i get the following error.
Passive data channel timed out.

I found that forcing the client to use active mode solves the issue
ftp.set_pasv(False)

However i would like to not have my clients forced to disable passive mode themselves, and rather disable it on the server.
How would one achieve this.

I has the same problem :D @giampaolo


Organisation vs. Institution - clarify and standardize language

I'm confused by "Organisation" vs. "Institution" terminology within the tool; will confer w/ @sjDCC to make sure we clarify what's what and use consistent language; possibly compromise to use term "Affilliation"?
So far we seem to agree that "Institutional credentials" make the most sense to end users (Org creds aren't really a thing). So it follows that a user selects an "Institution" to sign in via this route. But elsewhere we consider Institutions to be a type of Org and instead refer to Org affiliations, Org guidance, etc.
Org is more inclusive to encompass funders, disciplinary orgs and data centers, etc. But for end users it might make more sense to just stick with "Institution" since that's the term that is most familiar to them.
I'm happy to be convinced either way, but right now it's confusing.

per discussion w/ @sjDCC on 22 Jun we agreed to refer to "Institutions" in the plan interface (e.g., institutional credentials, institutional visibility, etc).
TBD on the admin side of things. there it might make sense to retain the concept of an Institution as a type of Org. For now I'll move this off the project board and keep in a holding position to reassess at a later date.

flip-flopping on the previous decision after deeper consideration of future machine-actionable use cases and integrations. i think it's better to retain Org throughout the tool (as you currently have in DMPonline) and just be careful and clear with language about "institutional credentials."
i would prefer to keep Org and test w/DMPTool users. if they're not confused by it we can expand the notion of Orgs to include disciplinary communities, etc.
@briri @JEK-III @rhu001 @sjDCC if you're all in agreement, please standardize wireframes and language in UI to refer to "Organisation" (e.g., visibility, etc). the one exception is where we need to refer to "institutional credentials" (profile page, sign in).

Sure, I'm happy either way. I don't think any of these changes had worked into current code yet, but just pinging @vyruss here to make sure we hadn't done any replacement of 'Organisation' with the term 'Institution' If so, revert back ;-)

Haven't changed anything yet.

Went for org across board so closing out


Raise an informative error message when object array has mixed types

[x] Closes #2620
[x] Tests added
[x] Passes isort . && black . && mypy . && flake8
[ ] User visible changes (including notable bug fixes) are documented in whats-new.rst
[ ] New functions/methods are listed in api.rst

Before
In [2]: data = np.array([["x", 1], ["y", 2]], dtype="object")

In [3]: xr.conventions._infer_dtype(data, 'test')
Out[3]: dtype('O')

After
In [2]: data = np.array([["x", 1], ["y", 2]], dtype="object")

In [3]: xr.conventions._infer_dtype(data, 'test')
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-3-addaab43c03a> in <module>
----> 1 xr.conventions._infer_dtype(data, 'test')

~/devel/pydata/xarray/xarray/conventions.py in _infer_dtype(array, name)
    142     native_dtypes = set(map(lambda x: type(x), array.flatten()))
    143     if len(native_dtypes) > 1:
--> 144         raise ValueError(
    145             "unable to infer dtype on variable {!r}; object array "
    146             "contains mixed native types: {}".format(

ValueError: unable to infer dtype on variable 'test'; object array contains mixed native types: str,int

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

In the file xarray/conventions.py:

Line 142:61: F821 undefined name 'a'

Alternatives — not ideal ones — would be to wait until the main error is raised, or only test a subset of the values.

I thought of taking a random sample from the array and checking the types on the sample only, but I wasn't so confident about how representative this sample would be and/or how to deal with misleading, skewed samples. If anyone has thoughts on this, please let me know.

It took around 40 s for an array of 10**9 elements. That would be around 150 years of daily data (180*360*150*365). I am not sure though how much sense it makes to have such a large array with object dtype. Also an array of this size is likely a dask array and there is already a performance warning on this. So I'd say go ahead.
https://github.com/pydata/xarray/blob/68d3c340304ccc57cac569b22781e2b9c3dac913/xarray/conventions.py#L194-L197

Also an array of this size is likely a dask array and there is already a performance warning on this. So I'd say go ahead.

@mathause, just to make sure I am not misinterpreting your comment, is this a go ahead to sampling the array to determine the types? :)

Yes, I'd say go ahead. (I just hope it's not too big of a performance hit for normal use cases.)

Yes, I'd say go ahead. (I just hope it's not too big of a performance hit for normal use cases.)

Yes, I'd say go ahead. (I just hope it's not too big of a performance hit for normal use cases.)

@mathause, I am noticing a performance hit even for the special use cases. Here's how I am doing the sampling
sample_indices = np.random.choice(array.size, size=min(20, array.size), replace=False)
native_dtypes = set(np.vectorize(type, otypes=[object])(array.ravel()[sample_indices]))

and here's the code snippet I tested this on:
In [1]: import xarray as xr, numpy as np

In [2]: x = np.asarray(list("abcdefghijklmnopqrstuvwxyz"), dtype="object")

In [3]: array = np.repeat(x, 5_000_000)

In [4]: array.size
Out[4]: 130000000

In [5]: array.dtype
Out[5]: dtype('O')

Without sampling
In [6]: %timeit xr.conventions._infer_dtype(array, "test")
7.63 s ± 515 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

With sampling
In [15]: %timeit xr.conventions._infer_dtype(array, "test")
8.31 s ± 395 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

Yes, I'd say go ahead. (I just hope it's not too big of a performance hit for normal use cases.)

@mathause, I am noticing a performance hit even for the special use cases. Here's how I am doing the sampling
sample_indices = np.random.choice(array.size, size=min(20, array.size), replace=False)
native_dtypes = set(np.vectorize(type, otypes=[object])(array.ravel()[sample_indices]))

and here's the code snippet I tested this on:
In [1]: import xarray as xr, numpy as np

In [2]: x = np.asarray(list("abcdefghijklmnopqrstuvwxyz"), dtype="object")

In [3]: array = np.repeat(x, 5_000_000)

In [4]: array.size
Out[4]: 130000000

In [5]: array.dtype
Out[5]: dtype('O')

Without sampling
In [6]: %timeit xr.conventions._infer_dtype(array, "test")
7.63 s ± 515 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

With sampling
In [15]: %timeit xr.conventions._infer_dtype(array, "test")
8.31 s ± 395 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

No I wouldn't subsample. With normal use case I meant saving legitimate object arrays. I am not sure how often they occur in the wild.

No I wouldn't subsample. With normal use case I meant saving legitimate object arrays. I am not sure how often they occur in the wild.

No I wouldn't subsample. With normal use case I meant saving legitimate object arrays. I am not sure how often they occur in the wild.

I think this is most likely for lots of strings which aren't using a numpy string type.
@andersy005 to the extent the perf difference is 7 seconds vs 8 seconds, I would definitely vote to merge. The case I was originally concerned about is that something suddenly takes 1000 seconds. If we're confident that that's not the case, I would also vote to merge...


Add Cycle Time Summary data elements to Import Endpoint

Add Cycle Time Summary data elements to Import Endpoint

For Planning prioritize export endpoint before the import endpoint is completed

Pull Request: https://github.com/US-EPA-CAMD/easey-qa-certification-api/pull/273

Test Case: TC1088

Test Passed


Can't order new environment at front

Version: 2.2.3
OS: Windows 10, 10.0.19044 Build 19044
Repro:

create a new 4th env, I called it local
go to manage environments menu
order the new env such that it's at the top, above "development"
this causes the env to appear at the back, after "production" instead, when it should appear before "development" env

If you put the new env in between "development" or "staging" or at the end of "production" the order seems to work fine.

This should now be fixed as of 2.2.5


issue in checkbox of loginpage

the checkbox isn't toggling on and off, nor is it mandatory to be checked before submitting
check the video

https://github.com/user-attachments/assets/6cdd1a74-b558-4f21-a544-1941c29d74bd


Add binder link generator

Fixes #25

Looks like we need to make a new release so jupyterlab/maintainer-tools/.github/actions/binder-link@v1 can be used in other repos with the v1 tag.
I can make a 0.4.3 release with the releaser, unless you had plans for 0.5 @blink1073?

Go for it!


Ignore Paths

This PR fixes the context_benchmark by setting auto_tokens manually (it's default 0 now).
I also realize, as I add benchmarks, that there should be a way to manually exclude files from auto-context, at least in the short term.
EDIT: What we do with exclude_paths is quite complicated (see PCSwingle's comment below), so I added a new argument called ignore_paths, which are applied to auto-context. This is analogous to a .mentatignore file - which might be a good future optimization. Especially if we support non-git projects.

Reverted everything to do with exclude_paths to how it was before, and added a new arg ignore_paths to be applied to auto-context and search. This along with a test for the new arg and some misc tweaks to context_benchmark.


bad_alloc error doing whole-collection queries using RocksDB

my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

[X] 3.2.8

Mode:

[X] Single-Server

Storage-Engine:

[X] rocksdb

On this operating system:

[ ] Linux

[X] Ubuntu .deb

this is an AQL-related issue:
I'm issuing AQL via:

[X] web interface with this browser: FireFox   running on this OS: Linux Mint 18

I initially posted this over in #3655 but opened a new issue since I'm using a single server (not a cluster).
Linux Mint 18 (Ubuntu), 16gb ram.
This will crash it reliably for me:
FOR n IN 1..10000000
    INSERT {n, otherData: "test test test"} INTO TestNums

FOR n IN TestNums
    UPDATE n WITH {otherData: "test some more"} IN TestNums

I also get similar errors with large REPLACE statements, and even had it crash a few times when using arangodump.
I get two different errors, one like this:
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

And one mentioning that V8 is out of memory (don't have the exact error available right now, sorry).

(still crashes in 3.2.9)

Another query that takes 60 seconds, and then if you try to run it again it crashes ArangoDB with a similar bad_alloc message: (using the TestNums collection created above)
LET randomDoc = (FOR doc IN TestNums SORT RAND() LIMIT 1 RETURN doc._id)
RETURN randomDoc

Hi @lewisdiamond,
ArangoDB 3.4 RC1 has been released. You can find it here . Please try reproducing the crash and let us know your feedback.
Thanks!

Hi @lewisdiamond, @ropeladder,
did you already try 3.4 RC1?
FYI: The latest available 3.4 Release Candidate is RC2 and can be found in the download section.
Your feedback is highly appreciated!

Hi,
We haven't received feedback from you for a while, I am closing this issue for now.
Please consider testing this issue on 3.4.0 RC3. You can download it from the download section. If it does not resolve your problem, please feel free to reopen the issue by adding a new comment.
Thanks!


Rfx zones

I found the process of creating RFX devices a bit cumbersome. I left what you had built but I also added another way of doing things. Basically I copied your idea of setting a zone in each device, you can now also set the RF serial #. If that serial # is set, it uses the RFX messages to trigger zone faults/restore instead of the zone tracker. I also added custom attributes for the low_battery message and to keep track of the last time a supervisor checkin was received. This just seems like a much easier way to configure it to me. Let me know what you think.

I want to add a bit more functionality to this for specific loops


fix: add esm format

add esm format to resolve import issues.

Thanks a lot for this contribution I am using your polyfill and works well in our current create-react-app version 5 setup. Thanks again Sir.

Thanks a lot for this contribution I am using your polyfill and works well in our current create-react-app version 5 setup. Thanks again Sir.

@yaldram my pleasure. If you are not using the latest release with the conversion of the file extension to mjs, I would give that a try, as the original package size was restored moving to the mjs extension compared to the additional bloat required for ESM... admittedly the size difference is negligible, and functionally should be no difference between the two, however, I am curious to know if that approach works for you when using react as it seems to work well in Angular at least.

@Marshal27 Yep I am working with version 1.7 and it is working as expected.


Add formulae for anybar v0.1.2

Thank you. For future reference, we don’t call them formulae, but casks.

Okay, good. Thank you.


Fix for situation where smp shell transport can respond on a different device than it receives from

The smp shell transport is configured to work over uart shell.
The uart shell's device can be reconfigured at runtime.
The Smp shell driver currently responds on the device defined as shell in the device tree while receiving data from the uart shell whose device can be changed during runtime.
A similar fix from 2020:
https://github.com/zephyrproject-rtos/zephyr/pull/27871
The issue came back here when the shell structures were changed.
https://github.com/zephyrproject-rtos/zephyr/commit/6d2e3b59a5d1ae0d6ca6e94ee95dc68459b5fea8
This pull request takes the device from the uart_shell structures.
Fixes: https://github.com/zephyrproject-rtos/zephyr/issues/81144

If you want this fix in zephyr 4.0, it will need a github issue that this marks as fixing, if so could you open one?

@zakport , can you add a Zephyr issue with details about the problem seen and link it to this PR.

Hey,
I created an issue https://github.com/zephyrproject-rtos/zephyr/issues/81144


X Axis Tick Count

Is it possible to set the x-axis tick count ?
Example: http://c3js.org/samples/axes_x_tick_count.html

This option is not implemented yet, but it will be added with the other configuration parameters in the 0.3 version of angular-chart

You can now set the tick count in the chart part of the options.
See a working example in this grafiddle.


🐛 [firebase_UI_auth] "credential linked" callback not getting called

Bug report
If someone registers using google federated login, then on the profile page they add an additional signin method of email/password, they are asked for email address and password.   The profile page updates correctly to show the second login method. If the user has entered a different email address from their google federated login, an email is sent to the users old google email address telling them that their email address has been changed to the new one.  The new email address becomes the users primary email address on firebase  - accessible via user.email.  However the system (the example app) fails to immediately verify the users new email address.  If they log out and back in, they do get asked to verify the new email address.  The system should immediately ask them to verify the new email address without them logging out and back in.  I tried adding an auth state change for "credential linked" to the profile screen constructor but it did not get triggered.
      return ProfileScreen(
        actions: [
          AuthStateChangeAction<CredentialLinked>((context, state) {
            if (!state.user.emailVerified) {
              Navigator.pushNamed(context, '/verify-email');
            } else {
              Navigator.pushReplacementNamed(context, '/profile');
            }

Steps to reproduce
Use the example app and follow the description above.
Expected behavior
The user should be asked to verify their email address immediately, possibly via the CredentialLinked callback.

Whereabouts do I put that code?

@graemep-nz assuming this is reproducible on web (since CredentialLinked is properly propagated on other platforms), https://github.com/firebase/flutterfire/pull/11168 this should fix it.


floating label feature fixed for select component

Hi, I have just updated select component to work more consistent with approach introduced in mdl-textfield component in addition to label and placeholder managing. The way it works now is:

placeholder is applied only for input field (previously it was set to floating label)
label input property has been added
floating-label works only with label field

So for now we have two options: we can use placeholder or label (optionally with floating-label) as in mdl-textfield component.

Coverage increased (+0.4%) to 94.753% when pulling 1e450782dd8b9cf3c965c2a96b5fcde3084d245b on adasq:master into 2d08663bcd5091d354ef02057ab4d2bd0dec99e7 on mseemann:master.

hi. sorry form the late replay! is this a breaking change?

Hey, placeholder value will no longer acts as floating-label, so yes - it is breaking change.

ok, can you add a hint to the readme in the select package? also i would set the version of the select package to 0.9.0 or is it more suitable to set the version to 1.0.0? thx.

Coverage increased (+0.4%) to 94.753% when pulling fd1379a9d298b08ffca63ce9b68fce7ebc1bca15 on adasq:master into 2d08663bcd5091d354ef02057ab4d2bd0dec99e7 on mseemann:master.

Sure, README has been updated.
As it is still in experimental status, I would suggest setting 0.9.0.

thx a lot! will be released in a few minutes...

Thanks!


Tutorial completion

It is a pity that the tutorial was not smoothed out and completed. Although I manage to fill the (few) gaps here and there, due to my own ignorance, I could not make the Slack - Wiki integration running.

Same here. Getting http client error.  Will work on some things.


Move detail namespace into separate files

Details for DragInput, Input etc.

Builders and such should be moved as well


New Crowdin updates

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

v0.41.2
GitHub release

Your semantic-release bot :package::rocket:


how to setup?

please help, I'm a noob

If you already have the webui installed, you can set it up by going to the extensions tab > Install from URL > paste https://github.com/ModelSurge/sd-webui-comfyui into the textbox and press install. When it is done installing, go back to extensions > Installed tab and press "Apply and restart".


MSGraphClient and External Users

Category

[x] Question
[ ] Typo
[ ] Bug
[ ] Additional article idea

Expected or Desired Behavior
We are using MSGraphClient to get the user profile photo.
Observed Behavior
401 errors occur when the user is an external one and trying to request https://graph.microsoft.com/v1.0/me/photo/$value. What permissions should be given to the user?

Please submit this through the StackOverflow. We can only support dev topics through this issue list. Sorry for the inconvenience.


[FEATURE] Change NumberOfReplicas only for one deployment

It would be a good option to be able to change the number of replicas for a single deployment or pvc, and override the global configuration NumberOfReplicas.
There are some deployments that don't really require replication, for example elasticsearch eck implement their own index replication internally, and replication on top just takes up disk space unnecessarily.

@joepa37
You can edit the volume's replica count directly.
To change the global setting, you can edit setting > general > replica count.

Yes, I know there is a option to change the global replica count (NumberOfReplicas), for that reason I am asking for "for a single deployment or pvc" feature.

Why not create a dedicated storage class for the volumes?

Thanks for your response. Can I create a second longhorn storage class?
That would be perfect since the rancher's local-path storage class doesn't support AllowVolumeExpansion.
Can I have

Longhorn (default) with 3 NumberOfReplicas
Longhorn (single) with 1 NumberOfReplicas

How can I install the second storage class and prevent kubernetes from getting confused with each other's CRDs?

Solution: I created this second storage class following this doc resource
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: single
provisioner: driver.longhorn.io
allowVolumeExpansion: true
reclaimPolicy: Delete
volumeBindingMode: Immediate
parameters:
  numberOfReplicas: "1"
  staleReplicaTimeout: "2880" # 48 hours in minutes
  fromBackup: ""
  fsType: "ext4"
  dataLocality: "best-effort"

Everything is running smoothly


Added .unsubscribe() and .force_update() fn's to Fermi

I suggest this PR to be more flexible with Fermi.

Nice, i hope it will be merged asap :)


Ray doesn't show file that executed ray helper

Windows 10, IIS
Laravel v8.21.0
Controller:
class MyController extends Controller
{
    ...
    public function index()
    {
        ray()->showQueries();

        ray('Hello world');

        return $this->repository->allCarWashes();
    }
    ...
}

Changing 'ray/src/helpers.php' to  'ray\src\helpers.php' helps on Windows
https://github.com/spatie/laravel-ray/blob/8eb9f9ad37a64f8327f032baca08c0fed78e558e/src/OriginFactory.php#L52

Changing 'ray/src/helpers.php' to  'ray\src\helpers.php' helps on Windows
https://github.com/spatie/laravel-ray/blob/8eb9f9ad37a64f8327f032baca08c0fed78e558e/src/OriginFactory.php#L52

Resolved in PR #20

Resolved in PR #20


Generate base interface for __typename operations

Use case
When using  addTypename.set("always"), Apollo generates models all with __typename fields.
These fields are unique to each fragment, query data, etc. We want to capture those field names for debugging / logging purposes easily in a unified way. :
public data class SomeType(
  public val __typename: String,
  public val title: String,
) : Fragment.Data

public data class AnotherType(
  public val __typename: String,
  public val title: String,
) : Fragment.Data

We cannot find a common interface to easily do this, and have to manually switch on each instance of fragment , which is not safe and prone to error:
fun logTypeName(input: Fragment.Data) {
 when(input){
  is SomeType -> input.__typename
  is AnotherType -> input.__typename
  else -> error("Unhandled fragment type")
 }
}

Describe the solution you'd like
Create an interface:
interface HasTypeName {
  val typename: string
}

that all generate files implement if:

 addTypename.set("always")
Or __typename is requested in the query:

query SomeQuery {
  user {
     __typename
   }
}

Then
public data class SomeType(
  public override val __typename: String,
  public val title: String,
) : Fragment.Data, HasTypeName

public data class AnotherType(
  public override val __typename: String,
  public val title: String,
) : Fragment.Data, HasTypeName

logTypename becomes:
fun logTypeName(input: HasTypeName)  = input.__typename

Thanks for sending this 🙏 . I'd love this to be another use case of https://github.com/apollographql/apollo-kotlin/issues/4026.
We're currently thinking of an API that would expose the KotlinPoet typeSpecs before actually writing them so that you have the chance to patch them. This would allow to experiment with this kind of things without having to make a new release of apollo every time and more generally be more flexible in what is generated. Any thoughts about this?

@agrosner You can know use the KotlinCompilerHooks API from 3.7.0 to do so. You can find an example in the integration tests: https://github.com/apollographql/apollo-kotlin/blob/fb51dafaa4b02a55b6926546927d176078513543/tests/compiler-hooks/build.gradle.kts#L134
Let us know how that works for you.

woah @martinbonnin this is so cool. ill have to try this out when we upgrade. we're on 3.5.0 at the moment, but in process of upgrading this week.

I apologize for not responding so fast previously

No worries at all, let us know what you think!

I'm going to close this one for now, feel free to comment if the KotlinCompilerHooks solution doesn't work and we'll dive more.

Oh thanks for reminding me. We are using the compiler hooks with success. Thank you!


Binance MySQL,  SQL error: (1062, "Duplicate entry '748' for key 'PRIMARY'")

when running Binance , there is always an
SQL error: (1062, "Duplicate entry '748' for key 'PRIMARY'")
I'm a DBA and I have no experience with python, just read little documents,
so if following issue analysis maybe incorrect .
I have done some trace,
BTCUSDT 747
print from following code in gateway.py
    def get_instmt_snapshot_id(self, instmt):
        with self.lock:
            self.exch_snapshot_id += 1
            print(instmt.instmt_name, self.exch_snapshot_id)

ordrbook BTCUSDT 747  ----> print from gateway.py  insert_order_book
trade BTCUSDT 746    ----> print from gateway.py insert_trade
BTCUSDT 747
ordrbook BTCUSDT 747
BTCUSDT 748
ordrbook BTCUSDT 748
BTCUSDT 746
trade BTCUSDT 746

BTCUSDT 749
ordrbook BTCUSDT 749
BTCUSDT 747
trade BTCUSDT 747

BTCUSDT 750
ordrbook BTCUSDT 750
BTCUSDT 748
trade BTCUSDT 748

BTCUSDT 749
trade BTCUSDT 749

BTCUSDT 750
trade BTCUSDT 750

from above trace message
we can find that the exch_snapshot_id for trade worker is not synced with exch_snapshot_id for orderbook worker.
eg,  orderbook worker get exch_snapshot_id 747 first  , and insert order_book to snapshot tables with id 747
and then , after some time , trade worker get exch_snapshot_id 747,  when trade worker insert into same snapshot table with id 747, there will be a duplicate pk error.
to reslove this,  ether add some Synchronization mechanism to make exch_snapshot_id synced in both worker.
or , insert trade and orderbook into different table.
Here I also have another question , why put the trade data and order book data into same table?

#107
maybe related with issue 107

#107

Yes I spotted that a few exchanges use multiprocessing.Process to spawn the child processes, rather than thread. The lock does not work on that way. It will be resolved soon.
Thanks for reporting the issue.

Here I also have another question , why put the trade data and order book data into same table?

Well it's due to the design to make analysis easy. Open to hear how the users use this project and the expected changes to facilitate your work.

In my case, I have a problem with Bitfinex exchange. But I think it does not have a problem with locks. It shows the same error if there are some records in the table. In other words, if you start with empty tables, there is no problem.
@pelyxp does the problem occurs even when you start with empty tables?

@ddeath the problem occurs whether start with an empty table or not
following is a log for start from empty tables.
`XRPETH 1
ordrbook XRPETH 1
ETHUSDT 1
ordrbook ETHUSDT 1
ETHUSDT 2
ordrbook ETHUSDT 2
XRPETH 2
ordrbook XRPETH 2
ETHUSDT 1
trade ETHUSDT 1
2018-03-02 00:17:00,322 - INFO
[MysqlClient]
SQL error: (1062, "Duplicate entry '1' for key 'PRIMARY'")
ETHUSDT 2
trade ETHUSDT 2
2018-03-02 00:17:00,333 - INFO
[MysqlClient]
SQL error: (1062, "Duplicate entry '2' for key 'PRIMARY'")
ETHUSDT 3
ordrbook ETHUSDT 3
ETHUSDT 3
trade ETHUSDT 3
2018-03-02 00:17:02,276 - INFO
[MysqlClient]
SQL error: (1062, "Duplicate entry '3' for key 'PRIMARY'")
ETHUSDT 4
trade ETHUSDT 4
ETHUSDT 5
trade ETHUSDT 5
ETHUSDT 6
trade ETHUSDT 6
ETHUSDT 7
trade ETHUSDT 7
ETHUSDT 8
trade ETHUSDT 8
ETHUSDT 9
trade ETHUSDT 9
ETHUSDT 10
trade ETHUSDT 10
ETHUSDT 11
trade ETHUSDT 11
ETHUSDT 12
trade ETHUSDT 12
ETHUSDT 13
trade ETHUSDT 13
ETHUSDT 14
trade ETHUSDT 14
ETHUSDT 15
trade ETHUSDT 15
ETHUSDT 16
trade ETHUSDT 16
XRPETH 3
ordrbook XRPETH 3
ETHUSDT 4
ordrbook ETHUSDT 4
2018-03-02 00:17:04,175 - INFO
[MysqlClient]
SQL error: (1062, "Duplicate entry '4' for key 'PRIMARY'")     `


pac solution import / export operations shows random % complete when using async flag

Hi Team,
When using pac solution import with --async the progress results show a % complete value which is not a true value. It shows a very low % value and usually ends at some random percentage between 1 and 10.

The phrasing is not really clear here, but that percentage is not a work-done percentage, but a percentage of the max wait time before pac times out.   The Dataverse services don't provide any information about the progress of the task other than "running, failed, complete", so it's not possible for pac to give a reasonable work-done percentage.

Thanks @tehcrashxor , the percentage makes much more sense now :)
For reference though, the statement around Dataverse services not providing information about progress, is not entirely true. Async solution import jobs do provide a progress indicator. Solution Upgrade jobs don't though.
Prior to wanting to use the pac solution import (as we use many of the other pac cli tools too) we were using the ImportSolutionToCrmAsync method of the CrmServiceClient which returns a .progress property. Just FYI ;)
Polling Import for Solution: WSDTBase : In Progress - 90.58%
Polling Import for Solution: WSDTBase : In Progress - 90.58%
Polling Import for Solution: WSDTBase : In Progress - 90.58%
Polling Import for Solution: WSDTBase : In Progress - 90.78%
Polling Import for Solution: WSDTBase : In Progress - 90.78%
Polling Import for Solution: WSDTBase : In Progress - 90.78%
Polling Import for Solution: WSDTBase : In Progress - 90.98%
Polling Import for Solution: WSDTBase : In Progress - 91.38%
Polling Import for Solution: WSDTBase : In Progress - 91.58%
Polling Import for Solution: WSDTBase : In Progress - 92.38%
Polling Import for Solution: WSDTBase : In Progress - 92.79%
Polling Import for Solution: WSDTBase : In Progress - 92.99%
Polling Import for Solution: WSDTBase : In Progress - 100.00%
Polling Import for Solution: WSDTBase : Succeeded - 100.00%
Applying Upgrade to Solution
Async Operation ID: f9e99cb7-e0bb-ed11-83fe-00224818a66b
Polling Promotion status for Solution: WSDTBase : In Progress
Polling Promotion status for Solution: WSDTBase : In Progress
Polling Promotion status for Solution: WSDTBase : In Progress

PAC uses the DatverseServiceClient's ImportSolutionAsync(...), which returns an Async Operation ID.
We then poll over GetEntityDataByID("asyncoperation", jobId, ...), but that response does not have any progress property.


7.8.4

7.8.4 has been out for quite some time now and is more stable than 7.8.3. I tried to modify the Dockerfile to install 7.8.4 but ran into problems.
W: Failed to fetch http://deb.haskell.org/stable/./Release.gpg  Cannot initiate the connection to deb.haskell.org:80 (2001:4801:7824:101:b6d8:5ee5:ff11:5e07). - connect (101: Network is unreachable) [IP: 2001:4801:7824:101:b6d8:5ee5:ff11:5e07 80]

W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
E: Unable to locate package ghc-7.8.4
E: Couldn't find any package by regex 'ghc-7.8.4'
2015/03/22 09:02:21 The command [/bin/sh -c apt-get

It looks like deb.haskell.org is down: http://www.downforeveryoneorjustme.com/http://deb.haskell.org/stable/

cf. https://status.haskell.org/

February 25, 2015 4:00PM CST / February 25, 2015 10:00PM UTC
[Investigating] deb.haskell.org remains down while we discuss restoring functionality.

Yes, I was re-attempting this yesterday, but since deb.haskell.org has been down (since Feb) it obviously failed.
We could switch the base image to Ubuntu, which would allow us to use a ppa but a better solution may be switching to installing from downloads.haskell.org for 7.8.4. (I'll look into this)

@nomeata I believe you run deb.haskell.org from what I could glean. Hope you don't mind me pinging you for your opinion here.

Ah, there are users of deb.haskell.org? That’s news to us... :-)
I don’t know when deb.haskell.org will be back, that’s up to<EMAIL_ADDRESS>You can indicate interest, though...

thanks @nomeata
I sent an email. If it doesn't look like deb.haskell.org will be up in a timely manner, Using hvr's ppa as described here seems to be the best solution going forward.

Even if the Debian repo comes back up, will it have the latest version 7.10.1 just released?  How about 7.8.4?  Before it went down, it still had 7.8.3, so we were stuck in this situation anyway.  In the past week 7.10.1 was released and is really the only supported version now, but we could probably convince the official image powers that be to accept a three month late 7.8.4 tag.
I resurrected my haskell Dockerfiles + hacky tests and put them back up at https://github.com/psftw/docker-haskell. These are based on upstream release binaries designed for deb7, which seem to be better supported and released in tandem with GHC releases.  The downside of these is that they still need alex/happy and are huge in comparison:
$ docker images haskell
REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
haskell             7.8.3               c0a54a2c768a        9 hours ago         1.675 GB
haskell             7.10.1              6e0de97b397b        9 hours ago         1.817 GB
haskell             7.8.4               f3b9a46aced8        10 hours ago        1.799 GB
haskell             latest              bc0206a9b75f        8 weeks ago         601.4 MB
haskell             7.8                 bc0206a9b75f        8 weeks ago         601.4 MB

I'm not sure why they are so big or how much fat could be trimmed.  Anyhow, just another idea/option if there is interest.  It looks like the PPA mentioned above is up to date, and at least semi-official based on who is maintaining it.

It looks like there are a bunch of files like /usr/local/lib/ghc-7.10.1/ghc_EMlWrQ42XY0BNVbSrKixqY/libHSghc-7.10.1-EMlWrQ42XY0BNVbSrKixqY_p.a in there that seem to be temp files. I'm not sure why make install would copy those out of /usr/src/ghc.

Yup, strange those were included.  They appear to be archives of object files, which are totally unnecessary.  I need to find out more about the configure/install options for the binary releases.  I see other things such as docs that could be disabled as well.

@psftw Any chance you could rebase that against this repo to get a shared ancestor?

@psftw #21 is probably relevant if we're going to switch to your dockerfiles.

@md5 I don't think that would make sense as it's totally different history, and I'm not convinced it is the best solution to the problem yet either.
@ChristopherBiscardi cool, I've somehow missed that ping and that issue altogether.  I will check it out for sure, and I can hit both methodologies with the same test scripts from my GH repo.

tags 7.8 and 7.8.4 are now on the registry.
7.10.1, 7.10, 7, latest now point to 7.10 as well.
Please file issues if you encounter difficulties with the new tags.

Thank you! I just upgraded.


Build failure due to ambiguous symbol

I’m seeing a build failure with ghc-8.8.1 and current hie-bios (0.3.0) & ghcide (6cf1d60d8a763e07fe778695faf5e5c423cc1fcc):
$ cabal update
$ cabal install exe:ghcide
…
In order, the following will be built (use -v for more details):
…
 - hie-bios-0.3.0 (lib) (requires download & build)
…
exe/Main.hs:116:78: error:
    Ambiguous occurrence ‘Info’
    It could refer to
       either ‘Development.IDE.Types.Logger.Info’,
              imported from ‘Development.IDE.Types.Logger’ at exe/Main.hs:27:1-35
           or ‘Development.Shake.Info’,
              imported from ‘Development.Shake’ at exe/Main.hs:41:1-37
              (and originally defined in ‘shake-0.18.4:Development.Shake.Internal.Options’)
    |
116 |         ide <- initialise mainRule (pure $ IdInt 0) (showEvent lock) (logger Info) (defaultIdeOptions $ return $ return . grab) vfs
    |                                                                              ^^^^

Easy enough to work around locally:
-        ide <- initialise mainRule (pure $ IdInt 0) (showEvent lock) (logger Info) (defaultIdeOptions $ return $ return . grab) vfs
+        ide <- initialise mainRule (pure $ IdInt 0) (showEvent lock) (logger Development.IDE.Types.Logger.Info) (defaultIdeOptions $ return $ return . grab) vfs

Originally encountered by @aymannadeem & myself.

#272 fixes the issue, I’ve published a revision to Hackage that adds an upper bound.

Thank you!


Using multiple templates as starter for LCEL

Issue with current documentation:
Dear all,
Happy new year!
Due to work legacy stuff, I am still forced to use this library. I am wondering if there is a way to pass multiple prompt template (system, human and ai) instead of just one
Hopefully my man Dosubot can help!
Thanks you so much
Cheers,
Fra
Idea or request for content:
No response

🤖
Hello @FrancescoSaverioZuppichini! 😄
Happy New Year to you too! It's always a pleasure to see familiar names like yours pop up on the issue tracker.
I'm currently diving into your question about multiple prompt templates. Hang tight, and I'll be back with a full answer shortly.

my man! how are you? Love to see you back

?


Cannot use command podman and docker at Pipeline build in containerd environment

I cannot use command podman and docker at Pipeline build in containerd environment normally.
Environment
Container runtime: containerd
KubeSphere: v3.2.0
Kubernetes: 1.19.14
Steps to reproduce

Change base pod template in ConfigMap jenkins-casc-config#jenkins_user.yaml
     templates:
       - name: "base"
         namespace: "kubesphere-devops-worker"
         label: "base"
         nodeUsageMode: "NORMAL"
         idleMinutes: 0
         containers:
         - name: "base"
-              image: "kubespheredev/builder-base:v3.2.0"
+              image: "kubespheredev/builder-base:v3.2.0-podman"

Wait for 70s at least

Create DevOps Project and Pipeline, and it's Jenkinsfile is as follows:
pipeline {
agent {
  label "base"
}

stages {
  stage ('Test podman') {
    steps {
        container ('base') {
            sh '''
            podman version
            podman pull halohub/halo
            '''
        }
      }
    }
  }
}

Run the Pipeline and got the following error:
+ podman version
Error: mount /var/lib/containers/storage/overlay:/var/lib/containers/storage/overlay, flags: 0x1000: operation not permitted
script returned exit code 125

I've figured out a work around which we can use docker or podman command in containerd container runtime. As shown below:
pipeline {
  agent {
    kubernetes {
      inheritFrom 'base'
      containerTemplate {
        name 'base'
        image 'kubespheredev/builder-base:v3.2.0-podman'
        privileged 'true'
      }
    }
  }

  stages {
    stage('Print Podman version') {
      steps {
        container('base') {
          sh '''
          podman version
          podman pull halohub/halo
          '''
        }
      }
    }
  }
}

See also about Dockerless https://github.com/kubesphere-sigs/ks-devops-helm-chart/tree/master/charts/ks-devops#dockerless.

/close

Please notice that the following usage is not recommended:
  agent {
    kubernetes {
      inheritFrom 'base'
      containerTemplate {
        name 'base'
        image 'kubespheredev/builder-base:v3.2.0-podman'
        privileged 'true'
      }
    }
  }

We suggest that users put that configuration into podTemplate.


Manifest Version Updates to v1.19

executed build pipeline:
https://github.com/OfficeDev/Microsoft-Teams-Samples/actions/runs/12112677998


Optimize createIdentifier() on Nodejs/v8, ~30% faster

This PR is also a question at the same time for ticket #3594
Are these sorts of optimizations accepted? Used around 100 000 interfaces to look at function overloading costs and stumbled on this.

Hi @jbondc, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Are these sorts of optimizations accepted?

Absolutely! I think we just need to confirm this on our end. I assume you mean a 30% decrease in time spent in createIdentifier. What kind of changes in time are we seeing in the two calling functions (parseIdentifier and parseIdentifierName)?
Regardless, I actually prefer this code because the intent is much more explicit.

With patch: jake LKG
PS E:\OPENSOURCE\TypeScript> node .\bin\tsc.js --diagnostics --noLib .\tests\labs\bench\inheritance.bench.ts
error TS2318: Cannot find global type 'Array'.
....
Files:               1
Lines:          440016
Nodes:          850033
Identifiers:    420014
Symbols:        410010
Types:           10019
Memory used:   422080K
I/O read:        0.19s
I/O write:       0.00s
Parse time:      4.66s
Bind time:       3.05s
Check time:      8.13s
Emit time:       0.04s
Total time:     15.88s

Revert the changes of patch and build master: jake
PS E:\OPENSOURCE\TypeScript> node .\built\local\tsc.js --diagnostics --noLib .\tests\labs\bench\inheritance.bench.ts
error TS2318: Cannot find global type 'Array'.
....

When I try to compile down typescriptServices.js, I'm getting very close or inconsistent results (probably due to V8 variance). If you'd like to share a gist so we can see similar numbers, that would be helpful.
Regardless of the degree of optimization, :+1:

Do you get perf benefits consistently if you run the test i.e. 10 times?  I can see the reason why parse time can decrease, but difference in in check time look strange since createIdentifier is not used in the checker - I would consider it more like a noise.

Well after upgrading to node 12, this patch can probably be closed:
PS E:\OPENSOURCE\TypeScript> node .\tests\labs\bench\parser\v8\source.js
0,907407571s - 100000 patch identifiers created
0,805910181s - 100000 master identifiers created
PS E:\OPENSOURCE\TypeScript> node .\tests\labs\bench\parser\v8\source.js
0,913622412s - 100000 patch identifiers created
0,808447087s - 100000 master identifiers created
PS E:\OPENSOURCE\TypeScript> node -v
v0.12.4
PS E:\OPENSOURCE\TypeScript>  E:\OPENSOURCE\node-win32\node-10.39.exe .\tests\labs\bench\parser\v8\source.js
0,774618857s - 100000 patch identifiers created
0,840980300s - 100000 master identifiers created
PS E:\OPENSOURCE\TypeScript>  E:\OPENSOURCE\node-win32\node-10.39.exe .\tests\labs\bench\parser\v8\source.js
0,783119609s - 100000 patch identifiers created
0,846238893s - 100000 master identifiers created
PS E:\OPENSOURCE\TypeScript>  E:\OPENSOURCE\node-win32\node-10.39.exe .\tests\labs\bench\parser\v8\source.js
0,773275722s - 100000 patch identifiers created
0,833018498s - 100000 master identifiers created

Oddly enough, the patch is only better with the older v8. Test I used here:
https://gist.github.com/jbondc/3577d48ecfc2ab2a8aa6
Probably better to optimize other parts of compiler than this.

fair enough. I'm closing this PR since we are not getting consistent perf benefits across the widely used versions of node. Thanks for figuring this out!

@vladima @mhegazy would we feel okay accepting this for the sake of making intent more explicit in the code?

The code change looks fine to me. if you want to do a quick perf test using the internal perf script to see if there is any unintended effects on other scenarios, i am fine taking it.

Hi @jbondc, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Great. I'm reopening, and I'll do a RWC perf test when I'm back in the office

looking again at perf numbers, looks like this is slower on node v 0.12; closing again. sorry for the noise. did not see these first time around.


no color output in make command generate by cmake

it seem that only st terminal has no color output in make command

in left is the st,and sakura(an other terminal) in right
I have no idea about how to fix it.

It seem`s that change termname to xterm-256color work, but I wonder why？


AStar2D bidirectional

This pull request closes godotengine/godot-proposals#4142 - it can be cherry-picked for 3.x

@akien-mga should be added. Tested and looks ok.

Cherry-picked for 3.5.


template error

Template doesn't work with the latest version

backend/src/Backend.hs:14:29-47: error:
    • Couldn't match type ‘Data.Functor.Sum.Sum
                             BackendRoute (Obelisk.Route.ObeliskRoute FrontendRoute)’
                     with ‘Obelisk.Route.FullRoute BackendRoute FrontendRoute’
      Expected type: Obelisk.Route.Encoder
                       (Either Data.Text.Internal.Text)
                       Data.Functor.Identity.Identity
                       (Obelisk.Route.R
                          (Obelisk.Route.FullRoute BackendRoute FrontendRoute))
                       Obelisk.Route.PageName
        Actual type: Obelisk.Route.Encoder
                       (Either Data.Text.Internal.Text)
                       Data.Functor.Identity.Identity
                       (Obelisk.Route.R
                          (Data.Functor.Sum.Sum
                             BackendRoute (Obelisk.Route.ObeliskRoute FrontendRoute)))
                       Obelisk.Route.PageName

By any chance was this template generated by a months-old obelisk?
When FullRoute was added, the skeleton was also updated to use it: https://github.com/obsidiansystems/obelisk/commit/b6da186353c525aaf674e16933b48311dca5a1d3#diff-74f0557b71855f6d339b789317ca8ad6R14

Hm, I did reinstall ob beforehand, I will try it again

Yeah if you run ob init and then later ob thunk update .obelisk/impl then your template can be out-of-sync with the version of obelisk you just upgraded to.

Ok, it does work but nix-shell -A shells.ghc gives me
error: attribute 'shells' in selection path 'shells' not found

Thanks, it works fine


Support additionalData for the lightningcss css transformer

Description
The additionalData option for other preprocessors is extremely valuable in sharing variables and other items to other files without explicit inclusion. While this largely isn't necessary for most things with Lightning CSS, it's still really useful for sharing @custom-media directives throughout your CSS.
Suggested solution
Offer the ability to prepend a string to all CSS files/segments when using the Lightning CSS transformer.
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

I've been tinkering with this issue and it seems like CSS plugin skips preprocessing steps if the transformer is lightningCSS(1), thus it can't benefit from the additionalData option. additionalData might be better as a separate option rather than a sub-option under css.preprocessorOptions, since it isn’t originally a preprocessing option. It really is an additional field.
Would it make sense to move it up as css.additionalData so that it could also be available to non-preprocessed CSS?
(1):
https://github.com/vitejs/vite/blob/bb2f8bb55fdd64e4f16831ff98921c221a5e734a/packages/vite/src/node/plugins/css.ts#L1215-L1223

As it's called out in doc https://vitejs.dev/config/shared-options.html#css-preprocessoroptions-extension-additionaldata, one of the intended usage is to inject a pre-processor specific variable since otherwise it would cause a duplication:

Note that if you include actual styles and not just variables, those styles will be duplicated in the final bundle.

For this reason, using additionalData for raw css files might not be recommended.
@soluml I'm not familiar with @custom-media. Can you elaborate how you intend to use additionalData and whether it would cause style duplication (or is it something lightningcss would transpile it away)?

While it seems reasonable to support additionalData for lightningcss, I'm wondering if this can be easily implemented as Vite plugin.
I made an example here https://github.com/hi-ogawa/reproductions/tree/main/vite-17724-lightningcss-custom-media
import { defineConfig } from "vite";

export default defineConfig({
  css: {
    transformer: "lightningcss",
    lightningcss: {
      drafts: {
        customMedia: true,
      },
    },
  },
  plugins: [
    {
      name: "css-additional-data",
      enforce: "pre",
      transform(code, id) {
        if (id.endsWith(".css")) {
          // probably shouldn't inject `@custom-media` directly since it can cause an error such as:
          //   @import rules must precede all rules aside from @charset and @layer statements
          return `@import "/src/custom-media.css";` + code;
        }
      },
    },
  ],
});

@hi-ogawa, thanks for the code snippet! I tested it and it works great. According to the LightningCSS documentation, imports should be relative only so I'm surprised this works. To handle the case of precedence for @charset and @layer which has to be before @import, I modified the snippet a little:
import { defineConfig } from 'vite';

export default defineConfig({
	build: {
		cssMinify: 'lightningcss',
	},
	css: {
		transformer: 'lightningcss',
		lightningcss: {
			targets,
			drafts: {
				customMedia: true,
			},
		},
	},
	plugins: [
		{
			name: 'css-additional-data',
			enforce: 'pre',
			transform(code, id) {
				if (id.endsWith('.css')) {
					const parts = code.split('\n');
					let insertIndex = 0;

					// Skip @charset and @layer statements
					for (const part of parts) {
						const trimmedPart = part.trim();
						if (
							trimmedPart.startsWith('@charset') ||
							trimmedPart.startsWith('@layer')
						) {
							insertIndex++;
						} else {
							break;
						}
					}

					// Insert the @import rule
					parts.splice(insertIndex, 0, '@import "/app/styles/_media.css"');

					return parts.join(';');
				}
			},
		},
	],
});

This approach could be a problem when parsing minified code e.g. third party CSS but typically they shouldn't need @custom-media. On the other hand, splitting on semi-colons has a whole load of edge cases such as semi-colons in url() or content etc. To cover those cases, an actual CSS parser would make sense over simple JS string manipulation.

Alternatively, you can actually just simply import @custom-media directly because it will be transpiled away until the syntax is moved outside draft status and is widely supported. Bit of a ticking time bomb that might break builds in a few years, but imo it's a much safer approach than any of the other approaches above otherwise.
import fs from 'node:fs';
import { defineConfig } from 'vite';

const customMedia = fs.readFileSync('./app/styles/_media.css', 'utf-8');

export default defineConfig({
	build: {
		cssMinify: 'lightningcss',
	},
	css: {
		transformer: 'lightningcss',
		lightningcss: {
			targets,
			drafts: {
				customMedia: true,
			},
		},
	},
	plugins: [
		{
			name: 'css-custom-media',
			enforce: 'pre',
			transform(code, id) {
				if (id.endsWith('.css')) {
					return `${customMedia}\n${code}`;
				}
			},
		},
	],
});

@mattpilott thanks for the snippet, it works just fine for CSS files. However, a similar strategy doesn't work with styles declared inside the <style> block of Astro and Vue components. Is there a solution?

Hey @ShayanTheNerd im not sure why it wouldnt work in those frameworks, i use svelte and its working in component


Psych engine 0.6.2 song crash

Describe your problem here.
Everytime I load up a song it shows the stage and the characters but nothing happens, no arrows, no time bar,
Nothing it just stays at that
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No

you need a
return Function_Continue
on your onStartCountdown function

Or you don’t have your songs in the right place

You sure?

Yah but what do I use the return Function_Continue on? And it's in songs/songname

Oop wait

I don't think I have any onStartCountdown function


Update code.json

more translate to Chinese
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Which issue(s) this PR fixes:

Documentation
i18n code transalte to Chinese of almost message field

Special notes for your reviewer:

make karmada is great

/assign @pigletfly Please get your student involved.

ok

@SAMZONG You might have to squash your commits.

@RainbowMango it's done.

@SAMZONG You might need to sign your commits.
Here is a guideline:https://github.com/karmada-io/website/pull/89/checks?check_run_id=7065413929

@RainbowMango Thanks, I got it, pls confirm

/approve


Revisit MCMC diagnostic plots

We should revisit the display and discussion around MCMC diagnostics.  Is what we have sufficient?  What else should be included?  Does MCMC work completed by Cole Monnahan (Trevor Branch student) have any significance to these decisions (MCMC diagnostics and/or MCMC runs and/or software, etc...).

I know Cole gave a talk the other week that I didn't sit in on, but I think nothing is published and so wouldn't have any bearing. I think Trevor mentioned that it might not even work out, and since he didn't give us an explicit reference I don't think we need to include anything.
Maybe, yes, just check the diagnostics text again, and update main text to point to the new Appendix.

Yep, that is all I'm doing via #278.  I labelled this one for milestone 2018 just to remember to look at (if anything) comes out of that work as well as revisit mcmc diagnostics next go around.

Cole's improvements to ADMB just being merged into main ADMB for testing now. Not ready for 2018 hake assessment.
Leaving open to remind us to at least research what the status-quo diagnotics means so we can answer any questions if they happen to arise.

I haven't done anything with updating ss with new version of ADMB that would likely allow our use of Cole's adnuts package, so not doing anything further on that.
I did compare two separate mcmc chains and the diagnostics look good.  Output probably just useful for SRG discussion, rather than inputting into assessment document.
KeyParameterTrace.pdf
KeyParameterGelman.pdf

The within chain and among chain variance is compared using a shrink factor, and typically anything less than 1.1 or 1.05 is considered good in terms of convergence.  Just comparing some key posterior values here, but also did all the nuisance parameters as well.  bottom-line = no worried about convergence, similar to what our standard single chain diagnostics indicate.

Thanks Aaron - yes, they seem to look good.
Is it worth including in the document (given you've made them)? Can just put them in as they are (if you can make .eps), rather than automate them (just don't tell Chris).
Or, yes, just show at the SRG. Which will be easier, but I kind of feel if it's worth showing at the SRG it's probably worth having in the document.

I just uploaded eps files for these into the main-figures folder.  We can eventually decide if we want them in the document or just for SRG presentation.  I could go either way, but originally thought just for SRG discussion.
I think this issue can be closed for now, but (I) need to remember to do a memory refresh of all diagnostic plots before SRG.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v4.14.253",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4ec0f9abc512cc02fb04daa89ccf6697e80ab417"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "4ec0f9abc512cc02fb04daa89ccf6697e80ab417",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "net: mdiobus: Fix memory leak in __mdiobus_register\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.14.253 by commit 4ec0f9abc512cc02fb04daa89ccf6697e80ab417. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001962


Not compatible with VSCode Insiders

Wasn't able to install 'dexxiez.shadcn-color-preview' extension because it is not compatible with the current version of Visual Studio Code - Insiders (version 1.85.0-insider).
What can we do about this?

Hi @ReticentFacade
Can you make sure you're updated to the latest stable of VSCode which is version of 1.89 or the current insiders build which is 1.90-insider. Is there a specific reason you're staying on the insider build of 1.85?


Problem with lfs_stat on new files in a dir

Hello,
I'm trying to use LFS to create a directory in which log files will be stored. To do this I'm creating a directory on startup and adding files one at a time as they exceed the desired maximum file size.
The first file works fine, and then I create the next file, which is created fine.
However, when lfs_stat is called on the path of the second file, it always returns LFS_ERR_NOENT, even though writing to that exact same path works fine.
For testing, I'm formatting on each boot.
I've attached the trace below
00> lfs_trace:3522: lfs_format(2001A068, 200004D8 {.context=00000000, .read=08022879, .prog=080228B9, .erase=080228FD, .sync=0802292F, .read_size=16, .prog_size=16, .block_size=262144, .block_count=256, .block_cycles=500, .cache_size=512, .lookahead_size=512, .read_buffer=2001B258, .prog_buffer=2001B058, .lookahead_buffer=2001B458, .name_max=0, .file_max=0, .attr_max=0})
00> lfs_trace:3583: lfs_format -> 0
00> lfs_trace:3603: lfs_mount(2001A068, 200004D8 {.context=00000000, .read=08022879, .prog=080228B9, .erase=080228FD, .sync=0802292F, .read_size=16, .prog_size=16, .block_size=262144, .block_count=256, .block_cycles=500, .cache_size=512, .lookahead_size=512, .read_buffer=2001B258, .prog_buffer=2001B058, .lookahead_buffer=2001B458, .name_max=0, .file_max=0, .attr_max=0})
00> lfs_trace:3717: lfs_mount -> 0
00> lfs_trace:1859: lfs_mkdir(2001A068, "hk-dir")
00> lfs_trace:3738: lfs_fs_traverse(2001A068, 080025E1, 2001A068)
00> lfs_trace:3821: lfs_fs_traverse -> 0
00> lfs_trace:1941: lfs_mkdir -> 0
00> lfs_trace:1946: lfs_dir_open(2001A068, 20010750, "hk-dir")
00> lfs_trace:1992: lfs_dir_open -> 0
00> lfs_trace:2012: lfs_dir_read(2001A068, 20010750, 20010578)
00> lfs_trace:2020: lfs_dir_read -> 1
00> lfs_trace:2012: lfs_dir_read(2001A068, 20010750, 20010578)
00> lfs_trace:2026: lfs_dir_read -> 1
00> lfs_trace:2012: lfs_dir_read(2001A068, 20010750, 20010578)
00> lfs_trace:2033: lfs_dir_read -> 0
00> lfs_trace:1997: lfs_dir_close(2001A068, 20010750)
00> lfs_trace:2006: lfs_dir_close -> 0
00> lfs_trace:2330: lfs_file_opencfg(2001A068, 2001A594, "hk-dir/0", 903, 2001A588 {.buffer=2001A388, .attrs=00000000, .attr_count=0})
00> lfs_trace:2467: lfs_file_opencfg -> 0
00> lfs_trace:3088: lfs_stat(2001A068, "hk-dir/0", 20010D00)
00> lfs_trace:3097: lfs_stat -> 0
00> current size: 0
00> lfs_trace:2824: lfs_file_write(2001A068, 2001A594, 20010E28, 321)
00> lfs_trace:2948: lfs_file_write -> 321
00> lfs_trace:2676: lfs_file_sync(2001A068, 2001A594)
00> lfs_trace:2727: lfs_file_sync -> 0
00> lfs_trace:3088: lfs_stat(2001A068, "hk-dir/0", 20010D00)
00> lfs_trace:3097: lfs_stat -> 0
00> current size: 321
00> lfs_trace:2824: lfs_file_write(2001A068, 2001A594, 20010E28, 321)
00> lfs_trace:2948: lfs_file_write -> 321
00> lfs_trace:2676: lfs_file_sync(2001A068, 2001A594)
00> lfs_trace:2727: lfs_file_sync -> 0
00> lfs_trace:3088: lfs_stat(2001A068, "hk-dir/0", 20010D00)
00> lfs_trace:3097: lfs_stat -> 0
00> current size: 642
00> lfs_trace:2824: lfs_file_write(2001A068, 2001A594, 20010E28, 321)
00> lfs_trace:2948: lfs_file_write -> 321
00> lfs_trace:2676: lfs_file_sync(2001A068, 2001A594)
00> lfs_trace:2727: lfs_file_sync -> 0

-- snip--

00> lfs_trace:3088: lfs_stat(2001A068, "hk-dir/0", 20010D00)
00> lfs_trace:3097: lfs_stat -> 0
00> current size: 3210
00> lfs_trace:2824: lfs_file_write(2001A068, 2001A594, 20010E28, 321)
00> lfs_trace:2948: lfs_file_write -> 321
00> lfs_trace:2676: lfs_file_sync(2001A068, 2001A594)
00> lfs_trace:2727: lfs_file_sync -> 0
00> lfs_trace:3088: lfs_stat(2001A068, "hk-dir/0", 20010D00)
00> lfs_trace:3097: lfs_stat -> 0
00> current size: 3531
00> lfs_trace:2824: lfs_file_write(2001A068, 2001A594, 20010E28, 321)
00> lfs_trace:2948: lfs_file_write -> 321
00> lfs_trace:2676: lfs_file_sync(2001A068, 2001A594)
00> lfs_trace:2727: lfs_file_sync -> 0
00> lfs_trace:3088: lfs_stat(2001A068, "hk-dir/0", 20010D00)
00> lfs_trace:3097: lfs_stat -> 0
00> current size: 3852
00> lfs_trace:2489: lfs_file_close(2001A068, 2001A594)
00> lfs_trace:2676: lfs_file_sync(2001A068, 2001A594)
00> lfs_trace:2727: lfs_file_sync -> 0
00> lfs_trace:2508: lfs_file_close -> 0
00> lfs_trace:1946: lfs_dir_open(2001A068, 20010610, "hk-dir")
00> lfs_trace:1992: lfs_dir_open -> 0
00> lfs_trace:2012: lfs_dir_read(2001A068, 20010610, 20010438)
00> lfs_trace:2020: lfs_dir_read -> 1
00> lfs_trace:2012: lfs_dir_read(2001A068, 20010610, 20010438)
00> lfs_trace:2026: lfs_dir_read -> 1
00> lfs_trace:2012: lfs_dir_read(2001A068, 20010610, 20010438)
00> lfs_trace:2059: lfs_dir_read -> 1
00> lfs_trace:2012: lfs_dir_read(2001A068, 20010610, 20010438)
00> lfs_trace:2033: lfs_dir_read -> 0
00> lfs_trace:1997: lfs_dir_close(2001A068, 20010610)
00> lfs_trace:2006: lfs_dir_close -> 0
00> lfs_trace:2330: lfs_file_opencfg(2001A068, 2001A594, "hk-dir/1", 903, 2001A588 {.buffer=2001A388, .attrs=00000000, .attr_count=0})
00> lfs_trace:2467: lfs_file_opencfg -> 0
00> lfs_trace:1946: lfs_dir_open(2001A068, 20010610, "hk-dir")
00> lfs_trace:1992: lfs_dir_open -> 0
00> lfs_trace:2012: lfs_dir_read(2001A068, 20010610, 20010438)
00> lfs_trace:2020: lfs_dir_read -> 1
00> lfs_trace:2012: lfs_dir_read(2001A068, 20010610, 20010438)
00> lfs_trace:2026: lfs_dir_read -> 1
00> lfs_trace:2012: lfs_dir_read(2001A068, 20010610, 20010438)
00> lfs_trace:2059: lfs_dir_read -> 1
00> lfs_trace:2012: lfs_dir_read(2001A068, 20010610, 20010438)
00> lfs_trace:2059: lfs_dir_read -> 1
00> lfs_trace:2012: lfs_dir_read(2001A068, 20010610, 20010438)
00> lfs_trace:2033: lfs_dir_read -> 0
00> lfs_trace:1997: lfs_dir_close(2001A068, 20010610)
00> lfs_trace:2006: lfs_dir_close -> 0
00> lfs_trace:2824: lfs_file_write(2001A068, 2001A594, 20010E28, 321)
00> lfs_trace:2948: lfs_file_write -> 321
00> lfs_trace:2676: lfs_file_sync(2001A068, 2001A594)
00> lfs_trace:2727: lfs_file_sync -> 0
00> lfs_trace:3088: lfs_stat(2001A068, "hk-dir/1", 20010D00)
00> lfs_trace:3092: lfs_stat -> -2
00> current size: 0
00> lfs_trace:2824: lfs_file_write(2001A068, 2001A594, 20010E28, 321)
00> lfs_trace:2948: lfs_file_write -> 321
00> lfs_trace:2676: lfs_file_sync(2001A068, 2001A594)
00> lfs_trace:2727: lfs_file_sync -> 0

Hi @keck-in-space, thanks for creating an issue. This doesn't look like any bug I've seen before, so I'm not sure what could be causing the issue. I'm currently prioritizing a couple other bugs so it will be a bit before I can look into this.

Thanks for the reply, @geky. I'm going to keep looking into this and I'll update this issue if I find a solution. Right now it's looking like it is something I'm doing wrong. I'm reusing all the structures used by the first file to create the next file and I'm wondering if that's causing the issue.

A few more details:

When the file is created, walking the directory shows that it exists.
I am able to call lfs_stat on the file successfully until I call lfs_file_write
The lfs_file_write call seems to corrupt the entire directory as the previously written file (file "0") now has the wrong size when lfs_stat is called on it.

I'm pretty sure this is a memory over-write problem. I'm not sure why this changed things, but if the LFS_CACHE_SIZE is 64 instead of 512, I don't see this error.
The LFS_CACHE_SIZE is used to define the sizes of the lookahead_size, cache_size, and the read_buffer, prog_buffer, and lookahead_buffer. Also, it defines the size of the buffer used by the lfs_file_config in the call to lfs_file_open_cfg.
My current cofiguration is below.
#define LFS_CACHE_SIZE 64U

uint8_t readBuffer[LFS_CACHE_SIZE];
uint8_t writeBuffer[LFS_CACHE_SIZE];
uint8_t lookBuffer[LFS_CACHE_SIZE] __attribute__((aligned(32)));

int lfs_read(const struct lfs_config *c, lfs_block_t block, lfs_off_t off, void *buffer, lfs_size_t size);
int lfs_write(const struct lfs_config *c, lfs_block_t block, lfs_off_t off, const void *buffer, lfs_size_t size);
int lfs_erase(const struct lfs_config *c, lfs_block_t block);
int lfs_sync(const struct lfs_config *c);

struct lfs_config cfg = {
    // block device operations
    .read = &lfs_read,
    .prog = &lfs_write,
    .erase = &lfs_erase,
    .sync = &lfs_sync,

    // block device configuration
    .read_size = 16,
    .prog_size = 16,
    .block_size = 256 * 1024,
    .block_count = (64 * 1024 * 1024) / (256 * 1024),
    .block_cycles = 500,
    .cache_size = LFS_CACHE_SIZE,
    .lookahead_size = LFS_CACHE_SIZE,

    .read_buffer = readBuffer,
    .prog_buffer = writeBuffer,
    .lookahead_buffer = lookBuffer,
};

uint8_t fileBuffer[LFS_CACHE_SIZE];

Possibly related to #335
(Not trying to flood you with notifications, geky... just documenting this issue for reference.)

I think I have a configuration that works now.
Note I am using S25FL256L chip now which has 4KB sectors.
Pasting config here in case it helps anyone else
#define LFS_CACHE_SIZE 256U

uint8_t readBuffer[LFS_CACHE_SIZE];
uint8_t writeBuffer[LFS_CACHE_SIZE];
uint8_t lookBuffer[LFS_CACHE_SIZE] __attribute__((aligned(32)));

int lfs_read(const struct lfs_config *c, lfs_block_t block, lfs_off_t off, void *buffer, lfs_size_t size);
int lfs_write(const struct lfs_config *c, lfs_block_t block, lfs_off_t off, const void *buffer, lfs_size_t size);
int lfs_erase(const struct lfs_config *c, lfs_block_t block);
int lfs_sync(const struct lfs_config *c);

struct lfs_config cfg = {
    // block device operations
    .read = &lfs_read,
    .prog = &lfs_write,
    .erase = &lfs_erase,
    .sync = &lfs_sync,

    // block device configuration
    .read_size = LFS_CACHE_SIZE,
    .prog_size = LFS_CACHE_SIZE,
    .block_size = 4096,
    .block_count = 8192,
	.block_cycles = 500,
    .cache_size = LFS_CACHE_SIZE,
    .lookahead_size = LFS_CACHE_SIZE,

    .read_buffer = readBuffer,
    .prog_buffer = writeBuffer,
    .lookahead_buffer = lookBuffer,
};

I am facing a very similar / identical problem as well.
After creating, deleting and recreating some small files a call to lfs_stat returns LFS_ERR_NOENT.
The problem occurs to me when I have set the config as following:
``
#define READ_SIZE 8
#define WRITE_SIZE 32
#define CACHE_SIZE 128
#define BLOCK_SIZE 4096
#define BLOCK_COUNT 4096
#define LOOKAHEAD_SIZE 4096
#define METADATA_SIZE 512
#define BLOCK_CYCLES 10000
// the configuration for littleFS
const struct lfs_config cfg = {
// block device operations
.read = user_provided_block_device_read,
.prog = user_provided_block_device_prog,
.erase = user_provided_block_device_erase,
.sync = user_provided_block_device_sync,
// block device configuration
.read_size = READ_SIZE,
.prog_size = WRITE_SIZE,
.block_size = BLOCK_SIZE,
.block_count = BLOCK_COUNT,
.cache_size = CACHE_SIZE,
.lookahead_size = LOOKAHEAD_SIZE,
.block_cycles = BLOCK_CYCLES,
.metadata_max = METADATA_SIZE};

``
It does not occur when I increase the WRITE_SIZE to 128.
I'd prefer to have the WRITE_SIZE to be set to 32 as it improves the performance just enough to allow my device to write data every second to memory including sync with no delay whatsoever.
Any Idea what might be causing this issue?
Should I open a now Issue here on Github for this problem I'm facing here?


Program crashed when creating a new user - null pointer exception

Hi guys,
I am just playing around with the app right now, but when I try to create a new user, the program crashed with the following error

Any idea what's causing the problem?

fixed


Interval based redownload and/or service call

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
Currently a restart is required to update Powercalc database and initiate discovery routine.
Describe the solution you'd like
Would be nice to have a service call to do this on demand.
Or even an interval based approach, where DB is redownloaded few times a day on the background.
Describe alternatives you've considered

Additional context

WIP: #2864


Two amends to installation and usage docs: SELinux and SCCs

doc: Update SPO installation_usage with some SELinux specific documentation
doc: Add OCP specific docs

What type of PR is this?
/kind documentation

What this PR does / why we need it:
There's two patches in this PR. One adds at least some documentation about using
and recording SELinux policies and the other adds OpenShift-specific chapters
that help users avoid some common issues related to OpenShift's use of SCCs.
Which issue(s) this PR fixes:
Fixes #686

Does this PR have test?
N/A

Special notes for your reviewer:
N/A
Does this PR introduce a user-facing change?

NONE

/retest

thanks, for the review, I applied the suggestions using the GH UI, which I never did before so I hope I didn't break something :-)

Codecov Report

Merging #972 (be418cc) into main (740f032) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #972   +/-   ##
=======================================
  Coverage   50.73%   50.73%
=======================================
  Files          42       42
  Lines        4766     4766
=======================================
  Hits         2418     2418
  Misses       2262     2262
  Partials       86       86

/retest

/test pull-security-profiles-operator-test-e2e

Let's just merge this, it's only amending the docs, no reason to waste watts re-running CI jobs..


Default the maker parameters per network

fixes: https://github.com/itchysats/itchysats/issues/1757

CI is failing because the way this is implemented breaks the command line interface!
I am for this change but can we implement it in a non-breaking way AND include a changelog entry?
Otherwise we might have trouble when we do the next umbrel release.
We can do a follow-up release where we transition to a different structure of passing arguments if that is preferable for some reason! :)

We just have to update the Umbrel parameters for the docker container when we do the next release. There should not be any problem with that.
I think the maker should be network specific for defaulting the maker. Otherwise there is no way to specify a default testnet maker. The follow up-commit is possible, but I don't really see why we can't break this - am I missing something? :)

there is a way of specifying the default testnet maker - right now we specify different ones, we just need to look up the maker id when providing the maker (and it could easily be done in a non-breaking way too)

We just have to update the Umbrel parameters for the docker container when we do the next release. There should not be any problem with that.
I think the maker should be network specific for defaulting the maker. Otherwise there is no way to specify a default testnet maker. The follow up-commit is possible, but I don't really see why we can't break this - am I missing something? :)

there is a way of specifying the default testnet maker - right now we specify different ones, we just need to look up the maker id when providing the maker (and it could easily be done in a non-breaking way too)

Sorry, I cannot follow, could you elaborate more what you mean?
Before my changes the --maker and --maker-id parameters were global parameters, they were not related to the network at all. If we want to default both we will have to relate them to the network.

We just have to update the Umbrel parameters for the docker container when we do the next release. There should not be any problem with that.
I think the maker should be network specific for defaulting the maker. Otherwise there is no way to specify a default testnet maker. The follow up-commit is possible, but I don't really see why we can't break this - am I missing something? :)

there is a way of specifying the default testnet maker - right now we specify different ones, we just need to look up the maker id when providing the maker (and it could easily be done in a non-breaking way too)

Sorry, I cannot follow, could you elaborate more what you mean? Before my changes the --maker and --maker-id parameters were global parameters, they were not related to the network at all. If we want to default both (i.e. maker + maker id for mainnet + testnet) we will have to relate them. My goal is to allow users to start the binary without parameters, while at the same time allowing to configure something different when needed.

You can still default them in the code based on the network, you just have to move away from clap's default_value feature. Make them an Option and based on the chosen command, fill in the Option if it is empty.

We just have to update the Umbrel parameters for the docker container when we do the next release. There should not be any problem with that.
I think the maker should be network specific for defaulting the maker. Otherwise there is no way to specify a default testnet maker. The follow up-commit is possible, but I don't really see why we can't break this - am I missing something? :)

It is not a problem per se, just one more thing to think about when we do releases. I'd simply prefer to not break stuff if we don't have to and moving the parameters to the sub-command seems more of a stylistic choice to me rather than one that is necessary for this feature to work.

[snip]

You can still default them in the code based on the network, you just have to move away from clap's default_value feature. Make them an Option and based on the chosen command, fill in the Option if it is empty.

fair enough I can give that a try instead of the current solution

[snip]

I squashed the previous two commits and added a fixup with such a solution. I don't like it much, but if you feel that is better I don't mind much - it does the job either way.

@da-kami You edited my comment :joy:
Thanks for reworking the solution!

@da-kami are we bringing this in? I've noticed it's still a draft despite approvals.  would you like me to take over and address comments made by @thomaseizinger as a second commit here?

@da-kami are we bringing this in? I've noticed it's still a draft despite approvals. would you like me to take over and address comments made by @thomaseizinger as a second commit here?

Sorry, just saw this now. Since there was no urgency I did not come back to this one. Will work the rest of the feedback in now and then we can go for merge :)

@da-kami You edited my comment 😂
Thanks for reworking the solution!

Hahaha, sry the edit that was unintentional!

bors r+

bors retry


Trigger for each of the delivery pipelines

Hi,
First of all, it's a great project to learn from! Thanks for building it 😃.
Do I understand correctly that all pipelines will run on each commit? If so, wouldn't it be preferable (from time, cost and operations perspective) to have a separate Git repository for each component? That would include the pipeline, infrastructure and runtime.
I understand that it is much easier to reason about the workload when it is in the same Git repository. On the other hand, some components (generally) can have very different change rates and reasons from other components. This can make rollbacks and bisecting difficult.

Yes, all the pipelines trigger on any commit to this repo.  If this wasn't a demo project, I would probably split the code into the following repos, largely following the top-level directories in this mono repo:

static site
chat-bot
trivia-backend base image
trivia-backend app
canaries
alarms
pipelines

Yes, all the pipelines trigger on any commit to this repo.  If this wasn't a demo project, I would probably split the code into the following repos, largely following the top-level directories in this mono repo:

static site
chat-bot
trivia-backend base image
trivia-backend app
canaries
alarms
pipelines

Thank you Clare!

Thank you Clare!


Pin Geth version

Suggestion: use a specific tag for the base image to avoid breaking changes in "latest" builds.
In addition, fix the start script to cope with one of those breaking changes.

thanks!


Compatibility with JupyterHub

The multi-kernel nature of SoS makes installing sos and all the kernels a daunting job for the inexperienced. It is therefore very useful to have a JupyterHub set up with all the kernels and SoS, so that everyone can log in to the same location and perform analysis.
In theory sos should work with JupyterHub but we should test it.

Hi, after having installed jupyterhub (via pip) on our CentOS server and launching a SoS notebook for the very first time we get an access error denied error:
e.g.
[global]
parameter: cwd = path('/home/albot/kitematic')
[Errno 13] Permission denied: '/tmp/sos_lock_bin'
My colleagues narrowed the issue down to https://github.com/vatlab/sos-notebook/blob/master/src/sos_notebook/workflow_executor.py#L334
After removing the lock manually it works fine.

This is a known issue due to the use of global lock in a multi-user environment (someone else created this lock) and I will make sure all such locks are removed. This particular lock has been removed (https://github.com/vatlab/sos-notebook/commit/dca2a2b1fa039deca7fcd813cadb9068e803c1e7) because we now requires Python 3.6+ for which exist_ok exists for function os.makedirs.


TLS 1.3 support

Check my comment here:
https://github.com/AdguardTeam/AdguardForWindows/issues/1737#issuecomment-302839792

Check my patch for the TLS 1.3 support (migrating to the OpenSSL 1.1 branch) and check what should be done to CoreLibs to finish the migration.
We should find a way to access SSL.packet_length as removing this check may cause issues.

UPD: It appears that the guys have already solved both issues in CoreLibs:)
The only thing left is to recompile it with OpenSSL 1.1.1 once we're ready to test TLS 1.3.

Approved:
https://www.ietf.org/mail-archive/web/ietf-announce/current/msg17592.html

Guys, we should also let users configure if TLS 1.3 is enabled or not.

I'm all for more Settings > Advanced, but why make this configurable, unless part of a Min/Max TLS setting (for completeness)?

I'm all for more Settings > Advanced, but why make this configurable, unless part of a Min/Max TLS setting (for completeness)?

We'll put it to the low-level settings, people won't really need to change it except for really rare cases.

Min/Max TLS

That would be too much for an intermediate proxy like ours (the chance of an error if you set min version is too high). The max version is required though to avoid issues like we just encountered with the Win version: https://github.com/AdguardTeam/AdguardForWindows/issues/2241 (it seems that ISP's DPI was not ready to the type of TLS 1.3 handshake AG sends).

Then isn't the correct response to fix the TLS support, rather than disabling it? Not complaining, but, according to that issue, it seems to be an implementation problem from AG's side, since Chrome's works, right?

We did fix it indeed. But it shows that using TLS 1.3 might cause issues and to mitigate the possible issues (and to check if TLS is the cause) we need a new setting.

core/pull-requests/367


hcsoci: Add Cmd type for simplifying process launches

Cmd is modeled after os/exec.Cmd, which makes it easy to launch
and wait for processes and relay their stdio. This version of Cmd is
designed to take in an OCI process specification, and it can launch a
process on anything that implements cow.ProcessHost.

I have additional changes that update the rest of the code to use this interface, but I wanted to get a review just of this first.

I like :)

LGTM. We can bug fix from here.


Added configuration for the max attempt request

Related issues

closes #
Short description and why it's useful

Added configuration for the max attempt request in default.json to prevent many times attempt

Max Network Task Attempts
Max Cart Bypass Attempts

Screenshots of visual changes before/after (if there are any)

Which environment this relates to
Check your case. In case of any doubts please read about Release Cycle

[X] Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop
[ ] RC version (https://next.storefrontcloud.io) - this is a stabilisation fix for Release Candidate of Vue Storefront. I've created branch from release branch and want to merge it back to release
[ ] Stable version (https://demo.storefrontcloud.io) - this is an important fix for current stable version. I've created branch from hotfix or master branch and want to merge it back to hotfix

Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility and no breaking changes)
[ ] I've updated the Upgrade notes and Changelog on how to port existing VS sites with this new feature

IMPORTANT NOTICE - Remember to update CHANGELOG.md with description of your change
Contribution and currently important rules acceptance

[X] I read and followed contribution rules
[X] I read the TypeScript Action Plan and adjusted my PR according to it
[X] I read about Vue Storefront Modules and I am aware that every new feature should be a module

@cnviradiya could you also add info do docs, to describe what this config setting is doing?
This would really help devs to know what is it for and what to do with it :) for us it is clear now, but we should have in mind new developers.
cc @kkdg

@cnviradiya could you also add info do docs, to describe what this config setting is doing?
This would really help devs to know what is it for and what to do with it :) for us it is clear now, but we should have in mind new developers.
cc @kkdg

Yes, sure
I'll add info in docs.

@cnviradiya could you also add info do docs, to describe what this config setting is doing?
This would really help devs to know what is it for and what to do with it :) for us it is clear now, but we should have in mind new developers.
cc @kkdg

@patzick I've updated docs, please review it and share your feedback.
Thanks


Compass feature request

🚀 Feature Requests
A function that gives us the direction we need to head to get from one place to another.  An example being if I enter in coordinates/address for the Louvre museum and I'm standing at the Eiffel Tower, it will give me 266 degrees bearing. So the function itself will just return a double containing the bearing.
Contextualize the feature
I think it could be included in the calculating distance function as it can give the distance and the direction which can be used in navigation in a straight line.
Here is a picture of a website that shows the general idea of what I'm looking for.

Platforms affected (mark all that apply)

[x] :iphone: iOS
[x] :robot: Android

IMHO for such functionalities like distance, direction and all other coordinates calculations/manipulations should exist separate library. geolocator lib should focus on getting coordinates from GPS.
Separating these two functionalities would let to use calculation library without bringing GPS dependencies.

@audkar personally I can also appreciate the fact that these calculations are part of the Geolocator library. Changes are that most of the time I will need both packages anyway, so to me it sounds useful to have them in one library.
We could however simply create a second package library and make and have the Geolocator simply depend on this library to perform the calculations. In that case we have best of both worlds (similar to what we now to with the permission_handler). This does mean that we have to maintain the same API two times (once in the Geolocator and once in the calculation library) however, since they are proven calculations I don't see that the signatures will changes.
Any thoughts on this are welcome.

https://github.com/Baseflow/flutter-geolocator/pull/310


Add GCC8 support in Travis CI

This change adds GCC 8 support in Travis CI.
Let me know if there's some Makefile style things you want changed—the CC variable can probably be passed in the .travis.yml file, and a separate variable can be used to identify the version (if binaries are named differently) and determine which warnings to enable (which would get rid of this CI-only target).

Coverage remained the same at 93.407% when pulling ed007b51dcb097c9aeb5ad44d5401cdeb1c89581 on karlding:add_gcc8_support into 56b381b844c834e92ed0b00707cb94e20c4b9c1d on eerimoq:master.

Here is an autoconf-like approach finding out which flags that are supported by compiling a dummy-file, in this case tests/main.c.
# Flags added if the compiler supports them.


[chore] simplify-destroy-element-logic

Extends: https://github.com/lifeart/glimmer-next/pull/74
1

2

3

Looks like we need to deal with GC

Seems same results


How to train model of  largger scale as  input size?

I  changed   final_dim value  of  the bev_depth_lss_r50_256x704_128x128_24e.py  code:
final_dim = (896, 1600)
The train loss is  normal, but the metrices is very low.   How to train model of  largger scale as  input size?

You should change scale_factor in ida accordingly.

You should change scale_factor in ida accordingly.
ida_aug_conf = {     'resize_lim': (0.386, 0.55),     'final_dim':     final_dim,     'rot_lim': (-5.4, 5.4),     'H':     H,     'W':     W,     'rand_flip':     True,     'bot_pct_lim': (0.0, 0.0),     'cams': [         'CAM_FRONT_LEFT', 'CAM_FRONT', 'CAM_FRONT_RIGHT', 'CAM_BACK_LEFT',         'CAM_BACK', 'CAM_BACK_RIGHT'     ],     'Ncams':     6, }
The final_dim map is assigned final_dim variable ,   Is scale_factor you mean resize_lim ?

Yes, I mean resize_lim.

Yes, I mean resize_lim.
If input size is changed to  896x1600,  How to set the resize_lim value corresponding?

You may change to [0.95, 1.25].

You may change to [0.95, 1.25].
Ok, I will try it.  What is the reasons  that to set  [0.95, 1.25] ? It is an experimental parameter?


ClientIdValidationRegex is not configurable via deployment.toml

Describe the issue:
ClientIdValidationRegex can be defined under the OAuth tag in the identity.xml. This is useful when defining own client-ids via DCR endpoint.
The current default value is [a-zA-Z0-9_]{15,30} and if we pass a client id which is not matching with this regex, we get the following response for DCR.
{"error":"invalid_client_metadata","error_description":"Provided client id is not adhering to the provided regex [a-zA-Z0-9_]{15,30}"}

Environment information

Product Version: IS 5.10.0

@mevan-karu let's link the docs-is PRs to this issue.

This issue exists on IS 5.11 as well.