Little vs big endian

SSZ has been updated to little endian integer encoding, but the phase 0 spec still uses big endian encoding at a few of sites. Is there a specific reason for this? If not I'd advocate for using little endian here as well for the sake of consistency.

Good call. Agreed on consistency.

Hmmm, I feel not fully comfortable with this change for some reasons:

eth1.0 is still a big-endian world - so all the bytes conversion on deposit contract are still in big-endian.
Our BLS spec uses big-endian now. Moreover, BLS12-381curve uses big-endian now.

That's said, IMHO it's okay to only use little-endian in SSZ.

/cc @arnetheduck 😆

Yeah, there is actually a bug in the spec right now. The amount and timestamp logged in deposit_data from the deposit contract is assumed to be in a well formatted SSZ DepositData object. If we are to keep ssz little endian, then we need to either do the conversion in the deposit contract or clean it up on the 2.0 side. I asked the vyper guys if there is a built-in for int to little-endian bytes and they said no. This is definitely an argument for big endian...
contract code snippet below:
deposit_amount: bytes[8] = slice(concat("", convert(msg.value / GWEI_PER_ETH, bytes32)), start=24, len=8)
deposit_timestamp: bytes[8] = slice(concat("", convert(block.timestamp, bytes32)), start=24, len=8)
deposit_data: bytes[528] = concat(deposit_amount, deposit_timestamp, deposit_input)

/cc @vbuterin

My general take on this would be that for types that have a canonical serialization defined outside of the logic of the Eth2 spec, we should use bytesX types in the Eth2 spec - for example, a keypair is generally not considered to be an integer or a point on the curve, from the point of view of the consumer of the key - instead, it's just a blob that you pass as-is to the cryptography black box, and you let the cryptography black box define that serialization on its own terms, compartmentalized.
This goes for hashes, keys and other similar types.
The deposit is a little bit more tricky indeed. We can drop the idea of little endian completely and lose the other benefits, or one of the sides will have to make way - one alternative is to do the decoding on the Eth2 side by encoding deposits as a canonical bytes structure and specify a specific interop deserialization function which is not SSZ, for that exceptional case.

I'm thinking we properly encode deposit_amount and deposit_data to little endian within the deposit contract. We just need to define one method to do the byte manipulation for the encoding. Having the beacon chain and the VM (wasm) have the same encoding will be a win in the end, and handling the fix within the deposit contract ensures that DepositData to comes into eth2 well-formatted so we don't have to write an exceptional rule.

fixed the deposit contract endian formatting bug here https://github.com/ethereum/deposit_contract/pull/8
I think it makes sense to convert everything in the state transition spec to little endian. Fine with converting BLS spec too, but would rather just conform that to whatever other blockchains are using so we can wait on that change.


/tube oxford street doesn't return station information as expected

Jason Cartwright [10:45 AM]
/tube tottenham court road
london-tube BOT [10:45 AM]
Tottenham Court Road: Open
Jason Cartwright [10:45 AM]
/tube oxford street
london-tube BOT [10:45 AM]
Bakerloo: Good Service
Central: Good Service
Circle: Good Service
District: Severe Delays, Severe delays due to signal failure at Acton Town Town. Tickets valid on local buses and Great Western Railway.
Hammersmith and City: Good Service
Jubilee: Good Service
Metropolitan: Good Service
Northern: Good Service
Piccadilly: Severe Delays, Severe delays due to signal failure at Acton Town please change trains as necessary. Tickets valid on local buses and Heathrow Connect.
Victoria: Good Service
Waterloo and City: Good Service
Overground: Part Closure, No service between Highbury & Islington and Shadwell and Surrey Quays and New Cross due to planned engineering work.
TfL Rail: Good Service
DLR: Good Service
Trams: Good Service

Ignore me. Should have been Oxford Circus


Pkg metrics

[x] Fix ATN URL (I did not change anything, it seems that the page is back online)
[x] Cleaner logs (pdfminer pollutes the output)

Wait for #57 to merge this one.

@MathewBiddle this one is ready for review. The PyPI failure is b/c we don't have a tag yet.

something to investigate later, it takes a while to import ioos_metrics.ioos_metrics. On the order of a few seconds... Might be something of concern.
Otherwise this looks good to me.

something to investigate later, it takes a while to import ioos_metrics.ioos_metrics. On the order of a few seconds... Might be something of concern.
Otherwise this looks good to me.

Did you install it or did you try to import from the root directory? The the former than there may be a problem with your setup and/or Windows. If the latter than it is expected at the first time b/c Python will travese all the function definitions and create the pyc files. The second time you import it will be much faster, even in a new session. This is what I get when installing it with pip install -e . --no-deps --force-reinstall to force everything to rebuild:

ipython
Python 3.12.3 | packaged by conda-forge | (main, Apr 15 2024, 18:38:13) [GCC 12.3.0]
Type 'copyright', 'credits' or 'license' for more information
IPython 8.22.2 -- An enhanced Interactive Python. Type '?' for help.

In [1]: %time import ioos_metrics.ioos_metrics
CPU times: user 1.52 s, sys: 56 ms, total: 1.57 s
Wall time: 485 ms

483 ms is not bad for a library with so many different dependencies.

Did you install it or did you try to import from the root directory?

import from the root directory.

the former than there may be a problem with your setup and/or Windows.

Agreed. At some point I'd like to reinstall the entire library. At some point...

Agreed. At some point I'd like to reinstall the entire library. At some point...

We can tag a version and upload it to PyPI+conda-forge now. Then installing it will be conda install ioos_metrics from any environment. That will help a lot to run this, and the glider metrics, on Google colab.

I went with v0.0.1-alpha 😄

Do you mind renaming that tag v0.1.0a0. That scheme is PEP440 compliant and will be accepted by PyPI and conda-forge. Also, I added manually a 0.1.0 dev0 to help Kathy out with the glider, before you merged this one, so we need to be higher than a 0.1.0.dev0.

Can I just rename the release?

how about https://github.com/ioos/ioos_metrics/releases/tag/v0.1.0a0

Can I just rename the release?

You can edit it and issue a new tag. Or, if it is easier, delete both the release and tag and mint new ones.


Energy Usage in dimlets.

Good Day,
We have created the age but seems like that it is using around 2x of the energy it should use.
Below is the image of the problem, you can see that Ender IO Capacitors banks drain 2x as much they should use. Only dimension builder is connected to those capacitors...
http://puu.sh/gkMTN/c404217bf1.jpg
Best Regards,
DeForce

I will investigate this.

Very good catch.  I will fix this for 2.54 which I will release in a moment.


Pattern matching

What are use-cases we might and need to cover?
How it could look and work in Nevalang?

Structure sub-typing
Check if struct v of type {a int, b int} is actually of type {a int, b int, c string}

Union sub-typing
Check if v of type int | string is actually int or string, or check that int | string | bool is at least int | string

Any sub-typing
Checking that v of type any is T1 or T2 or Tn.

"Switch true"
(Covered by switch in traditional languages)
Just (ordered) set of conditions where first that results into true selects the branch

Handling maybe<T>
In Rust handling of Option<T> with match is not a special case, because option is just an enum.
However, it's not the case for Nevalang, where maybe<T> is "base" type (it's not explained in terms of other types).
It means that this syntax that looks obvious for match:
maybeValue -> match {
    some: ...
    none: ...
}

Collides with its existing semantics, that should compare values by equality - in this case compare maybeValue with other values of type maybe.
Same things goes for switch:
maybeValue -> switch {
    some -> ...
    none -> ...
}

Multiple values?
How do we support case when several patterns lead to same branch? Example (v-lang):
enum Color {
	red
	blue
	green
}

fn is_red_or_blue(c Color) bool {
	return match c {
		.red, .blue { true } // comma can be used to test multiple values
		.green { false }
	}
}


Percentage of the battery

Would be nice if the percentage of the battery is showed when the phone is charging

Hi @joelocandol I'm not able to update the widget when the battery percentage changes. I'm only able to react to the low battery or to the full charge.


Casting docs: undefined and null are not casted

As far as I can tell, this is true. If it's not, let me know, thanks!

I don't think it's relevant. It's quite obvious that null and undefined values shouldn't be casted.

Perhaps it is obvious. I previously (mistakenly) thought that in required fields, they would be cast like empty strings, i.e.
item.set('number', null, {cast: true});  // would cast to 0
item.set('boolean', null, {cast: true}); // would cast to false
item.set('string', null, {cast: true});  // would cast to ''

I know that it seems to be natural to cast null and undefined in a case of the boolean type for instance. However, null or undefined is the lack of value and if you get somehow null or undefined value from the form that means that there is no input field in the form.
Moreover, even if I would like to change that and allow casting null and undefined values for the required fields that would be a compatibility breaking change.

Ok, I will merge your docs change to make it clear. Thanks

Thank you, I appreciate it!
Certainly no need to make any breaking changes; people can write their own casting functions if they want that behavior.


is there a way to retry failed urls after the job has completed?

my job has temporary loss of internet connection in the middle causing many failed urls during that time. is it possible to retry downloading those images?

Same issue here, keep watching.

You can simply delete the last N shards (you can check the json files to
know at what point the success rate dropped to 0)
On Fri, Sep 8, 2023, 08:59 JXD @.***> wrote:

Same issue here, keep watching.
—
Reply to this email directly, view it on GitHub
https://github.com/rom1504/img2dataset/issues/333#issuecomment-1711120195,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR437V4ZICZY2CVCUUPHBDXZKX5NANCNFSM6AAAAAA2W3KMKA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

"delete last N shards" -

what should N be?
What happens if the error occurs at the start and not at the end. Do I still delete the last N shards? What is the logic here?

you can check the output json files to
know at what point the success rate dropped to 0
Delete any shard with success rate below some threshold

“Delete any shard with success rate below some threshold”
Is there a way to solve this problem with a download success rate of 33% for almost all of the shards?

@kobebeen824 maybe but I'd rather recommend you fix your DNS setup (see readme) to increase the success rate

What should I do if I want to re-download the images that failed to download for the first time? The failed images appear randomly.

You could filter the parquet in img2dataset output by status to keep only the failed samples and retry those
I guess I would rather advise you redownload though


Run brew services list before travis/script.sh

#214

A new inspection was created.

Codecov Report

Merging #218 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #218   +/-   ##
========================================
  Coverage    84.69%   84.69%
========================================
  Files           28       28
  Lines         1117     1117
========================================
  Hits           946      946
  Misses         171      171

Continue to review full report at Codecov.

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

The inspection completed: No new issues


Allow creation of custom decoders

As far as I can tell there is no way to create your own decoders. That would be useful e.g. for dates and such.

I just understood how andThen() can be used in combination with succeed() and fail() to create custom decoders. If anybody else is wondering how this can work, here is how I did it:
export function localDate(): Decoder<LocalDate> {
  return andThen(string(), (string) => succeed(LocalDate.parse(string)));
}

Explanations how this works in Elm: https://www.brianthicks.com/post/2017/01/13/create-custom-json-decoders-in-elm-018/
Sorry for the noise.


catalog-backend: initial catalog ingestion rules implementation

Fixes #1853
This implements the minimal config needed for #1853, and there's plenty of space for expanding the set of rules that can be defined. Keeping it simple for now though.
This adds support for following kind of config:
catalog:
  rules:
  - deny: [User, Group, System]

  locations:
  - type: github
    target: https://github.com/org/repo/blob/master/users.yaml
    allow: [User, Group]
  - type: github
    target: https://github.com/org/repo/blob/master/systems.yaml
    allow: [System]

... and not much more :grin:
The catalog.rules config can only contain deny rules, and catalog.locations can only contain allow rules. The rules defined in catalog.locations are applied after the ones defined in catalog.rules.
If catalog.rules is not set in config it falls back to deny: [User, Group].
Hoping that this is good enough for the foreseeable future, and will allow us to safely bring in organizational and identity data into the catalog :grin:

Is there any kind of "deny all" planned? Then one could allow only the ones that are required, but don't has to be afraid that when new entities are added and this configuration was not updated. Kind of a allowlist vs blocklist discussion. Maybe a special semantic like:
catalog:
  rules:
  - deny: all

  locations:
  - type: github
    target: https://github.com/org/repo/blob/master/users.yaml
    allow: [User, Group]

@Fox32 yep, implementation is set up for that, just didn't hook it up to config yet. Wanted to keep things slim to begin with

Should rules and locations be separated? The example could just as well be expressed as
catalog
  rules:
  - type: github
    target: https://github.com/org/repo/blob/master/users.yaml
    allow: [User, Group]  # alternatively: deny: [] which means "allow anything"
  - type: github
    target: https://github.com/org/repo/blob/master/systems.yaml
    allow: [System]
  - deny: [User, Group, System] # implicitly: applies to any type and target

then the engine goes through the rules one by one in search of a match, picking the first one.
or even clearer if one wants to separate the filters from the action better:
catalog
  rules:
  - type: github
    target: https://github.com/org/repo/blob/master/users.yaml
    kind: [User, Group]
    action: accept
  - type: github
    target: https://github.com/org/repo/blob/master/systems.yaml
    kind: [System]
    action: accept
  - kind: [User, Group, System] # implicitly: applies to any type and target
    action: reject
  - action: accept

@freben Well the example would be expressed like this, unless you're suggesting the the rules spawn actual locations to traverse?
catalog:
  locations:
  - type: github
    target: https://github.com/org/repo/blob/master/users.yaml
  - type: github
    target: https://github.com/org/repo/blob/master/systems.yaml

  rules:
  - type: github
    target: https://github.com/org/repo/blob/master/users.yaml
    allow: [User, Group]  # alternatively: deny: [] which means "allow anything"
  - type: github
    target: https://github.com/org/repo/blob/master/systems.yaml
    allow: [System]
  - deny: [User, Group, System] # implicitly: applies to any type and target

Seems really verbose. I think it's fine to have the short-cut of being able to specify some rules in the location config?
I think we could change it to this though, a bit more explicit and provides some better grouping of the fields:
catalog:
  rules:
  - deny: [User, Group, System]

  locations:
  - type: github
    target: https://github.com/org/repo/blob/master/users.yaml
     rules:
      allow: [User, Group]
  - type: github
    target: https://github.com/org/repo/blob/master/systems.yaml
    rules:
      allow: [System]

Regarding the application of the rules, i pretty arbitrarily chose to go with having the last matching rule be the determining one. Stopping on the first matching rule does make the processing a tiny bit faster, and it might end up being a bit more intuitive. Gonna try switching to that.

Oh right, I somehow entirely forgot about the static locations thing, just looked at it as a standalone rules config - yes, agreed, the locations should have rules directly on them and then the fallback rules could be their own key. Maybe name them defaultRules even, signifying how it's used? The last example makes sense, and yes, first match would be the best probably.
Possible remaining gotcha for a rules writer is that you couldn't (?) write a default rule saying allow: [A] and then a locations entry that has allow: [B], and expect that it would allow both A and B. You'd have to repeat the A, right? Which is OK to me, just thinking out loud.

But is there any benefit to breaking out matchers as a separate thing from action?
catalog:
  rules:
  - kind: [User, Group, System]
    action: deny

  locations:
  - type: github
    target: https://github.com/org/repo/blob/master/users.yaml
     rules:
      - kind: [User, Group]
        action: allow
  - type: github
    target: https://github.com/org/repo/blob/master/systems.yaml
    rules:
      - kind: [System]
        action: allow

That way you open up to more kinds of matchers later on.

Updated to deny all entities that aren't covered by a rule, and added a default rule to allow: [Component, API].
Tried out a couple of models for a more generic match + action, but tbh I couldn't find anything that I'm happy with that felt forwards compatible enough. The current config format is now a simple allow: EntityMatchers[], so there's no location configuration and so on. That should make it possible for us to add more rules and matchers without too much trouble.
The main issue with making the entire thing generic is that we need more use-cases for catalog rules. Right now I have no idea if we always want to match on location + entity tuples, it could for example be that we want to add rules for relationships, annotations on entities, locations themselves, etc. Basically the extension of the API needs to be driven by some actual use-cases, and I think the current format is a good middle ground between forwards compatibility and a compact easy to read and write format.


Implement threshold for the intersection of lists of validators

High Level Overview of Change
Improve UNL security by allowing validators to set a minimum number of UNL publishers to agree on validators

Context of Change
In the current system, every node builds an internal list of validators to use, by performing union of UNLs received from all configured UNL publishers (validator lists), where the authenticity of each single UNL is verified by a manifest with a known master key.
This union is a weak security spot of the UNL publication system, as it allows a single UNL publisher to add an arbitrary number of validators, which will be subsequently used by all nodes trusting this UNL publisher. Currently the risk is managed by recommending only the use of two UNL publishers: vl.xrplf.org and vl.ripple.com . With this union approach, a hypothetical addition of a third (or more) UNL publisher would only increase the attack surface, in this way (counterintuitively) degrading the UNL system security.
This PR is replacing union with a configurable intersection threshold between UNL publishers, which by default is calculated as:
threshold =  size(validator_list_keys) < 3
  ? 1
  : floor(size(validator_list_keys) / 2) + 1

This means that for a default 2 UNL publishers, the default threshold will be 1. Since "intersection of 1 sets" is not an intersection (it's an union) this makes the default behaviour (for one or two UNL publishers) identical to the current union system.
If a node configuration contains a third UNL publisher, the default threshold will be calculated as floor(3 / 2) + 1, that is 1 + 1 that is 2. This means that, for 3 validator lists, the node will only use validators which are present on 2 or more lists (and will silently ignore validators which are on one list only).
If the configured validator list contains 4 or 5 publishers, the default threshold will be 3. If the configured validator list contains 6 or 7 publishers, the default threshold will be 4 etc.
This PR adds an optional configuration option [validator_list_threshold] to validators.txt which can  be explicitly set to the minimum number of the lists on which a validator must be listed in order to be used (this number must not be greater than the size of [validator_list_keys]). If it is not set, or set to 0, the value will be calculated at startup from the size of [validator_list_keys] as explained above.
The actually used threshold value will be also displayed in the output of validators RPC method (alongside with the used list of validators, and the content of each configured validator list, as is the current output).
This change is not altering the list of the default UNL publishers. The intent of this PR is to make it safe to extend this list in the future.

Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactor (non-breaking change that only restructures code)
[ ] Performance (increase or change in throughput and/or latency)
[ ] Tests (you added tests for code that already exists, or your new feature included in this PR)
[ ] Documentation update
[ ] Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
[ ] Release

API Impact
Add new value validator_list_threshold to the output from validators RPC method
Add new (optional) section [validator_list_threshold] to validators file.

[x] Public API: New feature (new methods and/or new fields)
[ ] Public API: Breaking change (in general, breaking changes should only impact the next api_version)
[ ] libxrpl change (any change that may affect libxrpl or dependents of libxrpl)
[ ] Peer protocol change (must be backward compatible or bump the peer protocol version)

Good catch, however:
The use of Union of X sets is still valid, however as stated by OP, an attack surface opens up with a malicious publisher. There may be cases where an operator would want to use the Union of X sets instead of the intersect. I recommend allowing the use of both Union and Intersect, where Intersect is the default as to the clear benefits of it.

The use of union is definitely allowed and this PR won't change it, it's just not the default. The user only needs to configure the "intersection of 1", which is functionally equivalent to union.
[validator_list_threshold]
1

The intent of this PR is to make it safe to extend this list in the future.

Agreed, this would welcome an influx of (reputable) UNL publishers to greater network relevance. I must argue that standards are still to be applied with the addition of new(er) publishers to the default lists (validators-example.txt). Maintainers and trustees of rippled should not add any publishers or author to this list unless:

a proven track record on the network is present and backed.
author is recognized, present, relevant and of sound mind within the "community" of network users and network operators.

This so called standard should not be ambiguous or overreaching in its limited scope. The consequence of such will result in extreme ends.

Agree, but this is outside of the scope of this PR.


Maven central version

The project seems to be updated to version 1.0.0. But it is not yet reflected in maven central yet (still shows v0.2). Is it still in testing?

It's very probably only a matter of days. We need to fix a few last things regarding the CI and then we will publish a version 1.0.0 to maven central. Stay tuned. ;-)


Application Insights count for events is doubled

The count for each event in Application Insights is double of what's the reality. For example the count for the event Authentication AUTOMATIC . should have been 2 since I only opened the app twice in that timeframe, but the count for that event is 4. The example is from testing with equinor/mad-project-hearing-test-client.

This package is getting phased out, and we do not plan to make any improvements unless they are critical for the remaining apps. Closing this issue


Is it possible to render react class inside the Playground component?

Question
First thank you for this awesome project 🚀
Description
I was wondering, can we render react class inside the Playground component?
For example like material ui is doing here https://material-ui.com/demos/dialogs/#simple-dialogs (you need to click on the "Show the source" button).
Thanks!

@pradel You can write out Playground like a text

Maybe more explanation, it's more how to do to write components with state, for example a modal with an open / close state, eg:
<Playground>
  {() => {
    class Test extends React.Component {
		state = { ... }
		// Class with a managed state
	}
    return <Test />
  }}
</Playground>

@pradel could please you upgrade docz? We sent a new release that what you want to do, work!

@nicholasess can you post an example? i tried to do it with the latest version but i get:

Cannot read property 'toString' of undefined
Stack trace
in Po (created by BasePlayground)
in BasePlayground
in Component (at slideNext.mdx:17)
in div (created by MDXTag)
in MDXTag
in Component (at slideNext.mdx:10)
in Component (created by o)
in o (created by AsyncComponent)
in AsyncComponent (created by t)
in t
in b (created by s)
in s
in Component (created by AsyncRoute)
in div (created by Styled(div))
in Styled(div) (created by ConsumerMemoization)
in div (created by Styled(div))
in Styled(div) (created by ConsumerMemoization)
in div (created by Styled(div))
in Styled(div) (created by Xe)
in Xe (created by ConsumerMemoization)
in ConsumerMemoization
in CopyOnWriteConsumer
in ThemeConfig (created by ht)
in ht (created by AsyncRoute)
in AsyncRoute (created by t)
in t (created by ConsumerMemoization)
in t (created by ConsumerMemoization)
in ConsumerMemoization
in CopyOnWriteConsumer
in MDXProvider (created by DocPreview)
in DocPreview (created by ConsumerMemoization)
in ThemeProvider (created by ConsumerMemoization)
in ConsumerMemoization
in CopyOnWriteConsumer
in ThemeConfig (created by Component)
in Component (created by DoczTheme)
in DefaultWrapper (created by DoczTheme)
in t (created by t)
in t (created by DoczTheme)
in DataServer (created by DoczTheme)
in CopyOnWriteStoreProvider (created by DoczTheme)
in ErrorBoundary (created by DoczTheme)
in DoczTheme (at root.jsx:9)
in Root (created by HotExportedRoot)
in AppContainer (created by HotExportedRoot)
in HotExportedRoot (at index.jsx:15)

I think this should have an example in the docz.

The "toString" error is because you need to define this.state in your constructor.

react-live can take regular classes and functions without wrap, is this possible in Playground somehow? It would be great to show examples unobstructed by boilerplate. Just a class with lifecycles would be great. I tried to do what @nicholasess said, writing it out as text, but i either don't get what that means, or it doesn't seem to work.

Here is a working example:
import { Playground } from 'docz'
import Modal from './'

<Playground>
  {() => {
    class Example extends React.Component {
      constructor (props) {
        super(props)

        this.state = {
          showModal: false
        }
      }

      handleShowModal () {
        this.setState({ showModal: true })
      }

      handleCloseModal () {
        this.setState({ showModal: false })
      }

      render () {
        return (
          <React.Fragment>
            {this.state.showModal &&
              <Modal
                title='Title'
                onClose={() => this.handleCloseModal()}
              >

                  Lorem ipsum dolor sit amet, consetetur sadipscing elitr,
                  sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua.
                  At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren,
                  no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet,
                  consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat,
                  sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren,
                  no sea takimata sanctus est Lorem ipsum dolor sit amet.

              </Modal>
            }
            <Button onClick={() => this.handleShowModal()}>Show Modal</Button>
          </React.Fragment>
        )
      }
	  }

    return <Example />
  }}
</Playground>

Fixed in the v0.12.9.
Now is possible to render a class directly inside the playground:
import { Playground } from 'docz'

<Playground>
  {class Counter extends React.Component {
    constructor() {
      super()
      this.state = { count: 0 }
    }

    componentDidMount() {
      this.interval = setInterval(() => {
        this.setState(state => ({ count: state.count + 1 }))
      }, 1000)
    }

    componentWillUnmount() {
      clearInterval(this.interval)
    }

    render() {
      return (

            {this.state.count}

      )
    }
  }}
</Playground>

Fixed in the v0.12.9.
Now is possible to render a class directly inside the playground:
import { Playground } from 'docz'

<Playground>
  {class Counter extends React.Component {
    constructor() {
      super()
      this.state = { count: 0 }
    }

    componentDidMount() {
      this.interval = setInterval(() => {
        this.setState(state => ({ count: state.count + 1 }))
      }, 1000)
    }

    componentWillUnmount() {
      clearInterval(this.interval)
    }

    render() {
      return (

            {this.state.count}

      )
    }
  }}
</Playground>

It is not work for v0.13.7.
Error
SyntaxError: Unexpected token (3:16) 1 : (<React.Fragment> 2 : class DemoModal extends React.Component { 3 : constructor() { ^

agree. please see #567 as many people have reported this issue

can someone fix this issue?


fix backend check

Hi @muellerzr
Related to #2652 . I think we'd better have a test on it.
I think the best way is to have an end-to-end test in the CI; it will avoid most issues : )

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Replace use of adoptopenjdk

See https://github.com/Senzing/docker-init-container/issues/426

Resolved in version 0.5.0


[Feature Request] Condition Lab & Triggler alternate

I might be in the minority, but DFRED Convenient Effects is not my favorite module.  Tried using it multiple times but Condition Lab & Triggler always seems to win. Is it possible to have Condition Lab as an alternate to DFreds?

See the response on your last issue.
https://github.com/TheGiddyLimit/plutonium-addon-automation/issues/100#issuecomment-1766691569


Fix some Travis warnings:

sudo is no-op;
matrix is a jobs alias.

Overview

See: https://jira.bf.local/browse/ECR-XYZ
Definition of Done

[ ] There are no TODOs left in the code
[ ] Change is covered by automated tests
[ ] The coding guidelines are followed
[ ] Public API has Javadoc
[ ] Method preconditions are checked and documented in the Javadoc of the method
[ ] Changelog is updated if needed (in case of notable or breaking changes)
[ ] The continuous integration build passes

Coverage remained the same at 85.114% when pulling ddb8a69a187d04802d93e1f21f435ab6118c6afd on fix-travis-warnings into e0212696d0715ed6fde4654a5d118d4eef03a3ad on master.


Crawling

About the PR
this pr adds the mechanics of crawling,  allowing you to crawl, take less damage from explosions, move slower, move over tables, not get up after being stunned, and fall after explosions.
and rebinds charecter menu to the U button, not the C button, which it is now used to toggle crawling.

More RP opportunities.
More immersive.
Futute cqc сombos

Technical details
the CrawlingComponent is the same with the SlowDownComponent, but is used to fix failures after a stun is performed
Media

[X] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase
https://discord.com/channels/310555209753690112/310555209753690112/1270844783253917857

Changelog
:cl:

add: Nanotrasen held a crawling workshop, now all crew members know how to crawl!
tweak: After the crawling masterclass, all crew members forgot how to automatically get up after a fall!

awaiting fixing tests....

This should probably be replicating SS13's UX for resting-based knockdowns, where you automatically attempt to stand back up after being knocked down (depending on the on-by-default setting) when you aren't already resting. Otherwise, this could end up being way too confusing for new players that find themselves in combat scenarios unprepared.
Aside from that, this is one hell of a banger of a first PR. Mad props tbh

At least in ss13 servers the rotation is different but here it destroys visual recognisability entirely? Now when someone is down you have no idea if they can even move or not.

Over time they will get used to it

Aye, that's pretty much the same growing pain that most SS13 servers that went for it had to go through. Some servers don't even try to address that at all, some servers go for a fairly subtle way of differentiating truly stunned from resting (like Citadel Main's deepfrying of stunned spacemen), and some servers go for status icons that pop up when someone's truly stunned (such as the status indicators from Polaris and its derivatives). All of those have their own sets of implications, pros, and cons!

Wouldn't this warrant a design doc? The concept itself is simple enough but I feel there should be do's and don'ts with this.

At least in ss13 servers the rotation is different but here it destroys visual recognisability entirely? Now when someone is down you have no idea if they can even move or not.

it's possible to determine whether a person is dead or alive by examining them

Wouldn't this warrant a design doc? The concept itself is simple enough but I feel there should be do's and don'ts with this.

Not at the moment, I don't know what or how to add to the documentation, but I can try to add something to the documentation

Yeah, the tests are passed

it's probably best not to disable auto stand, it'd just make combat clunkier imo

CHAT, dont worry i made icon so ANY newcomer will understand what to do
the designe is very human

bro why did you add sadam hussein to the game

it's probably best not to disable auto stand, it'd just make combat clunkier imo

Yea not so sure about this either, I feel like auto stand should stay but it'd be nice if you could cancel it by pressing the crawl keybind

auto standing up needs to stay or combat will become clunkier as a result imo

Small vote: whether to return the automatic elevator after stunned

waiting, waiting for the rewiew...

use r not c

if autostand got returned as comments suggest please remove the changelog that says you dont autostand

please dont abandon it, i want crawling so badly

everyone pray at the same time and focus energy so that this PR becomes reality

I've been waiting for this to get merged so I could play the game again, would be a shame if that doesn't happen

nevah give up. Give us crawling!

Crawling by Linkin Park starts playing

CRAWLING IN a week
nice, started a rally. need to keep the attention on this PR

aaaaaaaaaaaaaaaaaaaaaaaaaaaaa

just a week away....

we need this so bad bruh

As soon as this gets merged I'll be crawling back into playing ss14, no matter the consequences.

2 months later....

I would like to remind everyone that github comments are meant to be productive. Not "When merge".
These comments can be kept on our discord or forums. Thank you for your cooperation.


Adds support for $(location) expansion in aspect for C++ targets.

The aspect implementation goes around the deprecation of
ctx.expand_make_variable by providing its own implementation. However
support for $(location) expansion was not supported in the orifinal
fix which leads to errors being generated in targets which use this
expansion.
This patch addresses this issue by adding support for $(location)
expansion.
Checklist

[x] I have filed an issue about this change and discussed potential changes with the maintainers.
[] I have received the approval from the maintainers to make this change.
[x] This is not a stylistic, refactoring, or cleanup change.

Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.
Discussion thread for this change
Issue number: 522
Description of this change
The aspect implementation goes around the deprecation of
ctx.expand_make_variable by providing its own implementation. However
support for $(location) expansion was not supported in the orifinal
fix which leads to errors being generated in targets which use this
expansion.
This patch addresses this issue by adding support for $(location)
expansion.

I would say it stalled because no one reviewed the issue. The bug is still there, I guess. In any case, you should Cider-V anyway.

Hi @sambatyon thanks for clarifying, and apologies! I'll reopen it for now and leave it to the reviewers to look into it and determine what the next step should be for this PR.

Closing because I no longer have the context of this issue. ctx.expand_make_variables was deprecated a while ago, so hopefully the aspect does not rely on them anymore and the use of $(location) is currently discouraged


Canon and Gigue not audible on iOS/Safari

On iOS/Safari, this project loads and runs, but there is no sound.
https://arcade.makecode.com/49498-81415-29450-07533
To Reproduce

On your iPhone, open the above link.
Notice the project runs (screen fades in, snow is falling), but there is no sound.

Device: iPhone X
OS: iOS 14.1
Browser: Safari

iOS requires user interaction to get sounds. We should fix this.

From: Eric Anderson<EMAIL_ADDRESS>Sent: Friday, November 13, 2020 6:41:18 PM
To: microsoft/pxt-arcade<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [microsoft/pxt-arcade] Canon and Gigue not audible on iOS/Safari (#2563)
On iOS/Safari, this project loads and runs, but there is no sound.
https://arcade.makecode.com/49498-81415-29450-07533https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Farcade.makecode.com%2F49498-81415-29450-07533&data=04|01|jhalleux%40microsoft.com|0c9b9b01bb7d4816eff508d887fb53dc|72f988bf86f141af91ab2d7cd011db47|1|0|637408860798752332|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=TgW%2FojWDsCIoabHKSjR%2FFL9kInI9Z0kYRbZbf00x3HI%3D&reserved=0
To Reproduce

On your iPhone, open the above link.
Notice the project runs (screen fades in, snow is falling), but there is no sound.

Device: iPhone X
OS: iOS 14.1
Browser: Safari

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fpxt-arcade%2Fissues%2F2563&data=04|01|jhalleux%40microsoft.com|0c9b9b01bb7d4816eff508d887fb53dc|72f988bf86f141af91ab2d7cd011db47|1|0|637408860798762324|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=jUifwBZptyRT%2BHl1JVa5igqtGmboe7a9LfqfhAGZ8U0%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAA73QKPM5HOYHKE2NMNLMS3SPVVT5ANCNFSM4TU3LGEA&data=04|01|jhalleux%40microsoft.com|0c9b9b01bb7d4816eff508d887fb53dc|72f988bf86f141af91ab2d7cd011db47|1|0|637408860798762324|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=VbFJVt9gntSRgZ9hrMikw82ID8GTB75JGcNTyZyJlqQ%3D&reserved=0.

Fixed


Problem fixing it

How can I install current version in my phone

Ok

Please let me know when it's done fixing ok I will be glad


Full page screenshots on pages that make use of 100vh

This might be a more generic Chrome bug, but I'm running into it during my experience with puppeteer, so I apologize if it's outside of the scope of this project.
Certain websites that I am trying to render full page screenshots for are not rendering correctly due to their use of 100vh on containers. I'm assuming this is because before taking a screenshot it sets the viewport height to the height of the entire scrollable page? This causes the 100vh container to be incredibly tall, which of course breaks the layout of the page. Rendering non-full page screenshots pose no issue.
Is there any possibility to handle this issue without having to manually stitch together multiple smaller screenshots?

This is more of a "bug" in headless Chrome, but also expected due to the reasons you mentioned.
100vh gets pretty tricky. The opposite is described in https://github.com/GoogleChrome/puppeteer/issues/746 where the page users a 100vh/100vw container with overflow children content. The full page screenshot result turns out to be just the viewport width/height.
I'm not sure Puppeteer can provide solutions for these edge cases. You may have to stick multiple screenshots together for cases like this :\

Dupe of #703


Change diff to evaluate PKs for FK relationships

I am going to write up an issue to relate to this PR in the next day or two. At the moment, I'm focused on getting this fix merged into our fork to resolve some bloating on our LogEntry table. (Done, see attached issue)
Take a look and let me know what you think of this fix. I did look through the current issues and couldn't find anyone else complaining about this so maybe we've got some anti-patterns going on in our code. The issue is only happening in some of our more complex systems but I'm sure we're not that unique. I'll highlight the test case that shows the fix.
After letting this sit for an hour or two I realized this change will fix another more insidious bug. Currently, in cases where there are more than one object with the same string representation (e.g., two or more "John Smith" objects in the Customer model) and a related object is updated to a different object with the same string representation (e.g., an update to a PhoneNumber object "+1555-555-5555" to belong to a different "John Smith" Customer object) auditlog is not able to capture that update. This is because because the diff method is comparing object strings rather than primary keys and there is no guarantee that the __str__ method is returning a unique value. Therefore, a portion of updates to ForeignKey fields are likely not being captured by auditlog on current installations.
In this commit you can see a test case that demonstrates the flaw and how it is resolved by this change.

The diff method now evaluates the primary keys for changes to determine
if a new LogEntry should be created. Previously, the diff method was
evaluating the string representation of the object. This was flawed
because cases can occur when a parent object has in memory changes to
its string string representation and the child related object is saved
prior to these in memory changes being persisted. In these cases a new
LogEntry object would be created erroneously. This cases is asserted
with a test and a regression test will verify the bug.
The consequence of these updates is that the LogEntry.changes field
now stores primary keys rather than string representations for related
objects. To keep the changes dictionary display unaffected by this
update, a method was added to the LogEntry model. This method looks
up the object display string from the stored foreign key. Exceptions
were written to handle backwards compatibility.
Issue

I think this change is a breaking change as the patch is changing the representation of the related field. we need to add changelog for that and explain the change and the breaking change.
Also, It would be great if @alieh-rymasheuski can take a look.

Thanks @sum-rock for addressing the comments. As I mentioned in https://github.com/jazzband/django-auditlog/pull/420#issuecomment-1256233511 it is a breaking change and we can not include it in 2.2.
we will include it in 3.0

@sum-rock we are preparing v3.0. Could you please refresh this PR?

@hramezani This branch is now refreshed


How vscode plugins guarantee security

How vscode guarantees that plug-ins run securely(eg: modifying the file system by plugin )? Does it run them in In frame?

@Chetan11-dev VS Code does not offer a sandbox for extension execution. Extensions execute in a nodejs process with the same privileges as the VS Code process. You should therefore only install extensions from authors you trust.


Add adaptation for yaml_file from stdin

usage case:
curl -sSfL https://x.x.x.x/tools.yaml | ./download-utilities.sh -

I cut a new release and added validating checksums through stdin.


[bug] webview can not render

Describe the bug
Same code with different url gives different results in WebViewBuilder.
At first I thought it was a certificate issue, but it wasn't, the following is a test case.
Can render in dev mode and build app

https://www.taobao.com/
http://tv.cctv.com/lm/jdft/jd/index.shtml

Can render in dev mode but can not render in build app

http://news.cntv.cn/special/shzyhxjzg/

Can not render in dev mode and build app

https://www.baidu.com/

Reproduction

write test code

    let _webview = WebViewBuilder::new(window)?
        .with_url("test-url")?
        // .with_devtools(true)
        .with_initialization_script(script)
        .with_ipc_handler(handler)
        .build()?;

replace test-url with cases:

https://www.taobao.com/
http://tv.cctv.com/lm/jdft/jd/index.shtml
http://news.cntv.cn/special/shzyhxjzg/
https://www.baidu.com/

run dev and build to see results

Expected behavior
I can see website in dev mode and build apps.
Platform and versions
Environment
› OS: Mac OS 12.6.0 X64
› Node.js: 18.10.0
› npm: 8.19.2
› pnpm: 7.13.4
› yarn: 1.22.19
› rustup: 1.25.1
› rustc: 1.64.0
› cargo: 1.64.0
› Rust toolchain: stable-x86_64-apple-darwin
Stack trace
No response
Additional context
No response

All urls worked fine for me on Windows. maybe macos is different or maybe some urls are blocked for you? Could you try a vpn or use a proxy?

I will try it as you said.


NullPointerException when processing node_modules

Describe the bug
Gradle build checking the dependencies fails miserably with the NullPointerException.
Version of dependency-check used
The problem occurs using version 6.5.3 of the gradle plugin
It works OK using <IP_ADDRESS>
Log file
In the output I see:
An unexpected error occurred during analysis of 'blahblah/package-lock.json' (Node.js Package Analyzer): null

java.util.ConcurrentModificationException
        at java.base/java.util.TreeMap$KeySpliterator.forEachRemaining(TreeMap.java:2750)
        at java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:658)
        at org.owasp.dependencycheck.analyzer.DependencyMergingAnalyzer.mergeDependencies(DependencyMergingAnalyzer.java:155)
        at org.owasp.dependencycheck.analyzer.NodePackageAnalyzer.processDependencies(NodePackageAnalyzer.java:419)
        at org.owasp.dependencycheck.analyzer.NodePackageAnalyzer.processDependencies(NodePackageAnalyzer.java:364)
        at org.owasp.dependencycheck.analyzer.NodePackageAnalyzer.analyzeDependency(NodePackageAnalyzer.java:265)
        at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.analyze(AbstractAnalyzer.java:131)
        at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:88)
        at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:37)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:834)

and then the build fails with:
java.lang.NullPointerException
        at org.owasp.dependencycheck.exception.ExceptionCollection.nestedCauseList(ExceptionCollection.java:220)
        at org.owasp.dependencycheck.exception.ExceptionCollection.lambda$getMessage$2(ExceptionCollection.java:215)
        at org.owasp.dependencycheck.exception.ExceptionCollection.getMessage(ExceptionCollection.java:212)
        at org.gradle.internal.exceptions.DefaultMultiCauseException.printSingleCauseStackTrace(DefaultMultiCauseException.java:143)
        at org.gradle.internal.exceptions.DefaultMultiCauseException.printStackTrace(DefaultMultiCauseException.java:131)

These exceptions don't seem to be very helpful. I debugged the plugin and I caught it spitting NPE here:

jo.getBoolean("optional", false); throws NPE as the optional field is not present. Not sure of the problem is in org.glassfish.json.JsonObjectBuilderImpl:

that is explicitly throwing NPE in this case.
To Reproduce
Expected behavior
No NPE and finish the processing.
Additional context
Add any other context about the problem here.

Except for the fact that we're not calling javax.json.JsonObject#getBoolean(String), but javax.json.JsonObject#getBoolean(String, boolean), which is handling the NPE that you point to by returning the default value offered as a second parameter

So your analysis regarding the source of the NPE is wrong.
According to the stacktrace the NPE is at
at org.owasp.dependencycheck.exception.ExceptionCollection.nestedCauseList(ExceptionCollection.java:220)
where it is also logical that this can happen: at that line it's initializing a StringBuilder with the message of the Exception, which for various reasons known only to the creators of the exception may be null (as can be observed from the initial logged exception in your build):

An unexpected error occurred during analysis of 'blahblah/package-lock.json' (Node.js Package Analyzer): null .

So the stacktrace is perfectly usable to obtain the root-cause: trying to initialize a StringBuilder with null.

@pbielicki Would you be able to share a project that exhibits the throwing of the java.util.ConcurrentModificationException?
Because it's easy to fix the NPE in the next release, but that would still leave your project open to the initial ConcurrentModificationException, so I don't think just fixing the NPE would be any good to you.

@aikebah sorry for the late reply - I was off last week.
I can't share the project as it's a closed-source. I plan to work on a reproducer but I don't think it will be something quick and obvious.

@pbielicki If you happen to uncover the scenario under which the ConcurrentModificationException happens please comment to #4374 with your findings. The NPE will be fixed in our next release.


how to Controls for fullscreen playback

how can i use like this
// Configure the movie player controller
moviePlayer.controlStyle = MPMovieControlStyleDefault;
from scviewplayer class

please help me out as soon as possible.
my full code is here i want to default controller for play back full screen.
_player = [SCPlayer player];
_player.delegate = self;
playerView = [[SCVideoPlayerView alloc] initWithPlayer:_player];
playerView.frame = self.vWRecording.frame;
playerView.playerLayer.videoGravity = AVLayerVideoGravityResize;
[playerView sizeToFit];
[self.vWRecording insertSubview:playerView aboveSubview:self.vWRecording];
playerView.SCImageViewEnabled=YES;

UITapGestureRecognizer *TapRecognizer = [[UITapGestureRecognizer alloc] initWithTarget:self action:@selector(playerViewTouch:)];
self.vWRecording.userInteractionEnabled = YES;
[self.vwtranparant addGestureRecognizer:TapRecognizer];
.............
-(void)playerViewTouch :(UITapGestureRecognizer *)gesture{
[_player setItemByAsset:recordSession.assetRepresentingSegments];
if([_player isPlaying])

{
    self.vwtranparant.hidden = NO;

    [_player pause];

}else
{

    self.btnPlay.selected = YES;
    self.vwtranparant.hidden = YES;

    [_player play];
}

}


chore(release): v1.0.8 🎉

:robot: I have created a release beep boop
1.0.8 (2024-04-27)
Bug Fixes

migrate: embed ability to invoke migration as a command (17ca689)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ehmpathy/dynamodb-dao-generator/releases/tag/v1.0.8 :sunflower:


[dv] Improve jtag_riscv_agent

Addressed comments in #9149

This high-level driver is like a vseq, don't to check reset everywhere
as the lower-level should finish the item immediately once reset occurs.
change ref to output as it doesn't need to be ref

Signed-off-by: Weicai Yang<EMAIL_ADDRESS>

@NigelScales not sure if you have seen this. I merged it a bit too fast, but if you have any comment, I'm happy to address it in a separate PR.

@NigelScales not sure if you have seen this. I merged it a bit too fast, but if you have any comment, I'm happy to address it in a separate PR.

It's ok.
I can try a merge into my JTAG CSR branch and check the regression still passes.


Second build doesn't output CSS bundle

I'm using Webpack 4.2.0 and mini-css-extract-plugin to extract and bundle my CSS assets.
First build:
Hash: badd167d370d5517a181
Version: webpack 4.2.0
Time: 7179ms
Built at: 2018-3-26 08:47:58
                               Asset       Size  Chunks             Chunk Names
662ac09aa5b218926bf1ce839be78ff9.svg  868 bytes          [emitted]
                             app.css   19.9 KiB     app  [emitted]  app
                              app.js   9.35 MiB     app  [emitted]  app
                         app.css.map   25.1 KiB     app  [emitted]  app
                          app.js.map   12.5 MiB     app  [emitted]  app
                       ..\index.html   8.93 KiB          [emitted]
Entrypoint app = app.css app.js app.css.map app.js.map
[./Content/css/new-leave-management.css] 39 bytes {app} [built]
   [0] multi ./index.js 28 bytes {app} [built]
    + 567 hidden modules
Child html-webpack-plugin for "..\index.html":
     1 asset
    Entrypoint undefined = ..\index.html
       1 module
Child mini-css-extract-plugin node_modules/css-loader/index.js!Content/css/new-leave-management.css:
                                   Asset       Size  Chunks             Chunk Names
    662ac09aa5b218926bf1ce839be78ff9.svg  868 bytes          [emitted]
    Entrypoint mini-css-extract-plugin = *
    [./node_modules/css-loader/index.js!./Content/css/new-leave-management.css] ./node_modules/css-loader!./Content/css/new-leave-management.css 21.3 KiB {mini-css-extract-plugin} [built]
        + 3 hidden modules

Second build:
Hash: 3f2b5219997bbdef01c2
Version: webpack 4.2.0
Time: 6597ms
Built at: 2018-3-26 08:52:53
        Asset      Size  Chunks             Chunk Names
       app.js  9.35 MiB     app  [emitted]  app
   app.js.map  12.5 MiB     app  [emitted]  app
..\index.html  8.87 KiB          [emitted]
Entrypoint app = app.js app.js.map
   [0] multi ./index.js 28 bytes {app} [built]
    + 567 hidden modules
Child html-webpack-plugin for "..\index.html":
     1 asset
    Entrypoint undefined = ..\index.html
       1 module

As you can see, only Javascript files are generated. The main problem is that I no longer can clean the output folder before the build.
What could be the reason?

Might be related: CSS file is not emitted on incremental rebuild in watch mode

Having the same issue with Webpack 4.4.1 + mini-css-extract-plugin 0.4.0, even though the linked issues was closed.

Ended up removing hard source plugin. Webpack 4 is fast in watch mode anyway.

Any updates on this issue, looks this was addressed previously for extract-text-plugin and was a significant blocker for many in the community?  I imagine this will grow as more people adopt Webpack 4
https://github.com/mzgoddard/hard-source-webpack-plugin/issues/1
Also, many people aren't finding Webpack 4 faster, in fact slower on incremental builds
https://github.com/webpack/webpack/issues/6767

Created minimum use case example here https://github.com/dtothefp/hard-cache-mini-css-webpack-4

I'm having the same issue.
Here is my project repo: https://github.com/Venryx/DebateMap
And Webpack config: https://github.com/Venryx/DebateMap/blob/master/Scripts/Build/WebpackConfig.js

@Venryx that probably has to do with the stats that are generated by Webpack, have a look there as HTML plugin would read these stats to inject the <link>. I would also guess the file is not generated as well 🤷♂ .
Would be great to at least get some feedback on this issue. I've discovered that extracting CSS at all times in my dev builds took a large app that I have from a 30s rebuild to 3s. Would be good to combine with this plugin to decrease subsequent full Webpack builds

@dtothefp @nzav I added mini-css-extract support last week. The support went in along with a change to exclude modules from the disk cache who cannot be fully frozen. This was mini-css-extract's issue. It added a CssDependency to webpack and hard-source didn't know how to freeze it. mini-css-extract and it's CssDependency are now supported in hard-source and any other plugins that add Dependency types like that will work too (modules with those unknown-to-hard-source dependencies will not be written to disk).

We should be good on this issue.

thanks @mzgoddard. I'm going to add this into my project now and will report back if I come across any issues

@mzgoddard unfortunately this is now "broken" in a new way. I'm not sure of the intended use case of how CSS should update with caching but now if I save CSS, refresh the browser I will see updated CSS. But, if I quit the process and rebuild with the new CSS the styles will revert back to those at the time at the beginning of the first build.
I made a branch of my repo with updated plugin to v0.6.9 https://github.com/dtothefp/hard-cache-mini-css-webpack-4/tree/update-0.6.9
Steps to reproduce:

yarn install
yarn start
go to src/main.css and change the background color
refresh the browser and you will see the new CSS background color
quit the Node process and run yarn start again
open the browser and see that the CSS has reverted back to the original i.e. blue at the time of first build

I can open a new issue or you can re-open this one?

@dtothefp I would like a new issue if you could. What you posted is already really helpful. Please post that in the issue. What you are encountering is a separate issue from this one so I'd rather have a new one.
The issue you are having sounds like a symptom some other issues have where caches are not fully saved. In your case it sounds like the md5 cache is saved but the module cache is not. Causing the effect you're seeing. I'll write more on the new issue.

@mzgoddard thanks for the reply...made a new issue here https://github.com/mzgoddard/hard-source-webpack-plugin/issues/339


I love PicoModal, saved my day in one of my project.

picoModal({
      content: "Ah, the pitter patter of tiny feet in huge combat boots.",
      overlayStyles: {
          backgroundColor: "#169",
          opacity: 0.75
      }
  }).show();

I love the way it work. But is there any way we can load the data in Content from different files i mean with like
picoModal({
      content: "content.html",
      overlayStyles: {
          backgroundColor: "#169",
          opacity: 0.75
      }
  }).show();

This would be great.

I did this. Works fine.
picoModal({
      content: '<object type="text/html" data="content.html"></object>',
      overlayStyles: {
          backgroundColor: "#169",
          opacity: 0.75
      }
  }).show();

You could also do this via AJAX or an iframe. Cheers

//anAajxFunction();
picoModal({
      content: anAajxFunction(),
      overlayStyles: {
          backgroundColor: "#169",
          opacity: 0.75
      }
  }).show();

Thank you.. This is great. :+1:

Possible to add an example on how to use this with an iframe correctly please?


Creating Seamless UV maps (fails?)

Hi Kenshi,
First and foremost thanks a lot for providing this implementation!
I wanted to use this method to create a seamless uv-map for a 3D mesh. I came up with the following procedure:

Use the same mesh for A-orig.obj and B-orig.obj. I used this shape:
A-orig.obj.zip

Define some landmarks with your landmark picker while ensuring in a post-processing step (manual editing of landmarks.txt) that all landmarks are identical on both shapes. I picked the following landmarks:
landmarks.txt

Running the seamlesssurfmap implementation as follows: ./seamlesssurfmap --num-iter=10

Unfortunately results do not look very "seamless":

For creating the texture map i used the vertex and face information stored in A-disk-refined.obj while i assigned each vertex of A-disk-refined.obj a uv-coordinate by using the vertex information stored in A-gmap.obj.
I know this is the unofficial implementation but results look far different from what i expected from the paper. Do you have any suggestions where I made a mistake or how i can improve the results?
Thanks a lot!
Paul

Hi Paul,
Thank you for trying out my implementation, I'm very happy that it's useful to someone:)
Sorry but I have to point out that you're misunderstanding what the seamless maps are. If you try to paste a checkerboard pattern onto any genus-0 surface, there will necessarily be some visible seams somewhere, no matter what UV parameterization method is used.
The typical UV checkerboard pattern visualizations used in those cross-parameterization (or inter-surface mapping) papers use the simple method of projecting the mesh to a 2D image plane from a certain viewpoint and use the resulting 2D coordinates as the UVs (thus, the checkerboard looks nice from near that chosen viewpoint while it looks stretched in the "side" views). The map is "seamless" in that the checkerboard pattern transferred from A to B does not exhibit any visible seams (although the mapping itself involves seams).
I've pushed a small code (that I already had without committing) that generates UVs using the above-mentioned method, as well as an additional functionality to output B-with-A-uv.obj when A-orig.obj contains UV data.
https://github.com/kenshi84/seamlesssurfmap/commit/f4f4eb43020958ff61b4ca6cd5c228aeb3734e46
Below is a screenshot using your data: on the left is A with its original UV, on the right is B with UV transferred from A. Their cut graphs are also shown in green (notice the difference around the left arm).

ssm-test.zip

Hi Kenshi,
thanks for the reply. I already was very curios how it actually could work... so its no suprise that it doesnt work as i hoped it would.
Yes we are using the same procedure right now but our problem is that we want to display shapes  in different poses where this whole pipeline breaks...
Nevertheless, thanks a lot for your help! I will leave this issue open so that others can see what is possible and what is not possible with the seamless framework :)


New Coinbase API

Hello,
Any plans to support the new Gdax API scheduled for 12/31/2018?
GDAX API Integrations:

There will be no disruption to the gdax.com API during this time. GDAX APIs will continue to function until December 31, 2018.
We encourage Coinbase Pro users to begin migrating their API usage away from api.gdax.com to api.pro.coinbase.com.

Thank you!

Update config file and problem solved.
c.gdax.apiURI = 'https://api.pro.coinbase.com'
c.gdax.websocketURI = 'wss://ws-feed.pro.coinbase.com'


fix bug in cmorize_obs_eppley_vgpm_modis.py (#1729)

Tasks

[x] Create an issue to discuss what you are going to do, if you haven't done so already (and add the link at the bottom)
[x] Give this pull request a descriptive title that can be used as a one line summary in a changelog
[x] Make sure your code is composed of functions of no more than 50 lines and uses meaningful names for variables
[ ] Circle/CI tests pass. Status can be seen below your pull request. If the tests are failing, click the link to find out why.
[x] Preferably Codacy code quality checks pass, however a few remaining hard to solve Codacy issues are still acceptable. Status can be seen below your pull request. If there is an error, click the link to find out why. If you suspect Codacy may be wrong, please ask by commenting.
[x] Please use yamllint to check that your YAML files do not contain mistakes
[x] (Only if really necessary) Add any additional dependencies needed for the diagnostic script to setup.py, esmvaltool/install/R/r_requirements.txt or esmvaltool/install/Julia/Project.toml (depending on the language of your script) and also to package/meta.yaml for conda dependencies (includes Python and others, but not R/Julia)
[x] If new dependencies are introduced, check that the license is compatible with Apache2.0

Modified data reformatting script

[x] Test the CMORized data using recipes/example/recipe_check_obs.yml, to make sure the CMOR checks pass without errors
[ ] Tag @mattiarighi in this pull request, so that the updated dataset can be added to the OBS data pool at DKRZ and synchronized with CEDA-Jasmin

If you need help with any of the tasks above, please do not hesitate to ask by commenting in the issue or pull request.

Closes #1729

I think you need to add the package also to setup.py, @bouweandela ?

I think you need to add the package also to setup.py, @bouweandela ?

I think you are right mattia ...

The installation fails
ERROR: Could not find a version that satisfies the requirement pynio (from ESMValTool==2.0.0b4) (from versions: none)
ERROR: No matching distribution found for pynio (from ESMValTool==2.0.0b4)

which is I guess the same reason why the tests are failing.

Thank you for the fix.
@bouweandela please merge and cherry-pick into v2.0.0-release.

Done


I want to mark existing address as default billing address So I do not have to choose it every order

Context
There is a special flag in the addresses, which is Default Billing Address. I want to be able to set existing address as the default one for the billing.
Acceptance Criteria

In My Addresses link I can see the possibility of setting an address as default billing address.
I can see which address is currently set as default billing address.
After I change the default billing address then I can see the flag at the new default billing address.
Default billing address is used by default in a checkout.

It was already done.


Improve process for registering new harmonization techniques

Currently, new harmonization classes must be placed in the harmonization directory of habet. It would be nice if these techniques could be registered without needing to place them in a specific directory.
Probably depends on #22, as I know there's some kind of entry point / plugin infrastructure with setup.py, but I'm not familiar with it.

One option is that if the user points to the path where their API extension lives, then you can import it from that path using importlib.
Then again if someone wants to extend the API with their own harmonization technique, maybe they should have to fork the repo and do their own thing. They would already be comfortable with python programming. And it would encourage to contribute their extension back here.

After discussion, we favor something more like the importlib approach. Becuase it would be nice to be able to only pip install and have the ability to use custom harmonization


Some files is missing

Hi i found this project on Flutter Awesome and i want to try it but after i download i saw missing apikeys.dart file. I added that file but when i start to build it gives me "[VERBOSE-2:engine.cc(127)] Engine run configuration was invalid.
[VERBOSE-2:shell.cc(437)] Could not launch engine with configuration." errors. Can u show me what i am doing wrong?

Hi,
Have you got an API Key from newsapi.org ?

Please update your News API in the file apikeys.dart.


Improve the logic of generating the paginated users

Purpose

$subject
Fix https://github.com/wso2/product-is/issues/13752

Approach
With the previous implementation, we increase the pageIndex even if that page does not show users equal to pageSize. Usually, the page should have users equal to the page size (Except for the last page). With this improvement, pageIndex will only increment if the page shows users equal to the page size.

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2473702744

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2473702744
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2474484138

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2504072721
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2506542659

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2506542659
Status: success


make tests cross-platform

use the path/filepath package to make tests work cross-platform

Thanks for this improvement! Worked for me.

I have  a question: how do you use this? because I had to create a main package, and export a cams.MakeCoordinate constructor function

https://github.com/Lacrymology/make-stls/blob/master/make-stls.go

My original plan was that this would be a package used in a program with UI. Since I probably won't get around to doing that I should add the main you wrote. I have been using it via a worse main program I wrote.

Ok, I added a main. Thanks for the input, I am new at Go.

np, glad it was useful