Adjust Brightness Separately On Mac Touch Bar Has An Unexpected behaviour

Before opening the issue, have you...?

[X] Searched for existing issues
[X] Looked through the wiki
[X] Updated MonitorControl to the latest version (if applicable)

Describe the bug
On the touch bar of newer Macs the adjust brightness for only one screen using the "Control" key is only working when the adjust brightness key is on the left:

But not when it is on the right:

Steps to reproduce
I recorded a 30 second video where I do 3 steps.

Pressing the brightness button will change and synchronise both the laptop and external display's brightness. This works as expected.
From here trying to change only the laptop's brightness but not the one on the external display. Pressing the brightness slider on the touch bar (when it appears on the right of the bar) together with the "Control" key still changes both screens' brightness.
However when the brightness button is on the very left of the touch bar and it is pressed together with the "Control" key, the behaviour is the expected one: aka that only the laptop's brightness is changed.

Expected behavior
Explained above
Anything else?
No response
Environment Information (please complete the following information)
- macOS version: 12.1
- Mac model: M1, 2020
- MonitorControl version: 4.0.2 build 6965
- Monitor(s): Dell S2419H
- Apple Silicon/M1 (yes or no): yes

Hi @josep11 - Sadly Touch Bar sliders are not supported and won't be supported. There is however some limited support via the ability of syncing internal display brightness changes over to external displays. This does not read the slider itself, the change in the external display happens because of the syncing (the same way as when the brightness is changed by the ambient light sensor).
If your issue is that the internal display brightness change affects the external display change in this indirect way, you need to disable Sync brightness changes from Built-in and Apple dispalys (this option is not enabled by default, but is probably enabled in your setup).
Let me know if this helps!

Hi @josep11 - Sadly Touch Bar sliders are not supported and won't be supported. There is however some limited support via the ability of syncing internal display brightness changes over to external displays. This does not read the slider itself, the change in the external display happens because of the syncing (the same way as when the brightness is changed by the ambient light sensor).
If your issue is that the internal display brightness change affects the external display change in this indirect way, you need to disable Sync brightness changes from Built-in and Apple dispalys (this option is not enabled by default, but is probably enabled in your setup).
Let me know if this helps!

Hi @waydabber, thanks for the quick reply. Alright I understand. Actually, today it's my first day with a Mac with slider (the company one) and I think the slider is more of a nuisance than anything else hehe
It is fine, as there is the workaround and I can 1. control the brightness of the external display with the Mac and then 2. turn off my laptop's display, then everything is perfect. The app is great, by the way. Thanks!


Added Readme file for Gif Creator

Title and Issue number
To add a Readme file for Gif Creator Python Project,  #1530
Close #1692
by merging this pull request
Checklist:

[] I have mentioned the issue number in my Pull Request.
[] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md

@pranjay-poddar I have successfully pulled request for adding the readme file for gif creator python project please merge my request to complete it , will be thankful to you for your reply

@pranjay-poddar please review my request

@pranjay-poddar Thanks


"write after end" crashes that happen on multiple clients simultaneously

This bug is fairly low-priority for me as my production setup can recover from it with no issue, but it seemed worth reporting.
Occasionally, one or more of my twitch-irc instances will simultaneously crash with the following error:
2015-04-23 22:32: error: [lfg-sublistener] CRASH: write after end

 Error: write after end
    at writeAfterEnd (/nodecg_directory/bundles/lfg-sublistener/node_modules/twitch-irc/node_modules/readable-stream/lib/_stream_writable.js:144:12)
    at DestroyableTransform.Writable.write (/nodecg_directory/bundles/lfg-sublistener/node_modules/twitch-irc/node_modules/readable-stream/lib/_stream_writable.js:192:5)
    at Socket.ondata (_stream_readable.js:520:20)
    at emitOne (events.js:82:20)
    at Socket.emit (events.js:166:7)
    at readableAddChunk (_stream_readable.js:145:16)
    at Socket.Readable.push (_stream_readable.js:109:10)
    at TCP.onread (net.js:508:20)

I'm assuming this is somehow caused by something received from twitch. What's strange is that it doesn't happen to all of my instances, only some of them. Perhaps it's somehow dependent on some kind of tick cycle.

that's the error i get when the module tries to reconnect after a disconnection.
reconnecting is pretty much useless (not working at all?), easier to just crash the whole app and start it over

TL;DR skip to the bold section for the one-line quick fix to bypass the fastReconnect issue
I've been having the same problem; periodic crashes with the same 'write after end' error, always following a reconnect request from TMI (though not immediately after; the last one I saw didn't crash until 255 seconds after the old connection was dropped, and sometimes it doesn't crash at all, though other problems occur in those cases where it does survive). When TMI sends the reconnect request (line 196 in v1.2.6 of 'twitch-irc/libraries/client.js'), it calls for a fast reconnect (line 586 in v1.2.6 of 'twitch-irc/libraries/client.js'), which attempts to hot swap in a new TMI socket by keeping the old socket open until the new one is established (aka it waits 25 seconds before dropping the old one).
For me, the new socket successfully authenticates (transparently), and pipes output back over from '_fastReconnectMessage' to '_handleMessage' after authentication, but doesn't re-join channels during the authentication period, and leaves the old socket's input connected instead of the new socket's input.
I've been able to reproduce the general issue by calling client._handleMessage({command:'RECONNECT',prefix:{isServer:true}})` (assuming it's being called form a source file in which this 'twitch-irc' module is requred as 'client'), but haven't been able to determine why it sometimes results in the 'write after end' error and other times just results in the twisted in/out pipe. Maybe someone else will see the root cause of the problem; but I wasn't able to find it in the time I spent looking for it.
Additional notes: during authentication, while it's looking for message command 372 to tell it when to join channels, it checks for (message.prefix === 'tmi.twitch.tv') instead of (message.prefix.isServer) (line 485 in v1.2.6 of 'twitch-irc/libraries/client.js') the way it normally does (since 'message.prefix' is an object, not a string; maybe it was a string in an older revision?), and never gets past this check. It also sees the old socket's current-channels list (maybe a closure problem but I can't tell), which causes it to think that it's already joined the channels (if it gets that far). If I push it to join channels, I can see that it receives data from the channels, but can't write to them after the old socket closes and the new one is piped.
As a temporary workaround, I was able to prevent the crash by replacing self.fastReconnect(); with self.disconnect();self.connect(); (line 198 in v1.2.6 of 'twitch-irc/libraries/client.js'). Natural reconnect requests only seem so happen every few days, so I had to test the fix by emulating it using the above method, but this change of line 198 appears to work (it'll go down for a few seconds when it tries to reconnect, but at least it's able to reconnect successfully now, and without crashing). This works because it's able to reconnect if it's manually called to connect, though only if preceded by a manual disconnect first.

hey @OurFlagIsMined ! thanks a lot for your efforts! But could you put up a pull request or a fixed fork or a gist? it'd be a lot easier. and the author could check it out as well...

Thanks @OurFlagIsMined  it worked

Hey @Lange  how do you manage to recover from this error ? I just have one instance of twitch-irc and it always crashes. A bit of help would be very appreciatted

@larzuk91 I setup a crash handler and force exit the process on any unhandled error. The process manager I use, pm2, then restarts it. Not ideal, but does the job for now. For example:
client.addListener('crash', function (message, stack) {
    console.error(stack);
    process.exit(1);
})

Thank you for your help @Lange I didn't know about that program, I'll give it a try


Add ability to pass connectivity options to gRPC client code

The current options argument is really the credentials argument passed to the gRPC client code. We need the ability to also pass in connectivity options, to control things like load balancing policy and client-side keep alive policy.

(FWIW, I intended to open this PR into our local fork first but Github defaulted to the base repository.)

Hello,
Thanks for the PR.
Published as 0.7.0.


MAIN B-19164 add Okta customer group id for each environment to chamber & update config files (MERGE AFTER MAIN B-18821)

Agility ticket
INTEGRATION BRANCH PR
This includes code from Dre's MAIN B-18821 PR. Merge this after that PR gets merged.
Summary
This PR does contain the code of a currently open PR to use the customer form to ensure functionality.
B-18915
A requirement of E-04903 is for a SC to be able to create a MilMove account for a customer.
Using the form in the PR above, we can call the backend to do three things:

Create the user
Create the service member
Create the Okta profile (if chosen to do so)

This PR does the following:

creates a new GHC API endpoint, POST /createCustomerWithOktaOption
adds okta user creation API url to provider.go
adds handler for createCustomerWithOktaOption endpoint
adds function within handler to create the okta user
adds model to payload conversion in model_to_payload.go
add Okta Go models for profile creation
minor UI formatting and changes to better handle backend changes
add flash message to search page and display on successful creation of a customer

How to test

Fire up client and server
Login as a service counselor
Search for a user that doesn't exist and click the Add Customer button at the bottom of the page
You should now see the form to create a customer (click "yes" for okta account creation)
Fill it out and call the API (prob best to have your debugger turned on)
Make sure all values are being passed into the backend and go through the flow
An okta account should now be created and you should get an activation email if you were using the<EMAIL_ADDRESS>method
Log out as a service counselor
Log into MilMove as a customer and click the Local Sign-in option
You should now see the email for the user you just created in the list
You can sign in as that user and create a move if ya want

Would you mind updating the description on this PR? Then I'll approve!

Would you mind updating the description on this PR? Then I'll approve!

Whoops. Copy/paste went rogue. There ya go.


import using SampleModule.forRoot()

In your example you import the sample module to the app module using:
imports: [
    BrowserModule,

    // Specify your library as an import
    SampleModule
  ],

This cause me "no provider error".
When I use forRoot, it solve the problem:
imports: [
    BrowserModule,

    // Specify your library as an import
    SampleModule.forRoot()
  ],

Btw,
Good work. really helpful project.

@MadUser — Thank you for reporting. I have updated the README file 👍
PS: thanks for the kind words!

Please, remember to update the NPMJS readme in order to keep the docs in sync (here the .forRoot() isn't specified.
Thank you for this awesome project, you just save me a lot of hours trying to make a library.

@Kangcor — I have released v10.1.1 to update the documentation on the NPM registry.
Thank you for reporting! 👍


Keep typeof when getting types of a class' properties

See this failing test case https://github.com/microsoft/flow2dts/commit/db58ceb278fb9b354ea5136e2d78b586e1640239

This bug tries to address the issue at
https://github.com/microsoft/flow2dts/blob/main/workbench/react-native/v0.63.3/outputs/ios/Libraries/Lists/VirtualizedSectionList.d.ts#L103
in workbench\react-native\v0.63.3\hint\hint.json there is
        "/Libraries/Lists/VirtualizedSectionList.js.flow": {
...
                "defaultProps": [
                    {
                        "row": 116,
                        "column": 29,
                        "type": "type",
                        "resolvedDecl": {
                            "row": 273,
                            "column": 6,
                            "local": "DefaultProps",
                            "type": "type"
                        }
                    }
                ],

It comes from workbench\react-native\v0.63.3\hint\Libraries\Lists\VirtualizedSectionList.hint.json
        {
            "source": {
                "row": 116,
                "column": 29,
                "local": "defaultProps"
            },
            "resolved": {
                "begin": {
                    "row": 273,
                    "column": 21
                },
                "end": {
                    "row": 283,
                    "column": 2
                },
                "libraryFolder": -1,
                "file": "/Libraries/Lists/VirtualizedList.js.flow"
            }
        },

The resolved object comes directly from calling flow get-def
While in workbench\react-native\v0.63.3\inputs\Libraries\Lists\VirtualizedList.js.flow we can see in line 273 it is:
type DefaultProps = {|
  disableVirtualization: boolean,
  horizontal: boolean,
  initialNumToRender: number,
  keyExtractor: (item: Item, index: number) => string,
  maxToRenderPerBatch: number,
  onEndReachedThreshold: number,
  scrollEventThrottle: number,
  updateCellsBatchingPeriod: number,
  windowSize: number,
|};

but defaultProps must be in line 375:
static defaultProps: DefaultProps,

This causes the hint file to mark defaultProps as type instead of value.
Need to try the command in cli directly, if it actually reports wrong result, then the only way to fix it immediately is to add an override.

This bug tries to address the issue at
https://github.com/microsoft/flow2dts/blob/main/workbench/react-native/v0.63.3/outputs/ios/Libraries/Lists/VirtualizedSectionList.d.ts#L103
in workbench\react-native\v0.63.3\hint\hint.json there is
        "/Libraries/Lists/VirtualizedSectionList.js.flow": {
...
                "defaultProps": [
                    {
                        "row": 116,
                        "column": 29,
                        "type": "type",
                        "resolvedDecl": {
                            "row": 273,
                            "column": 6,
                            "local": "DefaultProps",
                            "type": "type"
                        }
                    }
                ],

It comes from workbench\react-native\v0.63.3\hint\Libraries\Lists\VirtualizedSectionList.hint.json
        {
            "source": {
                "row": 116,
                "column": 29,
                "local": "defaultProps"
            },
            "resolved": {
                "begin": {
                    "row": 273,
                    "column": 21
                },
                "end": {
                    "row": 283,
                    "column": 2
                },
                "libraryFolder": -1,
                "file": "/Libraries/Lists/VirtualizedList.js.flow"
            }
        },

The resolved object comes directly from calling flow get-def
While in workbench\react-native\v0.63.3\inputs\Libraries\Lists\VirtualizedList.js.flow we can see in line 273 it is:
type DefaultProps = {|
  disableVirtualization: boolean,
  horizontal: boolean,
  initialNumToRender: number,
  keyExtractor: (item: Item, index: number) => string,
  maxToRenderPerBatch: number,
  onEndReachedThreshold: number,
  scrollEventThrottle: number,
  updateCellsBatchingPeriod: number,
  windowSize: number,
|};

but defaultProps must be in line 375:
static defaultProps: DefaultProps,

This causes the hint file to mark defaultProps as type instead of value.
Need to try the command in cli directly, if it actually reports wrong result, then the only way to fix it immediately is to add an override.

Note that hintFile.typeofs["X"][0].resolvedDecl.local doesn't have to be X because import and export could do renaming.

Note that hintFile.typeofs["X"][0].resolvedDecl.local doesn't have to be X because import and export could do renaming.

$ yarn flow get-def workbench/react-native/v0.63.3/inputs/Libraries/Lists/VirtualizedSectionList.js.flow 116 29
/Users/eloy/Code/ReactNative/flow2dts/workbench/react-native/v0.63.3/inputs/Libraries/Lists/VirtualizedList.js.flow:273:21,283:2

This answer is correct, because on the requested this line/column typeof VirtualizedList.defaultProps is referring to the type of VirtualizedList.defaultProps and the type is indeed defined at line 273.
Now if you add to e.g. line 114 a reference to the value VirtualizedList.defaultProps and then ask flow for the definition you get the value that you were referring to.
$ yarn flow get-def workbench/react-native/v0.63.3/inputs/Libraries/Lists/VirtualizedSectionList.js.flow 114 17
/Users/eloy/Code/ReactNative/flow2dts/workbench/react-native/v0.63.3/inputs/Libraries/Lists/VirtualizedList.js.flow:375:10,375:21

$ yarn flow get-def workbench/react-native/v0.63.3/inputs/Libraries/Lists/VirtualizedSectionList.js.flow 116 29
/Users/eloy/Code/ReactNative/flow2dts/workbench/react-native/v0.63.3/inputs/Libraries/Lists/VirtualizedList.js.flow:273:21,283:2

This answer is correct, because on the requested this line/column typeof VirtualizedList.defaultProps is referring to the type of VirtualizedList.defaultProps and the type is indeed defined at line 273.
Now if you add to e.g. line 114 a reference to the value VirtualizedList.defaultProps and then ask flow for the definition you get the value that you were referring to.
$ yarn flow get-def workbench/react-native/v0.63.3/inputs/Libraries/Lists/VirtualizedSectionList.js.flow 114 17
/Users/eloy/Code/ReactNative/flow2dts/workbench/react-native/v0.63.3/inputs/Libraries/Lists/VirtualizedList.js.flow:375:10,375:21

Need to revert this workaround once this is fixed: https://github.com/microsoft/flow2dts/commit/8dca9d841f51d0aea270905541d007ef67017a3b

Need to revert this workaround once this is fixed: https://github.com/microsoft/flow2dts/commit/8dca9d841f51d0aea270905541d007ef67017a3b

Today flow2hint copies everything from workbench/react-native/VERSION/inputs to workbench/react-native/VERSION/hints/__modified__/ with all typeof removed except for import typeof.
When a type is needed and there is typeof XXX, by running flow get-def on a modified version which is        XXX, it reports:
"Could not get definition for /Libraries/Lists/VirtualizedSectionList.js.flow:116:28\r\nNo possible types\r\n"

I could take this error as "this is not a type", which means "this is a value", to skip the next step which matches the result with declaration position list to determine what it actually is. Since the hint file only need to know "this is a value/type/class".

Today flow2hint copies everything from workbench/react-native/VERSION/inputs to workbench/react-native/VERSION/hints/__modified__/ with all typeof removed except for import typeof.
When a type is needed and there is typeof XXX, by running flow get-def on a modified version which is        XXX, it reports:
"Could not get definition for /Libraries/Lists/VirtualizedSectionList.js.flow:116:28\r\nNo possible types\r\n"

I could take this error as "this is not a type", which means "this is a value", to skip the next step which matches the result with declaration position list to determine what it actually is. Since the hint file only need to know "this is a value/type/class".

Related, but kinda the inverse; here an instance of Linking is being exported, but we convert it to if a class was being exported.

Related, but kinda the inverse; here an instance of Linking is being exported, but we convert it to if a class was being exported.

Need to revert override once this is fixed: https://github.com/microsoft/flow2dts/commit/2e43b4043b5ef44936b461ea98edab89d61e10fa


Login is throwing GENERIC "0 - POST request to https://unite.nike.com/login blocked"

I tried the code and used it on our own country's Nike website but I am getting this error upon clicking log-in.
Image goes like this.

Hi
I tested a few days back and DID NOT change NIKE_HOME_URL = "https://www.nike.com/login" - I get automatically redirected to https://www.nike.com/COUNTRYCODE/login
Hope it helps
J

I see this issue in the US as well. Bot may be clicking the "SIGN IN" button too quickly. In my testing, I added 5 second sleep statement before the SIGN IN click and I've yet to see the error dialog appear.
Also, when running the bot (without sleep statement), I eventually got to a state where I ran the bot multiple times and always saw that error dialog. I deleted all cookies related to Nike and the dialog went away. Might be something worth looking into if it can be figured out which cookie it and deleting it before logging in as a possible long term solution (if this in fact eradicates the dialog).

can you fix it now? i got the same problem as you

Can't this problem be solved?

someone solve this problem?
when i launch thi command:
driver.find_element_by_xpath("//input[@value='ACCEDI']").click()
the page respond me:


runtime: Feature-flag optional components

Would you like to work on this feature?
We'd be happy to help implement this when we understand what solution would be acceptable.
What problem are you trying to solve?
We use only kube::runtime::watcher from kube_runtime and incur unnecessary dependencies like dashmap which are only used by kube::runtime::reflector. I'd love to be able to avoid unnecessary dependencies. This helps reduce security alerts, compile times, and potential duplicate dependencies.
Describe the solution you'd like
The easiest solution is probably to add a kube_runtime/reflector feature that optionally enables the reflector (and dash map). This would have to be wired through the higher level Kube crate so we could opt-in to runtime without runtime-reflector.
Describe alternatives you've considered
Alternatively, we could split out a kube_watcher crate that is used by kube_runtime so we could opt into watcher without incurring the rest of the runtime dependencies. This might make things simpler than having to wrestle feature flags through kube; but I'm not sure of the appetite for changing the crate layout.
Specifically, I think the feature-flag approach would require disabling the reflector feature by default. The crate approach would allow the runtime crate to always enable the reflector.
Documentation, Adoption, Migration Strategy
No response
Target crate for feature
kube-runtime

I think it'd make sense to move watcher into kube_client. The question (and I think we discussed this before) would be how we want to integrate it into Api. Then again, maybe it'd make sense to just move the module wholesale as a first step, and wait with deeper integration for later?

watcher currently depends on runtime::utils::ResetTimerBackoff. should the utils (at least ResetTimerBackoff and try_flatten_*) also be moved into client?

ResetTimerBackoff and try_flatten_* would probably make sense to migrate, yes, though we have been talking about moving the API surface of those into some StreamExt trait. Maybe it would make sense to make use of the natural API break here to make that move as well?
Then again, the compatibility wrappers for that would be trivial anyway, so it would probably be fine to punt on it for now.

hm, i'm not entirely sure about this. kube-client is intended to mimic api features only, and the watch mechanisms is a little more runtime choice imo (especially if we have to port streambackoffs, our own events wrappers and flatten utils).
it might make more sense to put a default-enabled "cache" feature on kube to propagate into kube-runtime and have this cause a disabling of reflector and controller modules.

@clux I think the problem here is the interaction of default features... If kube has a feature cache which enables kube-runtime/controller, it enables kube-runtime by default. If kube-runtime enables this feature by default, I think there's functionally no way disable the feature when using kube.

Good point. I forgot that runtime was not a default feature. I guess the way to do it with features then would be as you have done.
It does mean that the main change here would be to default-disable controller and reflector modules. I am open to that, it's not always needed. WDYT @teozkr ?

Alternatively: we could simply drop the DashMap dependency in favor of a parking_lot::RwLock<HashMap<..>>? I'm doubtful that any controller is going to actually need particularly high-throughput/low-latency access.  We already take a parking lot dependency via tokio (because, in Linkerd, we enable this feature in tokio). This would satisfy our goals without the need to introduce additional feature flags.

I would also be open to experiments along that line. I have not been impressed with the speed of dashmap in even low frequency use environments.
Doing this might change the Store api though, and that might require since more diligent thinking (I have been wanting more methods available on that anyway).

So.. this is basically the reason that we don't expose the DashMap itself (or any references to the objects) from the Store. It was always more of a stopgap solution than something that I was super in love with.
Ideally, I'd love to see the backing store traitified, which should also help out the use-case of wanting more exposed access methods. In that case I'd be fine with seeing RwLock<HashMap> be the default implementation.
Barring that, I'd be fine with just switching out the backend implementation as long as we can have some idea of what the perf impact is.

I'd be fine with just switching out the backend implementation as long as we can have some idea of what the perf impact is.

My basic assumptions are:

there should only be noticeable perf hit when there is actual concurrent access (i.e., the lock is contended);
there will never actually be concurrent writes, since all updates are driven from a single watch/task;
concurrent reads should be pretty cheap, as long as they don't contend with a write;

because Store doesn't expose any guarded references, it's not possible for applications to cause a lock to be held indefinitely
the main concerns, then, are:

time spent hashing a key for lookups; and
time spent in allocation (e.g. cloning resources).

so, the primary difference we'd expect to see is in workloads where there is both heavy read-load and frequent writes.

we could mitigate some of the lock contention by:

changing the cache to store Arc<K> values so cloning is cheaper, but this would change the public API for reflector;
changing the map's hasher to FxHash or, more likely, AHash (since I think we probably want DoS-resistance).

we could also look at hashbrown::HashMap, which uses AHash by default

The dashmap authors provide benchmarking results, but I think we should be a little skeptical about these results in the context of a kubernetes controller where most operations are coupled with network operations where message deserialization is likely to outweigh any of the costs we encounter in map access.
This is all to say: if we want to go down the path of benchmarking this, we probably want to do so in the context of a full controller/application. My hunch is that microbenchmarks are not going to be very informative about actual performance characteristics.


Vim keymap support complete - resolves #1361

After @johnpryan 's question a couple days ago about vim support he made me aware of issue #1361 , so I have completed full support for the Vim keymap within codemirror.   There had been some question about the level of Vim support in the codemirror editor but during this little project I have tested it quite a bit and found it to be very complete. It pretty much does everything from basic to advance Vim.  I suspect that Vim coders will love codemirror's vim keymapping.
The changes required fell into 3 categories:

changes for codemirror to use the Vim keymap and to display and handle everything correctly/display nicely

Adding a switch to the keyboard dialog to allow toggling the Vim keymap.  This seemed like the logical place for this but others more knowledgeable than me may have better places.  (The keyboard icon button was too easy).
One the embed pages you must access this with Shift-Ctrl-/ to switch.   The user's settings are remembered in localstorage so for most Vim users this is one time thing and Vim will be active in all the dartpad pages they open.
I found this works very nicely for now and allows you to try this out, I welcome any other/better UI solutions/suggestions.

The embed-XXX.html/embed.dart files have been changed to use the same editor sharing scheme that index.html/playground.dart use.  This has many benefits in addition to making the vim keymap toggling work smoothly across all editors.

3) There is one thing that I am not totally happy with... in the embed html pages/embed.dart we have 5 separate editor instances.  When the user switches here I can only change the current editors setting (although localstorage is updates so subsequent loads will have correct keymapping active on all editors).   UPDATE:  I am going to make the embed pages use a single editor and 5 documents, similar to how index.html/playground.dart work.  This will completely resolve this problem and is much better architecture for the embed pages anyway.  UPDATE 2:  The embed pages now use a single shared editor like the playground page
#3 is the only weakness in this change that I have been able to determine from testing. embed single editor fix resolves this
The Vim support in CodeMirror has proven to be VERY nice, check it out!
Thanks @johnpryan for the inspiration to investigate this!

the conflicting change in  web/styles/cm-dartpad-dark.scss and web/styles/cm-dartpad-light.scss are updates to the PR#2186 change to use "width: auto" in the style instead of "width: 0.6em"  - I left this in this code accidently but it is a preferable change to the PR#2186 solution.  I can also submit it separately if that would be better.

I slept on it.. and in thinking about how to address #3 the real solution seems to be to bring the embed-XXXX.html / embed.dart pages into parity with the way index.html / playground.html work - and that is with a single editor and multiple documents within that editor.
playground_context.dart is used to manage this for the playground pages, so I am going to do the same for the embed pages and create a embed_context.dart which will allow the embed pages to use a single editor (instead of having 5 different editors!)
There seems to be many advantages to this..

Thanks for sending a pull request!

I have completed the consolidation of the 3 to 5 editors used in the embed-XXX/embed.dart pages.  Embed now essentially works like index.html/playground.dart  (a single editor with multiple documents is used to support all of the needed tabs/documents.
The embed version of the editor sharing also supports some of the documents being read only, while the others are not (for test and solution editors).
This also makes the pages work faster/less memory now because there is only 1 single editor initialized and existing in the DOM instead of the up to 3-5.
This update completely resolves issue 3) that I mentioned in the original pull comment.

You can give this pull request a try and try out the vim support here:
https://timmaffett.github.io/vim/?id=ed2b5ebfba33a4d7710a4c0772e099d0


Feature: Integrate Code Quality Tools for Enhanced Consistency

This pull request introduces ESLint, Prettier, and Husky into our development workflow. The integration of these tools serves to enforce a consistent coding standard across the project, ensuring that all contributions adhere to our defined styles and practices.
Key Changes:

ESLint: Setup to analyze the codebase for adherence to our coding standards, helping identify potential errors and code smells.
Prettier: Configured to automatically format code according to our specified styles, ensuring consistency in the appearance and structure of our code.
Husky: Employed to trigger ESLint and Prettier checks before committing changes, ensuring that only code that meets our quality standards is added to the repository.

These tools collectively contribute to a more maintainable and error-free codebase, streamlining the development process and enhancing collaboration efficiency.

@hkirat  this is right approach  ?

I might be wrong but we do alreay have husky, eslint and prettier

@devsargam We've updated and fine-tuned our existing Husky, ESLint, and Prettier configurations to enhance code consistency and automation further

With so many files touched, its difficult to review the changes which are done particularly for this PR.

@adexh  This PR mainly updates our ESLint, Prettier, and Husky setups. Most changes are automatic formatting, so please focus on the config updates

Linting can be a separate pr actually

@devsargam  umm ???

I mean a lot of files have been changed which makes ur pr hard to review. Can u revert all the linted files and only focus on what was changed actually?

Most changes are automatic formatting  !!!!

lets see I'll revert the formatting changes in the linted files to highlight the key updates made to our ESLint, Prettier, and Husky configurations, ensure the PR focuses only on the essential modifications. good ?

@devsargam is right, need to be saparate changes
Wholesale lint will probably happen when PRs are at 0 so that people don't have merge conflicts
Can you PR just the eslint changes and remove the automatically generated code?

@devsargam is right, need to be saparate changes Wholesale lint will probably happen when PRs are at 0 so that people don't have merge conflicts Can you PR just the eslint changes and remove the automatically generated code?

okk


clarifying and updating a few paths in code examples (#594)

Will merge later when I have a chance to redeploy docs as well.


[WIP] Translate all strings into react-intl components

Small refactoring

TODO

[ ] Schemas

@martinpovolny

@martinpovolny Everything (except the pagination, which is missing options how to do it) should be in translatable form. :earth_americas:  Can you please test in UI if everything is working? Thanks.


Deprecation warnings in django 1.9a1

Besides #278, I get this deprication warning with django 1.9a1 and django-bootstrap  6.2.2
[...]site-packages/bootstrap3/utils.py:144: RemovedInDjango110Warning: render() must be called with a dict, not a Context.
  return template.render(Context(context))

The naive solution is to remove Context() wrap from this line. When I do that, the warning then changes to:
[...]site-packages/bootstrap3/utils.py:144: RemovedInDjango110Warning: render() must be called with a dict, not a RequestContext.
  return template.render(context)

Which seems to be because of the bootstrap_messages template tag passing the context param unchanged.
Not sure how to fix that. Just wrapping it in dict() seems dirty.

Thanks for the notes, is there anything I should be concern with 1.8.2?

Found another Deprecation warning in Django 1.9a1:

RemovedInDjango20Warning: django.forms.extras is deprecated. You can find SelectDateWidget in django.forms.widgets instead.

Seems to be from the renderers.py ... Unfortunately, the SelectDateWidget is not available in django.forms.widgets in Django 1.8 :(

Django 1.8.6 raises RemovedInDjango110Warning when encounters {% bootstrap_messages %} in a template.

I think we got most of these. Closin gthis now. Please report any warning with 1 warning per issue. Thanks!


WFLY-5246 upgrade RESTEasy to 3.0.12.Final

Windows Build 2997 is now running using a merge of 502b7dd67070116fadb791c20a1fdb2098f78c83

Linux Build 7957 is now running using a merge of 502b7dd67070116fadb791c20a1fdb2098f78c83

Linux Build 7957 outcome was SUCCESS using a merge of 502b7dd67070116fadb791c20a1fdb2098f78c83
Summary: Tests passed: 3060, ignored: 359 Build time: 00:50:43

Windows Build 2997 outcome was SUCCESS using a merge of 502b7dd67070116fadb791c20a1fdb2098f78c83
Summary: Tests passed: 3060, ignored: 359 Build time: 00:52:14


Proposal: add input_data to top level of processing schema

It would be an array, and we would use this to refer to an input acquisition session name, processing result name, or model name.  Basically any data asset.

is the only property the data asset name?

yeah, was thinking it would just be an array of strings


SingenBD2 - Feedback bug

Hi,
I've noticed this "bug" using an oscillator with 0 pitchdiff and higher feedback (i.e. steady signal):
https://github.com/ryukau/UhhyouWebSynthesizers/blob/main/oldsynth/SingenBD2/index.js#L115
Since this.pitchDiff = 0, 0^x will always be the same, so feedback (i.e. mod var) will do nothing, but it should, since feedback is not related with pitch envelope (i just got a steady signal, without feedback influence).  Right?
Curious about your pitch env modelling: which kind of envelope is pitch = diff ^ env?
Thanks for any tips

Ah, the definition of $t$ was unnecessary. I deleted the notation for function of time, as it looked cluttered.

Yeah of course. Its clear the params.
What I'm trying to say is that given a 0 pitchdiff, the feedback has no effect on signal in fm mode (which should, since its a fm feedback).

I added a few other FM options. The name of original tuning is changed to "Muffled FM". Also, let me know if you have a concrete code for modulation tuning. I'll add it. Or you can open PR for that.
I also recommend to try the subsequent synths like Singen0.2 ("Bassdrum" randomization) and SingenBD3 ("Dry BD" randomization).
Updated UI looks ugly, but I wouldn't like to spend too much time dealing with the code in oldsynth. If you really care, patches are welcome. The best way is to port the synth to new style of code, but it's not my priority.


Draft of iterator and enumerator

Adding in iterator
Change API of storage.Find to return an iterator
Adding in enumerator

This can be referenced in issue #13


JMX metrics of alluxio local cache are missing in Presto's JMX connector

Alluxio Version:
2.6.1, 2.6.2
Describe the bug
JMX metrics of alluxio local cache are missing in Presto's JMX connector.
The values such as bytes_in_cache exposed by JMX are always 0.  But these values are good via jConsole.
To Reproduce
1 Start presto with local cache enabled
2 Run some queries
3. Try to query the jmx via the build-in jmx connector in Presto.
Expected behavior
We expect to see accurate (non-zero) values in the JMX metrics
Urgency
Normal
Additional context
Reported by Zou Fei and Zhang Ce.  Many thanks!

I tried this out with the jmx connector in Presto and I can see data. The caveat is that due to how Alluxio jmx metric keys are constructed, by default it would include the ip address of the node in the metric name. In jmx connector, these names are mapped to table names. For example, run SHOW TABLES IN jmx.current, and you will see table names like com.facebook.alluxio:name=client.cachebytesreadexternal.192_168_0_15,type=meters. Since different worker would have different ip addresses, this no longer works in aggregate. The way to work around it for now is to overwrite alluxio.user.app.id. For example, add -Dalluxio.user.app.id=test to runtime configuration will change the metric name to com.facebook.alluxio:name=client.cachebytesreadexternal.test,type=meters. This way run SELECT * from current."com.facebook.alluxio:name=client.cachebytesreadexternal.test,type=meters" should give all entries from all worker nodes.

Hi @FeiZou , I think @rongrong worked out a work around for you.  You could use -Dalluxio.user.app.id=test to override the ip/hostname in the metrics key, then the JMX connector should work as expected.

Thanks for the workaround @rongrong . I'm able to see many counters after using the workaround but "client.cachehitrate" is still missing. I can view this counter using jConsole. But not showing up in jmx.current tables.

Hey @rongrong for providing the workaround. I have the same doubt as @nmahadevuni that I cannot see the some important metrics like Client.CacheHitRate ,Client.CacheSpaceAvailable and Client.CacheSpaceUsed through JMX.current.

hi @beinan @rongrong : Unless we set the Presto coordinator also as worker(node-scheduler.include-coordinator=true), we cannot see counters like Client.CacheHitRate, Client.CacheBytesReadCache, Client.CacheBytesReadExternal, Client.CacheBytesRequestedExternal
Is there any workaround for this?

@FeiZou Client.CacheSpaceAvailable and Client.CacheSpaceUsed should be available. CacheHitRate is missing because it's currently not registered on Presto coordinator. JMX connector would only list the metrics that are visible on coordinator. I'll send out a PR to register cache hit rate on coordinator as well. @nmahadevuni any other metrics missing while I'm at it?

BTW, the fundamental culprit of this is that Presto's JMX connector (and all other connectors pretty much)'s metadata queries are running on coordinator only. Since the JMX metrics are mapped to tables, and table listing is a metadata query, listing tables would only run on coordinator, thus only listing all the metrics that are registered on coordinator. So if caching is not enabled on coordinator, you will not get any cache metrics. In that case, I'd suggest to not rely on jmx connector, but use other jmx monitoring tools.

The ones I mentioned above are the only metrics missing, I found rest of them are registered on coordinator too.


Allows to register Tracker subscribers that fire later than other ones

The INotificationConsumer subscribers of Tracker fire in the order they are registered. For CNDB however, we want to register subscribers that fire only after all the internal subscribers of C* have fired, as some of those do important jobs (like the SAIGroup one, which essentially make built index visible on flush) that we want to make sure happen first.
This patch adds a new Tracker.subscribeLaterConsumer, which is similar to the existing Tracker.subscribe, but the former guarantees that the consumers it registers all fire after the ones registered by the later.

I was wondering if we should add a “subscribe priority” or similar so you could pass a big number to go last and a small number to go first and no number to be in the middle.
Maybe it’s not worth going that far and “normal” and “at the end” are enough distinction here.

@JeremiahDJordan I think that proposed API is clear, and you don't have to bother with prioirities


[CI] Recover integration test by skipping certificate check

After skipping certificate check, CI integration test will be recovered with new private IP.
The reason is this IP is not yet included in the vCenter certificate.
Signed-off-by: Shuyang Xin<EMAIL_ADDRESS>

Codecov Report

Merging #3162 (a73678b) into main (c135609) will decrease coverage by 18.40%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main    #3162       +/-   ##
===========================================
- Coverage   58.76%   40.36%   -18.41%
===========================================
  Files         292      167      -125
  Lines       24724    20879     -3845
===========================================
- Hits        14530     8427     -6103
- Misses       8622    11630     +3008
+ Partials     1572      822      -750

Flag
Coverage Δ

kind-e2e-tests
?

unit-tests
40.36% <ø> (+0.21%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

 However the integration test is failed. Failure is not related to CI. It's test case TestNoteAction failing. Maybe ask help from developer who wrote this case.
https://jenkins.antrea-ci.rocks/job/antrea-auto-integration-for-pull-request/402/console

/test-latest-e2e

/test-latest-e2e

/test-latest-e2e

/test-e2e

/test-integration

/test-integration

/test-integration

/test-integration

/test-integration

/test-integration

/skip-networkpolicy
/skip-conformance


Improve the csv-chatbot sample

Closes: #472

There might be better APIs in  Hibernate for this, however I am not really knowledgeable in its internals


Update linker to support link dependencies

What was wrong?
linker was not adding link_dependencies to manifests of newly created deployments that contained link references.
How was it fixed?

Requires runtime_bytecode to be present in contract type in manifest
Yanks link_references from runtime_bytecode and uses those to populate link_dependencies data
Started to update docs to reflect changes in library

Cute Animal Picture

@pipermerriam ping in case this got lost in the noise


walkImportChain: Maximum call stack size exceeded

Describe the bug
When I save a js file that is being imported in a lot of places the HMR breaks
Reproduction
I'm trying to do a much simpler repository but I'm having a hard time reproducing it with a simple one
But here's one where it breaks: https://github.com/quickbookio/app
Just:
git clone
yarn
yarn dev

then go to http://localhost:3000/#/app and in your editor go to the src/js/store.js file for example and save
Also I checked there is no import loop (would be cool if it could detected and notified though 👍, rollup does it)
System Info

required vite version: latest
required Operating System: Mac OS 10.15.5
required Node version: v14.4

Logs (Optional if provided reproduction)
(node:19651) UnhandledPromiseRejectionWarning: RangeError: Maximum call stack size exceeded
    at walkImportChain (/Users/k/code/quickbook/app/node_modules/vite/dist/server/serverPluginHmr.js:144:25)
    at walkImportChain (/Users/k/code/quickbook/app/node_modules/vite/dist/server/serverPluginHmr.js:169:22)
    at walkImportChain (/Users/k/code/quickbook/app/node_modules/vite/dist/server/serverPluginHmr.js:169:22)
    at walkImportChain (/Users/k/code/quickbook/app/node_modules/vite/dist/server/serverPluginHmr.js:169:22)
    at walkImportChain (/Users/k/code/quickbook/app/node_modules/vite/dist/server/serverPluginHmr.js:169:22)
    at walkImportChain (/Users/k/code/quickbook/app/node_modules/vite/dist/server/serverPluginHmr.js:169:22)
    at walkImportChain (/Users/k/code/quickbook/app/node_modules/vite/dist/server/serverPluginHmr.js:169:22)
    at walkImportChain (/Users/k/code/quickbook/app/node_modules/vite/dist/server/serverPluginHmr.js:169:22)
    at walkImportChain (/Users/k/code/quickbook/app/node_modules/vite/dist/server/serverPluginHmr.js:169:22)
    at walkImportChain (/Users/k/code/quickbook/app/node_modules/vite/dist/server/serverPluginHmr.js:169:22)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:19651) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:19651) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I noticed the load speed issue of the project is largely due to slow style insertion because of the huge tailwind css file, but that's a separate issue...

It's a bit slow indeed but still faster than my previous setup with rollup !
Hope that you guys will find a solution to make it faster 👍


Multiple production_environment

Describe the Issue
I've got a scenario where I have multiple production environments all managed in the same environment.
There doesn't seem to be a way to have multiple production environments managed within the same repository?  While there are ways to have multiple environments, it feels that the production_environment is meant for the main one?
Does it make sense to just set production_environment to something obscure if you have multiple production environments?
Action Configuration
No response
Relevant Actions Log Output
No response
Extra Information
No response

@mnaser have you read the little bitsof docs that float around about this variable here?
This variable effectively is just used to tell the GitHub API when a deployment starts if it is the "production" env or not.
You can read more about this variable in the official GitHub docs as well (see screenshot)

The majority of the use cases I have seen for this value is when users have a unique env name and they need to overwrite it. For example, if you call production something else like prd, or prod then you would want to use this variable.
That being said, I have actually not come across this use case that is yours yet. Please do some tinkering, swap around this variable, set it to something obscure, etc. Let me know the results here and how it works for you! If it doesn't work out well, I'll look into creating a solution. Thanks! 🙇

@GrantBirki thanks!! i'm playing around with it, I actually do not have a single "production" environment in this case, so I left it set to production and trying to play with it on how it will end up working.
So far, so good, I haven't seen anything wild, the only thing is that  if someone does .deploy with no target, it will deploy try to production and inevitably fail because that 'environment' doesn't exist... i think the nice thing I'm thinking about would be if there's a way to have a bool that says "enforce_env" or something like that, so users MUST have an environment in their .deploy command

@mnaser Would you be able to copy / paste or link to your branch-deploy configuration? I'm curious about what settings you have.

I think the solution here is to have production_environment become production_environments (with an s). Then this value would accept a comma separated list of strings -> beep,boop. The branch-deploy Action would then mark beep and boop as production environments when making deployment requests.
This would fix the problem at hand for you and likely all other users in the future.
The only issue is that this would be a pretty significant breaking change as the input variable would change values by adding that trailing "s". However, I think we can show deprecation messages in the logs and push a v8.0.0 tag.

@mnaser Please go ahead and give the pre-release tag v8.0.0 a go and let me know how it works! :rocket:

@GrantBirki worked beautifully, thank you.


access the actual data-object that is being dragged

Hi
I am trying to make confirmation dialog have some values from the object that is being dragged and using onDrop and beforeDrop, but they seem to not have the information about the object.
Is it possible to get an example?
Thank you.

Hey, did you find anything about your issue ? I'm trying to get the current dragged obj clone to add some attributes in order to add css class on it.

Hey, may be you can try something with onStart like storing your dragged obj in your scope then reused this on onDrop event.

@elarion, what I did was added a beforeDrop on draggable element, passing index, then cloning the object before showing the model, user then changes some attributes of the object from fields in model and when they hit submit, I reject the promise, but add the new object into array manually. so it looks like object was dropped and not cancelled.

here is my beforedrop handler
beforePersonDrop = function (event, ui, id) {
    var _this = this,
      person = _.cloneDeep(_this.people[id]),
      modalInstance,
      defer = prvt.$q.defer();

    modalInstance = $uibModal.open({
      templateUrl: "partials/model.html",
      backdrop: "static",
      controller: "controllers.ModelCtrl",
      controllerAs: "ctrl",
      resolve: {
        person: function () {
          return person;
        }
      }
    });
    modalInstance.result.then(function (person) {
        _this.list4.push(person);
      defer.reject();
    }, function () {
      defer.reject();
    });
    return defer.promise;
  }

and draggable property:
jqyoui-draggable="{index: {{$index}}, animate: true, placeholder: 'keep', beforeDrop: 'ctrl.beforePersonDrop($index)'}"


cardano-db-sync-extended sync stopps at the same point every time after upgrade to 9.0.0

After upgrading from 8.0.0 to 9.0.0, the cardano-db-sync-extended is not working anymore.
This is the point where the problem occurs:
Rolling back to SlotNo 4492289, hash 428b01626de393dff5c41916ec07be1b307213bc750dbf2ec0cadb5f9e8c2247

This is the upgraded version:
cardano-db-sync-extended --version
cardano-db-sync-extended 9.0.0 - linux-x86_64 - ghc-8.10
git revision 0b054e18aec3b1e387a1c7b713c562ade37417a3

I dropped the postgres database a few times and restarted the service, the result is the same.
I also downgraded cardano-node from 1.26.2 to 1.25.1, same result (with fresh empty database).
The postgresql version is the same as before the upgrade:
psql (11.11 (Debian 11.11-0+deb10u1))

The logs:
Apr 19 00:38:52 cardano4 bash[79188]: [db-sync-node:Info:4349] [2021-04-18 21:38:52.52 UTC] Starting epoch 208
Apr 19 00:38:52 cardano4 bash[79188]: [db-sync-node:Error:4349] [2021-04-18 21:38:52.64 UTC] runDBThread: DbInsertException "AdaPots" (SqlError {sqlState = "42P01", sqlExecStatus = FatalError, sqlErrorMsg = "relation \"ada_pots\" does not exist", sqlErrorDetail = "", sqlErrorHint = ""})
Apr 19 00:38:52 cardano4 bash[79188]: [db-sync-node:Error:4352] [2021-04-18 21:38:52.65 UTC] recvMsgRollForward: AsyncCancelled
Apr 19 00:38:52 cardano4 bash[79188]: [db-sync-node:Error:4345] [2021-04-18 21:38:52.65 UTC] ChainSyncWithBlocksPtcl: DbInsertException "AdaPots" (SqlError {sqlState = "42P01", sqlExecStatus = FatalError, sqlErrorMsg = "relation \"ada_pots\" does not exist", sqlErrorDetail = "", sqlErrorHint = ""})
Apr 19 00:38:52 cardano4 bash[79188]: [db-sync-node.Mux:Info:4342] [2021-04-18 21:38:52.65 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/home/cardano/cardano-node/db/socket"} event: State: Dead
Apr 19 00:38:52 cardano4 bash[79188]: [db-sync-node.Mux:Notice:4342] [2021-04-18 21:38:52.65 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/home/cardano/cardano-node/db/socket"} event: Miniprotocol MiniProtocolNum 5 InitiatorDir terminated with exception DbInsertException "AdaPots" (SqlError {sqlState = "42P01", sqlExecStatus = FatalError, sqlErrorMsg = "relation \"ada_pots\" does not exist", sqlErrorDetail = "", sqlErrorHint = ""})
Apr 19 00:38:52 cardano4 bash[79188]: [db-sync-node.Subscription:Error:4341] [2021-04-18 21:38:52.65 UTC] Identity Application Exception: LocalAddress "/home/cardano/cardano-node/db/socket" DbInsertException "AdaPots" (SqlError {sqlState = "42P01", sqlExecStatus = FatalError, sqlErrorMsg = "relation \"ada_pots\" does not exist", sqlErrorDetail = "", sqlErrorHint = ""})
Apr 19 00:38:52 cardano4 bash[79188]: [db-sync-node.ErrorPolicy:Error:4] [2021-04-18 21:38:52.65 UTC] IP LocalAddress "/home/cardano/cardano-node/db/socket" ErrorPolicyUnhandledApplicationException (DbInsertException "AdaPots" (SqlError {sqlState = "42P01", sqlExecStatus = FatalError, sqlErrorMsg = "relation \"ada_pots\" does not exist", sqlErrorDetail = "", sqlErrorHint = ""}))
Apr 19 00:38:53 cardano4 bash[79188]: [db-sync-node.Subscription:Notice:45] [2021-04-18 21:38:53.65 UTC] Identity Restarting Subscription after 15.211932397s desired valency 1 current valency 0
Apr 19 00:38:53 cardano4 bash[79188]: [db-sync-node.Subscription:Notice:45] [2021-04-18 21:38:53.65 UTC] Identity Starting Subscription Worker, valency 1
Apr 19 00:38:53 cardano4 bash[79188]: [db-sync-node.Subscription:Notice:4371] [2021-04-18 21:38:53.65 UTC] Identity Connection Attempt Start, destination LocalAddress "/home/cardano/cardano-node/db/socket"
Apr 19 00:38:53 cardano4 bash[79188]: [db-sync-node.Subscription:Notice:4371] [2021-04-18 21:38:53.65 UTC] Identity Connection Attempt End, destination LocalAddress "/home/cardano/cardano-node/db/socket" outcome: ConnectSuccessLast
Apr 19 00:38:53 cardano4 bash[79188]: [db-sync-node.Handshake:Info:4371] [2021-04-18 21:38:53.65 UTC] WithMuxBearer (ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/home/cardano/cardano-node/db/socket"}) Send (ClientAgency TokPropose,MsgProposeVersions (fromList [(NodeToClientV_1,TInt 764824073),(NodeToClientV_2,TInt 764824073),(NodeToClientV_3,TInt 764824073),(NodeToClientV_4,TInt 764824073),(NodeToClientV_5,TInt 764824073),(NodeToClientV_6,TInt 764824073),(NodeToClientV_7,TInt 764824073),(NodeToClientV_8,TInt 764824073)]))
Apr 19 00:38:53 cardano4 bash[79188]: [db-sync-node.Handshake:Info:4371] [2021-04-18 21:38:53.65 UTC] WithMuxBearer (ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/home/cardano/cardano-node/db/socket"}) Recv (ServerAgency TokConfirm,MsgAcceptVersion NodeToClientV_8 (TInt 764824073))
Apr 19 00:38:53 cardano4 bash[79188]: [db-sync-node.Mux:Info:4371] [2021-04-18 21:38:53.65 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/home/cardano/cardano-node/db/socket"} event: Handshake Client end, duration 0.001854432s
Apr 19 00:38:53 cardano4 bash[79188]: [db-sync-node.Mux:Info:4372] [2021-04-18 21:38:53.65 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/home/cardano/cardano-node/db/socket"} event: State: Mature
Apr 19 00:38:53 cardano4 bash[79188]: [db-sync-node:Info:4375] [2021-04-18 21:38:53.65 UTC] Starting chainSyncClient
Apr 19 00:38:53 cardano4 bash[79188]: [db-sync-node:Info:4375] [2021-04-18 21:38:53.67 UTC] Cardano.Db tip is at slot 4492289, block 4490000
Apr 19 00:38:53 cardano4 bash[79188]: [db-sync-node:Info:4379] [2021-04-18 21:38:53.67 UTC] Running DB thread
Apr 19 00:38:53 cardano4 bash[79188]: [db-sync-node.Subscription:Notice:45] [2021-04-18 21:38:53.67 UTC] Identity Required subscriptions started
Apr 19 00:38:53 cardano4 bash[79188]: [db-sync-node:Info:4379] [2021-04-18 21:38:53.88 UTC] Rolling back to SlotNo 4492289, hash 428b01626de393dff5c41916ec07be1b307213bc750dbf2ec0cadb5f9e8c2247
Apr 19 00:38:53 cardano4 bash[79188]: [db-sync-node:Info:4379] [2021-04-18 21:38:53.88 UTC] No Rollback is necessary
Apr 19 00:39:04 cardano4 bash[79188]: [db-sync-node:Info:4379] [2021-04-18 21:39:04.52 UTC] Starting epoch 208
Apr 19 00:39:04 cardano4 bash[79188]: [db-sync-node:Error:4379] [2021-04-18 21:39:04.69 UTC] runDBThread: DbInsertException "AdaPots" (SqlError {sqlState = "42P01", sqlExecStatus = FatalError, sqlErrorMsg = "relation \"ada_pots\" does not exist", sqlErrorDetail = "", sqlErrorHint = ""})
Apr 19 00:39:04 cardano4 bash[79188]: [db-sync-node:Error:4382] [2021-04-18 21:39:04.69 UTC] recvMsgRollForward: AsyncCancelled
Apr 19 00:39:04 cardano4 bash[79188]: [db-sync-node:Error:4375] [2021-04-18 21:39:04.69 UTC] ChainSyncWithBlocksPtcl: DbInsertException "AdaPots" (SqlError {sqlState = "42P01", sqlExecStatus = FatalError, sqlErrorMsg = "relation \"ada_pots\" does not exist", sqlErrorDetail = "", sqlErrorHint = ""})
Apr 19 00:39:04 cardano4 bash[79188]: [db-sync-node.Mux:Info:4372] [2021-04-18 21:39:04.69 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/home/cardano/cardano-node/db/socket"} event: State: Dead
Apr 19 00:39:04 cardano4 bash[79188]: [db-sync-node.Mux:Notice:4372] [2021-04-18 21:39:04.69 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/home/cardano/cardano-node/db/socket"} event: Miniprotocol MiniProtocolNum 5 InitiatorDir terminated with exception DbInsertException "AdaPots" (SqlError {sqlState = "42P01", sqlExecStatus = FatalError, sqlErrorMsg = "relation \"ada_pots\" does not exist", sqlErrorDetail = "", sqlErrorHint = ""})
Apr 19 00:39:04 cardano4 bash[79188]: [db-sync-node.Subscription:Error:4371] [2021-04-18 21:39:04.69 UTC] Identity Application Exception: LocalAddress "/home/cardano/cardano-node/db/socket" DbInsertException "AdaPots" (SqlError {sqlState = "42P01", sqlExecStatus = FatalError, sqlErrorMsg = "relation \"ada_pots\" does not exist", sqlErrorDetail = "", sqlErrorHint = ""})
Apr 19 00:39:04 cardano4 bash[79188]: [db-sync-node.ErrorPolicy:Error:4] [2021-04-18 21:39:04.69 UTC] IP LocalAddress "/home/cardano/cardano-node/db/socket" ErrorPolicyUnhandledApplicationException (DbInsertException "AdaPots" (SqlError {sqlState = "42P01", sqlExecStatus = FatalError, sqlErrorMsg = "relation \"ada_pots\" does not exist", sqlErrorDetail = "", sqlErrorHint = ""}))
Apr 19 00:39:05 cardano4 bash[79188]: [db-sync-node.Subscription:Notice:45] [2021-04-18 21:39:05.69 UTC] Identity Restarting Subscription after 12.044973358s desired valency 1 current valency 0
Apr 19 00:39:05 cardano4 bash[79188]: [db-sync-node.Subscription:Notice:45] [2021-04-18 21:39:05.69 UTC] Identity Starting Subscription Worker, valency 1
Apr 19 00:39:05 cardano4 bash[79188]: [db-sync-node.Subscription:Notice:4400] [2021-04-18 21:39:05.69 UTC] Identity Connection Attempt Start, destination LocalAddress "/home/cardano/cardano-node/db/socket"
Apr 19 00:39:05 cardano4 bash[79188]: [db-sync-node.Subscription:Notice:4400] [2021-04-18 21:39:05.69 UTC] Identity Connection Attempt End, destination LocalAddress "/home/cardano/cardano-node/db/socket" outcome: ConnectSuccessLast
Apr 19 00:39:05 cardano4 bash[79188]: [db-sync-node.Handshake:Info:4400] [2021-04-18 21:39:05.69 UTC] WithMuxBearer (ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/home/cardano/cardano-node/db/socket"}) Send (ClientAgency TokPropose,MsgProposeVersions (fromList [(NodeToClientV_1,TInt 764824073),(NodeToClientV_2,TInt 764824073),(NodeToClientV_3,TInt 764824073),(NodeToClientV_4,TInt 764824073),(NodeToClientV_5,TInt 764824073),(NodeToClientV_6,TInt 764824073),(NodeToClientV_7,TInt 764824073),(NodeToClientV_8,TInt 764824073)]))
Apr 19 00:39:05 cardano4 bash[79188]: [db-sync-node.Handshake:Info:4400] [2021-04-18 21:39:05.71 UTC] WithMuxBearer (ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/home/cardano/cardano-node/db/socket"}) Recv (ServerAgency TokConfirm,MsgAcceptVersion NodeToClientV_8 (TInt 764824073))
Apr 19 00:39:05 cardano4 bash[79188]: [db-sync-node.Mux:Info:4400] [2021-04-18 21:39:05.71 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/home/cardano/cardano-node/db/socket"} event: Handshake Client end, duration 0.020973373s
Apr 19 00:39:05 cardano4 bash[79188]: [db-sync-node.Mux:Info:4401] [2021-04-18 21:39:05.72 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/home/cardano/cardano-node/db/socket"} event: State: Mature
Apr 19 00:39:05 cardano4 bash[79188]: [db-sync-node:Info:4404] [2021-04-18 21:39:05.72 UTC] Starting chainSyncClient
Apr 19 00:39:05 cardano4 bash[79188]: [db-sync-node.Subscription:Notice:45] [2021-04-18 21:39:05.72 UTC] Identity Required subscriptions started
Apr 19 00:39:05 cardano4 bash[79188]: [db-sync-node:Info:4404] [2021-04-18 21:39:05.74 UTC] Cardano.Db tip is at slot 4492289, block 4490000
Apr 19 00:39:05 cardano4 bash[79188]: [db-sync-node:Info:4408] [2021-04-18 21:39:05.74 UTC] Running DB thread
Apr 19 00:39:05 cardano4 bash[79188]: [db-sync-node:Info:4408] [2021-04-18 21:39:05.90 UTC] Rolling back to SlotNo 4492289, hash 428b01626de393dff5c41916ec07be1b307213bc750dbf2ec0cadb5f9e8c2247
Apr 19 00:39:05 cardano4 bash[79188]: [db-sync-node:Info:4408] [2021-04-18 21:39:05.90 UTC] No Rollback is necessary
Apr 19 00:39:16 cardano4 bash[79188]: [db-sync-node:Info:4408] [2021-04-18 21:39:16.61 UTC] Starting epoch 208

runDBThread: DbInsertException "AdaPots" (SqlError {sqlState = "42P01", sqlExecStatus = FatalError, sqlErrorMsg = "relation \"ada_pots\" does not exist", sqlErrorDetail = "", sqlErrorHint = ""})

That line there means the the SQL schema in the database (set by the files in the directory specified by the --schema-dir command line option) disagrees with the schema compiled int db-sync.
You need to make sure the schema files are the correct ones for that version of db-sync and then you need to drop the database and resync.

That line there means the the SQL schema in the database (set by the files in the directory specified by the --schema-dir command line option) disagrees with the schema compiled int db-sync.
You need to make sure the schema files are the correct ones for that version of db-sync and then you need to drop the database and resync.

Thanks. I realized the problem, that's why I dropped the database a few times, and also downgraded the cardano-node an tried again, but I wasn't aware of the database migration files needing the be updated after the upgrade. I thought this is hardcoded in cardano-db-sync(-extended). Comparing the database migration files, I found a missing one, which was creating exactly this table.
I'm trying again now. It seems to be working now without dropping the database, just restarting the service (cardano-db-sync). If it fails, I'll also drop the database and try from the beginning again, and I'll post the result here.

Maybe you should update the new releases documentation, to mention the fact that there are new database migration files that need to be copied to the "--schema-dir" during the upgrade. I will close the issue now.

This is not a new thing. The need for those files to be there and to be correct, has always been a requirement. This ticket adds functionality to check that the SQL files are present and hat they are correct.


Add ability to prevent deletion of database

Is your request related to a new offering from AWS?
No
Is your request related to a problem? Please describe.
No
Describe the solution you'd like.
Add a configuration setting `prevent_destroy = [true|false]
I didn't see a setting to prevent deletion of the database. I think there is a
lifecycle {
   prevent_destroy  = true
}

Terraform does not support variables inside lifecycle blocks, so this is not possible to implement in the module.

In the terraform documenatation, there is an example of prevent_destroy being. Is this not applicable to rds?

https://github.com/hashicorp/terraform/issues/3116 and https://github.com/hashicorp/terraform/issues/25534


Use Draggabilly with the Packery layout of Isotope

Hi David,
is it possible to use draggabilly with Isotope implemented with the packery layout-mode?
Actually there is only the following link https://packery.metafizzy.co/draggable.html that explains how to use draggabilly with Packery as stand alone.
Thanks in advance.

Hello! The Packery layout mode for Isotope does not support dragging. See https://github.com/metafizzy/packery/issues/46#issuecomment-18617291 for my reasoning


adds sort child pages button

Closes #1496

Adds "SORT CHILD PAGES" button alongside page buttons

We want to keep the multi-select functionality that comes with wagtail 2.15.x, we just want to make this functionality more obvious to find and use for admin users as this functionality is already available but hidden under "MORE" menu.


Scroll lock does not indicate in floating windows

I think the indicator should show in all opened windows and for that you need to add it to all windows. I would monkey-see, monkey-do what we do for the accessibility status indicator:
https://github.com/microsoft/vscode/blob/b22f435d4848fa8f5ef3f1c89cf56f68d7ce6049/src/vs/workbench/contrib/accessibility/browser/accessibilityStatus.ts#L45
Specifically:
https://github.com/microsoft/vscode/blob/b22f435d4848fa8f5ef3f1c89cf56f68d7ce6049/src/vs/workbench/contrib/accessibility/browser/accessibilityStatus.ts#L94-L97

I now show it on all windows. Used the same approach as ScreenReaderModeStatusEntry. However, it would be great to not have to do it this way. In principle the main Status Bar Service could provide an option to add an entry across all windows. I think this could be possible as the main service creates the aux ones and hence can track them...


TextInput: Added new docs to PasswordRules Prop

Changelog
[iOS] [Added] - TextInput: Added new docs to PasswordRules Prop
Test Plan
No need of a test plan
Summary
This wasn't documented when merged #25407 , spotted it while working on #1579

It seems that this was already getting documentation on #27999 feel free to close this PR.


botocore.exceptions.NoRegionError: You must specify a region.

I've just installed bridgy on a new machine (having it working on another), and with the exact same configuration file, I've hit this error upon updating: botocore.exceptions.NoRegionError: You must specify a region.. However, I do specify the region in the config file.
The full output of the bridgy update -v command:
Updating inventory...
Loading variable profile from defaults.
Loading variable config_file from defaults.
Loading variable credentials_file from defaults.
Loading variable data_path from defaults.
Loading variable profile from defaults.
Loading variable region from defaults.
attaching to session: Session(region_name=None)
datapath: /Users/pascaldevink/.bridgy/inventory/aws/production
Loading variable profile from defaults.
Loading variable region from defaults.
Loading variable profile from defaults.
Loading variable ca_bundle from defaults.
Loading variable profile from defaults.
Loading variable api_versions from defaults.
Loading variable profile from defaults.
Loading variable credentials_file from defaults.
Loading variable config_file from defaults.
Loading variable profile from defaults.
Loading variable metadata_service_timeout from defaults.
Loading variable profile from defaults.
Loading variable metadata_service_num_attempts from defaults.
Loading variable profile from defaults.
Looking for credentials via: env
Looking for credentials via: assume-role
Looking for credentials via: shared-credentials-file
Found credentials in shared credentials file: ~/.aws/credentials
Loading JSON file: /Users/pascaldevink/Library/Python/3.6/lib/python/site-packages/botocore/data/endpoints.json
Loading variable profile from defaults.
Event choose-service-name: calling handler <function handle_service_name_alias at 0x10cf509d8>
Loading JSON file: /Users/pascaldevink/Library/Python/3.6/lib/python/site-packages/botocore/data/ec2/2016-11-15/service-2.json
Event creating-client-class.ec2: calling handler <function add_generate_presigned_url at 0x10cf2a488>
Event creating-client-class.ec2: calling handler <bound method Pill._create_client of <placebo.pill.Pill object at 0x10d3c1d68>>
_create_client
Traceback (most recent call last):
  File "/Users/pascaldevink/.local/bin/bridgy", line 11, in <module>
    sys.exit(main())
  File "/Users/pascaldevink/Library/Python/3.6/lib/python/site-packages/bridgy/__main__.py", line 373, in main
    handler(args, config)
  File "/Users/pascaldevink/Library/Python/3.6/lib/python/site-packages/bridgy/utils.py", line 32, in wrapper
    func(*args,**kwargs)
  File "/Users/pascaldevink/Library/Python/3.6/lib/python/site-packages/bridgy/__main__.py", line 274, in update_handler
    inventory_obj = inventory.inventory(config)
  File "/Users/pascaldevink/Library/Python/3.6/lib/python/site-packages/bridgy/utils.py", line 49, in __call__
    return self[args]
  File "/Users/pascaldevink/Library/Python/3.6/lib/python/site-packages/bridgy/utils.py", line 51, in __missing__
    ret = self[key] = self.f(*key)
  File "/Users/pascaldevink/Library/Python/3.6/lib/python/site-packages/bridgy/inventory/__init__.py", line 43, in inventory
    inv = AwsInventory(cache_dir, **srcCfg)
  File "/Users/pascaldevink/Library/Python/3.6/lib/python/site-packages/bridgy/inventory/aws.py", line 41, in __init__
    self.client = session.client('ec2')
  File "/Users/pascaldevink/Library/Python/3.6/lib/python/site-packages/boto3/session.py", line 263, in client
    aws_session_token=aws_session_token, config=config)
  File "/Users/pascaldevink/Library/Python/3.6/lib/python/site-packages/botocore/session.py", line 861, in create_client
    client_config=config, api_version=api_version)
  File "/Users/pascaldevink/Library/Python/3.6/lib/python/site-packages/botocore/client.py", line 76, in create_client
    verify, credentials, scoped_config, client_config, endpoint_bridge)
  File "/Users/pascaldevink/Library/Python/3.6/lib/python/site-packages/botocore/client.py", line 288, in _get_client_args
    verify, credentials, scoped_config, client_config, endpoint_bridge)
  File "/Users/pascaldevink/Library/Python/3.6/lib/python/site-packages/botocore/args.py", line 45, in get_client_args
    endpoint_url, is_secure, scoped_config)
  File "/Users/pascaldevink/Library/Python/3.6/lib/python/site-packages/botocore/args.py", line 111, in compute_client_args
    service_name, region_name, endpoint_url, is_secure)
  File "/Users/pascaldevink/Library/Python/3.6/lib/python/site-packages/botocore/client.py", line 361, in resolve
    service_name, region_name)
  File "/Users/pascaldevink/Library/Python/3.6/lib/python/site-packages/botocore/regions.py", line 122, in construct_endpoint
    partition, service_name, region_name)
  File "/Users/pascaldevink/Library/Python/3.6/lib/python/site-packages/botocore/regions.py", line 135, in _endpoint_for_partition
    raise NoRegionError()
botocore.exceptions.NoRegionError: You must specify a region.

The relevant part of the config file:
config-schema: 2
inventory:
  update_at_start: true
  fuzzy_search: true
  source:
    - type: aws
      name: production
      region: eu-west-1

and of course I have a ~/.aws/credentials file with the correct access key and secret.
Any clue what might cause this? Could it be a version thing of a dependency maybe?

@pascaldevink did this solve your problem?

@wagoodman Thanks, that fixed it indeed!

By initializing the  os.environ['AWS_DEFAULT_REGION'] = 'us-east-1' below the imports fixed my issue


[MARXAN-128] Allow to delete one's own user

Overview
Ok to review, but needs to be rebased on develop before merging
DELETE /api/v1/users/me should (soft-) delete one's own user
Basically we set isActive = false and isDeleted = true, which flags the user for deletion and prevents them from logging in, while keeping the actual user account in the db.
We don't deal with the details of physically deleting the user at this stage - this would mean taking some decisions on "detaching" the user account from db entities it may be linked to. We may need to do something here because of data protection compliance, but we could also potentially deal with this by removing personal identification data from users flagged for deletion, without having to deal with more complexity which could be avoided in this phase.
Designs
N/A
Testing instructions
DELETE /api/v1/users/me should succeed for logged-in users
After this, any existing and still-valid (timestamp-wise) JWT tokens must be rejected, and it should not be possible to obtain new JWT tokens via POST /api/v1/auth/sign-in.
Feature relevant tickets
https://vizzuality.atlassian.net/browse/MARXAN-128

Checklist before submitting

[x] Meaningful commits and code rebased on develop.
[ ] If this PR adds feature that should be tested for regressions when
deploying to staging/production, please add brief testing instructions
to the deploy checklist (docs/deployment-checklist.md)
[x] Update CHANGELOG file

maybe is just because as you said to me earlier this week this prs are a bit chaotic, but I think the country stuff has slipped through this.

yep, that was because I based each PR on the previous one to be able to deploy on marxan49 all the successive changes for FEs to work with them.

I also miss a test for deleting users.

that's right - I had stashed this test file away and never remembered to bring it back, doing that now.
Adding tests is the change requested here, right? As for the countries changes, I have rebased this PR on the latest develop now and so those changes are not included in the PR anymore.

Apart from that testing the delete endpoint works as expected and does not allow me to sign in again.


StatusBarManager.getHeight Android Error

Android does not support StatusBarManager.getHeight, thus the package crashes when used on Android.

Hi @imoris11,
To raise a PR follow the instructions:
• Mutations in components/* and same in react-native-grid-image-viewer/components/*
• Raise the version in package.json, react-native-grid-image-viewer/package.json and package-lock.json
• Commit changes
Thanks for your interest

Alright. Thanks @ansh-099
I will do it later today. I downgraded to 1.0.6 for the time being. I'll update the PR as soon as I can

@ansh-099 PR is updated

Merged!


[Need Text Review] Support entitlement and evaluation editions

Description
The PR is to resolve #23 and resolve #24 so that the twas-single-server offer can support both entitlement and evaluation usages.
Text review required
As #23 mentioned, the text for evaluation case is TBD, which needs to be finalized during the review:

Screenshot:
Screenshot with tooltip:

TODO
The following items should be done before merging this PR:

Finalize the text for evaluation case
WASdev/azure.websphere-traditional.image/pull/56 is merged
The base image for twas-base is updated and available
Update twas.image.version in pom.xml with the new version of twas-base image
Deploy to a testing offer to verify the PR

Signed-off-by: Jianguo Ma<EMAIL_ADDRESS>

How about:
By accepting the IBM License Agreement you are accepting the Evaluation terms of the license.  An evaluation deployment does not include WebSphere interim fixes (ifixes).  The evaluation period runs for 60 days after which you must purchase entitlement to continue to use WebSphere.

Consider this existing UI:

Amend this to say "I have read and accept the IBM License Agreement."

Thank you @gcharters & @edburns for your suggestions, they look good. I'll apply your suggestions and attach the latest screenshot for your review later.

Hello @gcharters @edburns  Not it looks much better:

Deploy with existing WebSphere entitlement

Deploy with evaluation license?


Android Webview Err_Content_Decoding_Failed

I am using webview to access website from mobile application. Works perfectly for most websites but I'm getting error on some websites. This error only exists in android.
(
Here my simple WebView Code
 <WebView         style={webviewStyle}         source={{uri: https://www.randomwebsite.com}}       />
Environment:

OS: Android
OS version: Android 11
react-native version: 0.65.1
react-native-webview version: 11.14.1

+1

Still searching for solutions

+1

was there a solution to this ?

I encountered a similar problem recently. It turned out that the issue was caused by sharing the build with someone in the US region. Surprisingly, the build worked perfectly there. This leads me to believe that geographical location might play a role in these types of issues. Alternatively, you could try resolving the problem by enabling a VPN and checking if that resolves the situation. It's worth exploring these possibilities to get to the root of the problem.
:)


Primod's basin mapping can't deal with integer basin id's with latest Rasterio dependecy

problem: imod.prepare.rasterize results in a crash if node_id is an integer and fill-value is the default np.nan.
solution: We could use a fill-value of 0 if node_id is integer but this does not work in combination with NodeBasinMapping logic. Best is to force node_id to float64 dtype.

FYI: This is an issue with rasterio >=1.3.10.
Setting fillid to -1 caused the tests to succeed, but I don't know if this aspect is well tested.

FYI, as it is related: In this PR https://github.com/Deltares/imod_coupler/pull/348 I had to force the dtype argument for imod.prepare.rasterize to float, otherwise problems arose.
I recently updated iMOD Python to take a dtype argument for its rasterize function, but haven't released this yet.


Make the Hero transition animation configurable

The guidance about motion in material apps is more flexible than it was. Currently all hero transitions use a MaterialRectArcTween which can introduce aspect ratio distortions during the hero's flight.  This tween is hardwired by MaterialApp which creates the app's HeroController.
Added a Hero.createRectTween property that overrides HeroController.createRectTween.
Added MaterialRectCenterArcTween which can be used to define aspect-ratio preserving hero transitions.


Sample knapsack.json file for refrence

Pl add Sample knapsack.json file in Wiki Documentation Page

You're not supposed to write the knapsack yourself, ever. However, here's an example of what it could look like.
{
  "cypress/integration/some-spec.js": 13157
}


Normalize setting label + level on transport options

Context
By default the logger set label+level on the console configuration. However, each transport is optional and other transports require label+level too.
What has been done

Set label+level on the individual transport configuration.

How to test

npm test

closes #4


Cmake Error

I just clone your repository and compile it, and got the following error :
The Caffe2 is build with the last pytorch github commit.
> make -j8
Scanning dependencies of target caffe2_cpp_test
[ 50%] Building CXX object CMakeFiles/caffe2_cpp_test.dir/src/main.cpp.o
/home/cgilab/Desktop/Caffe2_Demo/03_cpp_forward/build/caffe2_Cpp_example/src/main.cpp: In function ‘void caffe2::caffe2_pretrained_run()’:
/home/cgilab/Desktop/Caffe2_Demo/03_cpp_forward/build/caffe2_Cpp_example/src/main.cpp:121:50: error: use of deleted function ‘caffe2::Tensor::Tensor(const caffe2::Tensor&)’
             auto output = TensorCPU(output_device);
                                                  ^
In file included from /usr/local/include/caffe2/core/blob.h:13:0,
                 from /usr/local/include/caffe2/core/operator.h:12,
                 from /home/cgilab/Desktop/Caffe2_Demo/03_cpp_forward/build/caffe2_Cpp_example/inc/utils.h:10,
                 from /home/cgilab/Desktop/Caffe2_Demo/03_cpp_forward/build/caffe2_Cpp_example/src/main.cpp:1:
/usr/local/include/caffe2/core/tensor.h:763:3: note: declared here
   Tensor(const Tensor& src) = delete;
   ^
In file included from /usr/local/include/caffe2/core/operator.h:12:0,
                 from /home/cgilab/Desktop/Caffe2_Demo/03_cpp_forward/build/caffe2_Cpp_example/inc/utils.h:10,
                 from /home/cgilab/Desktop/Caffe2_Demo/03_cpp_forward/build/caffe2_Cpp_example/src/main.cpp:1:
/usr/local/include/caffe2/core/blob.h: In instantiation of ‘T* caffe2::Blob::GetMutable() [with T = caffe2::Tensor]’:
/home/cgilab/Desktop/Caffe2_Demo/03_cpp_forward/build/caffe2_Cpp_example/src/main.cpp:77:75:   required from here
/usr/local/include/caffe2/core/blob.h:127:5: error: static assertion failed: GetMutable can't be called with non-default-constructible types. Try using specialized methods
     static_assert(
     ^
/usr/local/include/caffe2/core/blob.h:135:22: error: use of deleted function ‘caffe2::Tensor::Tensor()’
       return Reset<T>(new T());
                      ^
In file included from /usr/local/include/caffe2/core/blob.h:13:0,
                 from /usr/local/include/caffe2/core/operator.h:12,
                 from /home/cgilab/Desktop/Caffe2_Demo/03_cpp_forward/build/caffe2_Cpp_example/inc/utils.h:10,
                 from /home/cgilab/Desktop/Caffe2_Demo/03_cpp_forward/build/caffe2_Cpp_example/src/main.cpp:1:
/usr/local/include/caffe2/core/tensor.h:94:3: note: declared here
   Tensor() = delete;
   ^
CMakeFiles/caffe2_cpp_test.dir/build.make:62: recipe for target 'CMakeFiles/caffe2_cpp_test.dir/src/main.cpp.o' failed
make[2]: *** [CMakeFiles/caffe2_cpp_test.dir/src/main.cpp.o] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/caffe2_cpp_test.dir/all' failed
make[1]: *** [CMakeFiles/caffe2_cpp_test.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2

@zacario-li thanks for your reply.
and I just find there are lots of problems and bugs in caffe2. both tag 0.4v and 0.4.1v.
look forward to version 1.0.


[SPARK-25023] More detailed security guidance for K8S

What changes were proposed in this pull request?
Highlights specific security issues to be aware of with Spark on K8S and recommends K8S mechanisms that should be used to secure clusters.
How was this patch tested?
N/A - Documentation only
CC @felixcheung @tgravescs @skonto

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

Test build #98729 has started for PR 23013 at commit 5f2fe6e.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/98729/
Test PASSed.

@tgravescs @mccheah @rvesse is this pretty much OK with all of you?

@srowen I'm happy with it

The description is very useful and concise.

Merged to master/2.4

The SASL mechanisms still work, though it's more similar to something like standalone mode than having the robustness of YARN. We could generate the SASL secrets and put them in K8s secrets as a k8s specific solution, for example.


Optional / Nullable decorator or type helper

When using the @type decorator for field that don't necessarily need to be defined and don't have a default value, i.e. optional or "nullable" fields, it's a bit tedious to have to define a union just for that.
I suggest we add an @optional or @nullable decorator, that effectively wraps the specified type in a unionOf(specifiedType, unefined, null).
This would allow the following code:
import Component from '@ember/component';
import { argument } from '@ember-decorators/argument';
import { type, optional } from '@ember-decorators/argument/type';
import { immutable } from '@ember-decorators/argument/validation';

export default class ExampleComponent extends Component {
  @argument
  @optional
  @type('string')
  arg;
}

Alternatively optional or nullable could just be a helper:
import Component from '@ember/component';
import { argument } from '@ember-decorators/argument';
import { type, optional } from '@ember-decorators/argument/type';
import { immutable } from '@ember-decorators/argument/validation';

export default class ExampleComponent extends Component {
  @argument
  @type(optional('string'))
  arg;
}

Yeah, I agree that optional syntax is pretty cumbersome here. It also makes the @required decorator kind of redundant if you use @type 😛
I'm leaning towards it being a type helper, since that'd be much more straightforward to implement and apply universally. If it were a decorator, I would expect it to operate much like @required, only running the validation on component initialization, whereas a type helper would I think create a union type that applies at all times (whenever the field is set, or new properties are passed in, etc)

Awesome-sauce. Makes total sense. I'll fix up a PR tomorrow.


No standardized approach to serialize non-learnable parameter

There is no standardized approach to serialize non-learnable parameter such as a dilation rate of a convolution.
What is official way to include a non-learnable parameter for serialization? "add_persistent()"? or write custom serialize method?
An official documentation would help this.

Thank you for the feedback.
You can use add_persistent() for that purpose.
Please see https://docs.chainer.org/en/latest/guides/serializers.html for details.

@kmaehashi
Thanks for the comment. I understood the standardized way for the serialization. However, I wonder why chainer included only Link.add_param() to with self.init_scope() but did not replace Link.add_persistent() to such context managing function?

IMO registrations of serializable object should be explicit. If init_scope() automatically registers everything setattr-ed as persistent, it is will become hard to track down what will be serialized at a glance, especially when other instance method is called from inside init_scope() block.

I haven't understood your point yet. Do you mean "non-learnable parameters should not be serialized"?

What I meant is: I think it is rather unsafe to assume that every user wants to serialize every attributes set in init_scope. For example, it is common to keep constructor arguments as attributes, which should not be serialized.
On the other hand, automatically registering Parameters makes sense as it is obviously needed for serialization.

Hmm, partially I agree with your opinion that users doesn't have to intend to serialize all members registered within init_scope() clause.
Thanks for your kind reply!


Add Project Root Directory to Python Path

Custom tasks in the repository do not work as per the documentation. This is because the project's root directory is not added to the Python path.
To fix this, add the following line to the import_class() function in the core/utils.py before calling __import__()
sys.path.append(os.getcwd())

We should be adding the repo_root to Python Path during Cli initialization: https://github.com/SalesforceFoundation/CumulusCI/blob/master/cumulusci/cli/cli.py#L56. This worked at one time.
I'm trying to repro locally now.

I followed the tutorial exactly and this worked for me. Could you post your dir structure and how you have it wired up in cumulusci.yml?

The yml for the task (project details changed):
`project:
name: Test Project
package:
name: Test Package
namespace: testpackage
tasks:
output_message:
description: Output a message to the log
class_path: tasks.rest.SayHello
`
tasks folder in the root directory with the following in that directory:

__init__.py
rest.py

Contents of rest.py.
`from cumulusci.tasks.salesforce import BaseSalesforceApiTask
class SayHello(BaseSalesforceApiTask):
def _run_task(self):
self.logger.info("Hello")
`
The tutorial gives the wrong location for the BaseSalesforceApiTask class.

I added this to _add_repo_to_path():
print "repo root: " + self.project_config.repo_root

This is the output:
repo root: C:

It's quite possible this implementation actually hasn't been tested on a Windows setup... Thank you for finding this!
Could you send some environment details so I can standup a VM and reproduce? Version of Windows, where you installed Python, what shell are you running (i.e. cmd.exe, powershell, the linux thingy....)?

I'm using Windows 10 and a Python 2.7.11 virtual environment. I've tried running the command on cmder, Powershell and PyCharm with the same result in each.

Thanks Craig, I'll take a look. You can see from Chris's tag that we're aware that windows docs and usage is lacking right now. There are other problems you could face when repo_root isn't functioning, not just related to imports, so we wanna get this working.

Fixed in beta23

Reopening because the core issue is that self.project_config.repo_root returns unexpected value (e.g. "C:") on Windows. We should fix this in cumulusci/core/config.py BaseProjectConfig.repo_root then the changes from a386604 and a2f9419 should be removed.

Turns out it was not related to os.getcwd(). The problem is that the drive was being handled as part of the path and when joined back together was incorrect. For example "C:Users\Chris\MyProject" instead of "C:\Users\Chris\MyProject".


Multi-Lang Rich Text Box Won't Submit

Version information

Laravel: v5.6.40
Voyager: v1.1.3
PHP: 7.2.5
Database: mysqlnd 5.0.12-dev
env: Homestead v7.10.0

Description
Pages with translatable fields that have a rich text box bread prevent the creation of new items. Console displays an invalid form control with name="{fieldname}" is not focusable.  New item does not submit.
Steps To Reproduce

Create a fresh project composer create-project laravel/laravel project-name && cd project-name
Update env file for project. prepend setting APP_URL with http://
Run composer require tcg/voyager && php artisan voyager:install --with-dummy
In config/voyager.php: line 113 change false to true, uncomment line 130.
Navigate to /admin
Sign in.
Navigate to /admin/pages/create
Fill in the content of the page field.
Attempt to submit the form

Expected behavior
Form to submit. new page to be added.
Screenshots
Note my ss has the error twice because double click.
Additional context
Applies to more  than just the tcg voyager models. Custom models that have trait Translatable and the appropriate protected $translated values also display properly on the page, but error out and fail to save new items.
Additional notes
reverting config/voyager.php 113 to true no longer causes the submission to fail.
laravel.log is empty.
Additional oddity. If you refresh with f5 the form will sticky the entered data and in addition it will be submit able.

Please search before opening an issue.
This is a duplicate of #3209 #2965 #2895 and #2578

The issue is supposed to be resolved with #2660 and with release v1.0.16.
I'll state it again. I am using version v1.1.3. Still experiencing the same problem and not in a chrome based browser. Republishing the assets with the forced flag does not resolve the issue.
While I am glad there is a workaround with https://github.com/the-control-group/voyager/issues/3209#issuecomment-397290668. It's very sloppy as you lose the rest of your validation.
As fletch stated here: https://github.com/the-control-group/voyager/issues/2894#issuecomment-380538958 (and on slack when posted this topic).
Yet every issue related to it is closed with no resolution. Maybe when I have time during my current project it is something I can visit and make a pr for.

As @emptynick stated, this issue is a duplicate of those others.  You'll notice at least one of the issues he linked is still open, and is reported using v1.1.1.  Having multiple issues tracking the same problem only leads to confusion.  Therefore, this will remain closed.


error 400

*Describe the bug
when i run a mobile application in the physical device i get error
I/flutter (18392): ServerpodClientException: , statusCode = 400
To Reproduce
Steps to reproduce the behavior:

add my computer ip address to teh code
Click on submet
i get error 400

Serverpod versions

1.1.1
_Library version: 1.1.1

Platform information
windows / android

Can you please add some code example and a description of what you are trying to do.

ok i just try to run serverpod in physical device not in emulator and the phone is connected with the computer with wifi and usb

I/flutter (18392): ServerpodClientException: Internal server error. Call log id: 2, statusCode = 500

I/flutter (18392): ServerpodClientException: Internal server error. Call log id: 2, statusCode = 500

Suggests that something is crashing in your server. Hard to tell without seeing your implementation.


add grunt-cli so global install is not required

Without instructions, I cloned this repo, ran $ npm install and then $ npm test, which failed because grunt wasn't installed globally.
By adding grunt-cli to the devDependencies, a local grunt binary is created and doesn't require a global installation of grunt when using grunt via npm scripts.
This change also makes it unnecessary to install grunt-cli globally on Travis. Which I also removed.

love it!

Sweet, thanks!


Shape.union takes a really long time and sometimes says "Error: TODO: Need to implement more advanced disambiguation"

@marlitas and I were able to reproduce the bug reported in https://github.com/phetsims/mean-share-and-balance/issues/87 in both Mac/Safari and Mac/Chrome.  We isolated the problem to Shape.union which is being called in BeakerNode.
Perhaps the shapes being passed to Shape.union are triggering a difficult situation or corner case that kite is struggling with.
@marlitas and I will look for another way to render BeakerNode for the moment, but wanted to raise this issue for @jonathanolson to investigate.  May be best to collaborate with @marlitas to discuss how to trigger the error case.
@marlitas wonders if this is related to: https://github.com/phetsims/kite/issues/97

https://github.com/phetsims/kite/commit/eff96db2248ba0d720a6039d3a712e5eeb9af7b6 will unblock MSS so that things can be graceful in production, @jonathanolson would like to fix this at some point though!