A singletone noise in the enhanced speech

Hi!
thanks a lot for the code. It is very helpful. I have a small doubt and it would be great if you kindly address it.
In the enhanced speech, there is single tone noise in the background. Is this some kind of bug or is there any way to remove this single-tone frequency?
The single-tone noise can be seen the in spectrograms (at 4 Khz in the first sentence and at 7khz and 2 khz in the second sentence.)

The speech files are also added here. Please kindly suggest .
p232_102.zip

Hi @dipjyoti92,
I am also facing the exact same issue with the single tone uniform noise. Did you manage to fix this?

Had the same issue, but I have single tone noise at both 1k and 5k hz, I used the official dataset, not params changed from the original repo, and 100 epoch


feat: instagram oauth provider

Turns out the user response from the Instagram Basic API (see docs) is not compatible with the existing OIDC provider.

It's a pretty straightforward change, I've included the UI resources and ui/dist build too.
Let me know if you have any questions?

Thanks! To avoid the back-and-forth, I've merged it locally in the develop branch with some added minor missing tests.
The provider will be available as part of v0.17.0 release (there are no ETAs yet).

Brilliant, thank you

@ganigeorgiev reopening cause I found an issue:
On https://github.com/pocketbase/pocketbase/blob/develop/tools/auth/instagram.go#L56C7-L56C7 we would need to sanitize the username from instagram to PB restriction (alphanumeric I believe) otherwise creating the auth record could fail.
Is there any technical issue for why the PB auth record Username is only alphanumeric?

I don't think it is necessary as by default PocketBase will use the username only if it is "valid", otherwise will generate its own.

Is there any technical issue for why the PB auth record Username is only alphanumeric?

There is no specific reason, it is this way just because that is my use case in Presentator. There are plans in the future to convert the username field to a regular text field to make it customizable and even optional (see https://github.com/pocketbase/pocketbase/discussions/2425#discussioncomment-5818276).

Ok, so via oauth it will not fail insert even if the username has invalid chars? Also when updating on the admin screen?
I'm asking cause I actually noticed the issue using the forms.NewRecordUpsert, and that at least does not insert the record if it has invalid chars, I haven't tested update with it.

Ok, so via oauth it will not fail insert even if the username has invalid chars?

Yes, we have an extra check that verify the username before assign in when created via OAuth2. If it is invalid it will use an autogenerated one.

Also when updating on the admin screen?
I'm asking cause I actually noticed the issue using the forms.NewRecordUpsert

No, in this case the regular validation will be triggered. If you want to skip the username validation you can assign the username directly to the record model OR persist the record with the Dao.SaveRecord (aka. without any data validations).

If it is invalid it will use an autogenerated one.

Ah, this will be a problem for me as I need the IG username regardless if it's PB valid or not. And as I think most using the provider would assume the same, I'm more inclined to have the provider not set the username, I'll just grab it of RawUser and set it on a text field OnRecordAfterAuthWithOAuth2Request. Your thoughts?

persist the record with the Dao.SaveRecord (aka. without any data validations).

Would I be able to set the email and password this way? The reason I'm using the form upsert is cause of the form.SetFullManageAccess(true).

I'm more inclined to have the provider not set the username, it can be grabbed from the RawUser if needed and set it on a text field OnRecordAfterAuthWithOAuth2Request. Your thoughts?

I don't have strong opinion on this and I'm not sure what to recommend. It is possible to overwrite the record username in the OAuth2 hook (you can grab the raw provider username from the RecordAuthWithOAuth2Event.OAuth2User event field). Keep in mind that the PocketBase user and the Instagram user are 2 separate entities and also your application may have more than one OAuht2 provider enabled.

Would I be able to set the email and password this way?

Yes, the upsert form actually under the hood uses directly the Dao to save the record but with additional extra layer for validations. To set a password hash from a plain password, you can use models.Record.SetPassword().

I think this says it all:

PocketBase user and the Instagram user are 2 separate entities
I'm going to remove setting the PB username with IG's. And use the events to do so, it's a cleaner approach IMO.

Again, this may not be necessary. You can still overwrite the Record username if you want to and keep the Instagram username as default (when possible). This way the behavior would be consistent with the other providers.

@ganigeorgiev added named api scenario test runs to my fork (https://github.com/pocketbase/pocketbase/commit/d0154c129cf9cab63eed2e8a6a6af99cc062dae9) so that:

It's really handy for my project, would you consider adding it?
Thank you

Yes, I'll consider wrapping it in the near future.


TP2000-1052 - UI support for envelope validation failure

TP2000-1052 - UI support for envelope validation failure

Why

TARIC XML files are validated immediately after they have been generated from a workbasket's contents. The XML file creation process is performed in a Celery background task. Envelope creation is bound up with its associated XML file creation and validation: if an Envelope's XML file fails validation, then the Envelope instance process fails in its entirety. Information about file validation is therefore lost without means of establishing what error may have occurred. There's therefore no way of presenting failure infomation in TAP's packaging and envelope queues.
What

This PR introduces a ValidationState Choices class and new attribute, Envelope.validation_state, that takes a ValidationState value. Envelope instance creation no longer fails upon XML validation failure. When Envelope instances are created, TARIC XML file validation state is preserved, aiding failure diagnosis. However, because invalid XML files have no use, they are not stored to S3 and their associated Envelope's xml_file takes a value of None.
While implementing this UI-related feature, issues were found in the validation process. These have been fixed as part of this PR.
A unit test against empty transaction validation has been removed because it was redundant. The same validation feature is a part of the TARIC XML schema validation check, which has associated unit tests.

Checklist

Requires migrations? Yes
Requires dependency updates? No

Codecov Report
Attention: 11 lines in your changes are missing coverage. Please review.

Comparison is base (39a9c2b) 92.79% compared to head (eb87cf9) 92.79%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1082   +/-   ##
=======================================
  Coverage   92.79%   92.79%
=======================================
  Files         460      460
  Lines       34903    34932   +29
  Branches     2673     2673
=======================================
+ Hits        32388    32416   +28
- Misses       1991     1992    +1
  Partials      524      524

Files
Coverage Δ

publishing/models/__init__.py
100.00% <ø> (ø)

publishing/tasks.py
70.73% <100.00%> (+0.98%)
:arrow_up:

publishing/tests/test_model_envelope.py
100.00% <100.00%> (ø)

publishing/tests/test_models.py
86.97% <ø> (-0.30%)
:arrow_down:

publishing/tests/test_tasks.py
99.23% <ø> (ø)

publishing/tests/test_util.py
97.70% <100.00%> (+0.25%)
:arrow_up:

publishing/util.py
90.90% <80.00%> (+7.57%)
:arrow_up:

publishing/models/envelope.py
89.01% <81.57%> (-1.96%)
:arrow_down:

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Allow Ionic Icons to be use in AlertControl

This is really the same thing that was wanted here.
https://github.com/ionic-team/ionic/issues/7874
Code:
 let popupMessage = "<span>" + "Use the Search icon to do a search" + "</span>" + '<ion-icon name="ios-search"></ion-icon>';

        let welcomePopup = this.alertCtrl.create({
            title: "Popup Title"
            message: popupMessage,
            inputs: [
                {
                    type: 'checkbox',
                    label: "Don't show again",
                    value: 'Yes',
                    checked: false
                }],
            buttons: [{
                text: this.translateService.instant('OKBTN'),
                handler: data => {
                  //don't show popup
                }
            }]
        });
        welcomePopup.present();

No Ionic Icon shows up.
Inspecting the HTML the tag doesn't even show up.

@ionic/cli-utils  : 1.19.1
ionic (Ionic CLI) : 3.19.1
global packages:
cordova (Cordova CLI) : 7.0.1

local packages:
@ionic/app-scripts : 3.2.0
Cordova Platforms  : android 6.3.0 browser 4.1.0
Ionic Framework    : ionic-angular 3.9.2

System:
Android SDK Tools : 26.1.1
Node              : v6.12.3
npm               : 3.10.10
OS                : Linux 3.13

Thanks for the issue! This is no longer an issue in the latest version 4.4.2 so I am going to close this. If you're still having problems please open a new issue. Here's a Codepen where I was able to see the icon: https://codepen.io/brandyscarney/pen/yWWYoJ
Thanks! 🙂


Error loading JSON-LD in insecure mode

Currently when running:
bin/trust claim   --creator did:00a65b11-593c-4a46-bf64-8b83f3ef698f   --target did:59f269a0-0847-4f00-8c4c-26d84e6714c4   --description 'Elixir programming'   --value 0.99   --algorithm EcdsaKoblitzSignature2016   --private-key L4mEi7eEdTNNFQEWaa7JhUKAbtHdVvByGAqvpJKC53mfiqunjBjw

I get:
jsonld.NormalizeError: Could not convert input to RDF dataset before normalization.
    at /Users/harlan/code/trust-exchange/node_modules/jsonld/js/jsonld.js:806:25
    at /Users/harlan/code/trust-exchange/node_modules/jsonld/js/jsonld.js:952:14
    at /Users/harlan/code/trust-exchange/node_modules/jsonld/js/jsonld.js:326:16
    at Array.done (/Users/harlan/code/trust-exchange/node_modules/jsonld/js/jsonld.js:6848:20)
    at /Users/harlan/code/trust-exchange/node_modules/jsonld/js/jsonld.js:1557:21
    at loadDocument (/Users/harlan/code/trust-exchange/node_modules/jsonld/js/jsonld.js:1781:14)
    at ._loader (/Users/harlan/code/trust-exchange/node_modules/jsonld/js/jsonld.js:1769:5)
    at jsonld.RequestQueue.add (/Users/harlan/code/trust-exchange/node_modules/jsonld/js/jsonld.js:1553:10)
    at jsonld.loadDocument (/Users/harlan/code/trust-exchange/node_modules/jsonld/js/jsonld.js:1234:24)
    at /Users/harlan/code/trust-exchange/node_modules/jsonld/js/jsonld.js:6878:23

In debug mode, I found it was trying to load something within the jsonld node module from an HTTP url, while in secure mode.
If I hack into ./node_modules/jsonld-signatures/lib/jsonld-signatures.js and change secure: true to secure: false:
        libs[name].useDocumentLoader('node', {secure: false, strictSSL: true});

It "works" fine.
Um, correction, it did a minute ago, but stopped working when I reinstalled node modules, then did the tweak again.
All of the links to and within schemas ( https://github.com/CoMakery/trust-exchange-schema ) are https.  Not sure what the problem is here.

Working fine now, maybe the schema was cached...


Remember compact/pretty flow export user choice

closes #3849
Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Proposed changes
Saving flow is a specific format is not necessarily how a user wants to export a flow, especially when pasting to a forum/slack thread.
This PR remembers the user choice and reselects that mode in the export dialog.
Checklist

[x] I have read the contribution guidelines
[x] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage remained the same at 68.198% when pulling 7b52ef34beec0175ed6808794be86ccad9ea2b3b on Steve-Mcl:remember-export-format into c065d253e93302dd7761e529a7aaa0f4212b61ed on node-red:dev.


docs(www): add notes on how to compose multiple dialogs with menus

The proposed solution I have added is pretty much buried in a linked conversation and it took me some time to find it myself for the same problem I ran into. As such, I decided to contribute this to the docs.
As this is my first time contributing to this repository I wasn't sure about code conventions when writing docs so I'm looking forward to get this reviewed.

I just pushed a small change compared to the previous version to make the hook more type-safe by passing ElementRef<typeof DropdownMenuItem> rather than a HTMLDivElement to it in order to demo a realistic use of it.


Horizontal FAB with Actions on IR

Hello Vincent,
In Matrerial Design Theme, can Horizontal FAB with multiple actions be added to IR. e.g., in UT:
https://apex.oracle.com/pls/apex/f?p=102865:1:8196744598717:::::

Hello @Fatehcis,
From a technical standpoint, I think it would be doable. It would be very tricky though because of the way APEX dynamically generates this menu once you click on it.
We decided not to change the default behavior because it would necessitate for us to hard-code colors, icons, etc.
I believe you can achieve this yourself using custom Javascript and CSS, but we wouldn't recommend it.
Thanks.


UI Issue

Description

The "With an Existing Application1 Applications AvailableWith a New Application" appears in a single line in the following image in the DevPortal, which is not good for user experience.

Suggestions

It would look nice if you can improve the UI

This UI is changed now. See below


Download stats for various versions and platforms

As a product owner of Cucumber I'd like to understand more about the distribution of various platforms (JVM, Ruby, JavaScript, .NET etc) and versions that are used in the wild.
This can be done with a combination of:

Scripts that scrape various package manager stats
Including version/platform information in the message protocol and provide (a) service(s) where users can send their results (for example a report generators)

/cc @tooky

npm has a public API specifically for this https://github.com/npm/download-counts, e.g.
https://api.npmjs.org/downloads/point/last-month/cucumber

@davidjgoss most package managers have some sort of API to get download stats, but comparing those stats between platforms doesn't make sense.
This is because each package manager uses different caching strategies, so while the numbers might tell us Ruby has 3 times more downloads than Java, the number of people using Java might be twice as high as people using Ruby.
This is why I'd like to be able to collect real usage data. The main motivation for this is to understand better what platforms we should put more effort into supporting.

/cc @tooky


random function is not good for tree-shaking

Feature Request
Related to: https://github.com/samchon/typia/issues/1069
After several PRs including https://github.com/samchon/typia/pull/1133, the bundle size is decreasing !!
So basic functions like is or assert is well tree-shaked.
However, random generator is little bit hard to tree-shaking.
Here is why.
suppose you create a random function like this
import typia, { type tags } from "typia";

export const random = typia.createRandom<IMember>();

interface IMember {
  email: string & tags.Format<"email">;
}

this is compiled like this.
const RandomGenerator = /* @__PURE__ */ Object.freeze(/* @__PURE__ */ Object.defineProperty({
  __proto__: null,
  array,
  bigint,
  boolean,
  byte,
  date,
  datetime,
  duration,
  email,
  hostname,
  idnEmail,
  idnHostname,
  integer,
  ipv4,
  ipv6,
  iri,
  iriReference,
  jsonPointer,
  length,
  number,
  password,
  pattern,
  pick,
  regex,
  relativeJsonPointer,
  string,
  time,
  uri,
  uriReference,
  uriTemplate,
  url,
  uuid
}, Symbol.toStringTag, { value: "Module" }));
const random$2 = () => ({
  generator: RandomGenerator,
  pick
});
function random$1() {
  halt("random");
}
const randomPure = /* @__PURE__ */ Object.assign(
  random$1,
  /* @__PURE__ */ random$2()
);
function createRandom() {
  halt("createRandom");
}
const createRandomPure = /* @__PURE__ */ Object.assign(createRandom, randomPure);
function halt(name) {
  throw new Error(`Error on typia.${name}(): no transform has been configured. Read and follow https://typia.io/docs/setup please.`);
}
const random = (generator) => {
  const $generator = createRandomPure.generator;
  const $ro0 = (_recursive = false, _depth = 0) => {
    var _a, _b;
    return {
      email: ((_b = (_a = $generator.customs) == null ? void 0 : _a.string) == null ? void 0 : _b.call(_a, [
        {
          name: 'Format<"email">',
          kind: "format",
          value: "email"
        }
      ])) ?? (0, $generator.email)()
    };
  };
  return $ro0();
};

The implementation is here.
https://github.com/ryoppippi/typia/blob/b09a027d958fff0e384d4b6cae16f362fa4d6887/src/functional/Namespace/index.ts?plain=1#L73-L76
If this random function will be an exports like this
export { generator, pick }

and generater call method should be
random$2().generator.email
↓
random$2.generator.email
It is really great for tree-shaking.
I think this needs change APIs a little bit, and I don't know if I can tackle this change as I don't fully understand the API yet.
I also think that this should be included in v7 because this change is API level and users need re-compile

This problem would be cleared fixed in the next v7 update, and it is coming. Only LLm schema features are left.


Release 3.1.0 broke type inference on fastify route handler request parameter

Prerequisites

[X] I have written a descriptive issue title
[X] I have searched existing issues to ensure the bug has not already been reported

Fastify version
4.15.0
Plugin version
3.1.0
Node.js version
16.19.1
Operating system
macOS
Operating system version (i.e. 20.04, 11.3, 10)
Monterey 12.6.5
Description
Hi,
Just updated plugin to version 3.1.0 recently and it looks like I lost types inference on the fastify routes handler request object. I rollbacked to 3.0.0 which is working fine. The following screenshot is showing that I no longer get types inference on the params object of the fastify request despite schema definition being provided and Typebox type provider being used.

Thank you for your help ;)
Steps to Reproduce
import { TypeBoxTypeProvider } from '@fastify/type-provider-typebox';
import { Type } from '@sinclair/typebox';
import fastify from 'fastify';

fastify()
  .withTypeProvider<TypeBoxTypeProvider>()
  .get('/', {
    schema: {
      params: Type.Object({
        foo: Type.String()
      })
    },
    handler(req, rep) {
      console.log(req.params.foo);
      rep.send();
    }
  });

Expected Behavior

In the previous example, req.params.foo should be typed as a string.
Using strict flag with typescript, I should not get the following error:

'req.params' is of type 'unknown'.ts(18046)

I think this could be a Typebox version compatibility issue. I ran into something similar, type-provider-typebox now exports @sinclair/typebox directly so you should use that export. The docs have been updated to reflect the new usage.
import { TypeBoxTypeProvider, Type } from '@fastify/type-provider-typebox';
// Do not import @sinclair/typebox directly
import fastify from 'fastify';

fastify()
  .withTypeProvider<TypeBoxTypeProvider>()
  .get('/', {
    schema: {
      params: Type.Object({
        foo: Type.String()
      })
    },
    handler(req, rep) {
      console.log(req.params.foo);
      rep.send();
    }
  });

I'm experiencing the same problem - changed import to type-provider-typebox but it didn't help.

@sinclairzx81 any guidance here? Experiencing this upgrading from *27.8 to 28.5

@semoal Hi!
In 3.0, TypeBox was taken as a direct dependency on the provider (where as previously it was a peerDependency). If manually upgrading to TypeBox 0.28.x (or versions higher than the dependency used by the provider) this may be the cause type inference problems as TypeScript may be observing both installed versions of TypeBox (leading to type possible inference ambiguities).
There's a couple of options I can think of to resolve this.
A) Upgrade the provider to use TypeBox 0.28.x
B) Retain re-export of Type.* but revert to peerDependency,
I think option 2) might be the most flexible option for sourcing the most recent TB revisions.
@mcollina @RafaelGSS Any thoughts on this?

Hopefully, seems like the patches in progress.
Just sharing my use: I'm always write a dedicated import to TypeBox from the actual TypeBox package (@sinclair/typebox) instead of Type exported from @fastify/type-provider-typebox. It's because I want to match the import with other script files that uses TypeSystem.Format. For later releases, I also suggest that exporting the TypeSystem and other ecosystem in TypeBox is preferred.

Since I personally prefer reverting back to peerDependency approach i've opened PR #78 if we do agree to pick this alternative. If we pick other alternatives, PR can be closed.
For others looking for temporary solution, in the meantime, you can keep using 3.1.0 by version pinning your @sinclair/typebox dependency to 0.27.8 (but I also recommend also performing exact version pinning to 3.1.0 in case fix is being rolled out later for your project stability).

I'd go with option B. However, I'm not sure it will solve all the edge cases.

+1 for move it back to peerDependecies
more detail here

@mcollina okay to release 3.3.0 and close this?

I think this issue was solved in v3.2.0.

@mcollina v3.3.0 updated the ci/cd to test and support wider typebox minor version range to cover scenario like #63

yeah, there is no need for a release, the CI is already updated! Thx for your help!

I seem to be experiencing this issue again:
import { Type, TypeBoxTypeProvider } from "@fastify/type-provider-typebox";

// ...

fastify .get(
      "/:id",
      {
        schema: {
          params: Type.Object({
            _id: Type.String(),
          }),
          response: {
            200: UserRef,
            404: ErrorResponseRef,
          },
          description: "Get a user by ID",
          operationId: "getUserById",
          tags: ["Users"],
        },
        preHandler: [is_authenticated()],
      },
      async (request) => {
        const user = await users_service.getById(request.params._id); // 'request.params' is of type 'unknown'.ts(18046)
        // ...
      }
    )
    ```

@baughmann, I might be able to assist you further if you can provide more complete repo to get wider context of the general setup, my generic steps from previous experience when trying to figure out why inference doesn't get resolved correctly is to

Ensure I'm calling withTypeProvider() correctly
When I'm writing Fastify plugin (or as general rule if it's not within the same file where I would call withTypeProvider()), which is 90% of the time where I would be defining my route handlers, I would ensure to manually typed my plugin definition with FastifyPluginAsyncTypebox

So my plugin definition will generally always looks like
const plugin: FastifyPluginAsyncTypebox = async (fastify, _opts) => {
    // fastify.get() here will be correctly typed
}

Ensuring I'm currently using "CI-tested" version of TypeBox, you can see the list, I love using TypeBox but in general it's great to be aware that minor version update for this dependency can still break inference sometimes.

Recent example I went through, bumping my dependency from 0.29 -> 0.31 broke RegEx validation due to schema changes being discussed here. If you want less flaky update it might be beneficial to pin which TypeBox version to use.
I hope this somewhat helps, this approach had helped me to avoid overall flaky-ness I had before.

For people still facing this problem, this is the best solution to this problem that I could find for now:
 preHandler: (request, reply, done) => [authenticate(request, reply, done), rateLimiter(request, reply, done)]
A lot less clean than being able to just do:
preHandler: [authenticate, rateLimiter]
I found similar unresolved issues on other type providers like zod, would really like to see a better solution for this issue.

Please open new issues for new problems. This one was long solved, and adding comments here for seemingly unrelated things would not attract help. I'm locking this.


Update scodec-core to 1.11.8

Updates org.scodec:scodec-core from 1.11.7 to 1.11.8.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scodec", artifactId = "scodec-core" } ]

labels: library-update, semver-patch

Codecov Report

Merging #129 (2c4f75d) into master (812b407) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #129   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines           48        48
=========================================
  Hits            48        48

Continue to review full report at Codecov.

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


Minimum Score Not Recorded

Steps to reproduce
This is an issue discovered in my pull request (https://github.com/facebookresearch/nevergrad/pull/902). To isolate the issue, I have created a smaller test case.
import nevergrad as ng
min_score = None

def fake_training(score: int) -> float:
    global min_score
    if min_score is None or min_score > score:
        min_score = score
    return score

def test(choice_size=1000, budget=300):
    global min_score
    min_score = None
    parametrization = ng.p.Instrumentation(score=ng.p.Choice(list(range(0, choice_size))))
    optimizer = ng.optimizers.OnePlusOne(parametrization=parametrization, budget=budget, num_workers=1)
    recommendation = optimizer.minimize(fake_training)
    print((min_score, recommendation.kwargs['score']))
    return min_score==recommendation.kwargs['score']

To run the test:
for i in range(0, 100):
    if not test(1000, 300):
         break

Observed Results
(0, 0)
(1, 1)
(0, 0)
(2, 2)
(10, 10)
(9, 21)

Expected Results
Print 100 tuples and the elements in each tuple should be the same.
Investigation
The _update_archive_and_bests function in nevergrad/optimization/base.py should be responsible for incorrect behaviour.
I have checked that the minimum loss has been passed into this function but the archiving process may have some problems:

the value of mvalue can be None in if mvalue is self.current_bests[name]
Assertion file if assert mvalue.parameter.loss == candidate.loss is added before if mvalue.parameter.loss > candidate.loss
Not sure why this is the case because fake_training function is a deterministic function.

Hi @pacowong
Thanks for pointing this out. This was indeed an expected behavior which aim was to deal with noisy data. In this case however it was confusing and definitely suboptimal so we have updated the optimizers code. It should be way better indeed.

Thanks.


User cannot select cloud provider option while creating a cluster

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Click on Add cluster --> AWS.
User is not able to select any option from the Cloud Provider options seen

Expected Result:
User should be able to select the radio button
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.5-head commit id: 56bf444
Installation option (single install/HA): single

On 2.5-head latest commit id: 1599dc14 and master-head latest - commit id: 9124f6e

Click on Add cluster --> AWS.
User is able to select an option from the Cloud Provider options seen.
Select Amazon as the cloud provider.
Deploy a cluster.
User is able to deploy a cloud provider enabled cluster.


Fix for issue #191

Trivial fix for issue #191: change to output warning message to stderr.

Thanks for the PR!

No worries :)


Change Background Color dynamically

Looks like calling setBackgroundColor(Color c) doesn't affect the coloring, I can only setting color via XML!
any thoughts?

Ok, I forked the repo and added this ability myself :D, and sent a pull request just in case someone needs it one day :).


news fetch program in python

Assigned Issue Number ? { if does not exist then create one }
#007
Language Opted ?
Python
Number of files added or updated ?
2
Checklist

[x] I've read the contribution guidelines.
[x] I've referred the correct issue number.
[x] I've fill up this entire template correctly.

@Arsenic-ATG Please review this

@Arsenic-ATG Please review this

Will review it by tomorrow 👍

Will review it by tomorrow 👍

@Roshaen thanks again for your contribution 🏅

@Roshaen thanks again for your contribution 🏅


I see Unbabel comet is downloading models--xlm-roberta-large folder every time, is there any way to load it from local, if yes please share the hack.[QUESTION]

❓ Questions and Help
Before asking:

Search for similar issues.
Search the docs.

What is your question?
Code

What have you tried?
What's your environment?

OS: [e.g. iOS, Linux, Win]
Packaging [e.g. pip, conda]
Version [e.g. <IP_ADDRESS>]

I see Unbabel comet is downloading models--xlm-roberta-large folder every time, is there any way to load it from local, if yes please share the hack.

if there's a way, it will be helpful


Ensure that all HTML passes validation in redesign

Describe the bug
Some HTML does not pass validation.
To reproduce
N/A.
Expected behavior
All generated HTML passes validation.
Additional context or notes
Replaces FLOE-166.

can i work on this?

@Creatoon thanks for your interest. Our team will be addressing this as part of a larger redesign project.

Fixed in #232


[Bug] Cannot connect to server: Connection refused

I'm following this guide to build. After compile, I run irohad:
irohad --config example/config.sample --genesis_block example/genesis.block --keypair_name example/node0

But I got this following error:
[2018-08-10 02:27:43.324172160][th:1259][info] MAIN start
[2018-08-10 02:27:43.324300610][th:1259][info] MAIN config initialized
[2018-08-10 02:27:43.324721125][th:1259][info] IROHAD created
[2018-08-10 02:27:43.324782025][th:1259][info] StorageImpl:initConnection Start storage creation
[2018-08-10 02:27:43.324962358][th:1259][info] StorageImpl:initConnection block store created
terminate called after throwing an instance of 'soci::soci_error'
  what():  Cannot establish connection to the database.
could not connect to server: Connection refused
	Is the server running on host "localhost" (<IP_ADDRESS>) and accepting
	TCP/IP connections on port 5432?
could not connect to server: Cannot assign requested address
	Is the server running on host "localhost" (::1) and accepting
	TCP/IP connections on port 5432?

Aborted (core dumped)
I have no name!@68f9aa1ad5d0:/opt/iroha$

How to solve this issue?


mrtk port

the purpose of this fork to start is to port mrtk to godot and merge it back in to xr tools. i'm lazy and don't want the maintenance when it's done.
starting off will be merging in hand interactions from other xr tooling for godot, and then iteratively working on adding xr ux based on mrtk
the working theory behind this is that integrated xr ux in a mainline godot xr library would greatly enhance godot development as time goes on.

knowing how mrtk works, buttons are physics volumes that collide and animate. honestly thinking more about it, maybe merging in core hand tracking into this would be a good idea. it's kinda needed for the mrtk functionality.

upon further review it might be wise to create a new godot plugin and "surrender" it upon completion than to merge it all into mainline.


[batchnorm] Optimize batch norm for memory and speed

This patch optimizes batch normalization implementation.
Reduces the temporary memory allocation and provide speedup for the
layer execution. With this patch, resnet18 runtime improves by approx
5%.

update the tensor usage method to give the output tensor. Although the methods where already allocated output can be passed were available, they were not being used. This patch adds the corresponding support.

This patch optimizes batch norm layer and tries to share the
calculations performed in calcGradient and calcDerivative.

reuse dbeta and dgamma calculations
reduce number of required temporary variables
create all the required tensor variables with context
add support for checking if the layer is trainable or not via run
context
support average operation with the output tensor already allocated
this patch reduces as much as memory as possible without sacrificing
speed. more memory optimization is possible at the expense of speed but
has been ommitted for now.

Resolves #1591
Signed-off-by: Parichay Kapoor<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1590. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.

Rebase with #1584 and ensure that batch size 2 unittest is passing, and also check for batch size 4.


hint fallback to new action if there is no hint for edit action

#1344

@lucasmazza Could review this PR?

Done the changes. Please let me know if any changes are needed.

I'm gonna close this PR since it hasn't recently activity. Fell free to reopen case you are still planing to work on it.


Camera target, lerp camera back to target after panning

When you finish up this functionality, you should change the automatic camera to 3-5 seconds instead. 1 second is a little too soon.


Make renovatebot to run go mod tidy

See https://docs.renovatebot.com/golang/#module-tidying

This is probably not necessary, we can do it manually, should be rare.

Looks like this is really needed, 2 last updates failed because of it. Let's try enabling.


URGENT: All peripherals stopped working after updating hidehide last night.

[x] I have searched open and closed issues for duplicates
[x] I am submitting a bug report for existing functionality that does not work as intended
[x] I have read the project documentation and not found a solution to my problem there
[x] This isn't a feature request or a discussion topic

Bug description
I have multiple mouse and keyboards and none of them are working immediately following the latest hidehide update.  I'm assuming I'll have to figure out a way to fix my current issue on my own, but this HAS TO GET FIXED! Here is a reddit post from almost 2 years ago describing the exact behavior (https://www.reddit.com/r/DS4Windows/comments/u90y53/after_installing_hidhide_my_mouse_and_keyboard/).
The peripherals only work up until the windows splash screen.
I would very much like to avoid having to reinstall windows and losing all of my data because I work from home and would have a LOT of setup. I'm extremely lucky because my job is pretty chill, but this could very easily have career ending consequences for someone else. I cannot stress enough how important it is that this gets fixed.
Steps to reproduce

I was prompted multiple times through this week to update hidehide.
I finally updated last night (2/7/24).
I went through the setup wizard and selected default options.
I was prompted to restart my PC immediately, but the box said I could select "no" and restart at a later time.
I selected "no".
Probably about 15 minutes later I wrapped up the call I was on and turned off my PC.
This morning I booted up my PC to get started on work for the day and none of my peripherals worked.
Currently stuck at the windows user sign in screen.

Actual result: Mouse and keyboard does not work. I tried multiples. They work in BIOS and up to the point of the windows splash screen. My guess is this is when hidehide starts up and hides my devices.
Expected result: Mouse and keyboard should work.
Screenshots

Machine info

CPU-Architecture: Pretty sure it's x64.
Windows version: Windows 11.
Software/driver version(s): I assume it's the latest.
Any other helpful information
I believe I've provided all relevant information. If I think of anything else I will provide an update.

Duplicated of #131 please use the search.


[5.1] Fix off-by-one when initializing Data with discontiguous, underestimated Sequences

What's in this pull request?
Cherry-picks #23244 to swift-5.1-branch (resolves rdar://problem/48868256)

@swift-ci Please test macOS

@swift-ci Please smoke test linux

@swift-ci please test linux

Build failed
Swift Test Linux Platform
Git Sha - 3a6685e4745799cc062d4089d756f4e9ec6bb0fc

@itaiferber We re-branched 5.1 from master, do we still need this change? If not, can we close this PR?

@shahmishal Indeed, verified the changes are present in the re-branch, and this is no longer necessary. Thanks!


fix:

Description
Expect text doesn't work for text that's clearly visible on the screen.
Steps To Reproduce

Initialized fluttium
Created flow
Identified text I wanted to check is visible.
See error

Expected Behavior
A clear and concise description of what you expected to happen.
I expected expectVisible: Investing to result in true here because it's a button in the bottom tab navbar.

I expected expectVisible: open to result in true here because it's on the screen below the chart.

I expected expectVisible: "Your Market Value" to result in true here because it's also on the screen.

If applicable, add screenshots to help explain your problem.
Additional Context
At a high level, the nesting of widgets is  main > GoRouter with a Drawer > BottomNavBar > Scaffold.
Could you guys create a guide for nested navigators or troubleshooting?
I would gladly add code snippets but there are many more widgets nested than above if I include providers, Material Router, ResponsiveLayout, etc so not sure if it's even relevant. From my understanding the framework has no context of code and is focused on what the user can see so I feel pretty confident I shouldn't be seeing this problem.
Thanks in advance~!

I think this is related to https://github.com/wolfenrain/fluttium/issues/233 the navbar seems to ruin the Semantic lookup for Fluttium.


Documentation showing up in the wrong language

🐛 Bug Report
Sorry if this is the wrong place to put this report. This is not a bug with Jest, but with the documentation. When I view the documentation I am seeing multiple languages. Chrome will open a dialog offering to translate the text.

I have checked my language settings in Chrome

and on MacOS

All I have is English selected
To Reproduce
Steps to reproduce the behavior:
go to this page
https://jestjs.io/docs/ru/using-matchers
Expected behavior
A clear and concise description of what you expected to happen.
If you are using internationalization then it should show the correct language.
Link to repl or repo (highly encouraged)
Please provide either a repl.it demo or a minimal repository on GitHub.
Issues without a reproduction link are likely to stall.
Run npx envinfo --preset jest
Paste the results here:

Nevermind. I guess Google linked me to the russian version

The url you posted is Russian, seems to work like it should? If you want English, go to https://jestjs.io/docs/en/using-matchers or use the language selector next to the search.
There might be a bug here though - how did you end up on that url?

I got to that page from Google

Huh. I don't think there's much we can do with google indexing

Looks like Google does support multilingual
https://support.google.com/webmasters/answer/182192?hl=en
And you should usehreflang or sitemaps for language- or region-specific pages
https://support.google.com/webmasters/answer/189077

Sorry to bump an old issue, but this just happened for me as well via a Google search - https://jestjs.io/docs/uk/troubleshooting. I was searching for "speed up react testing library tests" but I think Google results are somewhat personalised so that might not be much use.
That Google indexing idea sounds like a good solution - would fix the problem at the source, and avoid penalties for duplicate content (I can see only part of the Troubleshooting has been translated, most is in English and presumably a dupe of the English version in Google's eyes).
Another possible solution - looking at my request for the page, my browser sent this header:
Accept-Language: en-GB,en;q=0.5

Whilst immedietly changing the language of the URL wouldn't be ideal (e.g. if I was trying to send a link to someone in their native language), perhaps there could be a feature to detect people who may be on the wrong language and highlight the language selector with some copy in the 'Accept-Language' language? It was described in Ukrainian on that page, which makes sense but went totally over my head :grin:
If this feature sounds like a worthwhile idea, and not too complicated to pull off, I'd be up for giving it a go with some guidance.

Definitely sounds useful @MattTennison! We're currently migrating to Docusarus 2, so website changes like this has a good timing (https://jestjs.netlify.app/). @slorber is the issue @MattTennison mentions something docusarus 2 does something about?


The skill details radio button on the client-display lacks necessary context for screen readers

Currently the skill details radio button in the client-display provides no context for screen readers (simply read as "checkbox not-checked/checkbox checked). Either an appropriately attached form label needs to be used for the radio button label (linked via for=id attribute) or the radio button checkbox input needs to include aria-label describing what the checkbox is

PR: #1339


fix: iOS support

Bug fixes, the app now works with iOS devices.
Vision camera version upgraded - 2.15.2 (testing on android required)

@ronakvijay : plz sync with stagging branch.


Proposal: consistent names for libraries and targets in CMake

Status
This has been implemented. We are waiting until 2022-02-15 to retire the legacy Bazel rules, CMake packages, and CMake rules.
Background
The Bigtable client library is called libbigtable_client.{a,so}, the CMake target is called bigtable_client.  The storage library follows the same pattern.
These names are prone to conflicts. Any other application or library provider could create a storage_client target.
When it came time to write Spanner we created an alias googleapis-c++::spanner_client, which at least is less prone to conflicts, but it is too redundant: it is unlikely that our Java googleapis will have CMake targets.  PubSub also uses the googleapis-c++:: prefix.
The common libraries (libgoogle_cloud_cpp_common.{a,so} and libgoogle_cloud_cpp_grpc_utils.{a,so}) do not have targets with the googleapis-c++:: prefix.
The proto libraries are exported with the googleapis-c++:: prefix.
Proposal

For CMake we will use a prefix (google-cloud-cpp::) consistently across all our exported libraries.
For Bazel we will recommend that applications use //:bigtable, //:pubsub, etc. as the target they link.
For CMake we will recommend google-cloud-cpp::bigtable, google-cloud-cpp::storage
For CMake packages will be imported with:find_package(google_cloud_cpp_bigtable)
find_package(google_cloud_cpp_pubsub)
find_package(google_cloud_cpp_storage)

Though rarely used, proto libraries will be imported with:find_package(google_cloud_cpp_googleapis)

T: As Soon as Possible

Export all libraries with the google-cloud-cpp:: prefix
Change all our examples and tests to use this prefix
Add aliases for the old names (storage_client, bigtable_client, etc.)
Declare these aliases as deprecated and announce that they will be removed ~in 2 * X months~ by a certain date.
Include this bug as a reference
We should explore using the DEPRECATION property to warn users.
Change the Bazel in google/cloud/*/BUILD to use the deprecation directive and reference this bug (as well as the top-level targets), see #3701
Rename the physical libraries to libgoogle_cloud_cpp_${name}.a (or .so)
Create backwards compatibility physical libraries.

T + 6 months

Change the CMake files to only export the backwards compatibility targets if a macro is set (e.g. GOOGLE_CLOUD_CPP_DEFINE_LEGACY_TARGET_NAMES)

T + 12 months

Remove the GOOGLE_CLOUD_CPP_DEFINE_LEGACY_TARGET_NAMES macro.
Change the Bazel files to mark the targets in google/cloud/*/BUILD as private
This decommissions the legacy targets.

Open Items
What do we do about physical library names?
Renaming the libraries, even when we create backwards compatibility targets, will break users that use -l${lib} options directly.  There is not much we can do for these users:

There is no way to magically link an additional library, not when the libraries are static.
There is no way to generate a warning / deprecation message, not when the libraries are static.

Work Estimates
All estimates in "ideal hours", that is, uninterrupted work.

[x] Create a test to verify the existing CMake targets remain usable (3h)
[x] Create a test to verify the existing Bazel targets remain usable (3h)
[x] Create a test to verify the existing CMake targets in external/googleapis remain usable (3h)
[x] Mark all the existing Bazel targets as deprecated (1h)
[x] Create new Bazel targets for ${library}_client_mocks named //:${library}_mocks (3h)
[x] Rename the googleapis CMake exported targets to use google-cloud-cpp:: prefix (5h)
[x] Rename the bigtable CMake exported targets to use google-cloud-cpp:: prefix (5h)
[x] Rename the pubsub CMake exported targets to use google-cloud-cpp:: prefix (5h)
[x] Rename the spanner CMake exported targets to use google-cloud-cpp:: prefix (5h)
[x] Rename the storage CMake exported targets to use google-cloud-cpp:: prefix (5h)
[x] Rename the iam CMake exported targets to use google-cloud-cpp:: prefix (5h)
[x] Rename the logging CMake exported targets to use google-cloud-cpp:: prefix (5h)
[x] Create new release (2h)
[x] Push new release to vcpkg (1h)
[x] Use new targets in quickstart programs (1h)

Good idea. I like it. Thanks. Cleaning up and simplifying the build targets is a good idea, especially before we add NN new libraries from the generator. A few other thoughts to consider:

https://github.com/googleapis/google-cloud-cpp/issues/3701 suggests cleaning up bazel targets by deprecating //google/cloud:foo_client in favor of //:foo_client. We may want to lump the build target deprecations/simplifications together. That is, only if we agree that we want to proceed with #3701 at all.
While we're cleaning up build target names, we may want to consider bazel as well so that we end up with names that are mostly consistent even between build systems. I.e., whatever pattern we choose for cmake, we may want to follow the same pattern w/ bazel target naming. (note: this is independent of whether or not we do #3701)
Regarding the spelling of the prefix, though a mouth full, it may be unsurprising for users if we pick the project name google-cloud-cpp:: as the cmake prefix.
To shorten the names of the library slightly, we could consider omitting "_client". For example, google-cloud-cpp::lib${prefix}_{storage,spanner}.*

Good idea. I like it. Thanks. Cleaning up and simplifying the build targets is a good idea, especially before we add NN new libraries from the generator. A few other thoughts to consider:

https://github.com/googleapis/google-cloud-cpp/issues/3701 suggests cleaning up bazel targets by deprecating //google/cloud:foo_client in favor of //:foo_client. We may want to lump the build target deprecations/simplifications together. That is, only if we agree that we want to proceed with #3701 at all.
While we're cleaning up build target names, we may want to consider bazel as well so that we end up with names that are mostly consistent even between build systems. I.e., whatever pattern we choose for cmake, we may want to follow the same pattern w/ bazel target naming. (note: this is independent of whether or not we do #3701)
Regarding the spelling of the prefix, though a mouth full, it may be unsurprising for users if we pick the project name google-cloud-cpp:: as the cmake prefix.
To shorten the names of the library slightly, we could consider omitting "_client". For example, google-cloud-cpp::lib${prefix}_{storage,spanner}.*

Collecting some notes, I will update the description later:

We also have bigtable::client and storage::client alialies.

The bigtable protos appear as bigtable_protos in some places, and googleapis-c++::bigtable_protos.

use google-cloud-cpp:: instead of googleapis-c++::

We need to think about the changes to pkg-config

need to rename the files for find_package(storage_client) vs. find_package(google_cloud_cpp_common)

we need to offer backwards compatibility .pc and .cmake files

if we define aliases in the ${foo}-config.cmake files we need to remember to protect them with if(NOT TARGET ...) otherwise the user cannot do find_package(${foo}) multiple times.

We need to decide if we would rename any lib${bar}.a to libgoogle_cloud_cpp_${bar}.a. For these we could:

Create a file with a undefined symbol called lib${bar}_is_deprecated_use_libgoogle_cloud_cpp_${bar}_instead
That way users saying -l${bar} explicitly (not through pkg-config or CMake) would get a link error.

We need to add tests to verify these backwards compatibility files are properly installed.  A series of quickstart-like programs in the ci/kokoro/install builds might work.

We should probably start with these tests.

Collecting some notes, I will update the description later:

We also have bigtable::client and storage::client alialies.

The bigtable protos appear as bigtable_protos in some places, and googleapis-c++::bigtable_protos.

use google-cloud-cpp:: instead of googleapis-c++::

We need to think about the changes to pkg-config

need to rename the files for find_package(storage_client) vs. find_package(google_cloud_cpp_common)

we need to offer backwards compatibility .pc and .cmake files

if we define aliases in the ${foo}-config.cmake files we need to remember to protect them with if(NOT TARGET ...) otherwise the user cannot do find_package(${foo}) multiple times.

We need to decide if we would rename any lib${bar}.a to libgoogle_cloud_cpp_${bar}.a. For these we could:

Create a file with a undefined symbol called lib${bar}_is_deprecated_use_libgoogle_cloud_cpp_${bar}_instead
That way users saying -l${bar} explicitly (not through pkg-config or CMake) would get a link error.

We need to add tests to verify these backwards compatibility files are properly installed.  A series of quickstart-like programs in the ci/kokoro/install builds might work.

We should probably start with these tests.

@devjgm I have updated the description with the work I think we should do.  It includes renaming the physical libraries (which I think is necessary), and creating backwards compatibility libraries (which I am less certain of).

@devjgm I have updated the description with the work I think we should do.  It includes renaming the physical libraries (which I think is necessary), and creating backwards compatibility libraries (which I am less certain of).

More notes:

We need to decide if the Bazel targets stay @...google_cloud_cpp//:${library}_client or become @...google_cloud_cpp//:${library}
Maintaining backwards compatibility physical libraries for the googleapis-c++::${foo}_protos (in external/googleapis) is a pain.

More notes:

We need to decide if the Bazel targets stay @...google_cloud_cpp//:${library}_client or become @...google_cloud_cpp//:${library}
Maintaining backwards compatibility physical libraries for the googleapis-c++::${foo}_protos (in external/googleapis) is a pain.

FYI the packaging doc does not work as is on current master as you now have renamed the packages to google_cloud_cpp_bigtable etc. instead of google_cloud_bigtable

@ecourreges-orange thank you again for pointing out the problems in the documentation, as you probably noticed we merged a PR to fix the problem earlier today.  Let us know if you have any other problems.

This is done as of #8413


BUG: rm: refusing to remove '.' or '..' directory: skipping '/run/scalpel/.

Hey, thank you very much for providing a way to customize configuration files that require some sops-managed passwords!
This is exactly what I've been looking for! :heart:
Though, I am having some issues and am relatively new to NixOS so sorry for not being able to provide a minimal example.

When I execute the container there is no issue
But when I call it via my flake configuration, I get the following issues:

rm: refusing to remove '.' or '..' directory: skipping '/run/scalpel/.`
rm: refusing to remove '.' or '..' directory: skipping '/run/scalpel/..`
Activation script snippet 'scalpelCreateStore' failed (1)

Looking at the code, the issue seems to come from
https://github.com/polygon/scalpel/blob/16c2103d613bb1c7adc6dbf2a17c2980ce08567f/modules/scalpel/default.nix#L113-L124
Where the shell is safeguarding recursively deleting . and ..
I've cloned this repository and changed it to:
system.activationScripts.scalpelCreateStore = {
       text = ''
         echo "[scalpel] Ensuring existance of ${cfg.secretsDir}"
         mkdir -p ${cfg.secretsDir}
         grep -q "${cfg.secretsDir} ramfs" /proc/mounts || mount -t ramfs none "${cfg.secretsDir}" -o nodev,nosuid,mode=0751

         echo "[scalpel] Clearing old secrets from ${cfg.secretsDir}"
         find . -name . -o -prune -exec rm -rf -- {} +
       '';
       deps = [ "specialfs" ];
     };

With inspiration from: https://unix.stackexchange.com/a/77313
Which allowed me to run the flake without any issues. :)
I would be happy to open a PR if you think this change would fix it.

I don't use scalpel, but don't use this as is, it'll nuke your system!

to be clear, I think this is only the case for the above patch linked by GitHub discussed here: https://github.com/ndarwincorn/scalpel/commit/6ab08ad635fd25be8cb9113d7a4971861f66ed54#commitcomment-95094918

Sorry, I must have missed this when it was posted. I'll have a look at it. Thanks for the contribution.

Wow, yeah that is a pretty bad mistake I made :cold_sweat:
Sorry for that!


[pick](Row store) pick #38236

Proposed changes
pick #38236

run buildall

run buildall

run buildall

run compile

run buildall


Search on formatter column

Hi!
Is it possible to search on a column using a formatter.
Currently, searching on a datagrid that contains a search-enabled formatted column throws an error.
Here it is :
TypeError: b.converter.to(a[b.id]).search is not a function. (In 'b.converter.to(a[b.id]).search(c)', 'b.converter.to(a[b.id]).search' is undefined)
cjquery.bootgrid.min.js:5:2113
wherejquery.bootgrid.min.js:5:23092
njquery.bootgrid.min.js:5:2973
Bjquery.bootgrid.min.js:5:10231
(anonymous function)jquery.bootgrid.min.js:5:10090

There a a few ways how this could be achieved :

Consider the column as a string and search it
Remove the possible HTML tags from the column and search the remaining text
Pass the content of the column to a converter and search the results

I already tried the third option, but it throws the same error.
Thoughts?

I resolve the same error by add data-type="numeric" to column has an interger data

There are a number of pull requests that already fix this so not going to add another one. For a quick fix just replace the following code in jquery.bootgrid.js
column.converter.to(row[column.id]).search(searchPattern) > -1`

with
searchPattern.test(column.converter.to(row[column.id]))


Remove event framework

This will greatly simplify code base and make it easier to fix bugs.

RIP events framework!


⚠ Slack has degraded performance

In 6db774f, Slack (https://status.slack.com/api/v2.0.0/current) experienced degraded performance:

HTTP code: 200
Response time: 108 ms

Resolved: Slack performance has improved in b666b5f.


Account for file-driven entrypoints exposed via library

Currently, compiling bevy-pbr-rust when imported as a library fails, as its entrypoints are tagged with a permutation file statement that ends up resolving its path relative to cargo's internal crate cache.
This is likely best accounted for by making the file statement fail silently (in the absence of proc-macro warning functionality), thus causing no entrypoints to be generated when imported in a library context.

Done, plus the addition of an env(...) statement to override permutation files for cases where a downstream library needs to generate entrypoints for library crates.


pigpiod on different port

I am running pigpiod on a different port to the standard 8888, using 'sudo pigpiod -p 8887' I am wanting to update my lights using pigs, but cant seem to work out how to get pigs to use the new port?
Thanks

pi@octopi:~ $ sudo pigpiod -p 8887
pi@octopi:~ $ sudo netstat -tulpn | grep :8887
tcp6       0      0 :::8887                 :::*                    LISTEN      1816/pigpiod

when I run
pigs hwver
or
sudo pigs hwver
Terminal just hangs...
When I do -
pi@octopi:~ $ sudo pigpiod
pi@octopi:~ $ sudo netstat -tulpn | grep :8888
tcp6       0      0 :::8888                 :::*                    LISTEN      1946/pigpiod

pi@octopi:~ $ pigs hwver
10494163

pi@octopi:~ $ cat /dev/pigerr&
[1] 1998
pi@octopi:~ $ echo "hwver" > /dev/pigpio

It seems that pigs just can't communicate with pigpiod when its not running on the standard port?
Thanks

Have you told pigs the changed port number?
PIGPIO_PORT=8887 pigs hwver

Hi Joan, is there a way i can change the default port for pigspiod? i want to run it on startup always and on a different port.

pigpiod accepts the following configuration options
http://abyz.me.uk/rpi/pigpio/pigpiod.html

Hi,
Thanks for quick reply and sorry for continuing on a closed thread.
I have gone through that documentation. I want to know how do i permanently set a different port for the daemon (change it from the default 8888 to say.. 8000). Running pigpiod -p 8000 will only keep that port until i reboot right? Sorry if it is too obvious, i might be missing something.

Enable the systemd service if one already exists.
sudo systemctl enable pigpiod
Edit the service file to include the port option.
Then do:
'sudo systemctl daemon-reload'
Followed by:
`sudo systemctl start pigpiod'
Or just reboot.
If the pigpiod.service file doesn't exist in your /etc/systemd/service directory, copy the one in the repo under /util.  Modify accordingly.

Hi,
I'm sorry to continue to a closed threat. I have the exact same problem as @sawansaurabh.
Unfortunately, I do not have a directory that is called  "/etc/systemd/service". I can find a pigpiod.service file at "/lib/systemd/system" or a public.conf file at "/etc/systemd/system/pigpiod.service.d" but both are not editable.
It would be really great if either @sawansaurabh could explain your solution if you fixed the problem or if @guymcswain could specify how I am able to edit the service file to include the port option.
Thanks a lot in advance!

I do not have a directory that is called "/etc/systemd/service"

The above is a typo.  It should be /etc/systemd/system.  There should be a file there named pigpiod.service.
Example showing a system that does not contain the above referenced file:
pi@blueberry:~ $ systemctl status pigpiod
Unit pigpiod.service could not be found.

In this case, you will need to copy the file from the /util directory of the repo.  Edit this line ExecStart=/usr/bin/pigpiod adding the -p xxxx option for the desired port number.
Resulting file in /etc/systemd/system/pigpiod.service should look like this:
ExecStart=/usr/bin/pigpiod[Unit]
Description=Pigpio daemon

[Service]
Type=forking
PIDFile=pigpio.pid
ExecStart=/usr/bin/pigpiod -p xxxx

[Install]
WantedBy=multi-user.target

Thanks for the quick response!
Unfortunately it looks a bit different at my Raspberry Pi.
My pigpiod.service file seems to be stored at /lib/systemd/system:
pi@raspberrypi:~ $ systemctl status pigpiod pigpiod.service - Daemon required to control GPIO pins via pigpio    Loaded: loaded (/lib/systemd/system/pigpiod.service; disabled; vendor preset:   Drop-In: /etc/systemd/system/pigpiod.service.d            \u2514\u2500public.conf    Active: inactive (dead) lines 1-5/5 (END)

Thanks for the fast response!
Unfortunately it looks differnent at my Raspberry Pi.
My pigpiod.service file seems to be stored at /lib/systemd/system
pi@raspberrypi:~ $ systemctl status pigpiod
pigpiod.service - Daemon required to control GPIO pins via pigpio'
Loaded: loaded (/lib/systemd/system/pigpiod.service; disabled; vendor preset:
Drop-In: /etc/systemd/system/pigpiod.service.d
public.conf
Active: inactive (dead)
lines 1-5/5 (END)
The /lib/systemd/system/system.config looks as the following:
[Unit]
Description=Daemon required to control GPIO pins via pigpio
[Service]
ExecStart=/usr/bin/pigpiod -l
ExecStop=/bin/systemctl kill pigpiod
Type=forking
[Install]
WantedBy=multi-user.target
and if I'm trying to change it i get the following error:

English: Document could not be saved. No rights.
Same error if I'm trying to create a file at **/etc/**systemd/system or change the public.config file at **/etc/**systemd/system/pigpiod.service.d

Yes, systemd now appears to be located in other directories.  Nevertheless, wherever it is located, the same edit to the line beginning with ExecStart applies - just append -p (your port number).  And yes, you need to use 'sudo' because these are root owned directories.

Thanks a lot! The hint with 'sudo' was very helpfull.
I am now able to start the pigpiod on port 8889 at startup. The systemctl status pigpiod.service command also indicates that the daemon is running(see screenshot).
BUT: when i try to test pigpiod by command pigs t or pigs hwver i get the error "socket connection failed". Which I assume needs to work to control the GPIO Pins remotely.
I tried PIGPIO_PORT=8889, but i doesn't help.

This error does not appear if i start pigpiod via sudo pigpiod --> on socket 8888.

I am really sorry for all the question and appreciate your help so far!

And how am I able to get the export PIGPIO_PORT=8889 command done automatically at reboot?

You can set environment variables within the pigpiod.service unit.  There is plenty of information on systemd available on the internet.


Add annotations to cluster app values schema for VCD

Towards https://github.com/giantswarm/roadmap/issues/1733

Done


Fix handling of chunked encoding end marker

Closes #27

Not sure if it is best solution tho... I feel like solving it on the I/O loop layer, where we fire the callbacks isn't either.

I think it's OK for now. We want some better reusable HTTP primitives that we can reuse later


Rootless docker installation issue on Ubuntu18 (after updates done on 21st March)

Hi, after some updates that were done in rootless docker on 21st March, I'm seeing an issue installing rootless docker on Ubuntu1-8.
We didn't see this error back in February 2022, and on rootless docker page nothing is mentioned about this issue. We did not see this message earlier during February on the same Ubuntu-18 vm that we are using now
+ PATH=/home/pipelinesRootless/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin /home/pipelinesRootless/bin/dockerd-rootless-setuptool.sh install
[INFO] systemd not detected, dockerd-rootless.sh needs to be started manually:
PATH=/home/pipelinesRootless/bin:/sbin:/usr/sbin:$PATH dockerd-rootless.sh
Full error logs:
root@ubuntu-bionic:/home/vagrant# sudo -E -u tempRootlessUser ./script.sh
# Installing stable version 20.10.12
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 60.4M  100 60.4M    0     0  6354k      0  0:00:09  0:00:09 --:--:-- 6783k
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 18.0M  100 18.0M    0     0  6157k      0  0:00:03  0:00:03 --:--:-- 6157k
+ PATH=/home/tempRootlessUser/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin /home/tempRootlessUser/bin/dockerd-rootless-setuptool.sh install
[INFO] systemd not detected, dockerd-rootless.sh needs to be started manually:
PATH=/home/tempRootlessUser/bin:/sbin:/usr/sbin:$PATH dockerd-rootless.sh
[INFO] Creating CLI context "rootless"
Successfully created context "rootless"
[INFO] Make sure the following environment variables are set (or add them to ~/.bashrc):
# WARNING: systemd not found. You have to remove XDG_RUNTIME_DIR manually on every logout.
export XDG_RUNTIME_DIR=/home/tempRootlessUser/.docker/run
export PATH=/home/tempRootlessUser/bin:$PATH
export DOCKER_HOST=unix:///home/tempRootlessUser/.docker/run/docker.sock
Can someone please take a look and let me know what we're missing here?

The INFO log comes from https://github.com/moby/moby/blob/master/contrib/dockerd-rootless-setuptool.sh#L349
Which is called if  the $SYSTEMD env var is not set; https://github.com/moby/moby/blob/master/contrib/dockerd-rootless-setuptool.sh#L381
Which is detected through these lines; https://github.com/docker/docker-install/blob/master/rootless-install.sh#L62

Thank you @thaJeztah for a reply, and pointing out where specific logs are being printed at.
I'll check the code and see why the setup is failing now, compared to back in Feb with the same Ubuntu-18 VM

@thaJeztah - It took me sometime to circle back to this, and this is my observation:
My changes still work good for latest Ubuntu18 : VERSION="18.04.6 LTS (Bionic Beaver)"
But, I still see issue related to systemd not detected for Ubuntu18: VERSION="18.04.5 LTS (Bionic Beaver)"

No immediate suggestions, but perhaps @AkihiroSuda has some (he's done a lot more with rootless installations, so perhaps some of these rings a bell)


Please add banner ads - Unity also launched banner ads in  Mediation

Unity own banner ads are useless always no fill. Please add mediation banner ads so we can use other networks to show banner ads in the apps

Unity Mediation doesn't support banner ads yet

Unity add Banner ads in new SDK

Banner Ads support is added in unity_mediation: 0.1.0


Add teacher pageview column to Research Matters export

Who is this PR for?
Research Matters.
What problem does this PR fix?
Adds missing column with # of pageviews in Mixpanel per teacher.

This PR should be good to go! I added a test case describing the pageview_count column in the teacher file, and the specs are passing. ✅
The only issue: When I try to run it locally, I either get an error message from Mixpanel ("error completing export request"), or it just hangs. I don't see anything that would explain this on the Mixpanel Status page (https://status.mixpanel.com/, "Data Export API: Operational").
Might just ship this PR and see if the Mixpanel query works in prod. Or wait a couple of hours, try again, and see if the Data Export API is more responsive.

The Mixpanel Data Export API calls are working now; no more error messages. Added more console output during the download phase to give developers more feedback, so they can see the difference between "downloading data..." and "hanging there..."


Feat/support toml

This PR adds two things.
1. Frontmatter format updates
Can now specify { frontmatterFormat: 'toml' | 'yaml' | 'json' } and {frontmatterDelimter: string | [string, string] }.
This allows the user to have more conrtol of how their frontmatter is parsed.
2. Adds yaml and toml format support for a collection
In a collection format can now be yaml or toml.
Video Demo: https://www.loom.com/share/aa45a2fd19704a14a273f02d95d3c621
Tina cloud updates
We will need to have access to the config/collection when we call parseFile here: https://github.com/tinacms/tina-cloud/blob/main/js/content-api/src/database/store/github/index.ts#L150
We will also need to have access config/collection when we call stringily file here: https://github.com/tinacms/tina-cloud/blob/d5ca6ab39f06911693477fba934b31410cee0db5/js/content-api/src/database/store/github/index.ts#L209

@logan-anderson we should verify, but I think most projects (maybe all active at this point) are using the dynamodb store, so I don't think that the github store should be an issue for this

Awesome! I think markdownFrontmatterFormat as a name is fine 🤷

Just recapping a few notes from chatting through this in happy hour:

maybe changing the name from markdownFrontmatterFormat to frontmatterFormat
sounds like we may need an optional config for frontmatterDelimiter (Hugo uses +++ for TOML)

Just recapping a few notes from chatting through this in happy hour:

maybe changing the name from markdownFrontmatterFormat to frontmatterFormat
sounds like we may need an optional config for frontmatterDelimiter (Hugo uses +++ for TOML)

This have been added.


Long delay when opening a serial port (around 30 seconds)

I am seeing a long delay when doing a .Open() on a serial port stream.
Delays of 15 to 30+ seconds are common.
A run of the VS 2015 performance profile shows that the delay appears to be in:
Ports.Native.Windows.CommModemStatus.ClearCommBreak().
Is this expected?
Note that this a USB virtual COM port.

Hello Terry,
I've not observed this behavior myself. Can you describe a little more of your setup? What driver are you using and what is the actual hardware? Have tried different drivers, like FTDI or Prolific?
I expected the method to just internally clear flags and not be more than the order of milliseconds. Do you use hardware flow control at all?
Sent from my Windows Phone

From: Terry<EMAIL_ADDRESS>Sent: 27/12/2016 15:04
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS>Subject: [jcurl/SerialPortStream] Long delay when opening a serial port (around 30 seconds) (#12)
I am seeing a long delay when doing a .Open() on a serial port stream.
Delays of 15 to 30+ seconds are common.
A run of the VS 2015 performance profile shows that the delay appears to be in:
Ports.Native.Windows.CommModemStatus.ClearCommBreak().
Is this expected?
Note that this a USB virtual COM port.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/jcurl/SerialPortStream/issues/12, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABfbf3ZxNbGc27exd0xOfTygjO902qj9ks5rMRrJgaJpZM4LWSrA.

Jason,
Thank you for the quick response.
The device I am using is a "FlexControl" from FlexRadio Systems.  It came with a a VSP driver, which is what I am using.  (Running at 9600, 8,None,1) on COM99.  No flow control is turned on.  Note that once the port is opened it works perfectly.
This is something I can live with (and potential users of my utility aren't likely going to want to change drivers).  I just wanted to check that this wasn't expected behavior.
I will put this on the back burner for now and may try to get the device working with alternate drivers in the future.  Once I do, I will report back my findings.
Happy New Year
Terry

Hello, I'm attaching a test binary. I've removed the code that calls this method on open and would like your confirmation that it works for you as expected.
SerialPortStream-2.0.3-Debug-0a840dc.zip

Jason,
I will try this out this afternoon and report back.
Terry
On Thu, Dec 29, 2016 at 7:15 AM, Jason Curl<EMAIL_ADDRESS>wrote:

Hello, I'm attaching a test binary. I've removed the code that calls this
method on open and would like your confirmation that it works for you as
expected.
SerialPortStream-2.0.3-Debug-0a840dc.zip
https://github.com/jcurl/SerialPortStream/files/677131/SerialPortStream-2.0.3-Debug-0a840dc.zip
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/jcurl/SerialPortStream/issues/12#issuecomment-269628799,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABiY_ZcR-TsofYcNlpIK61yvybEV28SCks5rM7KPgaJpZM4LWSrA
.

Jason,
I managed to fit this in this morning.  I can report that it works much better - the Open() call now takes on the order of 19ms rather than 30000ms - much improved.

Terry


Discrepancy in behavior of DoFn.process() when yield is combined with return statement, or vice versa

What happened?
Apache Beam SDK Version: 2.40.0
SDK Language: Python
Runner: All (DirectRunner, DataflowRunner, PortableRunner etc.)
TL;DR: If a DoFn.process has yield <some value> as well as return <some iterable> statements, then it does not emit element for statement return <some iterable>.
The Apache Beam, Programming Guide, <IP_ADDRESS>. Creating a DoFn states that:

Your process method should accept an argument element, which is the input element, and return an iterable with its output values. You can accomplish this by emitting individual elements with yield statements. You can also use a return statement with an iterable, like a list or a generator.

That statement is correct when a DoFn.process:

either uses yield <some value> only
or, uses return <some iterable>  only

to emit an element, within the definition.
If the combination of yield and return are used in the DoFn.process() definition, then it does not comply with the statement made in the document.
See this example pipeline:
# dofn_issue.py

import argparse
import logging

import apache_beam as beam
from apache_beam.options.pipeline_options import PipelineOptions

logger = logging.getLogger(__name__)
logger.setLevel("INFO")

class Pipeline:
    def run(self, args=None):
        parser = argparse.ArgumentParser()
        _, extra_args = parser.parse_known_args(args)
        pipeline_options = PipelineOptions(extra_args, save_main_session=True)
        with beam.Pipeline(options=pipeline_options) as pipeline:
            data_to_process = pipeline | beam.Create(
                [
                    {"key": 1},
                    {"key": 2},
                    {"key": None},
                    {"key": 4},
                ],
            )
            data_to_process | beam.ParDo(SetDefaultValFn1()) | "1" >> beam.ParDo(LogElementsFn(), 1)
            data_to_process | beam.ParDo(SetDefaultValFn2()) | "2" >> beam.ParDo(LogElementsFn(), 2)
            data_to_process | beam.ParDo(SetDefaultValFn3()) | "3" >> beam.ParDo(LogElementsFn(), 3)
            data_to_process | beam.ParDo(SetDefaultValFn4()) | "4" >> beam.ParDo(LogElementsFn(), 4)

# NOT EXPECTED - `return` statement doesn't emit data
class SetDefaultValFn1(beam.DoFn):
    def process(self, element):
        data = element.get("key")
        if not data:
            return [{"key": -9999}]
        yield element

# NOT EXPECTED - `yield` statement only emits data
class SetDefaultValFn2(beam.DoFn):
    def process(self, element):
        data = element.get("key")
        if not data:
            yield {"key": -9999}
            return
        return [element]

# EXPECTED
class SetDefaultValFn3(beam.DoFn):
    def process(self, element):
        data = element.get("key")
        if not data:
            return [{"key": -9999}]
        return [element]

# EXPECTED
class SetDefaultValFn4(beam.DoFn):
    def process(self, element):
        data = element.get("key")
        if not data:
            yield {"key": -9999}
            return
        yield element

class LogElementsFn(beam.DoFn):
    def process(self, element, where):
        logger.info(f"From {where} found {element}")
        yield element

if __name__ == "__main__":
    pipeline = Pipeline()
    pipeline.run()

Actual Output:
$ python dofn_issue.py \
--runner DirectRunner

INFO:__main__:From 1 found {'key': 1}
INFO:__main__:From 1 found {'key': 2}
# NOTE: SetDefaultValFn1 silently skipped element {'key': -9999}
INFO:__main__:From 1 found {'key': 4}
# NOTE: SetDefaultValFn2 silently skipped element {'key': 1}
# NOTE: SetDefaultValFn2 silently skipped element {'key': 2}
INFO:__main__:From 2 found {'key': -9999}
# NOTE: SetDefaultValFn2 silently skipped element {'key': 4}
INFO:__main__:From 3 found {'key': 1}
INFO:__main__:From 3 found {'key': 2}
INFO:__main__:From 3 found {'key': -9999}
INFO:__main__:From 3 found {'key': 4}
INFO:__main__:From 4 found {'key': 1}
INFO:__main__:From 4 found {'key': 2}
INFO:__main__:From 4 found {'key': -9999}
INFO:__main__:From 4 found {'key': 4}

PS: Output is manually ordered for ease of interpretation.

Expected Output:
$ python dofn_issue.py \
--runner DirectRunner

INFO:__main__:From 1 found {'key': 1}
INFO:__main__:From 1 found {'key': 2}
INFO:__main__:From 1 found {'key': -9999}
INFO:__main__:From 1 found {'key': 4}
INFO:__main__:From 2 found {'key': 1}
INFO:__main__:From 2 found {'key': 2}
INFO:__main__:From 2 found {'key': -9999}
INFO:__main__:From 2 found {'key': 4}
INFO:__main__:From 3 found {'key': 1}
INFO:__main__:From 3 found {'key': 2}
INFO:__main__:From 3 found {'key': -9999}
INFO:__main__:From 3 found {'key': 4}
INFO:__main__:From 4 found {'key': 1}
INFO:__main__:From 4 found {'key': 2}
INFO:__main__:From 4 found {'key': -9999}
INFO:__main__:From 4 found {'key': 4}

PS: Output is manually ordered for ease of interpretation.

If the analogy of DoFn.process is similar to a Python generator, then on running a similar code (made purely with generator):
# generator_eg.py

import logging

logging.basicConfig(level=logging.DEBUG)
logger = logging.getLogger(__name__)

class SetDefaultVal1:
    @staticmethod
    def process(element):
        data = element.get("key")
        if not data:
            return [{"key": -9999}]
        yield element

class SetDefaultVal2:
    @staticmethod
    def process(element):
        data = element.get("key")
        if not data:
            yield {"key": -9999}
            return
        return [element]

class SetDefaultVal3:
    @staticmethod
    def process(element):
        data = element.get("key")
        if not data:
            return [{"key": -9999}]
        return [element]

class SetDefaultVal4:
    @staticmethod
    def process(element):
        data = element.get("key")
        if not data:
            yield {"key": -9999}
            return
        yield element

def run_and_log(Generator, element, where):
    generator = Generator.process(element)
    try:
        processed_element = next(generator)
        logger.info(f"From {where} found {processed_element}")
    except Exception:
        pass

if __name__ == "__main__":
    for element in [
        {"key": 1},
        {"key": 2},
        {"key": None},
        {"key": 4},
    ]:
        run_and_log(SetDefaultVal1, element, 1)
        run_and_log(SetDefaultVal2, element, 2)
        run_and_log(SetDefaultVal3, element, 3)
        run_and_log(SetDefaultVal4, element, 4)

Outputs:
$ python generator_eg.py
INFO:__main__:From 1 found {'key': 1}
INFO:__main__:From 1 found {'key': 2}
INFO:__main__:From 1 found {'key': 4}
INFO:__main__:From 2 found {'key': -9999}
INFO:__main__:From 4 found {'key': 1}
INFO:__main__:From 4 found {'key': 2}
INFO:__main__:From 4 found {'key': -9999}
INFO:__main__:From 4 found {'key': 4}

# PS: Output is manually ordered for ease of interpretation.

If we compare behavior of DoFn.process with Python generator, for all 4 cases:
Case 4.

Output is expected for dofn_issue.py & generator_eg.py.
Output is same for dofn_issue.py & generator_eg.py.

Case 3.

Output is expected for dofn_issue.py & generator_eg.py.
Output is NOT  same for dofn_issue.py & generator_eg.py.

Case 2.

a) Output is NOT expected for dofn_issue.py. b)  Output is expected for generator_eg.py.
Output is same for dofn_issue.py & generator_eg.py.

Case 1.

a) Output is NOT expected for dofn_issue.py. b)  Output is expected for generator_eg.py.
Output is same for dofn_issue.py & generator_eg.py.

Discrepancy
If dofn_issue.py for case 3 emits on statement return <some iterable> (which is NOT the case with generator_eg.py), then why it does NOT emit for case 1 and case2's statement return <some iterable>.
Issue Priority
Priority: 1
Issue Component
Component: sdk-py-core

Thanks for the detailed report @toransahu
In the short-term we should at least update the docs to indicate that mixing return and yield leads to undefined behavior. (optional) medium-term: detect this situation and fail at construction time. Long-term: Enable mixing yield and return.
CC: @tvalentyn @robertwb

I think P1 is appropriate here since this could lead to data loss. I'm not sure updating docs is enough to drop to P2, since users could easily miss that.

@TheNeuralBit Thanks for promptly triaging the issue.

Has anything been done to mitigate this? It seems quite severe!

This is in be backlog awaiting available hands; doc update in flight. I think we can recommend yield for elements and yield from for iterators and not use return altogether, we should check that the issue wouldn't be reproducible in that case.

.take issue

Taking a closer look, the unexpected behavior is not caused by Beam but rather how Python interprets a function with yield and return statements mixed together. See: https://stackoverflow.com/questions/16780002/return-in-generator-together-with-yield which summarizes it.
For example:
def foo(c):
  if (c):
    yield "foo"
  else:
    return "bar

list(foo(True))
Out: ['foo']

list(foo(False))
Out: []

next(foo(False)) raises StopIteration: bar
Seems that such mix-and-match was an error in Python 2.

@liferoad Thanks for the PR. @tvalentyn Thanks for PR review & sharing the root cause.

.close-issue


Improve in contact us section

Is your feature request related to a problem? Please describe.
contact us section is currently not more appealing
Describe the solution you'd like.
By making some changes in white blocks in contact us section
Describe alternatives you've considered.
adding some effects to make it look good
Add any other context or screenshots about the feature request here.
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

Sure @gaur15

Hey can you please assign this issue to me ?


resolve Solr pod startup error: Failed to create collection 'dataone_index' due to: collection already exists: dataone_index

Not critical, since the pod automatically restarts, but should be cleaned up at some point to avoid confusion:
Looks like a race condition where one of the solr pods is trying to create the dataone_index collection when another one has already created it:
kc describe pod/metacatbrooke-solr-0
[...]
  Warning  FailedPostStartHook     48s    kubelet                  Exec lifecycle hook ([/bin/bash -c /solrconfig/config-solr.sh]) for Container "solr" in Pod "metacatbrooke-solr-0_brooke(cd1c3c64-74b6-4bf6-8b74-c9e301e93a36)" failed - error: command '/bin/bash -c /solrconfig/config-solr.sh' exited with 1: solr 19:40:01.60 INFO  ==> Waiting for Zookeeper to be up

ERROR: Failed to create collection 'dataone_index' due to: collection already exists: dataone_index

, message: "Uploading /bitnami/solr/server/solr/configsets/dataone_index/conf for config
dataone_index to ZooKeeper at metacatbrooke-zookeeper:2181/solr\nRe-using existing configuration
directory dataone_index\n\x1b[38;5;6msolr \x1b[38;5;5m19:40:01.60 \x1b[0m\x1b[38;5;2mINFO \x1b[0m
==> Waiting for Zookeeper to be up\n\nERROR: Failed to create collection 'dataone_index' due to:
collection already exists: dataone_index\n\n"

  Normal  Killing  48s                  kubelet  FailedPostStartHook

Ah yes, good catch. I meant to come back to that when I was working on the schema creation stuff. The issue is that the n-shards startup at the same time but only the first needs to create the shared collection. They probably all start to create it at roughly the same time, but only one should. In theory, line 55 of solr-config.sh should catch this:
if ! solr_collection_exists "$SOLR_COLLECTION"; then

but it does not seem to. The other issue is that this only needs to be done on a new PVC where SOLR is starting for the first time, and we need to figure out how to do schema upgrades with exsiting index data in place on the PVC. When I was working on this, I also considered doing some of it in the entrypoint.sh script, which is why we override that from the bitnami default, but IIRC I got rid of all of my changes there and we probably shouldn't override it any longer (so we get the proper bitnami script to run). I looked for a long time for a way to configure the bitnami chart to create our collection rather than their default, but never found a way to configure that through bitnami solr chart values.


Add GuildDeleteEvent.wasRemoved field

Description
As title says, from docs: If the unavailable field is not set, the user was removed from the guild.
Connected issues & other potential problems
None
Type of change
Please delete options that are not relevant.

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

Checklist:

[x] Ran dart analyze or make analyze and fixed all issues
[x] Ran dart format --set-exit-if-changed -l 160 ./lib or make format and fixed all issues
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

This is already supported by checking isUnavailable == false. If you think this is confusing, feel free to open a PR to nyxx_extensions that adds this alias.


Vue 3 Compatibility

This patch enables compatibility with Vue 3.
Aside from a couple deprecations that were fixed, I changed the build tool to rollup in stead of webpack.
Tests will likely need to be updated.

Thank you so much for this.

Thanks for your nice work! Maybe dev on full-clean branch then release a major version would be better?

And can this PR be released as an alpha version? Maybe the temp version that supported Vue.js 3.0 be helpful to users

@PeachScript  when merge ? and can I use nuxt width used composition api ?

@PeachScript when merge ? and can I use nuxt width used composition api ?

After all test cases updated. But we can first release a alpha version if @nVitius confirm this PR can be released

@PeachScript Sorry for the late reply from me. If you make a new branch on the main repo (I called mine next. I've seen that in a lot of other vue libs working on v3 support), I can change the PR to go there and we can merge in and make the alpha release. I'll also add a commit to update the package.json with a -beta version so we can publish to npm.

@nVitius thanks for your reply ❤  I've already create the next branch, but I hope merge it after we completed code review & test cases paased, so I've published an pre-alpha version<EMAIL_ADDRESS>base on the PR branch, as the temporary way for Vue.js 3.0 projects.
@printscreen @productfrontenddeveloper it would be better if you could test it with your projects and feedback :D

@nVitius thanks for your reply ❤ I've already create the next branch, but I hope merge it after we completed code review & test cases paased, so I've published an pre-alpha version<EMAIL_ADDRESS>base on the PR branch, as the temporary way for Vue.js 3.0 projects.
@printscreen @productfrontenddeveloper it would be better if you could test it with your projects and feedback :D

iam nuxt 2, vue 2 with nuxt compotion api. I can say that nuxt 3 will be out soon then. then i can try :D

Is there is any news of when a package will be ready for vue 3?

Currently, the spinner setting for the alpha version is very wired. You have to assign it like the following:
<infinite-loading :identifier="identifier" @infinite="load" :spinner="2">
  <template v-slot:no-more>no more</template>
  <template v-slot:no-results>no results</template>
</infinite-loading>

It's using an index to represent various spinner listed in the doc.

@phantomlsh Thanks for the report! I just pushed a commit that should fix that issue.
Will you test it out when you have the chance? You can install it like this:
npm i --save 'github:nvitius/vue-infinite-loading#next'

@nVitius Thanks for your work but i tested with your fork and it doesn't work.

There is another bug with spinner. If you use custom tag with slot="spinner" or <template #spinner> it doesn't hide the spinner after loading. It does for default spinners, but not from custom.

I forgot to re-run the build before committing. I pushed another commit with the updated dist files.
@noeGnh Could you provide a small reproduction for the custom spinner issue? We are using v-show on the parent div of the spinner slot. I don't immediately see why it wouldn't work.

Hi @nVitius,
here is a reproduction of the issue: https://codesandbox.io/s/vue-infinite-loading-issue-pi6cj

@noeGnh Thanks for setting that up.
I worked a bit on this over the weekend. It looks like Vue 3 has an issue where a v-bind:style that is undefined will overwrite the style on the element and set it to empty. I've opened a PR on the Vue repo to try and address it. In the meantime, I've fixed it so that slotStyles compute to an empty object instead of undefined.

@nVitius Thanks for your work !

@PeachScript Can you publish the new build to npm?
I've had the opportunity to work extensively with the Composition API over the past 6 months or so. I want to take some time soon and refactor the components in here to use it, as well as update the tests and such so we can get this PR merged in.

Is there any update on this issue?

Any update on this?

Currently, the spinner setting for the alpha version is very wired. You have to assign it like the following:
<infinite-loading :identifier="identifier" @infinite="load" :spinner="2">
  <template v-slot:no-more>no more</template>
  <template v-slot:no-results>no results</template>
</infinite-loading>

It's using an index to represent various spinner listed in the doc.
A brief inspection into the codes in src shows that it is due to the processing of spinnerView variable from the props.

I cannot have empty(no value) in the slots. It is possible with the previous version.

@shashank261 Thanks for the report. I just pushed up a commit that should fix that issue. You can try it out by installing from my fork:
npm i --save 'github:nvitius/vue-infinite-loading#next'

Hi, can someone explain what has to happen for this to make it into the main release? We're waiting on this over on https://github.com/antoine92190/vue-advanced-chat
Thanks!

@PeachScript any progress ?

@nVitius thanks for your reply ❤ I've already create the next branch, but I hope merge it after we completed code review & test cases paased, so I've published an pre-alpha version<EMAIL_ADDRESS>base on the PR branch, as the temporary way for Vue.js 3.0 projects.
@printscreen @productfrontenddeveloper it would be better if you could test it with your projects and feedback :D

@PeachScript We have been using 3.0.0-alpha.0-0 in production with no problem. Just following up from your previous comment.

npm i --save 'github:nvitius/vue-infinite-loading#next'
vue3 testted good workind

 node --version
v16.13.2
  npm --version
8.1.2

Hangs on install during "reify:nan" in "reify:audit" after these lines
npm http fetch GET 200 https://registry.npmjs.org/vue-loader 246ms (cache hit)
npm timing metavuln:packument:vue-loader Completed in 255ms
npm timing metavuln:load:security-advisory:vue-loader:Pp1IW5wVzYexdOySlO/aAbqI2U/7il4gIjSOUDymIHC8cUtXeZL9vUdcRSFS5haoxlwjfhRs5hiV4iRUz1rJCg== Completed in 2ms
npm timing metavuln:calculate:security-advisory:vue-loader:Pp1IW5wVzYexdOySlO/aAbqI2U/7il4gIjSOUDymIHC8cUtXeZL9vUdcRSFS5haoxlwjfhRs5hiV4iRUz1rJCg== Completed in 257ms
npm timing metavuln:cache:get:security-advisory:listr-update-renderer:zOQB0PbNfy+2HdBM0HrEL+BwfaUzJTv9ZlpJZ9JwcOJoaxHQN021S+9kwPsfZq0g9Uo1y3UYYMrWP0QqWPB5hQ== Completed in 2ms
npm timing metavuln:load:security-advisory:listr-update-renderer:J06/DTp8oqjxiBqYUWpEItMGCNfkKxzmVHNyz719u956SNJBNE5sR3ZQug0yKGv6PDdcwyMyG5eV8oIV9wifzw== Completed in 0ms
npm timing metavuln:calculate:security-advisory:listr-update-renderer:J06/DTp8oqjxiBqYUWpEItMGCNfkKxzmVHNyz719u956SNJBNE5sR3ZQug0yKGv6PDdcwyMyG5eV8oIV9wifzw== Completed in 2ms
npm timing metavuln:cache:get:security-advisory:@graphql-codegen/cli:6RQfdYOpFrVbzP+x3+oJvOOUSeIkwVhgGpKW5eLzfyRpGhXaDnseLtaQstrjmNAjI6NG9QDqKh7yLxYKOGd7TQ== Completed in 5ms
npm timing metavuln:load:security-advisory:@graphql-codegen/cli:J06/DTp8oqjxiBqYUWpEItMGCNfkKxzmVHNyz719u956SNJBNE5sR3ZQug0yKGv6PDdcwyMyG5eV8oIV9wifzw== Completed in 216ms
npm timing metavuln:calculate:security-advisory:@graphql-codegen/cli:J06/DTp8oqjxiBqYUWpEItMGCNfkKxzmVHNyz719u956SNJBNE5sR3ZQug0yKGv6PDdcwyMyG5eV8oIV9wifzw== Completed in 222ms
npm timing auditReport:init Completed in 2586ms
npm timing reify:audit Completed in 3200ms

@PeachScript please pull merge.

Does not work if more than one InfiniteLoading component on the same page

When are you planning to make release for Vue.js 3 support?

@printscreen is this 3.0.0-alpha.0-0 version works with multiple  component on the same page ? because for me it is not working if one component doesn't have data then the other component stopped the infinite loading and show just the initial loaded data. what to do ?

@PeachScript Also interested in checking in on this progress. Thank you!

"vue-infinite-loading": "3.0.0-alpha.0-0", is working fine for me already, please merge this PR

EventHub causes inner state error for multiple infinite loading instances, please notice this problem.


tkinter.TclError

Detection took 0.639s for 300 object proposals
Traceback (most recent call last):
File "tools/demo.py", line 136, in
demo(sess, net, im_name)
File "tools/demo.py", line 73, in demo
fig, ax = plt.subplots(figsize=(12, 12))
File "/usr/local/lib/python2.7/dist-packages/matplotlib/pyplot.py", line 1202, in subplots
fig = figure(**fig_kw)
File "/usr/local/lib/python2.7/dist-packages/matplotlib/pyplot.py", line 535, in figure
**kwargs)
File "/usr/local/lib/python2.7/dist-packages/matplotlib/backends/backend_tkagg.py", line 81, in new_figure_manager
return new_figure_manager_given_figure(num, figure)
File "/usr/local/lib/python2.7/dist-packages/matplotlib/backends/backend_tkagg.py", line 89, in new_figure_manager_given_figure
window = Tk.Tk()
File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1818, in init
self.tk = _tkinter.create(screenName, baseName, className, interactive, wantobjects, useTk, sync, use)
_tkinter.TclError: no display name and no $DISPLAY environment variable
what should I do

i have the same problem, have you solved it?

are your problem have solved ?

export DISPLAY=mymachine.com:0.0


Publish issue 71

Ping @jessesquires, did you mean to publish before? As you closed the issue and made a new one for next week, but you didn't put issue 71 in _posts. Also take a look at #263 before merging this one :)

Ooh, changing the post to the _posts directory doesn't confuse Travis / Danger anymore! 🎉

thanks @BasThomas !
lol -- time zones. that was all late wednesday night for me. now it's thursday morning. 😊
just published the issue before opening github!

thanks though! 🙌