Code Release

Hey,
great work! Any updates on the code release?
Thanks,
Eduard

Thank you for your interest in our work. I am currently occupied with preparations for a new research paper. I will endeavor to update the code repository as soon as possible.

Hey,
great work! Any updates on the code release?
Thanks, Eduard

Thank you for your interest in our work. I am currently occupied with preparations for a new research paper. I will endeavor to update the code repository as soon as possible


Add rollbar to tile server

This will require breaking out that functionality to a subproject. I think we should consider a core/common subproject for this type of stuff -- auth is already there.

Oh shoot - thanks @hectcastro


Survey api

Issue #219 :
https://github.com/bcgov/met-public/issues/219
adding survey schema to the database
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the sbc-auth license (Apache 2.0).

You are missing the db migration script, let me know if you need any help on it but you can add a migration using the command "python manage.py db revision -m ''  --autogenerate;"


Document Should Include how to pass group information in the claim

[Enter feedback here]
Hi Team,
I am looking for how to pass user's authorization/group information in the claim/SAML assertion post success authentication that are returned to the application. But there is no information provided in the document. Kindly update the document to have this information.
Regards,
Atul Gupta

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4ace5e69-e1db-52c5-9c57-026fc6145a84
Version Independent ID: f6fcdaac-449a-5a37-5fc8-bef1ed731a2a
Content: Add user attributes and customize user input - Azure AD B2C
Content Source: articles/active-directory-b2c/configure-user-input.md
Service: active-directory
Sub-service: b2c
GitHub Login: @kengaderdus
Microsoft Alias: kengaderdus

Hi @akg322 we do not have that feature at the moment. However, there is a work around (a few concepts combined to achieve the goal).
Be sure to watch the video included in the repo. Also, note that Microsoft Graph is recommended as Azure AD Graph is on a deprecation path since June 30, 2020, and will be retired on June 30, 2022.

#please-close


Lifecycle issues when using lib with Jetpack Compose

Hi!
I've used your library in my app, and I think I've encountered some kind of an issue? I've added the ArFromtFacingFragment from the library into Jetpack Compose function, and it seems that it can't initialize properly in the moment when the other compose ui components are ready, it just displays a black screen when the activity is opened, and I have to redraw the composable in order to see the AR function's result.
I wasn't able to use the library's Kotlin version, cause it's working unstable on my phone, and I wasn't able to load the screen at all, even without jetpack compose.
I'm storing the link to ARFragment in ViewModel as a LiveData object, so it seems that the ARFrontFacing fragment just can't load when the other UI components around it are done? It logs the model's coordinates as it's supposed to, for example, it just doesn't display it on the UI.
I'm not sure if it's a bug or not, maybe it's something to consider when updating the Kotlin library with jetpack compose support? Maybe I should add something to 'update' scet
I'm using Galaxy Note 9 for tests, if it makes any difference here.
Let me know if there's some other info that can be useful for the future versions.
Thanks for your time!

Nvm, I think I found it

Please share your results here.
For the SceneView (Kotlin) part, can you use the latest main branch version? It introduced some fixes on rendering and might work better.
We have an AugmentedImageNode in the private SceneView Extended repo.
I can add you there if you are open on sharing a simple Compose sample usage.

I'm sooooo sorry for a late response. :(
Here, I've made a very small app that just displays an ARFrontFacingFragment without any kind of models used. https://github.com/drdlx/Compose-Sceneform-Example
There are 2 branches in project, master one works flawlessly on my phone, whilst the other one with the livedata doesn't.
What's more interesting is that instead of posting it via separate function, it's possible to init the AR Fragment fine, but on, let's say, one initializing function from main activity, so if you init the screen and put the fragment in one place, it's working. But try and put it via some sort of async flow, and it's getting a black screen.
Maybe to use it properly, I should attach the initialization to lifecycle events?
Hope I'm making any sense here.

Hi!
That's perfect, thanks.
One simple question; Why are you using Sceneform instead of SceneView?

@ThomasGorisse I've tried it at first, but on my Galaxy Note 9 it just displayed a black scren in examples. I use Linage OS with Android 12 on it, which might be the reason it's happening.
It just stays like this: Imgur
I've had a chance to check the SceneView on Galaxy S20, though, and it works flawlessly there.


TypeError: Cannot read property 'current' of undefined

This happened after "enzyme-adapter-utils" was updated to version 1.10.0.
As well, I have import 'jsdom-global/register'; at the beginning of the test file.
API

[X] shallow
[ ] mount
[ ] render

Version

library
version

enzyme
3.7.0

react
16.6.3

react-dom
16.6.3

react-test-renderer
16.8.0

adapter (below)
1.6.0

jsdom-global
3.0.2

Adapter

[X] enzyme-adapter-react-16
[ ] enzyme-adapter-react-16.3
[ ] enzyme-adapter-react-16.2
[ ] enzyme-adapter-react-16.1
[ ] enzyme-adapter-react-15
[ ] enzyme-adapter-react-15.4
[ ] enzyme-adapter-react-14
[ ] enzyme-adapter-react-13
[ ] enzyme-adapter-react-helper
[ ] others ( )

As well, I have import 'jsdom-global/register'; at the beginning of the test file.

I have the same issue with the same packages

Same issue here!

 We have the same issue, but its only happening on components that are not extending from React.Component

Is this to do with being a stateless component that you're testing?`

Yes, it is the stateless component.

Update your React to 16.8. ReactCurrentDispatcher is missing from ReactSharedInternals in earlier releases when react-test-renderer in 16.8 is expecting it (probably because newer version of enzyme-react-adapter in 1.9.1 is downloading react-test-renderer in this version, due to your not locked deps)

Update your React to 16.8. ReactCurrentDispatcher is missing from ReactSharedInternals in earlier releases when react-test-renderer in 16.8 is expecting it (probably because newer version of enzyme-react-adapter in 1.9.1 is downloading react-test-renderer in this version, due to your not locked deps)

I updated both react & react Dom 16.8.0  along with enzyme-react-adapter version 1.9.1, and I get document is not defined error
the error:
var actContainerElement = document.createElement('div');
                          ^

ReferenceError: document is not defined
    at /var/code/node_modules/react-dom/cjs/react-dom-test-utils.development.js:944:27
    at Object.<anonymous> (/var/code/node_modules/react-dom/cjs/react-dom-test-utils.development.js:1283:5)
    at Module._compile (internal/modules/cjs/loader.js:688:30)
    at Module._compile (/var/code/node_modules/pirates/lib/index.js:83:24)
    at Module._extensions..js (internal/modules/cjs/loader.js:699:10)
    at Object.newLoader [as .js] (/var/code/node_modules/pirates/lib/index.js:88:7)
    at Module.load (internal/modules/cjs/loader.js:598:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
    at Function.Module._load (internal/modules/cjs/loader.js:529:3)
    at Module.require (internal/modules/cjs/loader.js:636:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at Object.<anonymous> (/var/code/node_modules/react-dom/test-utils.js:6:20)
    at Module._compile (internal/modules/cjs/loader.js:688:30)
    at Module._compile (/var/code/node_modules/pirates/lib/index.js:83:24)
    at Module._extensions..js (internal/modules/cjs/loader.js:699:10)

@MahaZaid what about react-test-renderer?

I added react-test-renderer but I am still getting the same error
"react": "^16.8.0",
"react-dom": "16.8.0",
"react-test-renderer": "16.8.0",

"enzyme-adapter-react-16": "^1.9.1"

@MahaZaid how you are running tests? It seems like Jest don't know that test should be run in JSDOM environment. Please try to add --env=jsdom to your test command

https://jestjs.io/docs/en/cli.html#env-environment

I am using mocha, enzyme, and @babel/register for running structural tests

I'm having a similar issue when using jest. All of my test are now failing. I'm getting a mix of errors, document is not defined and TypeError: Cannot read property 'current' of undefined.
"enzyme": "^3.8.0",
"react": "16.5.0",
"react-dom": "^16.8.0",
"react-test-renderer": "^16.8.0",
"jsdom": "^13.2.0",
"enzyme-adapter-react-16": "^1.9.1",
"babel-jest": "^23.6.0",
I don't have enzyme-adapter-utils in my pakcage.json file.

@c316 updating React to 16.8 should be IMO enough.

@benedyktdryl Updating React isn't always an option.

@benedyktdryl thanks, that update, plus adding the --env=jsdom to the test command fixed half of my test, now I get a different error. Cannot find module 'schedule/tracking' from 'ReactNativeRenderer-dev.js'. I'm looking to see if I can find what this means.

To resolve that error I had to install the npm i<EMAIL_ADDRESS>--save-dev package. See more info here https://github.com/facebook/react-native/issues/21150

@benedyktdryl Updating React isn't always an option.

I understand, but in most cases - this particular issue can be solved by syncing React version as in earlier I simply can't spot ReactCurrentDispatcher inside ReactSharedInternals

I updated both react & react Dom 16.8.0 along with enzyme-react-adapter version 1.9.1, and I get document is not defined error
the error:
var actContainerElement = document.createElement('div');
                          ^

ReferenceError: document is not defined
    at /var/code/node_modules/react-dom/cjs/react-dom-test-utils.development.js:944:27
    at Object.<anonymous> (/var/code/node_modules/react-dom/cjs/react-dom-test-utils.development.js:1283:5)
    at Module._compile (internal/modules/cjs/loader.js:688:30)
    at Module._compile (/var/code/node_modules/pirates/lib/index.js:83:24)
    at Module._extensions..js (internal/modules/cjs/loader.js:699:10)
    at Object.newLoader [as .js] (/var/code/node_modules/pirates/lib/index.js:88:7)
    at Module.load (internal/modules/cjs/loader.js:598:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
    at Function.Module._load (internal/modules/cjs/loader.js:529:3)
    at Module.require (internal/modules/cjs/loader.js:636:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at Object.<anonymous> (/var/code/node_modules/react-dom/test-utils.js:6:20)
    at Module._compile (internal/modules/cjs/loader.js:688:30)
    at Module._compile (/var/code/node_modules/pirates/lib/index.js:83:24)
    at Module._extensions..js (internal/modules/cjs/loader.js:699:10)

I have the exactly same error as @MahaZaid
"react": "^16.8.0", "react-dom": "^16.8.0", "enzyme-adapter-react-16": "1.9.1"

For those that can not upgrade react i solved the issue changing my react adapter form enzyme-adapter-react-16 to enzyme-adapter-react-16.3

I've been fighting with the document is not defined error for most of the morning. I got it working by rearranging things in my helper file. Note: I'm using AVA for my test runner
Before (broken)
import browserEnv from 'browser-env';

import Enzyme from 'enzyme';
import Adapter from 'enzyme-adapter-react-16';

Enzyme.configure({ adapter: new Adapter() });
browserEnv();

After (working)
const browserEnv = require('browser-env');
browserEnv();

const { configure } = require('enzyme');
const Adapter = require('enzyme-adapter-react-16');

configure({ adapter: new Adapter() });

My guess is the adapter is trying to access document during import.

Hey We found a solution, which was:

update "enzyme-adapter-react-16": "1.1.0" to "enzyme-adapter-react-16.3": "1.6.1",
within your enzymeSetup change import Adapter from 'enzyme-adapter-react-16 to Adapter from enzyme-adapter-react-16.3

@Zveroboev every react package must always have an identical minor; so the fact that you're using react-test-render 16.8 will break, since you're using react 16.6. You'll need to peg that as a dev dep at ~16.6.
If you've done that, and you're still having an issue, I'll reopen - if anyone else is having an issue, please file a separate one - and make sure all react packages have identical minor versions.

This just reoccurred now, I had to update all other react dependencies to 16.9 (in my case)

@tolumide-ng all react packages (including react-dom and react-test-renderer) must always have an identical minor version.

Keeping the react-test-renderer version the same as react and react-dom.
https://github.com/facebook/react/issues/14763#issuecomment-461016379

same issue

enzyme-adapter-react-16.3

not working for me:

@ghasemikasra39 your react, react-dom, and react-test-renderer must be on the same minor version - your react-dom is on 16.10.

See solution at https://github.com/testing-library/react-hooks-testing-library/issues/151#issuecomment-523865511; this is likely due to version mismatch as mentioned above.
Instead of trying to upgrade react, you could also simply downgrade react-test-renderer so that they're all on the same version (in this case 16.6.3).

Is there a workaround for those of us who cannot simply up/downgrade npm modules? I'm using them in a react native app, so the react-dom isn't an issue.

@mjstelly react-dom is still an issue there, unless there's a react-native enzyme adapter i'm unaware of.

You are correct @ljharb. I just overlooked it in the enormously long list of packages. ;-)

I have the following
"react-dom": "^16.3.2"
"react-test-renderer": "^16.8.6",
"react": "16.6.3",
So, we're all over the map. I've informed the powers-that-be of this issue.

All three need to match the same minor version, so presumably the easiest is to upgrade react-dom to 16.6, and downgrade rect-test-renderer to 16.6.

I updated those packages in my local branch and the original find error went away. Of course, it created a different error and invalidated over 60 snapshots. Yikes! It broke other tests, as well. Like I mentioned earlier, though, it's not as simple as making a command decision to update npm packages.
So, since this issue is closed, should I create a different issue to address my original problem?

If your original problem still occurs when the deps are fixed, yes please :-)

I solved this by

creating a test setup file called setup-tests.js ( directions here: https://airbnb.io/enzyme/docs/guides/react-native.html )
i coped and pasted it into my root project folder with no modifications
Added this to jest.config
setupFilesAfterEnv: [
"./setup-tests.js"
]
I have these packages and versions:
DEV dep:
"enzyme": "^3.11.0",
"enzyme-adapter-react-16": "^1.15.2",
"jest": "^24.1.0",
"jest-enzyme": "^7.1.2",
"jsdom": "^16.0.0",
DEP:
"react-native": "0.60.5",
"react-native-localize": "^1.3.3",

Note like WTF, i was using jsdom 6.0.1 and it had the above error: i changed it to 6.0.0
and it worked .
worked mean the error was gone and i my brake point after Mount got hit!


Relative paths for boilerplate are broken

#70 reverted a change I made a while ago, which fixes #63. But it also breaks relative paths:
ignite new Foo -b ../my-boilerplate

This has been fixed for some time.


nodeSelector and affinity consistency

The charts are currently all over the place with consistency on affinity and nodeSelectors
Related to #17 and #192

The values.yaml/docs does not have any reference to the selectorLabels config.

Another thing to note: tolerations are also handled differently. RSW appears to support a top-level tolerations field, while the Connect chart does not yet support tolerations. It would be great to consolidate these into a single approach or use a library helper for some of these common configurations files on the top-level pod

Unfortunately we're still facing placement issues on our mixed arch cluster: we have set
config:
  profiles:
    launcher.kubernetes.profiles.conf:
       "*":
         placement-constraints: "kubernetes.io/arch=amd64"

and we see

yet sessions still get scheduled on the arm64 nodes from time to time.
I double-checked that the entry is reflected correctly into /mnt/configmap/rstudio/launcher.kubernetes.profiles.conf in the WB server pod:
[*]
placement-constraints=kubernetes.io/arch=amd64

Is there anything I am still misconfiguring here? 🤔

I think the way you want to set these are:
config:
  profiles:
    launcher.kubernetes.profiles.conf:
       "*":
         placement-constraints:
           - "kubernetes.io/arch:amd64"

But it will only allow selection of amd64 - default will still be to not specify a placement constraint 😞

Thanks! Did so but that did not cause a change in /mnt/configmap/rstudio/launcher.kubernetes.profiles.conf (even after recreating the pod), i.e. the config specification is still looking like in my previous post.
Let's see how it unfolds as it's hard to test directly as most sessions first go to an amd64 node anyway if there's space (due to how the cluster is set up WRT to node resources).

Right 😭 This is pretty unfortunate. There is a pretty ugly workaround... which is "invert the logic in the templates" 😱
We have some work internally to make the default more configurable.
Would affinity work for you? If so, you can always hard-code an affinity here:
https://github.com/rstudio/helm/blob/c48d94fda4562795ca9010f334c2c11271a8073f/charts/rstudio-workbench/values.yaml#L97
I forget if we already talked about this and it's not an option though 😅

Would affinity work for you? If so, you can always hard-code an affinity for all sessions here:

We have affinity already in place and it helps but ofc not to the fullest, i.e. if the amd nodes are busy with CI/CD, the arm64 nodes are being chosen as it's just a "soft" selector.
OK I guess if there's no immediate solution I need to force getting the arm64 builds pushed alongside to be more flexible. While we have working images already, they are only valid for 22.04 and our amd64 stack still mainly runs on 20.04 - but maybe it's time to upgrade now :)
Or maybe to ask upfront: are you planning to tackle the nodeSelector harmonization soonish? I see it might be quite a task to align all charts, so I am not expecting this to be done just right now just because there's this one issue of ours in our mixed arch cluster 😅


Avery Labels

Hi,
I am trying to prepare one of the Avery Labels template that I would like to use with sablon and populate each label with some dynamic data. I am specifically trying to figure out how to do the loop.
Currently all the data is written out in single label instead of label by label.
Is there any way of saying NextRecord in next label or something similar?
I can't find a way to put :each and :endEach before and after the label.
Thx

I've never tried anything like this before. A quick google to see what an Avery label template look like gives me the impression you would probably have to put the :each and :endEach after an entire row of labels. That way the row will get repeated down the page.

No further information received, closing this for now.


Fix storage layer limit

Fixup for #10808
We cannot use atomics to store the storage layer counter because of the native runtime: In the native runtime multiple different calls into the runtime happen concurrently on the same memory. In the wasm case every call gets its own wasm instance with its own memory as it should be.
Storage access works as global data because the client uses thread local data for it.

can we use atomics for wasm runtime only?

can we use atomics for wasm runtime only?

AFAIK yes, but in this case, there is probably not a significant overhead between the two options here. I think using overlay storage is fine, and it will never commit anything to the runtime since it always resets.

Calling into the host should still be way slower than using atomics or environmental. But in this case it doesn't matter because it isn't a function that is called a lot of times.
I think a proper solution would be to pick up this PR and add some thread_local! storage in case of native. I might do that soon.

I don't get why the companion is failing. It seems unrelated. Was something missing from https://github.com/paritytech/substrate/pull/11136 ?


Typo error fixed and make code clean.

Made a few changes in the readme.Md file including spelling mistake of varcel. (on line 30)

Please don't make unnecessary changes, there is already some codes that needs to be fixed if you go through the codebase.


StreamField EmbedBlock renders the url only

Given the following setup:
class EmbedOnImage(StructBlock):
    embed = EmbedBlock()
    background_image = ImageChooserBlock(required=False)

    class Meta:
        template = 'streamfield_blocks/embed_on_image.html'

{{ self.embed }} outputs the embed url only in streamfield_blocks/embed_on_image.html.
And EmbedBlock.render_basic is never called: https://github.com/torchbox/wagtail/blob/master/wagtail/wagtailembeds/blocks.py#L8
Also, if I apply the embed filter too: {{ self.embed|embed }} then it outputs nothing because the embed filter won't call embed_to_frontend_html either, which would use the correct template to render it: https://github.com/torchbox/wagtail/blob/master/wagtail/wagtailembeds/templatetags/wagtailembeds_tags.py#L14

This is the intended behaviour. When you access a child of a StructBlock, such as self.embed, you get back the raw value of the field - the URL string, in this case - rather than the block object that's aware of the correct rendering. This is needed so that you can do things like {% if self.first_name == 'Bob' %} in templates - if self.first_name returned a renderable block object rather than a string, it would never match.
However, I can see that this behaviour is confusing for blocks that have a string value, but have a non-standard rendering: namely, RichTextBlock, RawHTMLBlock and EmbedBlock. I'll have a think about whether there's a better way of doing this.
(Currently, one way to get at the proper rendering would be {{ self.bound_blocks.embed.render }}. Not sure why {{ self.embed|embed }} wouldn't work...)

{{ self.bound_blocks.embed.render }} does work indeed, thanks. Now I can see how this makes sense, but it was a bit unexpected for the first time.
And the |embed filter is not documented or used anywhere in wagtail actually. It seems to be a lower level alternative to embed_to_frontend_html that doesn't use the embed_frontend.html template. @kaedroho ?

When you access a child of a StructBlock, such as self.embed, you get back the raw value of the field - the URL string, in this case - rather than the block object that's aware of the correct rendering.

On further consideration - EmbedBlock differs from RichTextBlock and RawHTMLBlock in that there's actually no reason to expect the native value of an EmbedBlock (i.e. the value you get when you access it as an item of a StructBlock) to be a string or string-like value. In particular, re the use case given above:

This is needed so that you can do things like {% if self.first_name == 'Bob' %} in templates

there's no expectation for something like {% if self.embed == 'https://www.youtube.com/watch?v=LxPXLIALJJI' %} to work. Instead, it would be sensible for the value of self.embed to be a Python object which has a url property, and outputs the embed HTML when rendered in a template. The existing wagtailembeds.Embed model could be made to serve this purpose, although those are specific to a particular max_width parameter which would lead to a wasted lookup if the template actually wants to use a non-default max_width - so it's probably better to introduce a new class for this purpose.
The serialized value of an EmbedBlock can still be a plain URL string - get_prep_value and to_python will handle the type conversion. This would also be a good time to change the blocks API slightly so that the default parameter of a block definition gets passed through to_python - in this case, this means we can still say things like EmbedBlock(default='https://www.youtube.com/watch?v=LxPXLIALJJI') instead of having to pass a custom Python object. (Default values aren't too useful for EmbedBlock, but this solves a more general problem of blocks having non-simple native values - see https://github.com/torchbox/wagtail/blob/2940ea9c9beff94b47a46559937c8fb0512dd4d8/wagtail/wagtailcore/blocks/stream_block.py#L25-L27)
Will put together a PR along these lines.

Fix: https://github.com/torchbox/wagtail/pull/1357


Update example

Fixes #2724. Correct the "-UserId" parameter in Example 2 to "-Identity".

OPS Build status updates of commit 273e676:
:clock10: Preparing: average preparing time is 1 min(s) 12 sec(s)

OPS Build status updates of commit 273e676:
:clock10: Incremental building: average incremental building time is 12 min(s) 22 sec(s)

OPS Build status updates of commit 3d4216d:
:clock10: Preparing: average preparing time is 1 min(s) 12 sec(s)

OPS Build status updates of commit 3d4216d:
:clock10: Incremental building: average incremental building time is 12 min(s) 22 sec(s)

OPS Build status updates of commit 3d4216d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsMeetingMigrationStatus.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Amend type hint to match default value

1. Why is this change necessary?
The phpdocs for the route defaults does not match the typehint in the arguments. This results in an an exception on the php side as the type constraint is not fulfilled. So the validity check whether the parameter is ok is never reached and no readable exception is thrown/logged.
2. What does this change do, exactly?
Loosen up the typehint by adding nullability.
3. Describe each step to reproduce the issue or behaviour.

Do not configure contact layout page
Click on contact in storefront
Do not get a contact form
Look in logs
Uncaught PHP Exception TypeError: "Argument 1 passed to Shopware\Storefront\Controller\CmsController::page() must be of the type string, null given
Expecting Parameter "Parameter id missing" is missing.
Wut?
Check message concatenation for MissingRequestParameterException
See weird refactoring result
Take notes for next pull request

4. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

I applied the requested changes

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-7907
Please use this issue to track the state of your pull request.

@JoshuaBehrens  can you please resolve the conflicts here :slightly_smiling_face: ?

I put it on my TODO 👍 👀

✔

Hi @JoshuaBehrens
The TravisCI is finally working again :rocket: but it looks like some test are failing :frowning_face: could you plase have a look at them
Sunny regards
Pantrtxp

Hi @JoshuaBehrens
This PR is still incomplete.
Will you please update this PR?
Sunny regards
Pantrtxp

I can retry testing it but the last time I tried my tests were not working because of a missing google client dependency.

Hi @JoshuaBehrens,
are those changes not the same as in this PR: https://github.com/shopware/platform/pull/471/files besides the route annotations?
Best regards
Tobias

@tobiasberge @JoshuaBehrens I guess there are a few commits to much :wink: needs a clean-up

Damn it I guess I rebased onto the wrong branch :D

@JoshuaBehrens Do you still have issues with the Google client dependency?

I resolved it on the boostday 😁

Hi @JoshuaBehrens,
there are still the changes from the other PR (EntityCollection class) in this branch.
Could you please update the branch?
Best regards
Tobias

Sorry for delaying. I try to get it into my schedule ASAP

Hey @tobiasberge I tidied things a bit up

Thanks for merging 👍 💙

Hi @JoshuaBehrens ,
thanks for your contribution!


Add files via upload

Belbullab, Delta 7, Sith Infultrator, Torrent and Vulture Droid.
Delta-7 [/backslash]
SithInfiltrator [/bracketright]   ]
Torrent [/asciicircum]   ^
Vulture [/underscore]   _
Belbullab [/bracketleft]   [

Oh hey that's not the button I wanted to click 😔


Fix documentation typo

I've found a mistake in the documentation regarding the links hover decoration.
While I was in the docs, I also fixed the typo mentionned in #14.

Cool, thanks @haleksandre!
I also see you've updated docs to fix the error in: --link-hover-text-decoration: underline;
I've made this typo in a couple of places in utiltities.md and have updated on 4.1.0 branch for release in v4.1.0 as soon as I can.
I might leave it there to keep the changes to the docs in independent commits for traceability if that's cool with you.


Your datasets?

would you  provide datasets? Thanks.

This is a private data set. but you can get the meteorological data from the url:http://www.meteomanz.com/index?l=1&cou=2250&ind=58362&ty=hp&d1=01&m1=01&y1=2012&h1=00Z&d2=07&m2=12&y2=2018&h2=23Z. If you are Chinese man, you can send a message to my email<EMAIL_ADDRESS>or wechat later.


bats should fail fast

Its overwhelming for a user doing a challenge to be presented with a long list of test failures as they are iterating through completing the challenge.

exit the entire test suite (skipping later tests) after first failure

see https://github.com/sstephenson/bats/issues/135


Using numpy > 1.26.4 ?

Thank you for writing and sharing this library for the slf3s sensors! I am curious to know whether the strict version matching (using ==) for numpy is required. A quick look at the code made me think that it might be compatible with higher versions; if so, could the version specifier be modified to allow for that?
Thank you for the consideration.

Hi Steven, thanks for raising this. Unfortunately I can't continue to develop/maintain this package for contractual reasons. I'm happy to transfer the PyPI project to you if you're interested in maintaining it.

Hello Tobias,
Thank you for this offer; however I likewise cannot take on this responsibility at this time. I wish you the best in your work.


Unbreak streaming logging on client

@paetling Previous code broke things on the client side, this should work for both

:ghost: :cow:


Using await / promise

I'd like to use decodeFileAsync as promise instead of supplying a callback.
Your decodeFileAsync function does not have "callback" as last argument as expected by util.promisify(), the last argument should be the callback, but here the last argument is "template".
Any plans to implement a decodeFile function which allows "async/await" to get the result? Or how could this be solved in an easy way with the existing implementation?

OK, it seems to be possible to fix the callback order by overriding the before passing it to util.promisify:
dbr.decodeFileAsync[util.promisify.custom] = (arg1, arg2, arg4) => { return new Promise........  }
but would be nice to have a non-callback variant available out of the box.

@richiewebgate thanks for your feedback. I've added the await/promise support. You can check out https://www.npmjs.com/package/barcode4nodejs/v/9.6.21

Tested and working! Thank you :)


Build(deps-dev): Bump @babel/core from 7.22.10 to 7.22.11 (#5082)

Pull request opened by the merge tool on behalf of #5082

Merged in 6737fff1c9df7c8483f0e4eec15e86375ef67e08


Add support to generate API token with tanzu api-token create

What this PR does / why we need it

Add support to generate API token with the tanzu api-token create command
Add unit tests

Sample output:

Which issue(s) this PR fixes

Fixes #
Describe testing done for PR

Manually tests the UAA login workflow. See the above screenshot

Release note

Add support to generate API token with `tanzu api-token create` (supported for UAA as IDP)

Additional information
Special notes for your reviewer

Do we know the expiration time easily?
Since we tell the user regenerate a new token before expiration, I find it nice to tell them when that will be. If not, is there another way for them to avoid their usage failing when expiration happens?

@marckhouzam regarding this, I discussed with @vuil and the conclusion is we do not have a way to know the expiration time for the Refresh Token at the moment. So, if needed we need to document the expiration time separately in the docs.

@marckhouzam regarding this, I discussed with @vuil and the conclusion is we do not have a way to know the expiration time for the Refresh Token at the moment. So, if needed we need to document the expiration time separately in the docs.

So we will document that the token has a lifetime of X time?
Do we prefer only putting it in the docs so we can more easily change it, instead of printing the value we currently know?
I assume there is no advanced notification for the user to know the token is about to expire?

@marckhouzam regarding this, I discussed with @vuil and the conclusion is we do not have a way to know the expiration time for the Refresh Token at the moment. So, if needed we need to document the expiration time separately in the docs.

So we will document that the token has a lifetime of X time? Do we prefer only putting it in the docs so we can more easily change it, instead of printing the value we currently know?
I assume there is no advanced notification for the user to know the token is about to expire?

Yes. We do not know the lifetime of this refresh token at the moment. And that can be updated without CLI's knowledge from the backend so it is safe to put that information in the docs.
Correct, there isn't any advanced notification for the user to know the token is about to expire.
Please note that this API token generation from the CLI is a temporary workaround for supporting the non- interactive login with UAA because UAA does not have any UI to generate this token. There will be updates and enhancement in this area in future would likely make CLI more user friendly.


CP-12288: K-Shortest paths - Hoffman Pavley

From unknown CodePlex user on Monday, 05 January 2009 23:18:23
Ok, sorry.

I've seen the extension method (To bidirectional) with the new changeset.Thanks!

I've a problem. Executing the code below, it returns always (KeyNotFoundException) Error: key not found in the dictionary:
            IBidirectionalGraph<int, Edge<int>> g1 = g.ToBidirectionalGraph();

            int Source = 1;
            int Target = 33;

            int pathCount = 5;

            foreach (IEnumerable<Edge<int>> path in g1.RankedShortestPathHoffmanPavley(E=> 5, Source, Target, pathCount))
            {
            }

Attached my serialized adjacency graph

Bye.
TestGraph.zip
AdjacencyGraph.zip

Form unknown CodePlex user on Tuesday, 06 January 2009 00:08:14
Please post the full test case to reproduce this issue. Thanks

Form unknown CodePlex user on Tuesday, 06 January 2009 00:14:47
Also please use the graphml file format.

Form unknown CodePlex user on Tuesday, 06 January 2009 00:27:04
Hi,  this is a sample application.
Bye.

Form unknown CodePlex user on Tuesday, 06 January 2009 00:57:32
See attachment (TestGraph.zip). Bye.

Form unknown CodePlex user on Tuesday, 06 January 2009 09:17:17
Resolved with changeset 29945.


Don't set CONTENT_TYPE / CONTENT_LENGTH if they're not provided by the client

Fix: https://github.com/pallets/werkzeug/issues/1049
according to (PEP333)(https://www.python.org/dev/peps/pep-0333/#environ-variables) it's ok if they're absent

Thanks for this PR, please rebase against 0.11-maintenance, add tests and a changelog entry.

Rebase: git rebase -i origin/0.11-maintenance and remove the commits that are not part of your PR (just delete the lines). Then git push -f. Then edit this PR to be against 0.11-maintenance (edit button at the top)

Tests: A test in tests/test_serving.py would be nice

Changelog: For the next 0.11.x version

@untitaker all set

Could you additionally verify that the tests fail without the fix applied? Thanks!

@untitaker oh I've made a mistake, the key in environ should be CONTENT_TYPE / CONTENT_LENGTH, not HTTP_CONTENT_TYPE/HTTP_CONTENT_LENGTH.
made a new push

the tests did fail without this patch

@untitaker plz review again

ping @untitaker

Thanks!


/tmp/terraform_1666793039.sh: line 3: docker-compose: command not found

Resource Manager Job failed: ... here you have the latest lines of the logs
...
oci_core_public_ip.WordPress_public_ip: Creating...
oci_core_public_ip.WordPress_public_ip: Creation complete after 0s [id=ocid1.publicip.oc1.eu-frankfurt-1.amaaaaaalguzq5iadfhztonqczwxcnmvtp3zwd62grwk4zex62fm6e3d4uza]
data.template_file.wordpress-docker-compose: Reading...
data.template_file.wordpress-docker-compose: Read complete after 0s [id=a22841fdc930fe3404173c4a762e4d26194a2bc1303f6df55c01602b24e108ed]
null_resource.WordPress_provisioner: Creating...
null_resource.WordPress_provisioner: Provisioning with 'file'...
null_resource.WordPress_provisioner: Provisioning with 'remote-exec'...
null_resource.WordPress_provisioner (remote-exec): Connecting to remote host via SSH...
null_resource.WordPress_provisioner (remote-exec):   Host: <IP_ADDRESS>
null_resource.WordPress_provisioner (remote-exec):   User: opc
null_resource.WordPress_provisioner (remote-exec):   Password: false
null_resource.WordPress_provisioner (remote-exec):   Private key: true
null_resource.WordPress_provisioner (remote-exec):   Certificate: false
null_resource.WordPress_provisioner (remote-exec):   SSH Agent: false
null_resource.WordPress_provisioner (remote-exec):   Checking Host Key: false
null_resource.WordPress_provisioner (remote-exec):   Target Platform: unix
null_resource.WordPress_provisioner (remote-exec): Connected!
null_resource.WordPress_provisioner: Still creating... [10s elapsed]
null_resource.WordPress_provisioner: Still creating... [20s elapsed]
null_resource.WordPress_provisioner (remote-exec): /tmp/terraform_1666793039.sh: line 3: docker-compose: command not found
Error: error executing "/tmp/terraform_1666793039.sh": Process exited with status 127

@jeevanjoseph can you please take a look at this isssue?

@jaimecid - this is likely caused by yum issues, where the docker installation fails. Can you try running a destroy followed by an apply ?
Logs from /var/log/messages are helpful to trouble shoot if you encounter this again, but they have to be captured soon after you see the issue.

Thanks @jeevanjoseph , i deleted everything, VCN and Compute Image and 2nd try was successful , ... i was testing in Always Free resources both times. The only difference was this second time i uploaded mykey.pub file.  BTW ,  congrats for this great WordPress micro Deployment on OCI. Great example and running on Always Free resources. @jeevanjoseph , @lfeldman  Thanks a lot !!!


Support data object is member of a collection

Discussions 13. november 2023
@jcrivenaes @daniel-sol @HansKallekleiv
In some cases, exported data objects from FMU are related to each other. The specific example discussed revolve around volume calculations, where the same data are represented as a table, a 3D grid parameter and a surface.
A need from Webviz is to programmatically link these together. Conceptually, they all "siblings". This has some parallels to the existing aggregation_id used for aggregated data, where multiple results from the same operation is assigned a common aggregation_id so that they can be linked together.
Elements discussed:

Should we simply add collection_id as an argument to ExportData.__init__(), and then forward this to the outgoing metadata? That means each object from this operation is tagged with the same ID. So, when a client is using one of the siblings, it will know that 1) there are other siblings and 2) be able to identify them from the collection_id
The name collection_id is perhaps not great.
From the data perspective, this may be more like member_of.
A data object can be member of more than one collection/family.
We want it to be unique per case, but we want elements exported from multiple realizations to belong to the same collection. Proposed solution is to give e.g. collection_tagname (placeholder name) as argument to ExportData(). Generate a uuid4 as a hash of current case.uuid and collection_tag. This ensures that the collection_id (placeholder name) is identical across all realizations, but unique per case.

(Also discussions on gathering all Volume-related exports into one single class, to make essentially a "one-liner". This proposal would be a first step towards this, by doing a very small iteration in the right direction - which includes some tag in the outgoing metadata that can be used. @daniel-sol can you describe in separate issue?)
Proposal

Add input argument collection_tagname to ExportData()
Create uuid4 as a hash of current case.uuid and collection_tagname
Append to data.member_of (placeholder name) in outgoing metadata.

In metadata definitions, add the necessary tag. Placeholder name: member_of.
Example:
data:
  name: MyName
  member_of:
    - b77e5c35-524b-43d7-9356-aa2ef2e382c3
    - d390eb27-f07f-4f9b-bf97-2b61a773753c

Example script:
from fmu.dataio import ExportData

exp = ExportData(collection_tagname="inplace_volumes")

for elem in AllTheElements:
    exp.export(elem)

The collection tagname is in this proposal not directly represented in outgoing metadata. It's only purpose is to be basis for the hash. We could include it, but risk is that it will be directly used by clients.
Please add discussion details I have forgotten.

Suggest adding a relations block in the metadata, next to data - not adding relational information inside the data block.
Example:
$schema: <schema_url>
data:
  x: y
  z: 1
relations:
  member_of:
    - <uuid4>
    - <uuid4>

Upside with using list is to capture when object is member of more than one collection. Downside is searchability. But probably possible to work around.

Since data object can be member of > 1 collection, input argument must support more than one collection_name.
Will use collection_name, not collection_tagname, to avoid confusion with the other "tagname".

Draft PR for discussions: #396
There are some unanswered questions still.

Possibly confusing that the collection_name disappears. Should keep this (in addition to uuid).

Instead of specifying collection_name we could consider simply using the instance of ExportData() as the identifier of the collection. Upside is invisibility, no API change. Downside is invisibility (user is not able to find "his" collection easily. No name.
Also, ExportData instances have no name/identifier.

Instead of specifying collection_name we could consider simply using the instance of ExportData() as the identifier of the collection. Upside is invisibility, no API change. Downside is invisibility (user is not able to find "his" collection easily. No name.

That is an interesting idea, but requires some user awareness: (1) You need to export all needed for you "collection" in the same script using the same instance, and (2) there is a risk of the opposite; people exports stuff not being indented as a collection by using the same instance. So they get a number of "unaware" collections...
For (1), the instance settings (properties) needs also to be updated in the export() jobs, since they in this case will a mix of e.g. surfaces and tables.

Yes, there are some snags. If combined with a "best practice" description of how we intent fmu-dataio to be used (#395) it could be part of the contract that everything exported within the same instance of ExportData implicitly is a collection. But I also see that this will quickly break down, and probably some will want to export parts of a "collection" from different scripts (hence different instances).
So I don't think we should pursuit this....

I wonder if the wanted collection names shall be defined at the "case" level (i.e. they must exists in global config or similar): Reasons:

The client (e.g. webviz) can then easily parse all possible collections early and add logics to further work
Avoid that typos in collection names in "various scripts around" are root to confusion (e.g. one script usename "volumetrics" while the other uses "Volumentrics"... the user is unaware
Avoid too many collections introduced as "nice to have"

I wonder if the wanted collection names shall be defined at the "case" level (i.e. they must exists in global config or similar)...

Technically on model level, which makes sense. It has been a stated requirement that a "collection" must be unique to the case (hence it is hashed together with the case.uuid). But it could be that it sometimes must be unique also on iteration (ensemble) level, and possibly on realization level.
So, given these "levels" in the "hierarchy":
fmu  (all FMU models)
model (this FMU model) <-- Should be defined here?
case (this specific case of this model)
ensemble (this specific ensemble, in this case)
realization (this specific realization of this iteration)
...we have assumed that it must be unique on case level, but that would still require clients to specify which iteration. So perhaps this should rather be unique on model level. Clients would then have to specify case but that is pretty common situation to be in?
Key question here is perhaps "what is the level of uniqueness needed for collections"? Do we need the unique id's at all, or is it enough with a string identifier/name?
Ref defining globally: So when exporting a data object tied to a collection, it must be verified that this collection is defined (in global config)? Not 100 % sure about the user experience, but that can be worked on.

Discussion 23.11.2023

Current user story is related to inplace volumes - what other collections are there?

HC thickness maps from simulator

Important that tagged collections can be grouped through Elasticsearch
Is tagname essentially a "collection"?

From: https://github.com/equinor/fmu-dataio/pull/396#issuecomment-1831429905 @daniel-sol

I have problems understanding how we are actually going to solve the multicollection part. In theory I think the idea is good, but in practice I cannot really see how this will be done. Imagine that you have a specific grid property. This can be part of several collections:

As part of the export of a 3D grid and related properties
As part of properties used as input to inplace calculations
As part of input to seismic forward modelling
Not thinking properly about this one would set these exports as three different scripts utilizing ExportData, should we then allow for checking that the object is exported already and then just writing to the connected metadata file? Or do we imagine people thinking this through upfront, and then adding all these x number of collection names in one script. I foresee that this will not scale all that well...

The alternative is that one exports this grid property three times with different collection name, or something similar..

Yes, I agree. This is conceptually hard to see a smooth solution to, given current constraints etc.
Multiple pointers to the same data object probably creates a HUGE overhead in bookkeeping (gut-feeling). Multiple uploads of the same object is an option, but doesn't feel good.
A possible option is that collections are pre-defined, and that export scripts point to one or more specific collections when exporting. In the metadata, they are then explicitly listed. But this does not solve how this is to be used by a client. Then the client must also know the context of each collection, etc.
The fundamental need here was to be able to link objects together, e.g. "as a consumer of FMU results, I would like to be able to find connected data, so that I can co-visualize connected data in multiple contexts." or something like that. The collections-concept may not be the best way to handle it. The current solution is using name which is not a good solution either.


Added a couple of articles/prepositions that were missing

Simple documentation errata.

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

Thank you for taking the time to make our documentation better. One of your changes was actually correct. Could you revert that one, please?

Hey David, thanks for letting me know that one of my changes for actually correct. The other one was correct, too.  That was really misleading. I wanted to say that one of your edits was actually unnecessary – the one that I was commenting on. I just messed up the comment, sorry about that.

cc @lacker @hramos

Hey @olgabanis thanks for sending these fixes! I think I get what David was attempting to say here - the "app bundle" is what that sentence is referring to, using bundle as a noun. So I just tweaked the PR to have the other three changes. Thanks again - I'll ship this now

@facebook-github-bot shipit

Thanks @lacker and sorry for letting this drag on, I thought it was resolved. Cheers


Kabanero controller can't create object, owner version and kind are empty

The following snip from kabanero-operator log:
{"level":"info","ts":1570825726.8186624,"logger":"manifestival","msg":"Updating","name":"kabanero/appsody-operator","type":"/v1, Kind=ServiceAccount"}
{"level":"error","ts":1570825726.821038,"logger":"controller_kabaneroplatform","msg":"Error reconciling appsody.","Request.Namespace":"kabanero","Request.Name":"kabanero","error":"ServiceAccount \"appsody-operator\" is invalid: [metadata.ownerReferences.apiVersion: Invalid value: \"\": version must not be empty, metadata.ownerReferences.kind: Invalid value: \"\": kind must not be empty]","stacktrace":"github.com/kabanero-io/kabanero-operator/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\tsrc/github.com/kabanero-io/kabanero-operator/vendor/github.com/go-logr/zapr/zapr.go:128\ngithub.com/kabanero-io/kabanero-operator/pkg/controller/kabaneroplatform.(*ReconcileKabanero).Reconcile\n\tsrc/github.com/kabanero-io/kabanero-operator/pkg/controller/kabaneroplatform/kabaneroplatform_controller.go:210\ngithub.com/kabanero-io/kabanero-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\tsrc/github.com/kabanero-io/kabanero-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:215\ngithub.com/kabanero-io/kabanero-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func1\n\tsrc/github.com/kabanero-io/kabanero-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:158\ngithub.com/kabanero-io/kabanero-operator/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1\n\tsrc/github.com/kabanero-io/kabanero-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133\ngithub.com/kabanero-io/kabanero-operator/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil\n\tsrc/github.com/kabanero-io/kabanero-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134\ngithub.com/kabanero-io/kabanero-operator/vendor/k8s.io/apimachinery/pkg/util/wait.Until\n\tsrc/github.com/kabanero-io/kabanero-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88"}

I think what is going on here, is we're trying to update an object (in this case the Appsody service account) with an owner.  The owner happens to be us (the Kabanero CR instance) that we got from the Kabanero controller.  The meta fields are not filled in.  There are other bug reports that mention things like this happening:
https://github.com/kubernetes-sigs/controller-runtime/issues/202
but I would have thought that this was fixed by now.  In any case, we've discovered this in other places in the code, and have fixed it by re-obtaining the object.  However it's not clear whether we obtained the object using the controller-runtime client, or with a new client (our first attempt at scheme registration used a separate client).  In any case, we need to be sure that the owner information is complete before attempting to set the owner reference when we call manifestival to apply yamls (https://github.com/kabanero-io/kabanero-operator/blob/75794d2192856ab9e5b9f8bc46559c0e9b2fa586/pkg/controller/kabaneroplatform/appsody.go#L57)

It looks like the controller-runtime PR went into 0.1.8 of controller-runtime.  Kabanero-operator has 0.1.10 in its vendor dir, which is pretty old, but should have the fix.  Perhaps something else is wrong.  I have to admit that I don't understand the packaging dependencies here, but we should explore whether we can come up in controller-runtime version.  It may be that the operator-sdk which was used to build the operator required (or requires) this version of controller-runtime.

I have another theory (I don't know if this is any more or less credible than the last one).  The first time thru the reconcile loop for an upgrade to kabanero-operator 0.2.0 and friends, we'll look to see if our finalizer is set on a Kabanero CR instance, and if not, we'll update it with a client.Update().  This controller-runtime PR:
https://github.com/kubernetes-sigs/controller-runtime/pull/528
fixes a bug where the GVK are cleared from the local object after a client.Update().  OK technically it look like kubernetes/apimachinery is clearing it.  But in any case, it would explain why the kabanero operator eventually does the right thing - the 2nd time thru the reconcile loop we wouldn't do the client.Update() because the finalizer is already set.  The GVK would still be valid and so we'd be able to create all of the other objects.
The controller-runtime PR is in v0.2.0 of the controller-runtime.  This is a major release and there are breaking changes.  This version of controller-runtime is also included in operator-sdk v0.11.0 (hot off the presses), whose release also has instructions for how to mitigate some of the breaking changes.


[DCOS-44873] Add file name to ClassicRPCAuthenticatee module

ClassicRPCAuthenticatee is used when using V0 API. We use V0 in 1.10 clusters.
HttpAuthenticatee is used when using V1 API.

Going forward, i think we can introduce helloworld in 1.10, 1.11, 1.12 (both permissive and strict) for our PR CI in dcos-commons. This would also be useful when we remove the frameworks from dcos-commons repo.

lgtm pending CI

Tested this manually by installing kafka from a stub generated from this PR and then using the stub to install kafka in 1.10 strict, 1.11 strict and 1.12 strict clusters. Merging this while a CI is still running to get this tested in nightlies. We can always revert if something doesn't work.


Update tf.image documentation

Fix https://github.com/tensorflow/tensorflow/issues/28169
Update tf.image documentation

Hi @MarkDaoust,
Please also review PR https://github.com/tensorflow/tensorflow/pull/37174 as this will have a minor effect on this PR.


PMM improvements

[ ] thread issue
[ ] removing frames

https://github.com/juspay/hyperswitch-sdk-ios/commit/b2076f06202018abea3d7ae5aabd2e3155d173cf


Zoom button positions are not adjusted for the new square minimap size

Zoom button positions are not yet adjusted for the new square minimap size.

Completed in https://github.com/TheLinuxITGuy/Turtle-Dragonflight/releases/tag/v2.6.1

Tested, I can confirm it's fixed.


(Re)introduce progress bar

A progress bar was originally implemented with ezcConsoleProgressbar,
but this was removed by commit 31d5d775f8bedb6a189ed8289047c3d87b04e7e4
This commit re-introduces a progress bar using Symfony\Component\Console\Helper\ProgressHelper

I lost interest in this project a long time ago, mostly due to the limitations of its implementation. Today I added a note that this project is no longer maintained to its documentation and closed all open tickets. Feel free to continue to work on this in a fork.


Fix SCRIPT_NAME being included in path

Removed environ['SCRIPT_NAME'] where it was being concatenated with environ['PATH_INFO'] to get path
Fixes #257
@tomchristie I have attempted to write a test for this, but if I change the environ dict in test.py it cascades and caused all the other URL tests to fail. Not sure what the best way to handle this is as SCRIPT_NAME is only set when deployed to Lambda

Good stuff, thanks!
We'll want to add MountPath and ApplicationPath components at some point.


Error: RSV2 and RSV3 must be clear

Please describe the problem you are having in as much detail as possible:
I don't exactly know how to explain it, but I also have no example code, because I don't know what is going on. It just started happening as soon as I tried to use disabledEvents on the client constructor, but it threw this error. I removed it and it's still giving me the same error. I moved the bot to my VPS and same error. It doesn't seem to be a port issue, because this is the only bot running. Anyone else having this error?
Include a reproducible code sample here, if possible:

Further details:

discord.js version: 12.0.0
node.js version: 8.2.1
Operating system: Debian 8.4
Priority this issue should have – please be realistic and elaborate if possible: Extremely High

[ ] I found this issue while running code on a user account
[x] I have also tested the issue on latest master, commit hash: 54ff8ce

weeee we aren't sure how to fix this either. we believe it to be an upstream bug with ws, but we aren't sure. please try reproducing with uws and with/without bufferutil installed.

@devsnek That seemed to fix the issue, thanks!

@PassTheMayo can you be specific on what fixed the issue, we aren't sure here how to fix it

@devsnek I just did npm install uws, and restarted the bot. It was successful at login and did everything correctly.

Hmm thanks! I was having this issue too but was just ignoring it.

https://tools.ietf.org/html/rfc6455#section-5.2
https://github.com/websockets/ws/issues/1140#issuecomment-308016758

@jaipradeesh That explains nothing. Plus we already got this resolved anyways, thanks.

   RSV1, RSV2, RSV3:  1 bit each

      MUST be 0 unless an extension is negotiated that defines meanings
      for non-zero values.  If a nonzero value is received and none of
      the negotiated extensions defines the meaning of such a nonzero
      value, the receiving endpoint MUST _Fail the WebSocket
      Connection_.

This error means that the client is sending a compressed frame but the permessage-deflate extension is disabled.

@jaipradeesh - Your saying this, but I'm unsure what you mean.

This error means that the client is sending a compressed frame but the permessage-deflate extension is disabled.

I've got a self made bot, which connects to a remote API, and I just got an error saying Error: RSV2 and RSV3 must be clear as well. I'm using the regular node ws lib for the websocket, so I'm not sure how I as a client am wrong in sending a compressed frame.
Have you got any tips on debugging this?

I'm still getting this error, and when its a fatal one so my script crashes

@kramer65 @lukeeey As PassTheMayo did, just install uws and it should work.

Don't you think I did that

I'm getting this when I stream data from an arduino IoT nano, it streams for about a few seconds, data is good, then it hits this error. Since it sends good data prior to this error, I don't believe the error message is accurate, otherwise the error message would show up in the first message(s). It's a bit of a showstopper, cannot seem to stream websocket data using ws and uws is not a realistic option due to it's various issues.


[mac]Notification Function not working properly

Bug Description
Notification not working properly
Steps to Reproduce
Steps to reproduce the behavior:

Installed TNB version 28 app on windows and mac o.s.
launch application on windows
Click on send coins button
Select friend account(mac)
5.Enter Coins & click on send button

Expected behavior
Notified friend when receiving coins from friends account
Actual behavior
Not notified friend when receiving coins from friends account
Screenshots/Recordings
mac o.s.:- https://prnt.sc/vhaw93
windows o.s. https://prnt.sc/vhavk0
OS and Browser

OS: [e.g. Windows 10,mac]
Browser [e.g. Chrome]

Due to bank not having any active confirmation services

Due to bank not having any active confirmation services


[2.10] Ability to configure service start types and dependencies

Summary
Issue https://github.com/rancher/rancher/issues/42458
Occurred changes and/or fixed issues
This PR refactors the SUC image with the aim of providing new ways to configure the rancher-wins and rke2 services. Namely, these changes introduce the ability to control the start type of the rancher-wins Windows service and to define a service dependency between rancher-wins and rke2.
These features can be controlled via environment variables, typically set by Rancher when deploying SUC plans. These variables can be provided in the Rancher UI by setting the following environment variables in the Agent Environment Variables section.
To change the rancher-wins start type to delayed, the CATTLE_ENABLE_WINS_DELAYED_START can be set to true. To add rancher-wins as a service dependency on rke2, the CATTLE_ENABLE_WINS_SERVICE_DEPENDENCY can be set to true. If a variable is omitted, it is treated as if it were disabled, reverting any changes made previously. If any errors are encountered during this process, any changes made will be reverted back to their initial state.
New integration tests have been created to cover this functionality, the Go version has been bumped, and the CI updated.
Areas or cases that should be tested
Provisioning and configuration via Rancher.
Areas which could experience regressions

Merging this as the only additional commit added past initial review is bumping of the system-agent dependency.


Check to see if Select2 Ajax infinite scrolling remote data returned null or empty data

STOP!
Before you open an issue:

Make sure that your issue is a BUG or FEATURE REQUEST.  General usage and troubleshooting questions should be directed to the forums or Stack Overflow.  Issues asking for general support WILL BE CLOSED automatically.
Search the current issues, both open and closed, for a similar issue. If the bug is still present but the relevant issue has been closed, you may ask us to reopen the issue. Duplicate issues will be closed automatically.
Make sure that you are using the latest stable version of Select2 (see the release history). Old minor/patch versions will not be supported.

If you are CERTAIN that it is appropriate to open a new issue, you must:

Create and link to a minimal, complete, and verifiable example by cloning our JSBin template. Code dumps, zip files, etc are NOT acceptable.
Any additional code snippets should be formatted using Markdown code fences and properly indented. Poorly formatted code is difficult to read and reflects badly on you as a programmer.
Include relevant screenshots or animations, if possible. Drag your screenshots directly into this text box. They will automatically be uploaded and the Markdown to display them will be generated.  Avoid third-party image hosts, or links which require extra clicks to view the image.
If you are not conversationally proficient in English, do NOT just post a machine translation (e.g. Google Translate) to GitHub. Get help in crafting your question, either via the forums or in chat. If all else fails, you may post your bug report or feature request in your native language, with a machine translation below that. We will tag it with translation-needed so that others who speak your language can find it.
State the steps needed to reproduce the problem.
Mention your version of Select2, as well as the browser(s) and operating system(s) in which the problem occurs.
Clear out this placeholder text.

Issues that ignore these rules will be closed without further comment!

I have a Select2 dropdown which loads data from my database using Select2 Ajax. It loads that data perfectly fine.
But I want to be able to know if the Ajax call returned null or empty; as some of the columns in my database are null, and this is fine. But what I want is to be able to know when empty or null data is returned in the Select2 Ajax function.
Thanks in anticipation.
I have this code, and it fetches all the required data perfectly.
$('#school_Sel').select2({
ajax: {
url: '{{'createOb_FtcSchools'}}',
data: function (params) {
return {
Name: Name,
search: params.term,
page: params.page || 1
};
},
dataType: 'json',
processResults: function (data) {
data.page = data.page || 1;
return {
results: data.items.map(function (item) {
return {
id: item.id,
text: item.name_local
};
}),
pagination: {more: data.pagination}
}
},
cache: true,
delay: 250
},
width: '80%',
placeholder: 'Select or type name',
});
How do i check to see if the returned data set is empty or null? Thanks once more people for your responses

Issues that ignore these rules will be closed without further comment!

This appears to be more of a usage question than a bug report or common feature request.  As we continue to keep the Select2 issue tracker geared towards these two areas, bug reports and common feature requests, we are redirecting usage questions to other communities such as the mailing list, IRC, or Stack Overflow.


Top-sheet modal

Add a new modal style "top-sheet", similar to "bottom-sheet"

As per Material Design Specs from Google, there shouldn't be a "Top Sheet" component: https://material.google.com/components/bottom-sheets.html


Remove screenshot.png and screenshot_w360.png from root folder

It's fixed in 769e1e4, 5186813, 81953c3 commits.


Update go-control-plane to drop PGV

For https://github.com/istio/istio/issues/48715

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
22e33ac1004fe03da333f3453fc84fe73e520a41
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


vulnerabilities when running npm install

Hi,
when i run "npm install"
im getting an npm error with:
added 1770 packages from 1186 contributors and audited 34504 packages in 82.563s
found 6 vulnerabilities (1 low, 4 high, 1 critical)
node version: 10.8.0
npm version: 6.2.0
i run "npm audit fix" but it didnt help.
im sure that all my tools (including vue-cli ) is up to date.
if anybody can help me with this issue that will be great!
Thanks
this is the npm audit report:
`                       === npm audit security report ===
                             Manual Review
         Some vulnerabilities require your attention to resolve

      Visit https://go.npm.me/audit-guide for additional guidance

Critical        Command Injection
Package         growl
Patched in      >=1.10.2
Dependency of   @vue/cli-plugin-e2e-nightwatch [dev]
Path            @vue/cli-plugin-e2e-nightwatch > nightwatch >
mocha-nightwatch > growl
More info       https://nodesecurity.io/advisories/146
High            Denial of Service
Package         http-proxy-agent
Patched in      >=2.1.0
Dependency of   @vue/cli-plugin-e2e-nightwatch [dev]
Path            @vue/cli-plugin-e2e-nightwatch > nightwatch > proxy-agent >
http-proxy-agent
More info       https://nodesecurity.io/advisories/607
High            Denial of Service
Package         http-proxy-agent
Patched in      >=2.1.0
Dependency of   @vue/cli-plugin-e2e-nightwatch [dev]
Path            @vue/cli-plugin-e2e-nightwatch > nightwatch > proxy-agent >
pac-proxy-agent > http-proxy-agent
More info       https://nodesecurity.io/advisories/607
High            Denial of Service
Package         https-proxy-agent
Patched in      >=2.2.0
Dependency of   @vue/cli-plugin-e2e-nightwatch [dev]
Path            @vue/cli-plugin-e2e-nightwatch > nightwatch > proxy-agent >
https-proxy-agent
More info       https://nodesecurity.io/advisories/593
High            Denial of Service
Package         https-proxy-agent
Patched in      >=2.2.0
Dependency of   @vue/cli-plugin-e2e-nightwatch [dev]
Path            @vue/cli-plugin-e2e-nightwatch > nightwatch > proxy-agent >
pac-proxy-agent > https-proxy-agent
More info       https://nodesecurity.io/advisories/593
Low             Regular Expression Denial of Service
Package         debug
Patched in      >= 2.6.9 < 3.0.0 || >= 3.1.0
Dependency of   @vue/cli-plugin-e2e-nightwatch [dev]
Path            @vue/cli-plugin-e2e-nightwatch > nightwatch >
mocha-nightwatch > debug
More info       https://nodesecurity.io/advisories/534`

wrong repo


All options are treated as user options

This wrapper takes either the value of the options attribute, or the options configuration (or the ngModel options otherwise) and adds them to Selectize via the addOption() API.
This is not a good behavior: Selectize itself treats the options configuration in a special way, using registerOption() instead, so these are base options that cannot be deleted.
Only the options really added by the user can be deleted, the others are just unselected and added back to the option list.
angular-selectize should use registerOption() too to initialize the component.

I have made a fix for this issue, it is in my fork, but to make a clean pull request, it seems the previous pull request must be merged.
Maybe I should have made parallel branches, but somehow these fixes are more or less interdependent.

I don't see how this distinction can be made by the wrapper. How does it know which options in $scope.options are from the user? If $scope.options becomes [] I think the wrapper should delete all options.

The wrapper doesn't need to make a distinction. It adds all options in $scope.options via registerOptions, and lets Selectize to add user options via its own addOption, ie. as user options. Ie. the former are "native" options (eg. coming from the server, or hard-coded) and the latter are really the new ones entered manually.
The distinction allows to put back native options to the drop-down if removed from the selection, while user-entered options doesn't go there.
My latest pull request managed proper deletion of options.

Honestly, this behavior is very annoying. I have another case where I really want to distinguish original options from typed ones!
I will see if I can rework my PR to fit current v3 version.


[Android] net::ERR_UNKNOWN_URL_SCHEME mynike:// Webpage not available

Environment

Technology
Version

Flutter version
2.0.4

Plugin version
5.3.1

Android version
11

iOS version

Xcode version

Device information:
Android 11 (API 30) (emulator)
Description
Expected behavior:
Visit https://www.nike.com/se/en/ through the InAppWebView and navigate to a product and be able to continue navigating on the page.
Current behavior:
Visit https://www.nike.com/se/en/ but after navigation to a product the InAppWebView tries to redirect to for example:  mynike://x-callback-url/product-details?style-color=CU4111-300&link_click_id=907905763154196244 and crashes. See image below.
Options
InAppWebViewGroupOptions options = InAppWebViewGroupOptions(       crossPlatform: InAppWebViewOptions(         mediaPlaybackRequiresUserGesture: false,       ),       android: AndroidInAppWebViewOptions(         useHybridComposition: true,       ),       ios: IOSInAppWebViewOptions(         allowsInlineMediaPlayback: true,       ));
If I use useShouldOverrideUrlLoading: true it opens a new window above the running app which is not a behavior I want.
Images

(It works in my iOS environment.)

That's the correct behavior. It's not a crash, but a load error.
The WebView does know nothing about the mynike:// scheme. It's not the http or https scheme as you would normally have on the web.
In general, iOS somehow manages other schemes if it finds other apps that know how to manage them.
However, using useShouldOverrideUrlLoading: true without implementing the actual event shouldOverrideUrlLoading doesn't make any sense.
If you want to manage custom schemes to open an App that knows how to manage the mynike scheme, you need to implement the shouldOverrideUrlLoading event, for example, as follow:
shouldOverrideUrlLoading: (controller, navigationAction) async {
  var uri = navigationAction.request.url;

  if (uri != null && uri.scheme == "mynike") {
    if (await canLaunch(url)) {
      // Launch the App
      await launch(
        url,
      );
      // and cancel the request
      return NavigationActionPolicy.CANCEL;
    }
  }

  return NavigationActionPolicy.ALLOW;
},

Thanks for the response. I did use a similar shouldOverrideUrlLoading that you mentioned, but the launch method open a new Chrome window above the app but I would like the user to maintain in the app. Is there any way to keep the user inside the InAppWebView?

I tested that website and it seems that the webpage itself is trying to redirect the user to use the official App.
In this case, to make it work, you can return NavigationActionPolicy.CANCEL when the request has the scheme mynike.
This works for this website, but the same logic could not work for other websites.
Here is the shouldOverrideUrlLoading implementation:
shouldOverrideUrlLoading: (controller, navigationAction) async {
  var uri = navigationAction.request.url!;

  if (uri.scheme == "mynike") {
    // and cancel the request
    return NavigationActionPolicy.CANCEL;
  }

  return NavigationActionPolicy.ALLOW;
},

However, this is something related to the website itself and not to this plugin.

I see, I'm not that experienced in web development, but thanks a lot for the fast response and the help! I works for that specific site now.


Getting wrong country code for North Korea

I am implemented same library but, this library showing same country code for Antarctica ( AQ ) +672
and same country code for North Korea ( KP ) +672, Actually North Korea have +850 country code,
Please resolve this and update library.

Sorry for the super super late response.
This bugs is fixed with https://github.com/joielechong/CountryCodePicker/commit/076f3b84e283df0cb48593cdccb84342edf4c392 commit.

Thanks :)


[FEAT] Code splitting

Every route should only have the code needed for it to run. This should be an option since it complicates deployment.

This should be optional, since it can impact performance, e.g. when a site has small number of requests and it makes sense to keep the function warm, or when the requests are expected to result in more requests (again, having the function warm is useful). Also, code splitting would only be good when the routes are large and the splitting actually makes the cold start faster, otherwise if it doesn't make the cold start any faster it's just fasting useful warm lambdas.


treewide: reduce assumptions made on runtime environment

This enables me personally to run this on NixOS.

Actually, development happens in the testsuite branch as of now. But anyways I rebased it onto the testsuite branch and applied it in both branches. Furthermore I switched the default branch to testsuite here, so pull requests are hopefully done against testsuite automagically next time. :)

Merged in 040a434.


Respect output settings from webpack config

This PR gives more control on the output settings. All files are still compiled to and read from memory, but this PR allows to use mocha-webpack with a plugin that writes files to disk at the desired location.
Use case is #203 and maybe #29.
Breaking changes:

use users output.filename if defined, otherwise use webpack's default
use users output.path if defined, otherwise mocha-webpack provides an path (.tmp as before)
use users output.publicPath if output.path is defined, otherwise if users output.path is missing, mocha-webpack provides an path

Codecov Report

Merging #222 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #222   +/-   ##
=====================================
  Coverage      97%    97%
=====================================
  Files          28     28
  Lines         767    767
=====================================
  Hits          744    744
  Misses         23     23

Impacted Files
Coverage Δ

src/runner/TestRunner.js
99.17% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Fix disconnection of magnesium acetate in covalent form.

Reference Issue
Fixes #5997
What does this implement/fix? Explain your changes.
Skips valence of -1 in metal valence list when patching charges after disconnection.
Any other comments?

It's a bit more complicated than that, it turns out.  More work being done.  The metal disconnector for
   {
        auto m(SmilesToMol("[O-]C(=O)C.[Mg+2][O-]C(=O)C", 0, false));
        MolOps::sanitizeMol(*m, failedOp, MolOps::SANITIZE_CLEANUP);
        TEST_ASSERT(m);
        md.disconnect(*m);
        std::cout << MolToSmiles(*m) << std::endl;
        TEST_ASSERT(MolToSmiles(*m) == "CC(=O)[O-].CC(=O)[O-].[Mg+2]");
    }

gives CC(=O)[O-].CC(=O)[O-].[Mg+3] which is an unconventional valence for Mg.
More work incoming.

@DavidACosgrove : this is very difficult to review since your IDE/editor has reformatted all the code.
Please reformat the code with clang-format (and maybe look at the configuration of your IDE to tell it to either use clang-format or to at least use the .clang-format information that's in the repo)


Add SASL Mechanisms DH-Blowfish and DH-AES

Presently, we only support plain SASL authentication, which sends credentials base 64 encoded. DH-AES is the preferred method of authentication. DH-Blowfish should be included for legacy networks until DH-AES is more widely deployed.

This issue should be closed since: Atheme dropped support for it (https://github.com/atheme/atheme/commit/15f6d84), the mechanisms are non-standard, and they provide no benefit over PLAIN authentication.


Add notes about Windows performance improvements for VirtualBox and Vagrant

Now that I have a Windows laptop (Lenovo ThinkPad T420 with 8GB RAM and upgraded SSD), I am doing some preliminary work testing different configurations, synced folder methods, etc. I'd like to document some tips and tricks specific to Windows users in the docs, so I'm leaving this issue open until I feel I've added as much as I can.
I don't want the poor Windows users to have to suffer through page loads 2x+ longer than Mac/Linux!

Did some initial informal testing with SMB vs. native shared folders in VirtualBox, and my results were a bit inconclusive. I'll need to do a bit more work to find some meaningful benchmark data.
Also, I had some trouble using NFS with the vagrant-winnfsd plugin and Windows 10, but I've since rebuilt the PC with a fresh copy of Windows 10, and I'd like to take another stab and see if NFS is more stable than SMB or native.

The winnfsd plugin has had some ups and downs. There was a point where it worked well, then a bug was introduced where it wasn't syncing right, and now it feels hit or miss..

I've added what I could think of so far. Other than that, if I (or anyone else) can think of more performance enhancements or gotchas to document, please open specific issues.


Add SchemaPropertyFetcher class

To retrieve and inspect al, the properties appearing in the issues tab.

@darecoder This is still marked as a Draft. When it's ready for review, please let us know.

@wetneb Thanks for the help!


style entry page

At present, the entry page on mobile devices looks like

Align the title and area for nickname at the center of page i.e. align the jumbotron properly.

@LalitNM I can fix this.

Go ahead and read contribiting guidelines to get an idea about how to self-assign this issue.

@kpbot claim


Replace base64 with data-encoding

Out of curiosity, what is the motivation behind this change?
The crate base64 seems well-maintained, is it a performance reason?

https://github.com/marshallpierce/rust-base64/issues/213


Saving input adds extra new line char

I was doing the 2018 day 5 challenge and my code didn't work. The problem was that the input file downloaded with aoc-cli had a newline at the end. Removing the newline fixed the issue.
Now I don't know if this can be considered a bug, since if I download the input with the browser, there is also a newline at the end. But if I copy-paste it, there isn't one. So I would understand if you reject this bug :-)
Nevertheless IMHO, the client should make it as easy as possible for developers, and so removing this newline would make sense I feel.

FWIW another AoC tool, "cargo-aoc" does such trimming. Here is even the issue where they switched from trim() to trim_end_matches('\n')


WebSocket problems

Today I updated the new version v0.98.0
When I using SSL:
WebSocket connection to 'wss://www.extratown.com:8443/' failed: Error during WebSocket handshake: Unexpected response code: 502
(https://www.extratown.com/webtorrent/download/public/2016/08/13/sintel.mp4)
When I without SSL:
WebSocket connection to 'ws://extra.town:8080/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
WebSocket connection to 'wss://extra.town:8443/' failed: WebSocket opening handshake was canceled
(http://extra.town/webtorrent/download/public/2016/08/13/sintel.mp4)

This is my problem, the tracker server is not available...


Create 'Species of Interest' input for percent coral cover

For percent coral cover by locality/year plot...
Create a user input widget where users can select a coral species of interest
The plot will filter to only show data related to the species of interest
By default, set to [none]

Done:
Commit 29df93f3b74d3e0c29af1f31457d5898741052d7


[AIRFLOW-2224] Add support for CSV files in mysql_to_gcs contrib oper…

JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-XXX

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

Adds support to export files in CSV format, including all traditional CSV formatting options

Column names in first row
Delimiter selection
Quote character selection
Character escape selection
Line termination character selection

Uses unicodecsv to handle all CSV formatting nuances.
Done through adding an additional parameter 'export_format' that defaults to 'json' (for retro-compatibility).
Parameter is a dictionary with muliple key-value pairs, see component documentation for details.
CSV file format is also split into multiple parts (as JSON).
Correct mime type 'application/csv' set when uploading to GCS.
Header is included in all parts (if muliple parts required).
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
No current test exists for the mysql_to_gcs operator, or any mysql hook. This also should be addressed by adding sample mysql database and increase test coverage.

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

[x] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

@bnajlis Could you add a test?

Sure, need to investigate a bit Airflow's testing infrastructure. Where can I reach out for documentation or support on this?

Added the tests, but every single travis-ci test run has come back with different non-deterministic errors or failures, none of them related to my code changes... How can I get this fixed?

Could you squash your commits, this will trigger Travis once more. I'll look into the failing tests.

Codecov Report

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

@@            Coverage Diff             @@
##           master    #3139      +/-   ##
==========================================
+ Coverage   72.98%   73.43%   +0.45%
==========================================
  Files         180      191      +11
  Lines       12654    14346    +1692
==========================================
+ Hits         9235    10535    +1300
- Misses       3419     3811     +392

Impacted Files
Coverage Δ

airflow/utils/state.py
93.33% <0%> (-3.34%)
:arrow_down:

airflow/utils/db.py
34.42% <0%> (-2.42%)
:arrow_down:

airflow/configuration.py
82.57% <0%> (-2.41%)
:arrow_down:

airflow/utils/dag_processing.py
87.55% <0%> (-0.89%)
:arrow_down:

airflow/jobs.py
79.37% <0%> (-0.27%)
:arrow_down:

airflow/www/views.py
71.56% <0%> (-0.14%)
:arrow_down:

airflow/models.py
87.21% <0%> (-0.12%)
:arrow_down:

airflow/settings.py
81.9% <0%> (ø)
:arrow_up:

airflow/exceptions.py
100% <0%> (ø)
:arrow_up:

airflow/www_rbac/app.py
96.38% <0%> (ø)

... and 13 more

Continue to review full report at Codecov.

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

Please squash into a single commit :-)

Can you resolve conflicts and rebase master?


Dev/2.0.0

Coverage increased (+5.8%) to 86.632% when pulling b88c19d2a34f646b598c533907f07899b667b638 on dev/2.0.0 into 0f3a5ff59f343ad518a73a23ada1b09569fa9b15 on master.


Implement a data grid

data-grid is a client-side pattern to render list data. we might want to consider using some existing solutions or implement our own. To my experience existing solutions are either paid or not easy to use. This task might involve some thinking/investigation stage.
Some acceptance criteria:

should be modular consisting of a data only react hook and a generic list component (using the hook) accepting a row template
should be implementing pagination on both the hook level and component level

The hook might look smth like:
function useDataGrid<T extends any>({ endpoint: string, params: QueryParams }): {
  data: T,
  isLoading: boolean,
  ...other state props,
  pagination: {
    hasNextPage: boolean,
    hasPreviousPage: boolean,
    nextPage: () => void,
    previousPage: () => void,
  }
}

The component interface might be accepting a template component or columns config with data getter, actions, etc.

I am not sure how much react-table/react-query is being used but it feels like this implies re-implementing logic on a solved problem. If this is just a higher layer hook, I would suggest ensuring your just creating reusable abstractions/lego's.

@pcfreak30 I'm 100% for smth ready to use if it would apply to our use cases. As it's mentioned this task would require some investigation stage.
React table looks like smth we could use, so I'd say this would be smth to test for sure before jumping into own implementation.


added equivalence test for nnx.Sequential

added equivalence test for nnx.Sequential

Codecov Report
Attention: Patch coverage is 0% with 22 lines in your changes are missing coverage. Please review.

Project coverage is 0.00%. Comparing base (2c7d7cd) to head (93a7c79).
Report is 46 commits behind head on main.

Files
Patch %
Lines

flax/experimental/nnx/tests/test_helpers.py
0.00%
22 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #3935       +/-   ##
==========================================
- Coverage   60.43%   0.00%   -60.44%
==========================================
  Files         105     101        -4
  Lines       13263   13139      -124
==========================================
- Hits         8015       0     -8015
- Misses       5248   13139     +7891

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


[Doc] Modules Update

This pull request has automatically created by PinpointAutoBot
Updated Item : [cxf-rt-rs-client] has been updated
*Updated item list may differ if this PR is updated*

Codecov Report

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

@@            Coverage Diff             @@
##           master    #7256      +/-   ##
==========================================
+ Coverage   39.22%   39.24%   +0.01%
==========================================
  Files        3299     3299
  Lines       95835    95835
  Branches    11841    11841
==========================================
+ Hits        37595    37610      +15
+ Misses      55326    55304      -22
- Partials     2914     2921       +7

Impacted Files
Coverage Δ

...p/pinpoint/rpc/client/WriteFailFutureListener.java
56.25% <0.00%> (-18.75%)
:arrow_down:

...vercorp/pinpoint/rpc/packet/ServerClosePacket.java
52.00% <0.00%> (-16.00%)
:arrow_down:

...rp/pinpoint/rpc/server/PinpointServerAcceptor.java
84.10% <0.00%> (-4.64%)
:arrow_down:

...rc/main/java/com/navercorp/pinpoint/test/Item.java
70.00% <0.00%> (-3.34%)
:arrow_down:

...tor/metric/datasource/DefaultDataSourceMetric.java
75.00% <0.00%> (-3.13%)
:arrow_down:

...om/navercorp/pinpoint/rpc/codec/PacketDecoder.java
57.44% <0.00%> (-2.13%)
:arrow_down:

...java/com/navercorp/pinpoint/rpc/DefaultFuture.java
72.50% <0.00%> (-1.67%)
:arrow_down:

...pinpoint/profiler/monitor/DeadlockMonitorTask.java
18.60% <0.00%> (-1.17%)
:arrow_down:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
78.39% <0.00%> (-1.05%)
:arrow_down:

...point/rpc/client/DefaultPinpointClientHandler.java
72.07% <0.00%> (-0.33%)
:arrow_down:

... and 10 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #7256 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #7256      +/-   ##
==========================================
- Coverage   39.01%   38.98%   -0.03%
==========================================
  Files        3321     3321
  Lines       95988    95966      -22
  Branches    11865    11864       -1
==========================================
- Hits        37445    37413      -32
- Misses      55633    55643      +10
  Partials     2910     2910

Impacted Files
Coverage Δ

...vercorp/pinpoint/rpc/packet/ServerClosePacket.java
52.00% <0.00%> (-16.00%)
:arrow_down:

...p/pinpoint/rpc/stream/StreamChannelRepository.java
75.00% <0.00%> (-10.00%)
:arrow_down:

...a/com/navercorp/pinpoint/web/scatter/DotGroup.java
60.00% <0.00%> (-9.24%)
:arrow_down:

...rp/pinpoint/rpc/server/PinpointServerAcceptor.java
84.10% <0.00%> (-4.64%)
:arrow_down:

.../com/navercorp/pinpoint/web/scatter/DotGroups.java
55.69% <0.00%> (-4.52%)
:arrow_down:

...navercorp/pinpoint/rpc/common/SocketStateCode.java
82.92% <0.00%> (-2.44%)
:arrow_down:

...cluster/zookeeper/ZookeeperClusterDataManager.java
52.90% <0.00%> (-1.94%)
:arrow_down:

...rcorp/pinpoint/web/scatter/ScatterDataBuilder.java
70.37% <0.00%> (-1.56%)
:arrow_down:

...point/rpc/client/DefaultPinpointClientHandler.java
72.40% <0.00%> (+0.32%)
:arrow_up:

...pinpoint/profiler/monitor/DeadlockMonitorTask.java
19.76% <0.00%> (+1.16%)
:arrow_up:

... and 3 more

Continue to review full report at Codecov.

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


pods install failed

pods install failed
Installing SDWebImage (3.7.2)
Using SVWebViewController (1.0)
Using UMengAnalytics (3.5.8)
Using UMengFeedback (2.3.3)
Installing libwebp (0.4.3)
[!] Pod::Executable clone https://chromium.googlesource.com/webm/libwebp /Users/yangeric/Library/Caches/CocoaPods/Git/20a7e0caa11500cb6a6e030259d3b3f9a29eea77 --mirror

Cloning into bare repository '/Users/yangeric/Library/Caches/CocoaPods/Git/20a7e0caa11500cb6a6e030259d3b3f9a29eea77'...
fatal: unable to access 'https://chromium.googlesource.com/webm/libwebp/': Failed to connect to chromium.googlesource.com port 443: Operation timed out

the operation timed out when trying to clone the libwebp repository as i can see from your post.
I tried it just now and it works just fine.

I have the same error @ygweric @mythodeia

i have the error :
Installing OpenUDID (1.0.0)
Installing SDWebImage (3.8.2)
Installing libwebp (0.5.0)
[!] Error installing libwebp
[!] /usr/bin/git clone https://chromium.googlesource.com/webm/libwebp /var/folders/0c/rt1dny3d64qfrncb1yq22_rc0000gn/T/d20161103-3177-11xvrzp --template= --single-branch --depth 1 --branch v0.5.0
Cloning into '/var/folders/0c/rt1dny3d64qfrncb1yq22_rc0000gn/T/d20161103-3177-11xvrzp'...
fatal: unable to access 'https://chromium.googlesource.com/webm/libwebp/': Failed to connect to chromium.googlesource.com port 443: Operation timed out

I have the same error:
fatal: unable to access 'https://github.com/rs/SDWebImage.git/': Failed to connect to apn.huanhuba.com port 8800: Operation timed out

@johnzhu12 this is a problem with your network setup. Not sure how to help you here.

refer to http://blog.csdn.net/dengbin9009/article/details/71125250


是已经不能用了么，请问现在有没有新的替代品

1203To protect your account, logging in to WeChat via the web has been suspended. Use WeChat for Windows or WeChat for Mac to log in on a computer. Download WeChat for Windows or Mac at http://wechat.com.

可以看下这个 缺点是收费 https://wkteam.gitbook.io/api/