Update multiple rows on one save

Please create a function to updates multiple rows at once.
await rows[1].save(); // save updates
this function is updates one by one

I also want this... badly.
Updating rows one by one doesn't work. You get rate-limited by the Google API very quickly when you are trying to update large batches of rows. This could be done in a single batch update operation.


Clean dirty dirs before syncing [skip ci]

This way it won't waste time by syncing 3 times

Uh what? rm sync.log is at the end of the script


LSP mode configurable from external source

The original LSP mode determination relied on the --lsp command-line argument, making it hard to set the mode from 3rd party LSP(-like) tools. This PR refines the API to resolve this issue. Additionally, as a side effect, it improves the mocking part of spec.
However, the APIs are still experimental and not yet mature.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[ ] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

making it hard to set the mode from 3rd party LSP(-like) tools

Can you share some example use-cases these changes target?

There are no specific use cases as examples yet. However, the root cause of something like https://github.com/rubocop/rubocop/issues/11033 was discovered in Solargraph. To resolve this, the API provided in this PR could be useful. I'm not familiar with Solargraph in detail, but it seems that applying a patch to the following could solve https://github.com/rubocop/rubocop/issues/11033.
https://github.com/castwide/solargraph/blob/v0.50.0/lib/solargraph/diagnostics/rubocop.rb#L25-L40

Got it. Let's try it out then.


Correct default for nowarn_obsolete_guard

By default, warnings for obsolete guards are turned on. Correct the description to make that clear.

Wrong repository.


Callback function "done" fires immediately

Hi, I'm not good with js/jquery, can you please let me know why this isn't working? It removes/replaces the class before the progress bar loads.
I have this at the bottom of my html file, before the closing body tag, after bootstrap-progressbar.js:
<script>
    $(document).ready(function() {
        $('.progress .progress-bar').progressbar({
          done: $('.loading').removeClass('loading').addClass('loaded')
        });
    });
</script>

That's simple: you should pass closure.
When you pass
done: $('.loading').removeClass('loading').addClass('loaded')
It's instantly evaluated. Instead try passing
done: function() { $('.loading').removeClass('loading').addClass('loaded') }
It's a closure that will be evaluated only after done really fires.

@ptihiy yep. thanks for replying :)


Create datatypes.sql

Closes #25

Should we merge this in a release/1.3.1 branch ?

Should we merge this in a release/1.3.1 branch ?

It can probably wait until release 1.4.0; I don't know of any compatibility issues that would be addressed by these changes. The goal here was more for future-proofing for compatibility with other packages.

@Jrmyy and @owenprough-sift I prefer option 1, as it's smoother for contributors. Also using releases in github we have the changelog automatically generated by github.

Fine by me, we can merge this then.

This PR would replace the https://github.com/lalalilo/athena-utils/blob/main/macros/dbt_utils/cross_db_utils/datatypes.sql from the lalalilo/athena-utils package that adds Athena support for dbt-utils.
In the future, we could probably move more to the dbt-athena package?

@jessedobbelaere nice idea, maybe you can propose the last suggestion in an issue, to avoid to forget that in a comment of a merged PR. All the macros here are super helpfull.

This PR would replace this file https://github.com/lalalilo/athena-utils/blob/main/macros/dbt_utils/cross_db_utils/datatypes.sql from the lalalilo/athena-utils package that adds Athena support for dbt-utils. In the future, we could probably move more to the dbt-athena package?

I agree that athena-utils could likely be obsoleted by implementing the dbt-core-recommended macros in this adapter itself. And it makes a lot of sense to me to copy/paste the implementations from athena-utils where appropriate. No need to reinvent the wheel (and reduces behavior changes for folks migrating from that package).

Can this PR  conflict with my PR?
I solved datatypes issues by adopter implementation.
https://github.com/dbt-athena/dbt-athena/pull/30/files#diff-786e4e9820eed125a3ea010af0b100bcf95e87aec14a18adbb84ecbcafc4e0a1

@hiro-o918 your AthenaColumn handle type mapping, in the end the final goal of it and this pr is the same, but I would like still to have this one merged, as it overwrites the default adapter behavior.
Even if I prefer generally python over jinjia macros, in this case I believe that having a macro for the data types is better.

OK :+1:
thank you for checking that.

I also think we should keep this PR. But I think this PR is missing the string type that was handled and transformed to varchar with the correct length.

@owenprough-sift could you address the comments then we can merge this one.

@Jrmyy I agree with you we should move this file to another utils section, but if we do so we should move macros, let's tackle in another PR and merge this one. I create this issue to keep track of this folder re-structuring: https://github.com/dbt-athena/dbt-athena/issues/41


Using longsum vs count for  queries.

select date_int, count(*) from MyTable group by date_int order by date_int produces the following JSON
The aggr type should be longsum to get the exact number of rows in the table.
......
"aggregations" : [ {
"jsonClass" : "FunctionAggregationSpec",
"type" : "count",
"name" : "alias-1",
"fieldName" : "count"
} ],

Fixed in b1a16da021206d2aa24700d51d8a07f3e2ba9cb9


Update account creation process

Currently functioning
When a user create an account, he has to define a username and a password
Expected functioning
When a user create an account, he has to define a firstname, lastname, email (optional) and a password

only email, need to add manualy all emails for Twenga people

Done in the last_meteor_version branch


Creating swagger-codegen for Flutter with the Flutter dio HTTP package

Hi, thanks for the library! Currently the swagger-codegen, a popular tool to generate API clients from specs, only generates dart code without the dio library (also without things like json_serialize). Thus, I am going to implement it. Is it OK? (Or is there already one hidden in the corner...?)

did you implement t @fzyzcjy ? it would be really useful

No :/ Indeed I created my own codegen

@fzyzcjy  can you share any link the one you created?

Sorry it is not open sourced yet


JPEG XL rendering

maybe convert JPEG XL to PNG using javascript and then render it?

Hi, I am just confirming with you that this is planned, among other formats. No promises, though.

Discord currently can natively render/use JXL images if you pass -enable-features=JXL as a launch parameter when opening it, This will continue to work until Discord drops support for Windows 7/8/8.1 since the version of Chromium that deleted all the JXL code is the same one that dropped support for anything older then Windows 10. In the meantime could JXL images be allowed to natively render in this plugin until another solution is implemented?
Maybe possibly have a toggle or something for it that says/notes somewhere that it requires -enable-features=JXL and will stop working in versions of the Discord client after support for Windows 7/8/8.1 is dropped? (unsure when Discord will decide to do this).


Bool return type not possible in readline()

readline() currently returns an empty string on EOF (rather than false).
Currently, comments suggest that the implementation works like fgets().
Incorrect usage :
while (($line = readline($stream, 2048)) !== false) {
    // Code loops forever
}

Correct usage:
// Read until the stream is closed
while (!$stream->eof()) {
    // Read a line from the stream
    $line = $stream->readLine();
}

👍 Please add a test to https://github.com/guzzle/psr7/blob/master/tests/FunctionsTest.php#L93 to check that an empty string is returned at the end.

Good idea. Done that!


HA 2025.6 problem

My home-assistant.log has some of these entries:
2024-09-11 18:52:37.768 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'salus' calls async_forward_entry_setup for integration, salus with title: Salus iT600 Gateway and entry_id: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/salus/init.py, line 80: hass.async_create_task(, please create a bug report at https://github.com/jvitkauskas/homeassistant_salus/issues

Looks like it is solved by PR which is suggested in #68.
Just need to wait until PR is merged.


Allow disabling Raven in Django.

I sometimes deploy Raven on production and use its Client, but staging or local dev don't have a DSN. It's currently rather hard to disable Raven from Django's settings, so if there could be a setting to disable it and print the traceback on the console instead (or something similar) rather than have it crash because a valid DSN was not found, that would be helpful.
The alternative would be for me to remove the app from the installed apps completely and add if settings.RAVEN_ENABLED checks throughout my code, which is less than ideal.

Indeed. I will have a look at that. I thought we already did in fact but it appears we do not.

This used to work for Django, but then I had to check for DSN before configuring Raven, I'm not sure if this has always been behaviour for Flask.

@skorokithakis so from basic testing if you set DSN to an empty string or None the client disables.  Does that not work for you?

Not the empty string, it used to work but recently broke, IIRC. I haven't tried None, but I can try it and report back.

A traceback or something would be cool.

Ah, yes, will submit soon.

Hmm, I can no longer reproduce this. It might have been a problem on our side (we're reading the RAVEN_CONFIG to configure the client somewhere, and I admit I didn't look at the traceback in detail). Feel free to close, sorry :/

The commit in #689 changes the code so that you can fully disable it, even if you have SENTRY_DSN exported as env-var. I wonder if that was the situation you ran into.

For posterity, this is what I was seeing:
  File "/home/proj/env/local/lib/python2.7/site-packages/raven/contrib/django/models.py", line 228, in register_handlers
    register_logger_signal(client, loglevel=loglevel)
  File "/home/proj/env/local/lib/python2.7/site-packages/raven/contrib/celery/__init__.py", line 44, in register_logger_signal
    handler = SentryHandler(client)
  File "/home/proj/env/local/lib/python2.7/site-packages/raven/handlers/logging.py", line 41, in __init__
    arg,
  File "/home/proj/env/local/lib/python2.7/site-packages/raven/contrib/django/models.py", line 53, in <lambda>
    __repr__ = lambda x: repr(get_client())
  File "/home/proj/env/local/lib/python2.7/site-packages/raven/contrib/django/models.py", line 155, in get_client
    instance = Client(**options)
  File "/home/proj/env/local/lib/python2.7/site-packages/raven/base.py", line 140, in __init__
    self.set_dsn(dsn, transport)
  File "/home/proj/env/local/lib/python2.7/site-packages/raven/base.py", line 194, in set_dsn
    transport_registry=self._registry,
  File "/home/proj/env/local/lib/python2.7/site-packages/raven/conf/remote.py", line 75, in from_string
    raise InvalidDsn(ERR_UNKNOWN_SCHEME.format(url.scheme, value))
InvalidDsn: Unsupported Sentry DSN scheme:  ()

Unfortunately, I'm not sure what the value of the DSN was at the time, and raven was at version 5.1.1, IIRC. I think the DSN was "", because I afterwards went and changed it to a fake URL.


Warning: Can't call setState (or forceUpdate) on an unmounted component

Current behaviour
the same behaviour in this issue:
https://github.com/react-navigation/react-navigation/issues/3992
Expected behaviour
No warning.
https://github.com/react-community/react-native-safe-area-view/pull/32
and I found this PR has fixed the warning.
Code sample
Screenshots (if applicable)
What have you tried
WHEN I modify the local package.json dependency file
FROM "react-native-safe-area-view": "0.7.0"
TO "react-native-safe-area-view": "0.8.0"
and the warning gone.
so maybe it's time to update your package.json file?
Your Environment

software
version

ios or android

react-native

react-navigation-tabs
0.6.0

node

npm or yarn

Closing since it seems that a newer version is used already: https://github.com/react-navigation/react-navigation-native/blob/master/package.json#L94


Support markdown in ingredients

Also support clicking a paragraph / element to highlight it temporarily (so you know where you are when you're cooking)


[Coverity CID :203400]Integer handling issues in /tests/lib/fdtable/src/main.c

Static code scan issues seen in File: /tests/lib/fdtable/src/main.c
Category: Integer handling issues
Function: test_z_finalize_fd
Component: Tests
CID: 203400
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

f1afb4c24d0
 62void test_z_finalize_fd(void)
 63{
 64        const struct fd_op_vtable *vtable;
 65
   	1. negative_return_fn: Function z_reserve_fd() returns a negative number. [show details]
   	2. assign: Assigning: fd = z_reserve_fd().
 66        int fd = z_reserve_fd();
 67        int *obj = z_get_fd_obj_and_vtable(fd, &vtable);
 68
 69        const struct fd_op_vtable *original_vtable = vtable;
 70        int *original_obj = obj;
 71

CID 203400 (#1 of 1): Improper use of negative value (NEGATIVE_RETURNS)
3. negative_returns: fd is passed to a parameter that cannot be negative. [show details]
 72        z_finalize_fd(fd, obj, vtable); /* function being tested */
 73
 74        obj = z_get_fd_obj_and_vtable(fd, &vtable);
 75
 76        zassert_equal_ptr(obj, original_obj, "obj is different after finalizing");
 77        zassert_equal_ptr(vtable, original_vtable, "vtable is different after finalizing");
 78
 79        z_free_fd(fd);
 80}

was fixed in afe5b2598d0a64c3943dfc507445d334a3c95f39


⚠ Bofrost.be has degraded performance

In 3871eb2, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1181 ms

Resolved: Bofrost.be performance has improved in 07257a1 after 46 minutes.


ci/cache: Use .bazelrc for docker cache key

Currently ci uses .devcontainer/Dockerfile for the docker cache key, but .bazelrc is actually more reliable
The cache is currently broken as .devcontainer/Dockerfile changed and it confused ci

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

pushing through to fix ci cache


JUnit Extension: Namespaces controlled by an operator gets stuck in Terminating state on Test Error

Bug Report
Often when a Controller fails(e.g. during tests) leaves orphan finalizers and the relevant Namespace cannot be removed.
What did you do?
Running operators and having failing test runs.
What did you expect to see?
Resources are correctly Garbage Collected by Kubernetes
What did you see instead? Under which circumstances?
Namespaces are in Terminating state forever.
Environment
Kubernetes cluster type:
minikube
$ Mention java-operator-sdk version from pom.xml file
2.0.3-SNAPSHOT
$ java -version
openjdk version "11.0.13" 2021-10-19
OpenJDK Runtime Environment Temurin-11.0.13+8 (build 11.0.13+8)
OpenJDK 64-Bit Server VM Temurin-11.0.13+8 (build 11.0.13+8, mixed mode)

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4", GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"clean", BuildDate:"2021-11-17T15:48:33Z", GoVersion:"go1.16.10", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.3", GitCommit:"c92036820499fedefec0f847e2054d824aea6cd1", GitTreeState:"clean", BuildDate:"2021-10-27T18:35:25Z", GoVersion:"go1.16.9", Compiler:"gc", Platform:"linux/amd64"}

Possible Solution
I do believe that the best solution would be to default to NO_FINALIZERS, but, since this would require additional discussions we can initially document the behaviour and the reasons for it to be in place as default, along with a workaround to actually remove such namespaces, such as:
export NAMESPACE_STUCK=<your stuck namespace name>
kubectl get namespace $NAMESPACE_STUCK -o json \
  | jq -r '.spec.finalizers = null' \
  | kubectl replace --raw "/api/v1/namespaces/${NAMESPACE_STUCK}/finalize" -f -

(command line adapted from: https://stackoverflow.com/a/59667608 )
Sadly enough finalizers in the namespace spec can't be removed with simple kubectl patch or similar, and the only way is to force the resource using the raw API.

That can be an issue and I tend to use a k8s mock server implementation like https://github.com/fabric8io/kubernetes-client#mocking-kubernetes.
I'm not in favor of having to deal with a real server in a CI/CD pipeline. Your test run can be killed at any moment and you have to deal with messy things left over. If one really want to, it should use some sort of virtualization (could be a minikube or a virtual one on top the real one like (https://github.com/loft-sh/vcluster)). And the creation/cleanup of this temporary environnement should be done outside the test runner. That way, cleaning can be trigger independently if needed. ie. you can delayed the deletion, if the test failed to be able to diagnose the state of it.
It is very rare I have to raw patch a CR on real cluster but yes that's a pitty it doesn't work out of the box. You can use some kubectl plugin like https://github.com/xcoulon/kubectl-terminate
IMHO, turning off NO_FINALIZERS will be of no help when you will test the clean up part.
Regarding default value, maybe the default value should be NO_FINALIZERS if the default implementation of cleanup is not overriden (not sure if it's possible to detect this). Or have the cleanup method in its own interface to make cleanup support more explicit and easier to build the controler configuration by reflection.


Any idea how to implement Responsive List?

At first: Thanks @bvaughn for this awesome lib - even considered if I can use it for select implementing virtualization of select menues and saw that there is already an existing react-select integration. Perfect.
At the moment I'm stuck at implementing a responsive grid - actually a list with rows and four cells in each. Depending on the screen size the count of items should be either for or three.
Without this lib I'll throw the cells into a bootstrap row and assign proper css classes for different screen sizes to the items, but here I have to manually chunk the plain collection into a collection of rows with items.
If there is any way that I don't have to reimplement responsive breakpoint detection in JS to handle chunking into rows containing 3 or 4 items, it will be great.
Another alternative will be to use Grid, define a min width for each cell, based on that there will be the amount of items per row and then the actual cell width can be computed so the row gets filled completely.
Am I missing something, that leads to the desired result more elegant/with existing component settings?

Hey thanks for the kind words. I'm glad you're enjoying the library.
Have you seen this Plunk?
http://plnkr.co/edit/zjCwNeRZ7XtmFp1PDBsc?p=preview
I think an approach like this should work for you.
On Jun 14, 2017 3:49 PM, "rmmjohann"<EMAIL_ADDRESS>wrote:

At first: Thanks @bvaughn https://github.com/bvaughn for this awesome
lib - even considered if I can use it for select implementing
virtualization of select menues and saw that there is already an existing
react-select integration. Perfect.
At the moment I'm stuck at implementing a responsive grid - actually a
list with rows and four cells in each. Depending on the screen size the
count of items should be either for or three.
Without this lib I'll throw the cells into a bootstrap row and assign
proper css classes for different screen sizes to the items, but here I have
to manually chunk the plain collection into a collection of rows with items.
If there is any way that I don't have to reimplement responsive breakpoint
detection in JS to handle chunking into rows containing 3 or 4 items, it
will be great.
Another alternative will be to use Grid, define a min width for each
cell, based on that there will be the amount of items per row and then the
actual cell width can be computed so the row gets filled completely.
Am I missing something, that leads to the desired result more elegant/with
existing component settings?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bvaughn/react-virtualized/issues/702, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AABznVyIOO9fnOX7OGPRlkHUgmxG0hgyks5sEGNpgaJpZM4N6iNG
.

I believe this question has been answered so I'm going to close this issue. Feel free to leave a reply if I misunderstood.

Thanks for the suggestion.
The goal should be to measure the items, which will be responsive via width.
Based on the width the count of of items per row will be determined.
I tried to use the cell measurer plus cache, but didn't get it work as I don't know the internals of the cell measurer.
Is it able to implement it this way?

I tried to use the cell measurer plus cache, but didn't get it work as I don't know the internals of the cell measurer.

The source is in GitHub if you'd like to take a look. CellMeasurer isn't actually that big.
If the size of your cells varies (which I didn't know, based on your original description) then you'll have to do some experimentation. I haven't tackled that use-case before.

I'll share the result if I have some time to fiddle out a proper solution


Implement IdentityPlugin in Security plugin

Description
This change implements the IdentityPlugin interface inside the Security Plugin codebase.
This change adds the methods getSubject and getTokenManager. It also adds a new class SecurityTokenManager which handles the issuance of Service Account tokens and OBO tokens. This is done by having the token manager wrap the appropriate methods inside the UserService (for service accounts) and JwtVendor (for OBO tokens).
Issues Resolved
This issue addresses the final check box for: https://github.com/opensearch-project/security/issues/3176
Testing
This change adds tests for issuing the tokens using the SecurityTokenManager. The other functionality has already been tested by the supporting classes.
Check List

[x] New functionality includes testing
[x] New functionality has been documented
[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Blocked by: https://github.com/opensearch-project/OpenSearch/pull/10614

Need to make this change: https://github.com/opensearch-project/OpenSearch/pull/10664
We don't want people to have to provide absolute times in JSON form. Right now we are running into an issue like this where the calculated time expects a Second value to be provided in the case of a JSON is used to request the token settings. But then it auto-propagates the fields with a millisecond absolute time value.
We want our times to be in similar magnitude not way out of scale like this:
Max expiry time is:<PHONE_NUMBER>
Provided expiry time is:<PHONE_NUMBER>

I want to make the Security Plugin instantiate its token manager on bootstrap i.e. put this in the OpenSearchSecurityPlugin class: tokenManager = new SecurityTokenManager(cs, threadPool, userService, null, settings);
However, we run into issues since the OnBehalfOf token logic requires us to have:

    /**
     * The constructor for the SecurityTokenManager
     * @param cs The cluster service for the token manager to use
     * @param threadPool The thread pool for the token manager to use
     * @param userService The global instance of the user service that should be used
     * @param timeProvider An optional time provider that yields the current time in SECONDS
     * @param settings Any settings. It should always include those used for creating JWTs
     */
    public SecurityTokenManager(ClusterService cs, ThreadPool threadPool, UserService userService, final Optional<LongSupplier> timeProvider, final Settings settings) {
        this.cs = cs;
        this.threadPool = threadPool;
        this.userService = userService;
        setKeySettings(timeProvider, settings);
    }

    /**
     * This method allows for configuration of the time provider and settings values
     * This should only be used for testing
     * @param timeProvider An optional time provider. Any provided should be in SECONDS
     * @param settings Any settings to use for creating the JWTs
     */
    public void setKeySettings(final Optional<LongSupplier> timeProvider, final Settings settings) {
        JoseJwtProducer jwtProducer = new JoseJwtProducer();
        try {
            this.signingKey = createJwkFromSettings(settings);
        } catch (Exception e) {
            throw ExceptionUtils.createJwkCreationException(e);
        }
        this.jwtProducer = jwtProducer;
        if (isKeyNull(settings, "encryption_key")) {
            throw new IllegalArgumentException("encryption_key cannot be null");
        } else {
            this.claimsEncryptionKey = settings.get("encryption_key");
            this.encryptionDecryptionUtil = new EncryptionDecryptionUtil(claimsEncryptionKey);
        }
        if (timeProvider != null && timeProvider.isPresent()) {  // Check if timeProvider is not null and then if it's present
            this.timeProvider = timeProvider.get();
        } else {
            this.timeProvider = () -> System.currentTimeMillis() / 1000;
        }
    }

Which includes a signing_key... This is going to be the same type of problem we are trying to fix with admin:admin. I don't want to put a default signing_key but don't know what alternative we reasonably have..
@RyanL1997  @peternied @davidlago thoughts?

I was think to keep reusing this PR, there has been good discussion here I wouldn't want to drop, @scrawfor99 does that work for you?

Hi @peternied, my bad I misunderstood. That is just fine.

Finished with the architectural changes, ./gradlew integrationTest --tests org.opensearch.security.http.OnBehalfOfJwtAuthenticationTest is passing again.
Next step, will patch up test scenarios and make sure config update scenario is correctly tested, afterward will take out of draft.  Feel free to review in the interim, or wait till later.

Thanks @cwperks & @DarshitChanpura I've responded to all feedback and resolved all threads - let me know what you think.

@cwperks @DarshitChanpura Anything holding up approval of this PR?


Loader doesn't consider rootDir (Issue while using src folder)

To Reproduce

quick start setup converted to use src folder

Current vs. Expected behavior
I updated the fumadocs packages to use the latest version
    "fumadocs-core": "^13.4.5",
    "fumadocs-mdx": "^10.0.1",
    "fumadocs-ui": "^13.4.5",

and source.ts file loader to use the rootDir: 'src/content/docs' all the mdx files data is available in the .source/index.js file but the data is not returned via getPages(), getPage()
Provide environment information
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home Single Language
  Available memory (MB): 15792
  Available CPU cores: 12
Binaries:
  Node: 22.7.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.7 // Latest available version is detected (14.2.7).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.4
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)
Content Sources (e.g. Fumadocs MDX, Content Collections)
Additional context
No response

Source API isn't related to this, it's a build time stuff.
The source file should be always generated in the root directory and you may configure path alias on tsconfig to import them using an alias.

I have updated the relevant docs for source API, hope it clarifies that


Keepass

Do you have an examples yet for implementing with keepass by anychance? Thanks

No, I am hoping someone in the community will do this, based on the example extension modules.

OK thanks for the quick response. Hashi Corp key vault would be another good one also for the community.

@thenecroscope
I made a Keepass Module
https://twitter.com/JustinWGrote/status/1308534809463906305

Awesome!


Implement an authenticator based on the domain socket peer credential

Summary
Implement a new front-end authenticator module that uses domain socket peer credentials to deduce and validate the client application identity.
Rationale
In the specific case where domain socket is being used as the transport, and a peer property (such as UID, GID or PID) can be used as a sufficient differentiator for the application identity, it allows for a simple means of identity management without a separate identity provider component.
Constraints
This authenticator can only be used with domain socket transport, because the notion of peer credentials only exists in that case. It can also only be used when some aspect of the peer credential is a suitable token of application identity. (Typically this would be the UID, but it could also be the GID - theoretically even the PID, although in practice this is probably far too volatile to be useful).
Details
Requires the following:

Assign and document an integer selector to be used as the auth_type field in the wire protocol.
Design and document how a client application should populate the authentication header when using this auth type.
Design and implement a means of passing data (which in this case is the peer credential) from the listener to the authenticator, which is captured as a separate issue here: https://github.com/parallaxsecond/parsec/issues/199
Rework the DomainSocketListener so that it can obtain peer credentials from the system. This might mean using a different UDS library, because it looks like the standard Rust UnixListener does not provide access to the peer credential.
Implement an authenticator module that can read the auth header and use the peer credential to validate it.
Suitable unit tests and integration tests to prove the mechanism.
May require modifications to the thread model and recommendations for secure deployment when this type of authenticator is being used.

Definition of Done
It is possible to create a demo deployment where at least two distinct client applications, running as different users, can both create and use a Parsec key with the same name. It is also possible to show that a request will be rejected if the client attempts to spoof its UID in the auth header of the request.

Design and document how a client application should populate the authentication header when using this auth type.

Are we making the assumption that multiple applications might run under the same user? Trying to gauge whether we need to actually pass anything in the authentication header or if we should just namespace on the user ID alone.
Also, given that the metadata is actually dependent on the listener, it might make sense to have it enabled conditionally on the listener in the config data - as in, attach or enable the processing of metadata for each authenticator that we have, when the service gets created. This would lead to app identity being a composite of metadata and request auth and there's no need for another authentication type - you can use any authentication and the request metadata gets mixed in automatically by the service, the client doesn't need to be aware.

it looks like the standard Rust UnixListener does not provide access to the peer credential.

Not for too long! @joechrisellis has made a PR on Rust to enable this: rust-lang/rust#75148

Implementation is in #214


textAlignment "text-end" not working in TableCell and TableHeaderCell

The "text-end" value of the textAlignment property in <TableCell> and <TableHeaderCell> doesn't work, though text-end works in other comopnents
Example:
<TableHeaderCell textAlignment="text-end">Duration</TableHeaderCell>

Ah ok that would be great indeed I was missing the classname


[test] protobuf 3.25.5 against 1.125.x for testing.

test for lts 6 patch

only failing conventionalcommits.


Should IteratorResult have optional value?

Looking at the ECMA spec for IteratorResult, it seems that value can be optional (when done is true)
In the TypeScript definition, this would translate to:
interface IteratorResult<T> {
    done: boolean;
    value?: T;
}

This does create a potentially annoying situation in which, when ``strictNullChecksis true, thevaluehas to be cast toT``` (unless the new control-flow based type guards are smart enough to recognise this).
As it is, however, it isn't possible to actually implement an Iterator with strictNullChecks because  we can't return an undefined value for value.
What is the correct approach here?

That value was declared optional previously, but that indeed caused to much casts. See #8357. Ideally IteratorResult would be defined as:
type IteratorResult<TYield, TReturn>
  = { done: true, value: TYield }
  | { done: false, value: TReturn }

But that's not possible yet. Then you could define an iterator that does not return as IteratorResult<T, undefined>.

As noted by @ivogabe we need to have boolean literal types, to be able to model this one accurately.

I'm fairly new to TypeScript, so maybe this is obvious to others, but I was able to work around with:
    return function next(): IteratorResult<T> {
      if (yielded < arr.length) {
        return { value: arr[yielded++], done: false }
      } else {
        return ({ done: true } as IteratorResult<T>)  // <= explicit cast here!
      }
    }

the definition is currently not correct, the correct one would be:
type IteratorResult<TYield, TReturn>
  = { done: false, value: TYield }
  | { done: done, value: TReturn | undefined }

Should this be closed in favor of #2983?

Yes.


Improved PHPDoc comments

This covers roughly half the class files in framework/control. Breaking the main body of work into two pull requests to help with review.

Nice improvement, thanks for all your hard work!


Redis State Storage

Add serialize and deserialize to structs
Add OperationStateManager for redis

Description
Basic Implementation of WorkerStateManager, ClientStateManager, and MatchingEngineStateManager for RedisStateManager. Adds Serialize and Deserialize to all structs required for storing in redis as json.
One of the following must be merged for this to work:

Serialize and Deserialize added to structs (done in a commit on this PR)
#941 must be merged and types here can be changed. #941 would enable storage of non-json values in Redis

Type of change
Please delete options that aren't relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
TDB
Checklist

[ ] Tests added/amended
[x] bazel test //...  passes locally
[ ] PR is contained in a single commit, using git amend see some docs

This change is

No longer working on this here, split into:
#1020
#1021
#1022
#1023


Don't use dev exception pages, always use reexecute

For dev-prod parity, and better urls.
Trying to troubleshoot an error that only happens in azure.

 🔒 Secure Search and Compare UI with optional authentication


Update Cats, circe, ScalaCheck, and ScalaTest versions

I'm not sure we want to merge this yet, but I wanted to show that it works. :smile:

Xor is gone.
Cats provides its own UUID instances.
ScalaTest has moved a couple of things around.
Arbitrary instances for functions now require Cogen instances for the argument types.

I need to take a closer look at the Cogen instances, but I think they make sense.

Current coverage is 75.67% (diff: 0.00%)

Merging #661 into master will not change coverage

@@             master       #661   diff @@
==========================================
  Files            28         28
  Lines           559        559
  Methods         542        542
  Messages          0          0
  Branches         17         17
==========================================
  Hits            423        423
  Misses          136        136
  Partials          0          0

Powered by Codecov. Last update f5398df...7f4e96d

Thanks @travisbrown! We totally want these upgrades in the 0.11 release so I'm happy to merge this in.


routes & DNS not working on OS X

nice work on minishift; it worked OOTB! I ran gofabric8 and it got everything up and running; the only downside is I can't access any of the routes from my host. I'm guessing its that we don't have a minishift equivalent of landrush. I could hack around it with /etc/hosts but its a bit of a shame. e.g. I can open the console via
minishift service fabric8

but the OAuth doesn't work as its redirecting to vagrant.f8 which doesn't resolve. I guess gofabric8 needs to remove all Routes if running on minishift so that we don't try to use DNS names and then tries to use the ip address & nodePort for all links etc

Easiest solution for now that I can think of that works cross platform is to use a service like xip.io to resolve to minikube ip.

thanks; I tried:
gofabric8 deploy -y --domain=<IP_ADDRESS>.xip.io

but can't seem to see anything at any of the routes
$ oc get route
NAME                      HOST/PORT                                     PATH      SERVICE                   TERMINATION   LABELS
fabric8                   fabric<IP_ADDRESS>.5.xip.io                             fabric8                                 provider=fabric8
fabric8-docker-registry   fabric8-docker-registry.<IP_ADDRESS>.xip.io             fabric8-docker-registry                 provider=fabric8
fabric8-forge             fabric8-forge.<IP_ADDRESS>.xip.io                       fabric8-forge                           provider=fabric8
gogs                      gogs.<IP_ADDRESS>.xip.io                                gogs                                    provider=fabric8
gogs-ssh                  gogs-ssh.<IP_ADDRESS>.xip.io                            gogs-ssh                                provider=fabric8
jenkins                   jenkins.<IP_ADDRESS>.xip.io                             jenkins                                 provider=fabric8
jenkins-jnlp              jenkins-jnlp.<IP_ADDRESS>.xip.io                        jenkins-jnlp                            provider=fabric8
nexus                     nexus.<IP_ADDRESS>.xip.io                               nexus                                   provider=fabric8

Try again.... it's not the most reliable service :-b

Works for me here btw:
$ dig +short fabric<IP_ADDRESS>.5.xip.io
<IP_ADDRESS>

I can look up the IP addresses just fine - just can't access any of the actual services

$ curl -v http://fabric<IP_ADDRESS>.5.xip.io
* Rebuilt URL to: http://fabric<IP_ADDRESS>.5.xip.io/
*   Trying <IP_ADDRESS>...
* connect to <IP_ADDRESS> port 80 failed: Connection refused
* Failed to connect to fabric<IP_ADDRESS>.5.xip.io port 80: Connection refused
* Closing connection 0
curl: (7) Failed to connect to fabric<IP_ADDRESS>.5.xip.io port 80: Connection refused

Have you deployed the openshift router? Is <IP_ADDRESS> the same as minishift ip?

DOH! :) I thought gofabric8 did that ;) Lemme try that...

haven't quite figured out how to run the router yet. My first attempt on host of
oc adm router --create

resulted in the router pod failing:
I0714 09:30:48.656004       1 router.go:161] Router is including routes in all namespaces
E0714 09:30:48.903149       1 ratelimiter.go:50] error reloading router: exit status 1
[ALERT] 195/093048 (25) : Starting frontend public_ssl: cannot bind socket [<IP_ADDRESS>:443]
E0714 09:30:53.708700       1 ratelimiter.go:50] error reloading router: exit status 1
[ALERT] 195/093053 (41) : Starting frontend public_ssl: cannot bind socket [<IP_ADDRESS>:443]

There's no oc inside the VM right?

As discussed on IRC, this was due to the router being unable to bind to port 443, which was occupied by the API server. 0.2.0 will bind the API server to 8443 instead so this will be solved in that version (releasing now).

Released - https://github.com/jimmidyson/minishift/releases/tag/v0.2.0


Quote Error

Hi there,
I'm working on a project and i need to implemente a Facebook login but i've an issue!
When FeatherJS need to create a user into my database (Mysql with KnexJS) i've an error : "ER_WRONG_VALUE_COUNT_ON_ROW: Column count doesn't match value count at row 1"
After some research i know why ! When FeatherJs try to add a new user it doesn't add single quote around the JSON object, and without these quote, MYSQL says.. No!
So do you have an idea to transform this ->
insert into `users` (`facebook`, `facebookId`) values ({"profile":{"id":"1306478419467189","displayName":"Popi Popo","name":{},"provider":"facebook","_raw":"{\"id\":\"1306478419467189\",\"name\":\"Popi Popo\"}","_json":{"id":"1306478419467189","name":"Popi Popo"}},"accessToken":"EAAbY4lfNNakBAokokigv5uYzoh225VZC3LwMcPcWohwwITqpQerNTjUTD2gBInKISPDft60ZBoYQ1cq950cw8v58LW4QCPy4MxLXthRgro3xNZBDxViloyI8y6THiWD8s5tGv7r822M2OrHAKZAo2Yzb0Y5zgU4x4GGq5R4ZC0AZDZD"}, '1300408410467080')

to
insert into `users` (`facebook`, `facebookId`) values ('{"profile":{"id":"1306478419467189","displayName":"Popi Popo","name":{},"provider":"facebook","_raw":"{\"id\":\"1306478419467189\",\"name\":\"Popi Popo\"}","_json":{"id":"1306478419467189","name":"Popi Popo"}},"accessToken":"EAAbY4lfNNakBAokokigv5uYzoh225VZC3LwMcPcWohwwITqpQerNTjUTD2gBInKISPDft60ZBoYQ1cq950cw8v58LW4QCPy4MxLXthRgro3xNZBDxViloyI8y6THiWD8s5tGv7r822M2OrHAKZAo2Yzb0Y5zgU4x4GGq5R4ZC0AZDZD"}', '1300408410467080')

Thank :-)

What version of feathers-authentication are you using?

I don't think this is a Feathers or feathers-authentication issue. Feathers-authentication isn't doing anything special to the JSON object. That is on you as the developer, to customize the data in a before hook before it is inserted in the DB.
@Clowning is this still an issue for you?

Since we haven't heard anything back in some time, I'm going to close this issue and assume it's been resolved. If it is still an issue we can re-open. 😄

Oh i'm sorry !  Not feathers :D ahha


Fixed DoctrineResource::findEntity() criteria #171

Related to issue #171
If the route parameter was stripped off of stripRouteParameterSuffix, it will not be added in the criteria if match in $fieldNames.

I'm fine with this patch but it needs a unit test to show it in action.

Of course. I'll do it asap.
I was thinking that what I've done it's not enough, it doesn't cover another possible problem, so I need to do much work.

Added a "parent" relation to the test Entity\Album with album name. Without my patch, tests fails.
My patch does:

Remove the route_identifier_name from criteria, because it's already added, and it's not possible to add another criteria with the same route_identifier_name. This resolve issue #171.
If a route param contains something like :message_id, the criteria ['message' => ':message_id' will not be added if key message is in field names and not in association names.

Tests updated with a self-reference association in the Album entity. Without my patch, tests fails.
I've done some little refactoring and fixed some annotations.

@TomHAnderson  Are you fine with this patch?

I edited the patch. I remove just the route identifier name from the criteria, it's enought to fix issue #171 without creating BC breaks. I also made a change on tests, to update them. I created a route like /test/rest[/artist/:artist_id]/album[/:album_id]. This is what should be an rpc service, but an user could be that.

merged to develop


poker: add a hints file

Document what the input and output of BestHand should be.
Closes #853

I know the README is supposed to be updated. Where is the tool that handles this?

It's configlet: your swiss army knife of track configuration! The README there is behind a bit (exercism/configlet#91), but I provide some instructions in our README. Do those make sense?

A reminder to me that this is waiting on exercism/configlet#91.

@shaleh I updated the configlet README to contain info on how to generate READMEs.

I'm gonna go ahead and merge this, then it will be available next time the README is generated.


Not working/showing in iPhone X

iOS 11 is now release with new phone X, 8 and 8+.

On iPhone X the popover is not showing.

I just do in your PR or In stockoverflow to run the library properly and it works now.

Hope you fix for the future.

Issue same #88

yes. same. will you guys fix soon? if not, I gona need to find another library since our app launch is very near to support ios 11.  Or is there any temp workaround?


Rainbow lights when standalone hyperion has no signal from USB grabber

Hi guys, first of all I want to say that you did and still do a wonderfull job with this beautiful project.
I post here an issue I have when for example, I finished to play with my PS3 and shut it down. All the LEDs turn statics with different color by group of 3 or 4 leds, yellow, blue, green, purple, red, blue and so on but only on my horizontal strip. Vertical strip are all green/white. I would like to tell hyperion to put the led black when the USB grabber has no signal. Is this possible ?
I use a USB grabber DC60 with a STK1160 chip.
thanks in advance for you help

I've also ran into this issue. We really need a reliable source for HDMI2AV convertors that do not display the rainbow bars when no signal is detected. For now I just unplug the power of the convertor but that is not a long-term solution.

I will close this, due to converter fault and age.

Actually i would like to see this re-opened again. A functionality to detect a no-signal image would be usefull.

I agree. Unless someone can provide a store where I can buy a good convertor (100% garantee not do display rainbow colours). I currently have 4 which are all bad (i.e. rainbow).

And how determine you a no-signal image? I don´t know how many color variants and steps are created out there. When you say you see rainbow colors, this is also on your grabbed picture right?
The main problem is: v4l2 shuts down if you have no signal. The hdmi to cvbs converter outputs weird stuff all time. So v4l2 never shuts down.

Would it be possible to provide a "no signal" screenshot to be able to do a comparison ?

Checkout this hint:
https://hyperion-project.org/threads/v4l2-add-shutdown-detection.146/#post-2034

I found what might be a good solution (after having bought 3 "white" HDMI2AV convertors). Either get the HDMI full HD kit from Lightberry (which is a nice all-in-one solution so handy if you haven't bought a splitter and grabber yet) or try and find the 4K convertor they use in their 4K kit. I found 1 on ebay and it works like a charm. No more rainbow colour lights for me.

redSignalThreshold

So, I found out a very simply solution (worked like a charm for me) - just get the hd capture stick (which will replace both the HDMI2AV and the regular video capture stick):
http://s.click.aliexpress.com/e/lUmAtO0u - for example
it will not send out signal if no signal received.
Worked out of the box!

@sivilya That sounds great. Drivers are already included? Which distribution do you use?

@sivilya That sounds great. Drivers are already included? Which distribution do you use?

Just the regular main distro...


fix(doc): invalid download sass link

close #127

wait, what? Nooo............ what's the purpose of 2 buttons leading to the same link? disappointed

Good catch.
Can you revert the commit and provide a new PR @roiLeo?

IMO, I would just commit the updated link without PR, we don't need to revert it.

IMO, I would just commit the updated link without PR, we don't need to revert it.

See my last comment. I already reverted it.
A PR should be the way to go so it goes through the review process.
I think we should make the current v1-dev branch protected to allow only changes by PRs.
We are not in a hurry so we can wait for a PR.

Original repo had 2 two .zip in last release, one with compiled css/js (materialize.css and materialize.js) and the other one with uncompiled sass/js files.
Maybe we should remove the sass download links, as we do not currently provide an archive containing sass files.

well github still generates a source code zip that we could use? If we want to make a proper src zip like they have with all the extras not included, we should build it into the release script.

Yes, the best solution is to generate the link out of the Process, otherwise we will face the same issue again at the nexr Release.

Yes, the best solution is to generate the link out of the Process, otherwise we will face the same issue again at the nexr Release.

the release process is just search "old version string" and replace it with "new version string". So as long as the link have similarity, I think it should be fine.

I more mean make the script generate these zips, not just making them by hand each time.

hmm... or maybe just point the link to the github repo? Instead of src zip file?


Migrate ListRuntimeObjectsForKind to use dynamic client

In https://github.com/kubernetes/perf-tests/pull/1023 I implemented using dynamic client as a fallback and we agreed that ultimately we want to migrate all cases to dynamic client how it's done in other places.
/assign @wojtek-t

/lgtm


[Automanage] Update code and prepare for the stable release

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.Automanage


(OraklNode) Rename function, StopHeartbeatTicker -> ResignLeader

Description
Previously, StopHeartbeatTicker function has been called to resign as leader, this renames the function and add few more missing steps to smoothly resign from raft leader

Updates own role into follower
Updates saved leader into empty string
Starts ElectionTimer

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.

Deployment

[ ] Should publish npm package
[ ] Should publish Docker image

@coderabbitai review


Support GHC 9.8.1

This PR bumps the bounds for supporting bytestring 0.12, base 4.19 and GHC 9.8.1

This fixes #50.

This can be closed since #53 was merged.


DNScrypt not enabled

DNScrypt not enabled even after enabling it.
installed using GUI osx installer dmg file, on OSX 10.12

Wrong project.
I think this screenshot is from https://github.com/alterstep/dnscrypt-osxclient


Unix Timestamp error from stripe when adding 1 day trial to new subscription

I have been having this issue intermittently for some time.
When a customer tries to add their card, I create a subscription for them in the back end. This subscription always has 1 trial day attached to it using the following pattern:
$company->newSubscription('sub', 'plan')                         ->trialDays($trialDays)                         ->create($token, ['various options']);
The majority of the time this works fine, but every now and then, I get the following error back from stripe:
{   "error": {     "message": "Invalid timestamp: must be an integer Unix timestamp in the future.",     "param": "trial_end",     "type": "invalid_request_error"   } }
I have checked in the stripe logs what actually gets submitted, and the "trial_end" parameter is indeed wrong, it's a unix timestamp about 2 hours before the request gets sent.
I have a strong feeling this is something to do with timezones. As a general note, my application is set to UTC timezone and all database dates are saved in UTC. Our customers are global. Taking a look at the trialDays function in the subscription builder, I see it's a simple Carbon::now()->addDays($trialDays); so it should be using my app's UTC timezone, but in this case it appears to be using the customer timezone somehow.
Any ideas? Perhaps force Carbon to UTC since that's what stripe expects?

I had tons of issues with time related operations when I left my virtual machine open and put my Windows computer into sleep. When I came back to my machine, API calls would fail left and right to different services I'm using because the time becomes shifted from putting the machine to sleep.
If you're in production though, I don't see that being an issue. Just some food for thought.

@driesvints the system timezone is also set to UTC. In either case I can't see much harm in changing that call to Carbon:now('UTC')->addDays($trialDays) in order to force carbon to use UTC when dealing with stripe?

@robtesch what's the output of echo date_default_timezone_get();? (sorry if this seems repetitive, just want to make sure we don't miss anything)
Using UTC in the Carbon::now calls is probably the way to go but I suspect there must be something wrong on your end since this has been working fine so far.

@driesvints agreed it probably is something on my side, but the server is definitely on UTC. Output of that command gives simply UTC. All indications point to carbon::now() using UTC, and i have no idea why it wouldn't be, but as i say, stripe seems to think differently.

I'm very sorry but as it seems this is probably something on your end I'm going to close this at the moment. We're using this issue tracker mainly for bug reporting and new feature tracking. I'm sorry I can't be of more help.
Something you can do is ask your question on one of the below channels to see if someone can help out:

Laracasts Forums
Laravel.io Forums
Discord
Larachat
IRC

Good luck. Hope you figure it out! Feel free to reach back once you found what's wrong.

@driesvints understood and fair enough. For what it's worth, for the time being i have simply removed the trial period and i haven't had any issues since. Still think it's worth changing any Carbon::now() calls to Carbon::now('UTC'). Could i make a pull request for it?

You can yeah but unsure if Taylor will merge it. I'm still not 100% convinced it's the right idea. You might want to gather some more opinions on it before sending in a PR.

Is this fixed? I am encountering the same error

@eberkund Ditto on my end. Care to show any code?
Here's what I'm working with in my RegisterController
public function register(Request $request)
    {
        $this->validator($request->all())->validate();

        DB::beginTransaction();

        event(new Registered($user = $this->create($request->all())));

        $user->newSubscription('main', 'starter')->create($request->token, ['email' => $user->email]);
        $user->trial_ends_at = NULL;
        $user->save();

        DB::commit();

        $this->guard()->login($user);

        return $this->registered($request, $user)
                        ?: redirect($this->redirectPath());
    }

I'll keep trying things on my end and reply back if I figure out my issue :)

@eberkund right you are, that worked!
🤦I just needed to keep trucking away at it.
If anyone needs help with this issue here is how I have fixed it. Here is my controller code:
public function register(Request $request)
    {
        $this->validator($request->all())->validate();

        DB::beginTransaction();

        event(new Registered($user = $this->create($request->all())));

        $user->newSubscription('main', 'starter')->create($request->payment_method, ['email' => $user->email]);
        $user->trial_ends_at = now();
        $user->save();

        DB::commit();

        $this->guard()->login($user);

        return $this->registered($request, $user)
                        ?: redirect($this->redirectPath());
    }

And here is the JS I used in my view. Would probably be good to show the form POST functionality in the docs. But either way, here is the JS I used on my end:
const stripe = Stripe('{{ env("STRIPE_KEY") }}');
        console.log(stripe);

        const elements = stripe.elements();
        const cardElement = elements.create('card');

        cardElement.mount('#card-element');

        const cardHolderName = document.getElementById('name');
        const cardButton = document.getElementById('card-button');
        const clientSecret = cardButton.dataset.secret;
        let validCard = false;
        const cardError = document.getElementById('card-errors');

        cardElement.addEventListener('change', function(event) {

            if (event.error) {
                validCard = false;
                cardError.textContent = event.error.message;
            } else {
                validCard = true;
                cardError.textContent = '';
            }
        });

        var form = document.getElementById('signup-form');

        form.addEventListener('click', async (e) => {
            event.preventDefault();

            const { paymentMethod, error } = await stripe.createPaymentMethod(
                'card', cardElement, {
                    billing_details: { name: cardHolderName.value }
                }
            );

            if (error) {
                // Display "error.message" to the user...
                console.log(error);
            } else {
                // The card has been verified successfully...
                var hiddenInput = document.createElement('input');
                hiddenInput.setAttribute('type', 'hidden');
                hiddenInput.setAttribute('name', 'payment_method');
                hiddenInput.setAttribute('value', paymentMethod.id);
                form.appendChild(hiddenInput);
                // Submit the form
                form.submit();
            }

        });


Reading ND (Norsk Data) format 17b floppies fails

So I'm trying to read a ND aka Norsk Data format 17b floppy (the floppy itself is a normal 5.25 inch DS, HD 1.2MB floppy) using the fe-readibm command so that I can capture the flux information into a file. I'm using this command:
$ ../.obj/fe-readibm  --output nd-525-210523g02-xx-02d.img --write-flux=nd-525-210523g02-xx-02d.flux
but it fails with an error
46.0: 162 ms in 102144 bytes (629 kB/s)
1.00 us clock; 20279 bytes encoded; 32 records
terminate called after throwing an instance of 'std::out_of_range'
what():  byte access out of range
Aborted
the floppy drive I am using is a Teac FD-55GFR floppy, and I have verified that it reads IBM formatted floppies ok.
ND format 17b has 1024 bytes per sector, 8 sectors per track, 77 tracks and is DS/DD.
When I read such a floppy on a FreeBSD machine, I set parameters with the fdcontrol command first,
# fdcontrol -f 1232 /dev/fd1
view settings
# fdcontrol -vF /dev/fd1
/dev/fd1: 1232 KB media type
   Format:        8,1024,0xff,0x35,77,500,2,0x74,1,0,+mfm
   Sector size:    1024
   Sectors/track:    8
   Heads/cylinder:    2
   Cylinders/disk:    77
   Transfer rate:    500 kbps
   Sector gap:    53
   Format gap:    116
   Interleave:    1
   Side offset:    0
   Flags        <MFM>
then read with the dd command like so
$ dd if=/dev/fd1 of=./test.image bs=1024
1232+0 records in
1232+0 records out
1261568 bytes transferred in 230.765575 secs (5467 bytes/sec)
Back to the fluxengine. Is this the correct way to capture the flux file of an unknown format?

Yup, just add --just-read and it'll skip all the analysis.
This is clearly a bug at my end; if you can send me the flux file I'll fix it. Email me at<EMAIL_ADDRESS>(and of course I promise to delete the file one I'm done with it).

ok, with '--just-read' it doesn't fail:
tingo@kg-bsbox:~/personal/projects/psoc/fluxengine/tmp$ ../.obj/fe-readibm --just-read --output nd-525-210523g02-xx-02d.img --write-flux=nd-525-210523g02-xx-02d.flux
Reading from: :d=0:s=0-1:t=0-79
Writing a copy of the flux to nd-525-210523g02-xx-02d.flux
... skipped ...
 79.1: 162 ms in 91264 bytes (561 kB/s)
--just-read specified, halting now
I'll send you the file.

There were a couple of nasty buffer overrun bugs, which I've fixed and pushed. Thanks.
...but the image you sent me won't decode. Thing is, I actually have a USB floppy drive which generates those 1232kB disks, and they read just fine. But with your image, I can see it correctly detecting the clock, there's a nice clean histogram, but the results are complete garbage. If I look at the raw data I can see fragments of mangled English text so it's almost getting the format right, but there's a bit error every few bytes.
You said you verified that it could read a IBM floppy --- was that a HD or DD floppy? I don't have any HD floppies to test with, and it's possible that I need to explicitly tell the drive it's HD or it won't read properly. 3.5" drives autodetect this so it's not a problem there.

IBM floppies - the 5.25 inch IBM floppies I have read (successfully) so far are physically HD, but the format has been 360k, like this
$ ../.obj/fe-readibm --output 525-brief-2.1.img
...
40 tracks, 2 heads, 9 sectors, 512 bytes per sector, 360 kB total

I've tried to set the clock rate manually (based on a histogram)
$ ../.obj/fe-readibm --just-read --output nd-525-210523g02-xx-02d_manual.img --write-flux=nd-525-210523g02-xx-02d_manual.flux --manual-clock-rate-us=3.75
I'll send you that image in case it helps.

Hmm.  What about the disks? Having a hub ring is usually a sign of a DD disk, and not having one is a HD disk. Mine are both (I only have two!) DD.
Also, the clock rate's only used during the decode phase and flux files don't use them. You can actually use a flux file as a source and try decoding with different clocks without wear and tear on the disk.

the disks have no hub ring; they also have the 3M brand label with the serial number, and the text

high density
formatted
DS, HD
IBM AT 1.2 MB

and I picked them out of a sealed 10-pack of 3M floppies back when I wrote them, so they are genuine
hmm - scratch that - what I wrote above is correct for the ND format floppies, not the IBM format floppies. I'll go back and check them.
the clock rate - good to know.

So this was slightly more complex than I thought --- it turns out I had gotten about half way through adding high density mode, except it defaulted to enabled...
Could you have a go with the hd branch? This should actually fix the support; there's now a --high-density (or -H) flag which sets the drive to high density mode when reading, and the default is double density as it should be. This should be set based on the media type, not the format. But I don't have any disks to test with!
You'll have to rebuild the firmware and flash, I'm afraid.

So, with firmware and client from the hd branch I can read and decode 5.25 inch HD floppies that are MS-DOS formatted, se my comment in #48 .
However, ND formatted floppies always fail with "USB underrun". example:
tingo@kg-u35jc:~/personal/projects/psoc/fluxengine/tmp$ ../.obj/fe-readibm -o 525-CIS-format-f1232-number-3.img -f 525-CIS-format-f1232-number-3.flux
[..]
  4.0: 160 ms in 143232 bytes (891 kB/s)
       0.96 us clock; 20951 bytes encoded; 16 records
       8 sectors;
       logical track 4.0; 8192 bytes decoded.
  4.1: Error: USB underrun (not enough bandwidth)

it doesn't matter is I use the '-H' switch
tingo@kg-u35jc:~/personal/projects/psoc/fluxengine/tmp$ ../.obj/fe-readibm -H -o 525-CIS-format-f1232-number-3_2.img -f 525-CIS-format-f1232-number-3_2.flux
[..]
  4.0: 160 ms in 143232 bytes (891 kB/s)
       0.96 us clock; 20951 bytes encoded; 16 records
       8 sectors;
       logical track 4.0; 8192 bytes decoded.
  4.1: Error: USB underrun (not enough bandwidth)

I don't understand why this fails when MS-DOS format works?
FWIW, this is what fe-rpm gives on this machine
tingo@kg-u35jc:~/personal/projects/psoc/fluxengine/tmp$ ../.obj/fe-rpm
Rotational period is 166 ms (361.446 rpm)

and fe-testbulktransport
tingo@kg-u35jc:~/personal/projects/psoc/fluxengine/tmp$ ../.obj/fe-testbulktransport
Transferred 1048576 bytes in 1096 (933 kB/s)

I've tried 15 different ND formatted floppies, none of them completed the reading, all failed with "USB underrun".
The machine I ran this test on runs Xubuntu 18.04.2 LTS with kernel
tingo@kg-u35jc:~/personal/projects/psoc/fluxengine/tmp$ uname -a
Linux kg-u35jc 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

the reason for using that machine is that my preferred laptop at home, which runs Debian 9.8 and kernel
tingo@z30b:~$ uname -a
Linux z30b 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux

failed on reading anything (even DD formatted floppies) with "USB underrun". Not sure it is relevant.

FWIW, I also tested the 'hd' branch on my work machine, but it also has the "USB underrun" problem. Example:
tingo@kg-bsbox:~/personal/projects/psoc/fluxengine/tmp$ ../.obj/fe-readibm -o nd-525-210523g02-xx-02d.image -f nd-525-210523g02-xx-02d.flux
[..]
 42.1: 161 ms in 128256 bytes (795 kB/s)
       0.96 us clock; 21025 bytes encoded; 16 records
       8 sectors;
       logical track 42.1; 8192 bytes decoded.
 43.0: Error: USB underrun (not enough bandwidth)

Do you want any of the flux files? Are they of any use to you (even if they don't contain a full image)?

USB underrun means that you're out of USB bandwidth. Each pulse on the disk uses up two bytes.
One of my 1232kB 3.5" disks takes 150kB to scan, at 785kB/s bandwidth. That's a 300rpm disk. 5.25" disks spin at 360rpm, which is 1.2x the speed, so I'd expect a 1232kB 3.5" disk to use 942kB/s of bandwidth, which looks like it's beyond your limit. Your 360kB disks are working because they have fewer pulses on the disk, and therefore use less bandwidth.
I suspect I'm going to need to reduce the bandwidth use, somehow. I can think of a few tricks but I just hope the board has enough CPU to manage it. You could try using lsusb -t and trying to find a connection as close to a high-speed hub as possible --- try a USB2 port if you've got one.
Re the high-density flag: I'm very confused. Previously the drive was stuck in a single mode. Unless I've managed to completely fluff the flag implementation, I would expect your disks to work with one setting but not the other...

One of my 1232kB 3.5" disks takes 150kB to scan, at 785kB/s bandwidth. That's a 300rpm disk.

Yes, no worries about that.

5.25" disks spin at 360rpm, which is 1.2x the speed, so I'd expect a 1232kB 3.5" disk to use 942kB/s of >bandwidth, which looks like it's beyond your limit. Your 360kB disks are working because they have >fewer pulses on the disk, and therefore use less bandwidth.

Well, the point I was trying to make was that my machines are apparently fast enough to capture 1200 kB 5.25 inch (in other words, ibm or ms-dos formatted) floppies without USB underrun, while 1232 kB  5.25 inch (ND formatted) floppies fails - every single of them. It could be that the limit is somewhere between 1200 and 1232, but it still "smells suspicious" to me. Anyway, if you manage to reduce the required bandwidth that would be great, currently it is hard to use the FluxEngine for 5.25 inch HD floppies. I'm guessing buffering more data on the PSOc wouldn't help?
I've already checked with lsusb -t, for some reason the FluxEngine always attaches at full speed (12Mbps) no matter which port (usb 2.0 or usb 3.0) I connect it to. Looking at my notes, I haven't documented lsusb -t output, I'll do that tomorrow (my FluxEngine is currently in my office).
About the high-density flag; alas, I have no clues. I can only report what I observe.

Oh, I'm sorry --- I thought you had 360kB 5.25" disks. Yes, that's really weird and extremely suspicious.
Sadly the Cypress board is a 12Mb/s device, so it won't get USB 2 speeds. However, USB 2 ports appear to be better at maxing out the bandwidth of a USB 1 connection, so you may get slightly better performance that way. If it's mostly working but marginal then that might make the difference.
I suppose I'll start thinking about really quick data compression...

I've opened issue #51 to document usb related issues (mainly ports, connections and bulktransport test results).

If you look in the 'crunch' branch there's an extremely experimental version using a compressed datastream from the device to the PC. Bandwidth requirements are about 500kB/s, so should be comfortably within your margin. PTAL?
Incidentally, the -H flag has been renamed --hd (note the two dashes); there was a name conflict in one of the tools.

report on 'crunch' branch testing in #53.

ok, testing with latest firmware and client from master branch, since 'crunch' is no more. Trying to decode a 5.25 inch, HD, ND format 17b floppy (written from the same image as the one I sent you):
tingo@kg-bsbox:~/personal/projects/psoc/fluxengine/tmp$ ../.obj/fe-readibm -s :t=0-76 --retries=0 -o nd-525-211024-c01-xx-01d-hd.image -f nd-525-211024-c01-xx-01d-hd.flux --hd
Reading from: :d=0:s=0-1:t=0-76
Writing a copy of the flux to nd-525-211024-c01-xx-01d-hd.flux
  0.0: (56840 bytes crunched) 162 ms in 90944 bytes
       1.04 us clock; 19534 bytes encoded; 16 records
       0 sectors;
       0 bytes decoded.
  0.1: (54080 bytes crunched) 162 ms in 86528 bytes
       1.04 us clock; 19556 bytes encoded; 16 records
       0 sectors;
       0 bytes decoded.
[..]
 76.0: (55521 bytes crunched) 162 ms in 88832 bytes
       1.04 us clock; 19546 bytes encoded; 16 records
       0 sectors;
       0 bytes decoded.
 76.1: (53721 bytes crunched) 162 ms in 85952 bytes
       1.08 us clock; 18801 bytes encoded; 3 records
       0 sectors;
       0 bytes decoded.
H.SS Tracks --->
No sectors in output; skipping analysis
0 tracks, 0 heads, 0 sectors, 0 bytes per sector, 0 kB total

for some reason, it doesn't want to decode anything. If I try without the '--hd' flag:
tingo@kg-bsbox:~/personal/projects/psoc/fluxengine/tmp$ ../.obj/fe-readibm -s :t=0-76 --retries=0 -o nd-525-211024-c01-xx-01d.image -f nd-525-211024-c01-xx-01d.flux
[..]
 76.0: (78560 bytes crunched) 161 ms in 125696 bytes
       0.92 us clock; 21995 bytes encoded; 16 records
       8 sectors;
       Failed to read sector 0 (bad checksum);
       Failed to read sector 1 (bad checksum);
       Failed to read sector 2 (bad checksum);
       Failed to read sector 4 (bad checksum);
       Failed to read sector 5 (bad checksum);
       giving up
       logical track 76.0; 8192 bytes decoded.
 76.1: (78560 bytes crunched) 161 ms in 125696 bytes
       0.92 us clock; 22003 bytes encoded; 16 records
       8 sectors;
       logical track 76.1; 8192 bytes decoded.
H.SS Tracks --->
0. 0 BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB.B.B..B.B..B.BBBB.B......BBBBB.BBBBBBBBBBB.B
0. 1 BBBBBBBBBBBBBBBBBBBBBBBB.BBB.BBB..B.B.......X.BBBB.B......BXBBB.BBBBBBBBB.B.B
0. 2 BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB.BB.....BB.BBBB.B......BBBBB.BBBBBBBBBBB.B
0. 3 BBBBBBBBBBBBBBBBBBBBBBBBXBBB.BBB..BBB.....BBB.BBBB.B......BBBBB.BBBBBBBBBBBB.
0. 4 BBBBBBBBBBBBBBBBBXBBBBBBBBBBBBBBB.BBBB......X.BBBB.B......BBBBB.BBBBBBBBXBBBB
0. 5 BBBBBBBBBBBBBBBBBBBBBBBBBBBB.BBB..B..B.B...BX.BBBB.B......BBBBB.BBBBBBBBBBBBB
0. 6 BBBBBBBBBBBBBBBBBBBBBB.BBBBBBBBBBBB....B....B.BBBB.B......BBBBB.BBBBBBBBBBBB.
0. 7 BBBBBBBBBBBBBBBBBBBBBBBBBBBB.BB.BBB.B..B....B.BXBB.B......BBBBX.BBBBBBBBBBBB.
1. 0 BBBBBBBBBBBBBBBBBBBBBB.BB...................B.BBB.BB...BBBBBBBB.BB...........
1. 1 BBBBBBBBBBBB.BBB.BBBBBBBB...................B.BBB.BB...BBBBBBBB....BB........
1. 2 BBBBBBBBBBBBBBBBBBBBBB.BBBBBBB..............B.BBB.BB...BBBBBBBB.B..B.........
1. 3 BBBBXXBBBBBBBBBBBBBB.BBB.B...BB.............B.BBB.BB...BXBBBBBB.BB.B.........
1. 4 BBBXBXBBBBBBBBBBBBBBBB.BB.B...BX............B.BBB.BB...BBBBXBBB.B..BB.B......
1. 5 BBBBBBXBBBBBBBBBBBBBBBBB..BB.BB.............B.BBB.BX...BXXBBBBB.B.XB.........
1. 6 BBBXBXBBBBBBBBBBBBBBBB.BBBBBB...............B.BBB.BB....BBBBBBB.BBBB..B......
1. 7 BBXBBBBBBBBBBBBBBBBB.B..B..B................B.BBB.BB...BBBBXBBB....B..X......
Good sectors: 420/1232 (34%)
Missing sectors: 26/1232 (2%)
Bad sectors: 786/1232 (63%)
77 tracks, 2 heads, 8 sectors, 1024 bytes per sector, 1232 kB total

this looks  better. Let me try to use ndfs-tool (from Tor Arntsen) to see if the image can be read:
tingo@kg-bsbox:~/personal/projects/psoc/fluxengine/tmp$ ~/bin/ndfs -t nd-525-211024-c01-xx-01d.image
Directory name            : FF&&.f.%+
                                     &.(
Object file index pointer : 134217791 SI: 0x2 (sub-indexed)
User file index pointer   : 134217791 SI: 0x2 (sub-indexed)
Bit file pointer          : 38 SI: 0x3 (reserved for future extension)
No. of unreserved pages   :<PHONE_NUMBER>
Error reading page<PHONE_NUMBER>: Success

not a total success, but something is readable here. The correct output from the 'ndfs' command looks like
tingo@kg-bsbox:/zs/tingo/doc/ND/software/211024c01$ ~/bin/ndfs -t 211024C01-XX-01D.image
Directory name            : 211024C01-XX-01D
Object file index pointer : 508 SI: 0x1 (indexed)
User file index pointer   : 510 SI: 0x1 (indexed)
Bit file pointer          : 306 SI: 0x0 (contiguous)
No. of unreserved pages   : 1
Files:
  0   0: I       89 pages    184320 bytes 1987-09-21 12:21:10 (FLOPPY-USER)S3-CONFIG-C00:PROG
  0   1: I       16 pages     32448 bytes 1987-05-18 08:39:11 (FLOPPY-USER)DDBTABLES-E07:VTM
  0   2: I       51 pages     86016 bytes 1987-09-21 12:21:27 (FLOPPY-USER)NOTS-SERVICE-C00:PROG
Directory size: 611 pages
Bit file size : 1 page

I hope this helps.

Perhaps something is marginal? Increasing revolutions seems to help. Example:
tingo@kg-bsbox:~/personal/projects/psoc/fluxengine/tmp$ ../.obj/fe-readibm -s :t=0-76 --retries=0 -o nd-525-210523g02-xx-02d.image -f nd-525-210523g02-xx-02d.flux
[..]
H.SS Tracks --->
0. 0 .B..BB...BB.................................BBBBBB.B....B....................
0. 1 BBB.B.BB.BBBB.......B.......................BBBBBB.B.B..BBB.B.B...B..........
0. 2 ..B....B.......B............................BBBBBB.B.BB.BBB..................
0. 3 B.BB..BB....................................BBBB.B.B.BB.BBB..B...............
0. 4 .BBB.BB...B...B.............................BBBBBB.B.BB.B...B................
0. 5 BB...BB.B....B..............................BBBBBB.B.BB.B....................
0. 6 BB...BX.....B...............................BBBBB..B.BB.B.B..................
0. 7 BBB.B...BB..................................BBBBBB.B..B.....B................
1. 0 BBBB.B..BB..................................B.B.BB...BB.B....................
1. 1 BBBBBBBBBBBBB..B............................B.B.BBB.BBB.BB...B...............
1. 2 BXBBBBBB.B.B.B..............................B.B.BBB.BBB.BBB..B...............
1. 3 BBBBBBBBBBB..B..............................X.B.BBB.BBB..BB..B...............
1. 4 BBBBBXBBBBBB.B..B.B.........................B.B.BBB.BBB.BB...................
1. 5 BBBBBBBB.BB..B....B.........................B.X.BBB.BB..BB...................
1. 6 B.BBBB..B.B.................................B.B.BBB..B...B...................
1. 7 BB.BB.B.B..B................................B.B.BBB.BBB...B..................
Good sectors: 937/1232 (76%)
Missing sectors: 5/1232 (0%)
Bad sectors: 290/1232 (23%)
77 tracks, 2 heads, 8 sectors, 1024 bytes per sector, 1232 kB total

with '--revolutions=7':
tingo@kg-bsbox:~/personal/projects/psoc/fluxengine/tmp$ ../.obj/fe-readibm -s :t=0-76 --retries=0 --revolutions=7 -o nd-525-210523g02-xx-02d.image -f nd-525-210523g02-xx-02d.flux
[..]
Good sectors: 1023/1232 (83%)
Missing sectors: 0/1232 (0%)
Bad sectors: 209/1232 (16%)
77 tracks, 2 heads, 8 sectors, 1024 bytes per sector, 1232 kB total

Hope this helps.

That's really interesting. You're using the same drive that you used to write the disks, right? That means that drive alignment isn't an issue. The fact that more revolutions produces a better result suggests some kind of random noise.
The very clear stripe at track 44 is extremely suspicious, but only appears if you don't use --hd. I think this is related to the reduced write current needed past track 44 --- 8" drives needed this supplied by the disk controller, but it's automatic with 5.25" and 3.5" drives.
I have had a thought about whether I have the right pullup resistor at the FluxEngine end. Let me go and try something...

You're using the same drive that you used to write the disks, right?

Unfortunately, no. My media conversion machine (has 3.5 inch and 5.25 inch floppies and more) isn't easily accessible.
However, I have used the drives in it to write a lot of floppies (both 3.5 and 5.25 inch) which I then has read in other drives, so I don't think the drives in my media conversion machine has alignment or other issues.

I spent some time fiddling with the firmware.
This is weird.

the weird noise only appears on your ND disks. A 1200kB PC floppy works fine for me (at least mostly, it's a preformatted one and is partially demagnetised) doesn't show the noise.
1200kB PC floppies don't work for you either (although I believe you haven't tried making one with your hardware?).
you have more than one drive, ruling out alignment or other drive quirks at your end.
I see the precisely the same results you do with your disks, ruling out alignment or other drive quirks at my end.
it only happens on 5.25" disks. 3.5" disks, HD or otherwise, read fine.
it only happens on HD disks. DD ones read fine.

Have I missed anything?
My previous working hypothesis was that the drive pulses were too brief to be sampled... but it turns out the pulses are at least 150ns, and my sample rate is 12MHz which is 83ns per pulse, and I tried running them through a pulse conditioner first which samples at 64MHz, so that's not it.
One thing I have noticed is that if I push the clock rate on the FluxEngine up to 72MHz, the quality of the data gets slightly better, although that could be coincidence as I was testing. But... why would this only affect 5.25" disks?
I'm going to have to buy a logic analyser and find out exactly what's coming off the disk, which will take a bit of time, but in the mean time is there any chance you could format a 1200kB PC disk on your hardware and then try to read it with FluxEngine? Sorry to keep asking you to do stuff...

one thing you have perhaps missed:
'--hd' flag doesn't work for me, but it does for you.

Sorry for the delay in getting back to you --- good to know it's being useful to you in its current state. Did you have any problems with the 0b floppies?
I don't think the 17b flux files will be of any use to me at this point; what's happening is that the sampling's going awry and the FluxEngine is reading bad data --- I think it's dropping bits. I still don't know why. My suspicion is that the 5.25" drives in HD mode aren't behaving electrically like other drives.
Accordingly, I've ordered a logic analyser, and now I'm waiting for it to arrive. That'll let me independently capture the output of the drive so that I can compare it with what the FluxEngine hardware is producing. It'll take a few weeks to arrive, unfortunately.
If it does turn out that the drive is behaving weirdly, there are a few things I can do; the PSoC5 has some ability to do software configurable analogue electronics so I may be able to hook up an opamp or something, but this is getting increasingly esoteric and I don't know much about this area, so I'm crossing my fingers.
I'll let you know when it arrives...

No, I didn't have any problems with the format 0b floppies (caveat: the only testing done on each image was listing the contents via the 'ndfs' tool).
Hmm, the "reading bad data" part is probably bad news for me as well - it probably means that there isn't any parameters or "tweaks" I can use on the flux files I captured to improve the resulting images?
Today I tested a format 17b image by writing it to a physical floppy (using my media machine, not the FluxEngine). Then I put the floppy in a real ND machine and attempted to load it. Unfortunately, it stopped after loading the floppy monitor (think of it as a boot loader) and wouldn't show any files on the floppy. So the image is not good enough to be working.

I haven't forgotten about this!
I've managed to confirm that this is a sampler bug. See #75.

I've managed to confirm that it's not a sampler bug, or at least not a current one. I think I actually fixed this a while ago with another change and never noticed. Certainly, I can read your 17b disk absolutely fine now.
Could you update your firmware and client and have another go and see if it works? Thanks!

I tested on a small sample set (7 floppies, ND format 17b) It is much better now:
tingo@kg-bsbox:~/personal/projects/psoc/fluxengine/tmp$ ../fluxengine read ibm -s :t=0-76 --retries=0 -o test-nd-525-250305m05-xx-03d.image
[..]
H.SS Tracks --->
0. 0 .......?.......?..........?..................................................
0. 1 ...............X..........X..................................................
0. 2 ...............X..........X..................................................
0. 3 ............?..X..........X..................................................
0. 4 ...............X..........X..................................................
0. 5 ...............X..........X..................................................
0. 6 ...............X..........X..................................................
0. 7 ...............X..........X..................................................
1. 0 .........................X.................................?.................
1. 1 ...........................................................X.................
1. 2 ...........................................................X.................
1. 3 ...........................................................X.................
1. 4 ...........................................................X.................
1. 5 ...........................................................X.................
1. 6 ...........................................................X.................
1. 7 ...........................................................X.................
Good sectors: 1210/1232 (98%)
Missing sectors: 22/1232 (1%)
Bad sectors: 0/1232 (0%)
77 tracks, 2 heads, 8 sectors, 1024 bytes per sector, 1232 kB total

for most floppies I can get improvements by adding '--revolutions=2', like this
tingo@kg-bsbox:~/personal/projects/psoc/fluxengine/tmp$ ../fluxengine read ibm -s :t=0-76 --retries=0 --revolutions=2 -o test-nd-525-250305m05-xx-03d_r2.image
[..]
H.SS Tracks --->
0. 0 .............................................................................
0. 1 .............................................................................
0. 2 .............................................................................
0. 3 .............................................................................
0. 4 .............................................................................
0. 5 .............................................................................
0. 6 .............................................................................
0. 7 .............................................................................
1. 0 .............................................................................
1. 1 .............................................................................
1. 2 .............................................................................
1. 3 .............................................................................
1. 4 .............................................................................
1. 5 .............................................................................
1. 6 .............................................................................
1. 7 .............................................................................
Good sectors: 1232/1232 (100%)
Missing sectors: 0/1232 (0%)
Bad sectors: 0/1232 (0%)
77 tracks, 2 heads, 8 sectors, 1024 bytes per sector, 1232 kB total

as you can see, I'm not using the '--hd' flag.
Out of the seven, only one image can't be read by the 'ndfs' tool (and that might possible be caused by a different filesystem format)

Oh, good --- yes, the --revolutions=2 is probably because on this format the sectors aren't lined up with the index hole and one sector overlaps it. You need two revolutions to be able to read a complete copy of it. The whole row of Xs is a little bit strange, however. The error rate is probably low enough that you can use automatic retries now.
I'm going to close the bug as fixed --- let me know if you have any problems...


Add tutorial.md and reference to tutorial in README.md

Help new users install and use the tool.
Signed-off-by: John Speed Meyers<EMAIL_ADDRESS>

@justinabrahms, I edited tutorial.md to include the binary installation instructions. I did, however, place instruction for downloading and building the source code at the bottom of the tutorial. I'm glad to remove that too if you think that's too much.


Bump extwitter to 0.12

This allows us to get very close to full replacement of Poison with
Jason. Phoenix update is the final leg.

Coverage remained the same at 83.797% when pulling 7bce3a44abac9b20259dafb6c170ea7935d0d16a on tmock12/update-extwitter into 8ccc7f4a70ddcfa619d916a99b546d47b1fd605a on master.

closing as authors have decided to upgrade in larger commit


update angular dependences

Replace angular 1.3x dependencies w/ 1.4x

Is this an accidental PR by chance? The package name has been changed to foundation-apps-custom, so this can't be pulled in as-is.
As for Angular 1.4, we haven't tested the framework with it yet, so we're staying on 1.3 for now.


Comprehensive readme for package users

Overview
Datapackage is one of the most important package in our eco-system. Also it's the most high-level (public facing). So eventually to have comprehensive readme like https://github.com/frictionlessdata/jsontableschema-py is vital.
Tasks

[ ] update readme
[ ] add examples
[ ] check code in readme/example works
[ ] fix readme on PyPi (see other libs approach)
[ ] be clearer what validate does (#126)
[ ] mark push/pull_datapackage as a provisional API (#130)

:+1:

MERGED
#93


Typescript errors in api/base.ts and .hathora/patch.ts

I've been working on  a simple game and when I import HathoraClient from .hathora/client (as is done in the ship example) the web client compilation errors with typescript errors coming from api/base.ts and .hathora/patch.ts.
If required I can share more of my code, but since this errors in the automatically generated api code I'm unsure if that's needed.
Extra info:
$ hathora --version
0.9.12
$ node -v
v16.12.0

Thank you for the report @MartijnWelker. Can you try again with hathora 0.9.13 and let me know if that fixes the issue for you?

Yep. No more errors 👍 Thanks for the quick reply


Issue with gradle sync and dependencies

"Gradle's dependency cache may be corrupt" I tried  to re-download the dependencies but that didn't help

Try updating your gradle plugin https://stackoverflow.com/questions/38442901/gradles-dependency-cache-may-be-corrupt-this-sometimes-occurs-after-a-network

The Gradle sync worked but a new issue came up
Facing issue
error: cannot find symbol
InputStream is = getResources().openRawResource(R.raw.trained);
^
symbol:   variable raw
location: class R
I tried with some available suggestions on StackOverflow but they didn't  work
Could you please help me with this

Hello,
It sounds like you don't have a "trained.xml" available to the app - this is the pre-trained SVM model which will allow for detection of hand gestures.
This file is generated using my offline-trainer repository - have you followed my guide on how to do this?


[2023.10.12-Beta] climate and water_heater could not be set up

Hi,
I get this error in the notification:

When inspecting the logs, I get these errors:
Logger: homeassistant.setup
Source: setup.py:359
First occurred: 06:58:16 (2 occurrences)
Last logged: 06:58:16

Unable to prepare setup for platform luxtronik2.climate: Platform not found (Exception importing custom_components.luxtronik2.climate).
Unable to prepare setup for platform luxtronik2.water_heater: Platform not found (Exception importing custom_components.luxtronik2.water_heater).

Logger: homeassistant.loader
Source: loader.py:838
First occurred: 06:58:16 (1 occurrences)
Last logged: 06:58:16

Unexpected exception importing platform custom_components.luxtronik2.water_heater
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/loader.py", line 838, in get_platform
    cache[full_name] = self._import_platform(platform_name)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 855, in _import_platform
    return importlib.import_module(f"{self.pkg_path}.{platform_name}")
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1204, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1176, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1147, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 940, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/config/custom_components/luxtronik2/water_heater.py", line 52, in <module>
    LuxtronikWaterHeaterDescription(
TypeError: LuxtronikWaterHeaterDescription.__init__() got an unexpected keyword argument 'temperature_unit'

Logger: homeassistant.loader
Source: loader.py:838
First occurred: 06:58:16 (1 occurrences)
Last logged: 06:58:16

Unexpected exception importing platform custom_components.luxtronik2.climate
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/loader.py", line 838, in get_platform
    cache[full_name] = self._import_platform(platform_name)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 855, in _import_platform
    return importlib.import_module(f"{self.pkg_path}.{platform_name}")
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1204, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1176, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1147, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 940, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/config/custom_components/luxtronik2/climate.py", line 88, in <module>
    LuxtronikClimateDescription(
TypeError: LuxtronikClimateDescription.__init__() got an unexpected keyword argument 'temperature_unit'

I'm on 2023.10.12-Beta and on Home Assistant 2023.10.1. I've also restarted the Heatpump, just to be sure, didn't fix it. (And of course rebooted HA). I have also removed and reinstalled the custom component, didn't work.

Sorry, my mistake, forgot to include 2 small changes in model.py

Seems to be fixed in latest beta (2023.10.13).


BUG - Popup does not fit within the boundaries of the viewport

I have a simple reproducible test case (on Chrome at least).

  <link rel="stylesheet" type="text/css"
        href="https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.2.2/semantic.min.css">

  <meta name="viewport" content="width=device-width, initial-scale=1">

Text here

Fabrics

			Cashmere
			Linen
			Cotton
			Viscose

Open in Chrome and hover mouse over the vertical ellipsis icon and see console output. Also, the menu does not open. This seems to be due to the padding on body tag.

I've now modified the code in first comment (in this issue) and now it uses files directly from CDN, so no need to download etc and link files anymore.

Copy and paste the code in an html file and
open that file in a browser (Chrome) and
click on the elliptical icon

you'll see the issue yourself. You can open console log to see errors.

would be great if you can add a jsfiddle example

here it is: https://jsfiddle.net/9amow2f2/1/

Is there any reason that you want to add boundary:   $('body'), beacause if i remove that, popup seem to work fine.

no special reason but just wanted to inform devs about it to make sure it does not break something else somewhere else

I think it is an expected behavior... since your popup does not fit inside boundary, SUI log that warning for you to know.

You can use lastResort to force a direction when a popup doesnt fit.


root permissions & openssl/aes.h file not found

Running with user permissions:
$ python setup.py install
Checking .pth file support in /Library/Python/2.7/site-packages/
error: can't create or remove files in install directory

The following error occurred while trying to add or remove files in the
installation directory:

    [Errno 13] Permission denied: '/Library/Python/2.7/site-packages/test-easy-install-12740.pth'

The installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

    /Library/Python/2.7/site-packages/

Perhaps your account does not have write access to this directory?  If the
installation directory is a system-owned directory, you may need to sign in
as the administrator or "root" account.  If you do not have administrative
access to this machine, you may wish to choose a different installation
directory, preferably one that is listed in your PYTHONPATH environment
variable.

For information on other options, you may wish to consult the
documentation at:

  https://pythonhosted.org/setuptools/easy_install.html

Please make the appropriate changes for your system and try again.

Running with sudo:
$ sudo python setup.py install
Generates some warning, and then the fatal error:
scrypt-1.1.6/lib/crypto/crypto_aesctr.c:38:10: fatal error: 'openssl/aes.h' file not found

Then when trying to execute:
$ pappy -l
Traceback (most recent call last):
  File "/usr/local/bin/pappy", line 5, in <module>
    from pkg_resources import load_entry_point
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 2793, in <module>
    working_set.require(__requires__)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 673, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 576, in resolve
    raise DistributionNotFound(req)
pkg_resources.DistributionNotFound: scrypt>=0.7.1

Running under El Capitan 10.11.6

I think there is some dependency for scrypt that you do not have installed. I vaguely remember running into this a while ago but I must have just fixed it myself and forgotten to document it. Sicne a dependency is missing, the scrypt library isn't being installed. Then because Pappy depends on the library, Pappy isn't being run. I don't know what the dependency is off the top of my head unfortunately. I suggest setting up a virtual environment and seeing if you can install the scrypt by itself.

No update for a while, closing. If you still have this problem, feel free to post an update and we can reopen this.