Remove tooltip default styles

:boom: Breaking Changes

:rocket: Enhancements

Enable users to use or remove default tooltip styles

:memo: Documentation

Update tooltip docs

:bug: Bug Fix

:house: Internal

Fixes https://github.com/hshoff/vx/issues/650

@dennisja thanks for the PR including tests! 🙌
It differs slightly from the solution @hshoff discussed/proposed in #650, instead of adding withDefaultStyles, can we add unstyled (with a default to = false), and also update the default of style to be = defaultStyles? (along with the export of defaultStyles)
this would support the current behavior + styles by default, but allow you override all of (or a subset of) defaultStyles, or apply no styles whatsoever.

I have changed it to behave like how @hshoff suggested but there is an issue with the implementation. If a user accidentally uses the tooltip like
<Tooltip unstyled style={{...someStylesAUserWantsToApply}} />

The styles will not be applied

@dennisja thanks for this contribution! I think that the case you call out is okay, unstyled seems like it should be self-explanatory and we can revisit if we get negative feedback about this 👍
will try and get this out in the 0.0.196 release today.

out in 0.0.196

Just a note that this is a breaking change for anyone who was passing in a style prop to Tooltip. Might be worth updating the CHANGELOG to reflect that.

We’ll update the changelog.
For now, work around is to import defaultStyles and extend it through style prop.
<Tooltip style={{ ...defaultStyle, style }} />

Updated the changelog and included a before/after 👍


About train step

Hi,Wang,I have run your project in Ubuntu20.04 successfully,and I run this code you have mentioned python main.py --env_name walker2d-medium-expert-v2 --device 0 --ms offline --lr_decay --early_stop
Now,I want to know how many steps I should train the agent if I wanna get a better training effect.Or, could you tell me which file contains the largest training step.
Thank you!

It will print out the experiment log, and it usually converge very quickly and you will see the score around 1.1 (110%). The default is for training 2000 epochs, where epoch consists of 1000 training steps. Usually, 500 epochs you should see good results.

Thanks for your reply!It is very helpful for me.


Children Flatlist with horizontal direction not working

Current behavior
Configuring a flatlist with horizontal direction on a Tab.ScrollView is not working as expected, the content is being displayed vertically instead of horizontally
Expected behaviour
The Content to be displayed in the horizontal direction
Code sample
https://github.com/tcorreiaubi/CollapsibleTabViewsDemo

Screenshots (if applicable)

What have you tried

@PedroBern Hey, sorry to bother, im a bit stuck on this one, not sure if this is caused because of the tabs being wrapped on a flatlist with horizontal direction

No worries :)
Yes maybe, I'm not sure, didn't have the time to test. Try to add nestedScrollEnabled={true}

Just tested it, not working, I think the issue is related to the width that's forced to the ScrollView,
  function useCollapsibleStyle(): CollapsibleStyle {
    const { headerHeight, tabBarHeight, containerHeight } = useTabsContext()
    const windowWidth = useWindowDimensions().width

    return {
      style: { width: windowWidth }, // If I remove the width the scroll does work, but obviously everything else stops working properly
      contentContainerStyle: {
        minHeight: (containerHeight || 0) + headerHeight,
        paddingTop: headerHeight + tabBarHeight,
      },
      progressViewOffset: headerHeight + tabBarHeight,
    }
  }

    const {
      style: _style,
      contentContainerStyle: _contentContainerStyle,
    } = useCollapsibleStyle()

    return (
      <Animated.ScrollView
        ref={refMap[name] as any}
        nestedScrollEnabled
        bouncesZoom={false}
        style={[_style, style]}
        contentContainerStyle={[
          _contentContainerStyle,
          // @ts-ignore
          contentContainerStyle,
        ]}
        onScroll={scrollHandler}
        scrollEventThrottle={16}
        {...rest}
      >
        {children}
      </Animated.ScrollView>
    )
  }

Didn't work, strange enough, if I use a scrollview instead of a flatlist as child the content is displayed correctly, im confused

I was able to get it working by disabling the scroll on the pagerProps and rendering a Tabs.Flatlist instead of scrollview and also passing the content as the prop ListEmptyComponent, feels kinda hacky, but I believe the issue is related with nesting a flatlist in the same direction, Tabs.container(aka horizontal flatlist) > Tabs.ScrollView/Tabs.Flatlist(vertical) > View > Flatlist horizontal
There was also some scenarios where I would lose the ref of nested flatlists
Just leaving the issue open to hear what you think about it, but feel free to close it if there's nothing to be added

See #163 for the same issue and a workaround.

@andreialecu same issue yes but a workaround is no fix. In my opinion one of these issues should remain open and deserves more attention.


What is the effort?

I've been going through PowerShell, psake etc creating Build, Test and Deploy steps. This can include ARM templates and inserting JSON snippets into the overall provisioning steps. I know 80% can be done with convention over configuration. I'm wondering what the effort would be to leverage Plaster to do this?

Have a look at the Examples\NewModuleTemplate\plasterManifest.xml.  It should give you an idea of what is possible.  Also look at the build.ps1 file that gets scaffolded if you select the PSake option.

@dfinke I'm closing this issue but if you disagree let me know and I'll re-open it.


Questions: Modules and :id/edit

Hi James,
I'm trying to migrate a "large" react application which has modules with it's own routes from react-router v4 to junctions.
I have two questions:
Modules
I currently have an Auth module which has all components like /sign-in and /register. These are "root" routes, but I don't really want them in my root junction. As I find in the documentation, this isn't really possible with junctions because it only has relative paths, and I should OR have it like /auth/sign-in with a auth-junction OR have the routes in the main junction. Is that correct?
:id/edit
I have three routes:
/assets
/assets/:id
/assets/:id/edit
How would I create these in junctions?
Currently I got this far:
const mainJunction = createJunction({
  Auth: {
    next: AuthScreen.junction,
  },
  Assets: {
    next: AssetsScreen.junction,
  }
});

// Junction in AssetsScreen
const junction = createJunction({
  Asset: {
    path: '/:id',
    paramTypes: {
      id: { required: true },
    },
  // idea for /edit
  AssetEdit: {
    path: '/:id/edit',
    paramTypes: {
      id: { required: true },
    },
});

When I do it like this, I get an error that the routes match.
"Two branches have paths "undefined" and "undefined" that match the same URLs!"
(the undefined is caused by trying to grab .path on this line: https://github.com/jamesknelson/junctions/blob/master/source/createJunction.js#L106)
Is that correct or is that a bug? (I can send a PR if it's a bug)
I also tried /:id(/edit) or /:id/(edit) but none work. Do you think it's possible to have routes like this?
I'm also curious if you have any plans for Junctions. If I'm going to use it I could help you maintain it if you want (and write some more docs).
I also made a Redirect component and a withHistory decorator for react-junctions based on the context. This made it easier to migrate some components from react-router. If you want I could make a PR for them.
Thanks for the library, and looking forward to your reply :)

For your first question, you seem to have the idea. You'd either need to have a separate auth junction with its own path, or you could put them in the root junction.
For your second question, this error is actually intentional. The reasoning is that you don't know what will be under the next property of the /assets/:id junction, so you can't guarantee that /assets/:id/edit will not collide with /assets/:id.
You can get around his by making /edit the next junction for /assets/:id. For example:
const junction = createJunction({
  Asset: {
    path: '/:id',
    paramTypes: {
      id: { required: true },
    },
    next: createJunction({
      Edit: {
        path: '/edit',
      }
    }),
  }

The only tricky part here is that you'll need to pass the id down via component props -- junctions won't do it for you.
I do have plans to improve the docs and add a bit more sugar, but not sure when I'll get around to it. Help with maintenance would definitely be appreciated! Also, I'd love to see the Redirect and other components you've made -- I don't have one yet myself.

Closing this due to inactivity. If you'd still like help with this, please re-open and I'll take another look.


Adding registry failed: Validation failed in API: name InvalidFormat 422: invalid value gitlab.com

Rancher versions:
rancher/server or rancher/rancher: v2.0.2
Infrastructure Stack versions:
healthcheck:
ipsec:
network-services:
scheduler:
kubernetes (if applicable):
Steps to Reproduce:
Add a private registry via the fronted. I was trying to add "registry.gitlab.com".
Results:
Validation failed in API: name InvalidFormat 422: invalid value gitlab.com: a DNS-1123 label must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character (e.g. 'my-name', or '123-abc', regex used for validation is 'a-z0-9?')

ok that was stupid .. I just named it also "gitlab.com" which is not allowed ..


interface for set/get

Hello,
I would expect a public API solution to allow for programmatic setting/getting values on the storage.
A common scenario that comes to my mind would be:
someElem.globalStorage.set('key', value)

For example setting initial values from window.SOME_CONFIG or other data manipulation if required.

Hi,
I've been working in a new element, global-data, which allows to set, and get any path in the storage. This element throw as well events with every change into the storage. For example:
<global-data on-subscribe="_onSubscribe" on-unsubscribe="_onUnsubscribe" on-set="_onSet"></global-data>
This is currently into the development branch.
Anyway, i'm thinking about try to achieve this using the Redux library and the Polymer element.

Google recently released:
https://google.github.io/uniflow-polymer/
You might be interested in that.

Oh wow! Thank you.


How might this support .transform()?

Here's an example:
const stringToNumber: toZod<string> = z.string().transform((val) => val.length);
const a = stringToNumber.parse('string'); // => 6

It'd be nice to know that the value passed to the schema WAS a string, but that the parsed object would return a number? Have you run into this?
My use case is that:

All my endpoints that take dates (in queries or request bodies) hit my backend as strings.
I'd like to .refine() the schema to make sure that they are ISO strings even
But after parsing with zod I'd love to use Date objects again.

So this is my example:
const stringToNumber: toZod<string> = z.string().transform((val) => new Date(val));
const a = stringToNumber.parse('2022-01-01'); => // Date('2022-01-01')

All my endpoints that take dates (in queries or request bodies) hit my backend as strings.

Same problem. It does not seem like there is a solution for this.

I did not end up using toZod. Here's my schema:

export const ZCoerceDate = z.any()
  .superRefine((v, ctx) => {
    if (!v) {
      ctx.addIssue({
        code: 'custom',
        params: {
          customCode: 'required'
        },
        message: 'Required',
      })
    }
  })
  .transform((v: any, ctx) => {
    if (typeof v === 'number') {
      v = v.toString()
    }
    const day = dw(v);
    if (!day.isValid()) {
      ctx.addIssue({
        code: 'custom',
        params: {
          customCode: 'could-not-parse'
        },
        message: 'Not a valid date, ISO date string, or YYYY-MM-DD formatted string',
        received: v
      });
    }
    return day.toDate();
  });

In the case above dw is really just a wrapper around dayjs.

I ended up using toZod when it works, but when things are too complicated and it fails, I have the following helper function:
/** Makes sure two types are equal */
export function TypesAreEqual<T,U>(trueOrFalse: T extends U ? U extends T ? true : false : false) {
    return trueOrFalse ? true : false
}

It doesn't tell me what is not compatible, but at least it tells me if they're incompatible.  For example:
export type Client = {
    client: string;
    score: number;
}

export const ClientSchema = z.object({
    client: z
        .string()
        .uuid()
        .transform((uuid) => uuid.toLowerCase())
        .refine((uuid) => uuid !== '00000000-0000-0000-0000-000000000000', { message: 'Client is required' }),
    score: z.number().min(1, { message: 'Score must be greater than 0' }),
})

// This will not compile if they don't match: Argument of type 'true' is not assignable to parameter of type 'false'
TypesAreEqual<Client,z.infer<typeof ClientSchema>>(true)


Issue #958

a few tests failed
[error] (gearpump-examples-complexdag/test:test) sbt.TestsFailedException: Tests unsuccessful
[error] (gearpump-examples-transport/test:test) sbt.TestsFailedException: Tests unsuccessful
[error] (gearpump-examples-fsio/test:test) sbt.TestsFailedException: Tests unsuccessful
[error] (gearpump-examples-sol/test:test) sbt.TestsFailedException: Tests unsuccessful

it seems all of them are timeout like
[info] DagSpec:
[info] - Dag should succeed to submit application with required arguments *** FAILED ***
[info]   java.lang.AssertionError: assertion failed: timeout (25 seconds) during expectMsgClass waiting for class org.apache.gearpump.cluster.ClientToMaster$SubmitApplication
[info]   at scala.Predef$.assert(Predef.scala:165)
[info]   at akka.testkit.TestKitBase$class.expectMsgClass_internal(TestKit.scala:423)
[info]   at akka.testkit.TestKitBase$class.expectMsgType(TestKit.scala:405)
[info]   at akka.testkit.TestKit.expectMsgType(TestKit.scala:718)
[info]   at org.apache.gearpump.streaming.examples.complexdag.DagSpec$$anonfun$3.apply$mcV$sp(DagSpec.scala:52)
[info]   at org.apache.gearpump.streaming.examples.complexdag.DagSpec$$anonfun$3.apply(DagSpec.scala:42)
[info]   at org.apache.gearpump.streaming.examples.complexdag.DagSpec$$anonfun$3.apply(DagSpec.scala:42)
[info]   at org.scalatest.Transformer$$anonfun$apply$1.apply$mcV$sp(Transformer.scala:22)
[info]   at org.scalatest.OutcomeOf$class.outcomeOf(OutcomeOf.scala:85)
[info]   at org.scalatest.OutcomeOf$.outcomeOf(OutcomeOf.scala:104)

+1 for issue 959.
+0 for issue 960
For issue 960, as it is a costy operation to create a test cluster, changing the testcluster implementation may more easy trigger the UT failure.

#959 is merged.

This is incorrect. Test time difference between creating a TestCluster per test suite and just one for all suites under services is negligible. See below timings
Time to run when creating a cluster per test suite under services
[info] Run completed in 3 seconds, 623 milliseconds.
[info] Total number of tests run: 13
[info] Suites: completed 10, aborted 0
[info] Tests: succeeded 13, failed 0, canceled 0, ignored 0, pending 0
[info] All tests passed.

Time to run when creating just one TestCluster for all test suites under services
[info] Run completed in 3 seconds, 208 milliseconds.
[info] Total number of tests run: 13
[info] Suites: completed 10, aborted 0
[info] Tests: succeeded 13, failed 0, canceled 0, ignored 0, pending 0

Also since the ClockService is never shut down after services test runs,
it may cause various other problems in other test suites.
There are many problems with tests for SequenceFileIOSpec, DagSpec, SOLSpec and TransportSpec 1

they start a masterHarness per test rather than a testsuite - potentially much more costly than creating a TestCluster per suite since it appears that each test spawns a separate process.
they spawn a separate process to run
they accrue many disassociated messages and other errors due their tests - see below
they require way too much time to just submit an application. Time to run one test under gearpump-examples-sol is 12 seconds. There should be a separate story to resolve some of these problems.

[WARN] [05/27/2015 22:38:34.106] [ReliableDeliverySupervisor] Association with remote system [akka.tcp://client1205992021@<IP_ADDRESS>:59328] has failed, address is now gated for [5000] ms. Reason is: [Disassociated].
[INFO] [05/27/2015 22:38:34.106] [LocalActorRef] Message [akka.remote.transport.ActorTransportAdapter$DisassociateUnderlying] from Actor[akka://master/deadLetters] to Actor[akka://master/system/transports/akkaprotocolmanager.tcp1/akkaProtocol-tcp%3A%2F%2Fmaster%40<IP_ADDRESS>%3A59329-4#1356873985] was not delivered. [4] dead letters encountered. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[INFO] [05/27/2015 22:38:34.252] [redirect] [INFO] [05/27/2015 22:38:34.251] [ClusterConfig$] loading config file application.conf...
[INFO] [05/27/2015 22:38:34.654] [redirect] [INFO] [05/27/2015 22:38:34.654] [Slf4jLogger] Slf4jLogger started
[INFO] [05/27/2015 22:38:34.742] [redirect] [INFO] [05/27/2015 22:38:34.741] [Remoting] Starting remoting
[INFO] [05/27/2015 22:38:34.905] [redirect] [INFO] [05/27/2015 22:38:34.905] [Remoting] Remoting started; listening on addresses :[akka.tcp://client1993150949@<IP_ADDRESS>:59331]
[INFO] [05/27/2015 22:38:34.934] [redirect] [INFO] [05/27/2015 22:38:34.934] [Metrics$] Metrics is enabled...,  false
[INFO] [05/27/2015 22:38:34.936] [redirect] [INFO] [05/27/2015 22:38:34.936] [ClientContext] Starting system client1993150949
[INFO] [05/27/2015 22:38:34.944] [redirect] [INFO] [05/27/2015 22:38:34.944] [ClientContext] Creating master proxy Actor[akka://client1993150949/user/client1993150949#1034391742] for master list: List(HostPort(<IP_ADDRESS>,59319))
[INFO] [05/27/2015 22:38:34.946] [redirect] [INFO] [05/27/2015 22:38:34.946] [MasterProxy@client1993150949] Contacts point URL: akka.tcp://master@<IP_ADDRESS>:59319/user/master
[INFO] [05/27/2015 22:38:34.949] [redirect] [INFO] [05/27/2015 22:38:34.949] [MasterProxy@client1993150949] sending identity to ActorSelection[Anchor(akka.tcp://master@<IP_ADDRESS>:59319/), Path(/user/master)]
[INFO] [05/27/2015 22:38:34.950] [redirect] [INFO] [05/27/2015 22:38:34.950] [MasterProxy@client1993150949] Master Proxy is started...
[INFO] [05/27/2015 22:38:34.971] [redirect] [INFO] [05/27/2015 22:38:34.971] [ClusterConfig$] loading config file applic

OK
+1


[Feature request] Ability to serve and run tests against pre-compiled output directory

There is currently no way to serve the site (or run tests) against the result of a previously executed ng build. This is problematic for a few reasons explained in detail below.
This is a continuation of the discussion started here: https://github.com/angular/angular-cli/pull/4975
ATTN: @johnpapa / @filipesilva
Motivation

Consistency - There are some inconsistencies between ng serve and what ng build places in the dist folder. For instance, ng serve serves everything in the root of the src directory which means that static assets can be loaded from src that will not be available after deployment.

Debugging - Sometimes it's useful to be able to serve the app exactly as it will be deployed. I've used this when debugging AOT related issues that only present at run-time in a production build. There are other options for this scenario, but running simple http server in the dist folder was the easiest option, but I think ng-cli should be able to use it's included server for this instead of me needing to use another http server.

Deployment pipeline - currently my continuous deployment is building the app 3 times. Once each for ng test, ng e2e, ng build. Ideally I could run ng build then run the tests against the code in the dist folder.

Before discussing anything else, I would like to mention that your first point was true a while ago, but has since been fixed in https://github.com/angular/angular-cli/pull/4691. So files in ./src are not served unless they are truly part of the build.

I agree that there is a need for this sort of functionality, but not as far reaching as you propose.
Unit testing is not a real scenario in my opinion. Build code does not include unit tests, and it doesn't make any sense to try and run outside unit tests over already built code.
The e2e scenario is also a minor issue since you can disable serving via ng e2e --no-serve. After that you can configure a different baseUrl for protractor and it will test whatever you point it at. Admittedly, we don't offer --baseUrl flag but you do offer a --config flag instead to use a different config file.
So as long as you can serve the built version somehow, you can e2e test it right now.
So that leaves us with the matter of consistency and debugging 'real' builds.
You mentioned running a simple http server. But you must agree that is a poor simulacrum of your real server. The only real point of commonality are that it serves files somehow. So the need for consistency is not being fulfilled, and the debugging one only partially.
I think that the very least such a server would need is:

the real host (not localhost)
--deploy-url and --base-url to match your build
proxies (if you use them via --proxy-config)
fallback configuration (as described in https://angular.io/docs/ts/latest/guide/deployment.html#!#fallback)
the same routing rules as your real server
a ssl cert if used

So I argue that simulating ones real server with fidelity is not just a matter of firing up a simple http server.
That is not to say this isn't a real need. It is. And if we had this, there would be a lot of problems that would be caught before the app is deployed somewhere.
So I would like to see such a command in the CLI in the future. Something like ng serve --dir=./dist or ng serve-build. But it needs to be a high-fidelity simulation.

I'm actually running ngServe with most of the criteria you listed today (custom host name, ssl cert, same routing, fallback) this is needed because our app has an oAuth scenario that requires https and a valid hostname in the callback URI.
I'm using IIS in production (I work at Microsoft btw) so I'm happy with just a similar enough http server for e2e tests, and honestly the web pack dev server does fine. We also have a staging deployment and flighting so the e2e's are just the first line of defense.
I suppose given the criteria you mentioned it might just make more sense to not even use ng to spin up the server because everyone will have their own production server story so building the app then running your own server for E2Es and local prod-like testing makes more sense.

I would like to add an argument.  I'm fond of VS Code because it has some great remote debugging possibilities.  With the current version of the cli this is no longer possible as the .map files only exist in memory and VS Code needs them physically.

I agree for all of the reasons stated above.
Most compelling to me is the reduction of unnecessary work on CI builds.
In addition, the issue about running against a production-like environment isn't so much about running against the real deployment environment, as it is running against the code that you actually intend to deploy to your server, to then be served to your client (we are, after all, testing client applications that a dumb server just serves up).
When something odd happens in an e2e build, there's little ability to truly introspect what the test is running against, short of obtaining a whole separate environment and deploying code (this is difficult in corporate environments where setting an environment up and/or sharing environments for different purposes, i.e. mock or instrumented code, can be a huge pain in the neck).
Another use case is that doing things like instrumenting code for coverage details before a one-off test run, or as mentioned above, editor configuration, becomes much simpler.
Free the compiled assets :-D!

I am very surprised that there's no option for the ng test command to test against an already built app. The main motivation for me is reducing CI build time too as @MonkeyIncinerator noticed.
Is there already someone working on this topic ? I can be a volunteer in case

Is there any plans to solve that problem?

To me the most important problem to solve is testing. ng test tests one thing, and what we later run in production comes from ng build. This breaks a basic rule of consistency. Our builds are not trustworthy. We don't know if we tested what is actually in production. It could be something else.
Also, the total build time increases, as we build twice, once for the test, and another for the actual build.
And the test time increases as well, as there is a lot of compilation happening during testing, which we could already had ran with aot.

Hi, is there any progress on this topic?
I'm working on a project where we have to prove that our binary (aka a docker image containing an Angular app on nginx) is tested (using ng test). We can't build a binary, test a second binary (build by ng test) and then promoting the first (untested) binary to the next stage in our CI/CD.
Any ideas? - Thanks, Markus

To me the primary motivation here is to avoid building twice on CI server, but the added benefit of testing on the same compiled output is compelling as well 😄
Can we get a status on this request?

According to this comment (https://github.com/angular/angular/issues/12409#issuecomment-561908267), the speed problem I mentioned above (https://github.com/angular/angular-cli/issues/5378#issuecomment-422997969) has been resolved. The other problems remain. I still have to validate the speed to make sure.

Following up from 2022, I think Filipe's original comment is still pretty accurate.
Unit test builds are distinct from typical application builds, using different files (includes test files, doesn't include application bootstrap), so you can't just ng build and then run the tests afterwards. It also doesn't really make sense to do a "test build" without actually running the test, since there's nothing else you could have done with that build anyways. Most of the motivations in this issue seem to be reducing duplicate CI work, and while ng build and ng test do build the app similarly, they are fundamentally incompatible with each other in this way. There's no work that can be meaningfully reused like this.
ng e2e is a little different since we recommend third party builders. End-to-end tests definitely should use some form of your production server (with test data or in a test environment), and the e2e builders should support that. If not, we recommend following up with those maintainers for the support you need.
When it comes to debugging and serving for unit tests, devservers typically differ from prod servers. To be truly identical you need to do use your prod server for testing, which means it should support live reload, sourcemaps, etc. Doing so also means you're using production data for testing, which should generally be mocked. A separate test server with mock data is usually the best way to address this. The only middle ground is if your prod server is effectively a static file server, but at that point using a separate dev server is identical anyways and doesn't really cause any challenges.
Hopefully that helps explain some of our thought process around this. As a result, we don't think there's much value in supporting a test setup that works from a pre-compiled directory.

you can't just ng build and then run the tests afterwards.

Except that you totally could by simply importing from the prod assets when you compile the tests, as if they were a library, instead of treating a 2nd run of compilation as an inherent part of the testing process.

It also doesn't really make sense to do a "test build" without actually running the test, since there's nothing else you could have done with that build anyways.

Tell that to Java and Maven! They've been doing test builds as part of the build process since forever! Yes there is no other use for that code but to run the test, but...uhh...isn't that the only point to writing the test too? The value is that by decoupling the production build, you are assured that your prod assets === assets under test

When it comes to debugging and serving for unit tests, devservers typically differ from prod servers.

Yes, and JVM test runners differ from running from the main, but at least the code under test is the same, and only compiled once!
You're not testing the servers, you're testing the code you wrote, compiled, and are going to deploy. You're confusing a runtime constraint with a compile time constraint.
Anyways, I doubt you're reopening, but I disagree, for the record 😁


Configure Errbit via env vars

This removes the file that is added at deploy time. There are related PRs going into puppet, deployment and alphagov-deployment.

Thanks for the reviews @cbaines 👍


Hopefully the llava:34b model will work

Please add support for more ollama multimodal models, such as llava:34b

I tried.  But it's not working


firebase 4.5.0 and firebase.Promise

Hi guys,
With the new firebase sdk, the typings has changed and the AngularFire RC 2 got errors (not in the RC1) :
Firebase: 4.5.0
AngularFire: 4.0.0-rc2
With Typescript
Based on this commit : https://github.com/firebase/firebase-js-sdk/pull/172
** Errors in the JavaScript console **
typescript: node_modules/angularfire2/database/firebase_list_observable.d.ts, line: 15
            Namespace 'firebase' has no exported member 'Promise'.

typescript: node_modules/angularfire2/firebase.app.module.d.ts, line: 12

typescript: node_modules/angularfire2/database/interfaces.d.ts, line: 7

...

You will need to update the typings of some files,
Regards

@tgensol Wait a few minutes and I'll have the new 5.0 version out with these fixes.

@davideast Perfect thanks !

@tgensol Just as an FYI though, the database breaking changes happen in 5.0 too. You can either upgrade to the new apI (recommended) or use the angularfire2/database-deprecated for the time being.

@tgensol The latest is out on npm!


Instructions do not produce a working container

The instructions at Install Build Tools into a container do not produce a working container.
Step 5 (docker build -t buildtools2019:latest -m 2GB .) of the directions produces the following warning:
 ---> [Warning] Shell-form ENTRYPOINT and exec-form CMD may have unexpected results
And then running the container as directed (docker run -it buildtools2019) produces:
docker: Error response from daemon: container bde8fd3c54cb5ebd9c09d296c5c85b87561a90059761f18ca2bac92e933a576a encountered an error during CreateProcess: failure in a Windows system call: The system cannot find the file specified. (0x2)
[Event Detail:  Provider: 00000000-0000-0000-0000-000000000000]
[Event Detail:  Provider: 00000000-0000-0000-0000-000000000000]
[Event Detail: onecore\vm\compute\management\orchestration\vmhostedcontainer\processmanagement.cpp(173)\vmcomputeagent.exe!00007FF604DB9D2B: (caller: 00007FF604D6E13A) Exception(2) tid(394) 80070002 The system cannot find the file specified.
    CallContext:[\Bridge_ProcessMessage\VmHostedContainer_ExecuteProcess]
 Provider: 00000000-0000-0000-0000-000000000000] extra info: {"CommandLine":"\"cmd /S /C C:\\BuildTools\\Common7\\Tools\\VsDevCmd.bat \u0026\u0026\" powershell.exe -NoLogo -ExecutionPolicy Bypass","WorkingDirectory":"C:\\","Environment":{"COMPLUS_NGenProtectedProcess_FeatureEnabled":"0","NUGET_VERSION":"4.4.1","ROSLYN_COMPILER_LOCATION":"C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\BuildTools\\MSBuild\\Current\\Bin\\Roslyn"},"EmulateConsole":true,"CreateStdInPipe":true,"CreateStdOutPipe":true,"ConsoleSize":[31,177]}.

This all done on a Windows 10, version 1903 system running Docker Desktop 2.1.04 (Docker Engine 19.03.4).

@klm1  Thank you for the feedback, assigning this to the author for review.

This is a duplicate of #3713, which is caused by a regression in Docker for Windows. Unfortunately, you'll have to change the ENTRYPOINT to fit your use case, which will be custom and not easy to document. The hope was the regression will be fixed.
@msebolt, I'm also no longer on the setup team. Could you change the owner?

It seems to me the goal of these instructions was to give one example of how the VS built tools can be loaded into and run from Docker. If it's no longer possible to document a working example of that, would it be better to (perhaps temporarily) remove the page?

@TerryGLee I could make one more edit to at least give people an interactive-only shell that couldn't be used for direct automation. Does that work for you? Honestly, I doubt Docker for Windows will fix the underlying issue given the open bug.

@heaths An edit would be much appreciated. :)

Perhaps it would be possible to capture the environment set by VsDevCmd.bat and automatically generate ENV lines to be added to the Dockerfile? One would need to build the container twice, but at least this way we'd have a container usable for automation.

I had considered that, but vsdevcmd has different options for the target architecture. How much those affect compiler/linker arguments over command-line arguments (or lack thereof) I don't know.

I've ended up with this script: https://github.com/Artem-B/tf-win/blob/master/setup_build_env.py
First I build an image with MSVC installed, with no environment set up yet. Then I tell this script to run vsdevcmd with given arguments in the container, capture environment after that and run 'docker commit -c....' to replicate the new environment in a new image.

Apparently it's impossible to use docker commit -c ENV... to set environment variable to a value that ends with a trailing backslash. Docker strips the trailing backslashes and ends up concatenating ENV lines from different -c options. This looks like a docker bug to me. This makes it impossible to replicate the environment exactly.  If VCINSTALLDIR and VSINSTALLDIR do not have trailing backslashes, it apparently causes problems for vsdevcmd.bat if it's re-run again. The ENV statements in a docker file do not have the same problem, so I ended up using the script above with --print and appended its output to the Dockerfile.

I've got the script working after all. The work around for https://github.com/docker/for-win/issues/5254 is to use a different escape character.

Thanks, but vsdevcmd supports different run modes. Capturing the environment fixes it to one, unless users run vsdevcmd again and vsdevcmd overwrites those environment variables. The original idea - that worked before the regression - was you can just launch the container and get an interactive prompt, or pass args to vsdevcmd to customize the environment and/or even build and exit, setting ERRORLEVEL from the container if applicable. This can't work with the regression and will have to either be interactive or make the user specify the entire command including the shell script. I'm working on testing configuration changes as I have time.

I'm not saying that the script is the solution. It's merely a workaround that's good enough to give me a working container. Making one container per configuration I need is a hassle, but it's quite a bit better than having no container at all.

Hi @klm1, we've updated the Build Tools documentation here. Please give the new instructions a try. We look forward to your feedback, and I'll be closing out this issue in the meantime.


General Edits for clarity

Deliver a personalized, rich, connected experience that's inspired through your brand. - not sure what this means?
Also, think about adding the architectural pillars to help you dive deeper into the scenario.  - From the context, it is not clear what 'scenario' means
There are inherent complexities and ground realities in building a data-driven culture to drive business forward in a consistent, forward-thinking, agile, and informed way. - Could this be simplified to something like "There are inherent  complexities in building a data driven culture that is forward thinking, agile and informed"? Wonder if the current version has too much jargon in a short sentence
Creating a strategy is one thing. Executing a strategy at enterprise-scale poses a great challenge to an organization's existing culture, people, processes, and technology choices. - there is no 'other thing' so maybe we shouldn't use 'one thing'?
Define a data strategy  - the document talks about defining a strategy much before this heading, so should we rethink the flow?
design principles for the layers in your data strategy. - layers in strategy have not been introduced before, so its unclear what this means

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

ID: 42a648bf-51ec-f9da-6c4f-d721616fcdb1
Version Independent ID: 7bdb8bfa-289e-bee5-bc45-a0a6fb78d5ff
Content: Integrate data management and analytics into your cloud adoption strategy - Cloud Adoption Framework
Content Source: docs/scenarios/data-management/strategy.md
Service: cloud-adoption-framework
Sub-service: scenario
GitHub Login: @BrianBlanchard
Microsoft Alias: brblanch

This section will be rewritten.
#assign: @simonlid

#close-off

It looks like this was addressed in review, #please-close


Feature request: Cross process communication

Are there any plans making communication between node.js processes possible?

That's possible already. Either use a combination of socket.io and socket.io-client, or push messages via e.g. Redis.

Isn't socket.io-client used for the browser?
I mean kinda like dnode where you communicate between two node.js processes without a browser or a database like Redis mediating in between.

Also, in Node.js 0.6 you got child_process.fork which does cross process communication.

Also you could use something like hook.io.

@3rd-Eden Yeah that looks very awesome! I should perhaps stick to node.js and socket.io.
@BRampersad I'm struggling with the communication between browser and an existing express server.

Closing this as cross process is already possible using the node.js 0.6 fork method or using the socket.io-client in node.js to connect with exiting socket.io servers


ci: merge opae-libs

Automated changes by create-pull-request GitHub action

Coverage increased (+0.04%) to 66.505% when pulling c9378fcc29f62770284699e8f16166bff436ecd5 on auto/update-libs into 7ed3a64559e8b8961109261af2a30aea3a3838f8 on master.


⚠ Bofrost.nl has degraded performance

In 5bb4f80, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 10058 ms

Resolved: Bofrost.nl performance has improved in cdd4464.


Switch CD to cmake build

Description
Switch CD to cmake build.

Superseded by https://github.com/apache/incubator-mxnet/pull/18205


[RCM] Fix missing comments on exported fields

What does this PR do?

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the config template has been updated.

@ameske Current build failures (python-related, 1 kitchen test) seem unrelated to this change and the Python issues seems to be unmasked by this PR (CircleCI checks pass for reference). Feel free to merge this as needed.


CollectionModelBinder and GenericModelBinder conspire to create two (often three) collection instances

In the normal case, MutableObjectModelBinder activates all properties and ensures bindingContext.Model != null before GenericModelBinder gets involved. However bindingContext.Model == null for top-level collection parameters and the GenericModelBinder ecosystem handles that case inefficiently. This is a call to measure performance for top-level collections and determine if activation is a significant drain. If activation is a problem for that scenario, we know where to look.

In the top-level collection case, first GenericModelBinder calls collectionBinder.CanCreateInstance() (where collectionBinder is always a CollectionModelBinder or a subclass). Unless collectionBinder is an ArrayModelBinder, this attempts to create a collection instance, compares it with null, and discards the instance.
Then CollectionModelBinder often needs to either create an empty instance (because model binding failed) or activate another instance because the intermediate List<T> cannot be used. This always happens when using ArrayModelBinder or DictionaryModelBinder but can easily occur with the base CollectionModelBinder as well.
I don't have the data available but recall @rynowak showing high costs associated with System.Activator use, though the parameterless constructor case isn't as bad as some.
Separately, the intermediate List<T> may be unavoidable for ArrayModelBinder but probably isn't necessary for most other collection binding scenarios. As long as bindingContext.Model or the activated collection implement ICollection<TElement>, should be fine with that instance.
Note the GenericModelBinder ecosystem appears correct. We should not change the visible behaviour of this part of the model binding system.

Partially addressed in d3c2463. CollectionModelBinder is now a bit more efficient. But it still creates an intermediate collection when property value could be used.


The app package is invalid: Could not zip the package

Following along the instructions in the README - and again starting from a re-provisioned and upgraded docker-machine - I get this failure message. What does it mean and what can I do to fix it?
App NOOP is a worker, skipping route creation
Uploading NOOP...
Uploading app files from: /home/docker/district-insurance-sample/tmp
Uploading 122B, 1 files
Done uploading
FAILED
Error processing app files: Error uploading application.
The app package is invalid: Could not zip the package
 STDOUT: "
zip error: Nothing to do! (try: zip -q -r -D --symlinks /var/vcap/data/cloud_controller_ng/tmp/safezipper20160715-31628-p75rde/package.zip . -i .)
"
 STDERR: ""
scripts/cf.mk:12: recipe for target '.deploy-cf' failed

The above leads eventually to:
No user-defined env variables have been set
Running Environment Variable Groups:
BLUEMIX_REGION: ibm:yp:eu-gb

Staging Environment Variable Groups:
BLUEMIX_REGION: ibm:yp:eu-gb

Note the Tradeoff Analytics password and username above and copy/paste them when prompted
Press any key to continue.
make[1]: Leaving directory '/home/docker/district-insurance-sample'
make[1]: Entering directory '/home/docker/district-insurance-sample'
cp scripts/build/Dockerfile .
cp scripts/build/.dockerignore .
ice build --local -t district-insurance-sample .
Error loading configuration.
Target is local host. Invoking docker with the given arguments...
Sending build context to Docker daemon 6.978 MB
Step 1 : FROM registry-ice.ng.bluemix.net/ibmnode:latest
Get https://registry-ice.ng.bluemix.net/v1/_ping: EOF
scripts/build/Makefile:9: recipe for target 'build-local' failed
make[1]: *** [build-local] Error 1
make[1]: Leaving directory '/home/docker/district-insurance-sample'
Makefile:15: recipe for target 'build-release-local' failed
make: *** [build-release-local] Error 2
docker@default:~/district-insurance-sample$

Hi @iainhouston  thanks for the report. Can you post the CF version that you get by typing in
cf -v? It looks like the behavior of the latest cloud foundry CLI changed and is causing this issue.

It's cf version 6.20.0+25b1961-2016-06-29

@iainhouston The option to run in a local Docker Machine should work now.


Our plan page improved

Closes #848
EDITS:

Editting done section by section
Navbar added, edited
Navbar is made responsive
Grids and row CSS added to sections
Icons imported to make the page look more clean
Everthing's matched to parent website's theme

BEFORE:

AFTER:
https://github.com/Its-Aman-Yadav/Community-Site/assets/146661411/61bddc30-8323-439c-8419-7f488d878bd8

Nice @sau-mili


Melee weapons: The third-person arm does not move

Describe the bug
Melee weapons: The third-person arm does not move
Reproducibility

[X] I reproduced this issue with as few other mods as possible installed.
[ ] I am unable to reproduce this issue consistently.

Screenshots and/or videos
No response
Logs
no logs
Debug Logs
No response
Crash Reports
No response
MWC Version
0.1.3
Forge Version
1.12.2 forge <IP_ADDRESS>60
Red Core Version
0.6 dev 3
MixinBooter Version
9.1
Java Version
1.8
Java Virtual Machine
Hotspot
Operating System
windows 11
GPU Vendor
NVIDIA
Code of Conduct

[X] I agree to follow this project's Code of Conduct

https://github.com/Cubed-Development/Modern-Warfare-Cubed/assets/130232431/4b4485ae-203f-40eb-bc5a-54c18f690d5b


[ToolbarAndroid] Important Warning!!

ExceptionsManager.js:76 Warning: setState(...): Can only update a mounted or mounting component. This usually means you called setState() on an unmounted component. This is a no-op.
How to solve?

@oblador

I got the same issue. It took alot of time to render a component.

I am having the same problem. The problem will be solved if we check for an _isMounted variable and call setState only when _isMounted == true. This variable should be initiated as false. Set it to true on componentDidMount and then set it to false on componentWillUnmount.

This will happen if you add and remove the component very quickly, which to me sounds like an application bug. It shouldn't affect performance noticeably.


Outdoor temperature & fan speed wrong and characteristic warnings for plugin

Describe Your Problem:
The outdoor temperature sensor on Model 'SYSTXCCITC01-B' is stuck at 32 degrees.  I can see the correct outdoor temperature on the unit (carrier) and on their website when I sign in.  The fan control is also showing off, when it's running. I am also getting characteristic issues for a number of settings.
Logs:
[11/9/2021, 10:53:32 AM] [CarrierInfinity] Adding new accessory:  ZONE 1 Environmental Sensor
[11/9/2021, 10:53:32 AM] [CarrierInfinity] Discovered outdoor temp sensor device serial:xxxxxxxx
[11/9/2021, 10:53:32 AM] [CarrierInfinity] Adding new accessory:  Outdoor Temperature
[11/9/2021, 10:53:44 AM] [homebridge-carrier-infinity] This plugin generated a warning from the characteristic 'Current Heating Cooling State': characteristic value expected valid finite number and received "[object Promise]" (object). See https://git.io/JtMGR for more info.
[11/9/2021, 10:53:44 AM] [homebridge-carrier-infinity] This plugin generated a warning from the characteristic 'Target Heating Cooling State': characteristic value expected valid finite number and received "[object Promise]" (object). See https://git.io/JtMGR for more info.
[11/9/2021, 10:53:44 AM] [homebridge-carrier-infinity] This plugin generated a warning from the characteristic 'Current Temperature': characteristic value expected valid finite number and received "[object Promise]" (object). See https://git.io/JtMGR for more info.
[11/9/2021, 10:53:44 AM] [homebridge-carrier-infinity] This plugin generated a warning from the characteristic 'Target Temperature': characteristic value expected valid finite number and received "[object Promise]" (object). See https://git.io/JtMGR for more info.
[11/9/2021, 10:53:44 AM] [homebridge-carrier-infinity] This plugin generated a warning from the characteristic 'Temperature Display Units': characteristic value expected valid finite number and received "[object Promise]" (object). See https://git.io/JtMGR for more info.
[11/9/2021, 10:53:44 AM] [homebridge-carrier-infinity] This plugin generated a warning from the characteristic 'Cooling Threshold Temperature': characteristic value expected valid finite number and received "[object Promise]" (object). See https://git.io/JtMGR for more info.
[11/9/2021, 10:53:44 AM] [homebridge-carrier-infinity] This plugin generated a warning from the characteristic 'Heating Threshold Temperature': characteristic value expected valid finite number and received "[object Promise]" (object). See https://git.io/JtMGR for more info.
[11/9/2021, 10:53:44 AM] [homebridge-carrier-infinity] This plugin generated a warning from the characteristic 'Filter Life Level': characteristic value expected valid finite number and received "[object Promise]" (object). See https://git.io/JtMGR for more info.
[11/9/2021, 10:53:44 AM] [homebridge-carrier-infinity] This plugin generated a warning from the characteristic 'Filter Change Indication': characteristic value expected valid finite number and received "[object Promise]" (object). See https://git.io/JtMGR for more info.
[11/9/2021, 10:53:44 AM] [homebridge-carrier-infinity] This plugin generated a warning from the characteristic 'Current Relative Humidity': characteristic value expected valid finite number and received "[object Promise]" (object). See https://git.io/JtMGR for more info.
[11/9/2021, 10:53:44 AM] [homebridge-carrier-infinity] This plugin generated a warning from the characteristic 'Active': characteristic value expected valid finite number and received "[object Promise]" (object). See https://git.io/JtMGR for more info.
[11/9/2021, 10:53:44 AM] [homebridge-carrier-infinity] This plugin generated a warning from the characteristic 'Rotation Speed': characteristic value expected valid finite number and received "[object Promise]" (object). See https://git.io/JtMGR for more info.
[11/9/2021, 10:53:44 AM] [homebridge-carrier-infinity] This plugin generated a warning from the characteristic 'Target Fan State': characteristic value expected valid finite number and received "[object Promise]" (object). See https://git.io/JtMGR for more info.
[11/9/2021, 10:53:44 AM] [homebridge-carrier-infinity] This plugin generated a warning from the characteristic 'Current Relative Humidity': characteristic value expected valid finite number and received "[object Promise]" (object). See https://git.io/JtMGR for more info.
[11/9/2021, 10:53:44 AM] [homebridge-carrier-infinity] This plugin generated a warning from the characteristic 'Current Temperature': characteristic value expected valid finite number and received "[object Promise]" (object). See https://git.io/JtMGR for more info.

Plugin Config:
 {
            "username": "username",
            "password": "password",
            "holdBehavior": "activity",
            "showOutdoorTemperatureSensor": true,
            "showFanControl": true,
            "showIndoorHumiditySensors": true,
            "platform": "CarrierInfinity"
        },

Screenshots:

Environment:

Plugin Version: homebridge-carrier-infinity v1.5.4
Homebridge Version:  v1.3.5
Node.js Version: v16.13.0
NPM Version: v8.1.0
Operating System: Docker | Ubuntu Bionic Beaver (18.04.6 LTS)

Hey. Thanks for reporting! This is really weird. It looks like it’s not working at all. It’s just not actually running the code correctly.
Not sure what’s going on here. Ill have to look into it deeper. I see you’re running a newer version of node than I am. I’ll try to see if i can reproduce by running on the version you are.
In the meantime, I’d recommend trying the old standby: uninstalling and reinstalling, and turning it on and off.

Thanks! The old standby didn't work, but thanks for taking a look at this!

Hey,
I'm unfortunately not able to reproduce. By chance are you using any other homebridge plugins, and do they exhibit the same behavior? If not, could you try another plugin and see if it happens to that one too.
High level, for some reason the promise (async code) isn't being executed before it gets passed to the homekit bridge. But that execution is part of what homebridge itself is supposed to do, so I'm wondering if it is maybe an issue with homebridge itself.
If you can confirm other plugins are working, can you update to the latest node version (16.14.0) and see if that works?

No luck - same issue. 32
[image: image.png]
[image: image.png]
Thanks for looking into it.  Any logs I can send?
On Tue, Feb 15, 2022 at 12:06 AM Glenn Rivkees @.***>
wrote:

Hey,
I'm unfortunately not able to reproduce. By chance are you using any other
homebridge plugins, and do they exhibit the same behavior? If not, could
you try another plugin and see if it happens to that one too.
High level, for some reason the promise (async code) isn't being executed
before it gets passed to the homekit bridge. But that execution is part of
what homebridge itself is supposed to do, so I'm wondering if it is maybe
an issue with homebridge itself.
If you can confirm other plugins are working, can you update to the latest
node version (16.14.0) and see if that works?
—
Reply to this email directly, view it on GitHub
https://github.com/grivkees/homebridge-carrier-infinity/issues/132#issuecomment-1039863083,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADUH3RQKPWHEQWQMPSHAAHLU3HNNLANCNFSM5HVWTHUA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Just pushed some changes to the "next" channel. It has some unrelated changes, but its possible it may help indirectly.
Give it a try when you get a chance and let me know if this seems resolved.
npm install -g homebridge-carrier-infinity@next

Hey @tmills1073, when you get a chance, let me know if the latest version helps out at all.
Changes were pushed to latest, so you can try out the stable version now. Either you can click the update button in homebridge ui, or npm update the plugin.

Closing since I think this is fixed and can't reproduce the issue. If you are still experiencing the issue, please reopen and I'll keep investigating. Thanks!


Walkabout navigation editor

For #1052. Includes the first half of that issue and fixes #956. I can break this up if people would prefer. Particularly the changes to AIPlayer may need more careful review in terms of code style (use of defines everywhere).

Sweet

some files are missing in this pull
Missing file: tools/navEditor/NavEditorGui.cs!
Missing file: tools/navEditor/NavEditorAboutDlg.gui!
Executing tools/navEditor/NavEditorConsoleDlg.gui.
After executing NavEditorConsoleDlg.gui I get (simobject.cpp(1533) : Warning - SimObject::linkNamespaces -- Namespace linkage already in place)

Whoops, those were removed intentionally but I guess I forgot to remove the execs. Thanks, I'll check on that namespace error.

using that https://github.com/Azaezel/Torque3D/tree/linkNamespacesDebugOutput bit:
SimObject::linkNamespaces -- Namespace linkage already in place NavEditorConsoleListener


Byron only testnet and chairman test

We already had the code for this, but it wasn't set up to actually run the chairman test or exposed to the CLI to run a testnet.  This change exposes that functionality.

bors merge

bors merge

bors try

bors merge


Fix CORS responses issue

If an integration has no responses dictionary, the CORS code to inject responseParameters would throw. Generating a responses dictionary if it's missing to fix the error.

Partially fixes #20


Error in opencv, img_hash not found

Just cloned to my Mac (Catalina) and got an error in OpenCV I believe ...
(.env<EMAIL_ADDRESS>~/work/Projects/CatalogScanner ‹master*›
╰─(.env) ➤  python scanner.py /Users/dad/Dropbox/Photos/Switch/2020/09/07/2020090708554401-02CB906EA538A35643C1E1484C4B947D.mp4
I0907 10:11:30.954331<PHONE_NUMBER> scanner.py:38] Detected scan mode: catalog
Traceback (most recent call last):
  File "scanner.py", line 102, in <module>
    app.run(main)
  File "/Users/dad/work/Projects/CatalogScanner/.env/lib/python3.8/site-packages/absl/app.py", line 299, in run
    _run_main(main, args)
  File "/Users/dad/work/Projects/CatalogScanner/.env/lib/python3.8/site-packages/absl/app.py", line 250, in _run_main
    sys.exit(main(argv))
  File "scanner.py", line 89, in main
    result = scan_media(
  File "scanner.py", line 49, in scan_media
    return SCANNERS[mode].scan(filename, locale=locale, **kwargs)
  File "/Users/dad/work/Projects/CatalogScanner/catalog.py", line 57, in scan
    item_rows = parse_video(video_file, for_sale)
  File "/Users/dad/work/Projects/CatalogScanner/catalog.py", line 95, in parse_video
    all_rows = _dedupe_rows(all_rows)
  File "/Users/dad/work/Projects/CatalogScanner/catalog.py", line 218, in _dedupe_rows
    row_hash = str(cv2.img_hash.blockMeanHash(row, mode=1)[0])
AttributeError: module 'cv2.cv2' has no attribute 'img_hash'

pip ran without problems:
(.env<EMAIL_ADDRESS>~/work/Projects/CatalogScanner ‹master*›
╰─(.env) ➤  pip install -r requirements.txt
Collecting absl-py==0.9.0 (from -r requirements.txt (line 1))
  Downloading https://files.pythonhosted.org/packages/1a/53/9243c600e047bd4c3df9e69cfabc1e8004a82cac2e0c484580a78a94ba2a/absl-py-0.9.0.tar.gz (104kB)
     |████████████████████████████████| 112kB 2.1MB/s
Collecting imagehash==4.1.0 (from -r requirements.txt (line 2))
  Downloading https://files.pythonhosted.org/packages/1a/5d/cc81830be3c4705a46cdbca74439b67f1017881383ba0127c41c4cecb7b3/ImageHash-4.1.0.tar.gz (291kB)
     |████████████████████████████████| 296kB 9.3MB/s
Collecting opencv-contrib-python==<IP_ADDRESS> (from -r requirements.txt (line 3))
  Downloading https://files.pythonhosted.org/packages/d1/29/0e9583011e535c23b92a0ec64ff449b9e05d86423a6e5a16385f569b04d6/opencv_contrib_python-<IP_ADDRESS>-cp38-cp38-macosx_10_9_x86_64.whl (60.3MB)
     |████████████████████████████████| 60.3MB 9.3MB/s
Collecting opencv-python==<IP_ADDRESS> (from -r requirements.txt (line 4))
  Downloading https://files.pythonhosted.org/packages/f6/cd/0642144e580aa2fda0dc70276a432a48542351a620d26f0d1e3c5169ff49/opencv_python-<IP_ADDRESS>-cp38-cp38-macosx_10_9_x86_64.whl (49.1MB)
     |████████████████████████████████| 49.1MB 15.0MB/s
Collecting Pillow==7.1.2 (from -r requirements.txt (line 5))
  Using cached https://files.pythonhosted.org/packages/20/20/a0f9f20469aae7017a578fdc4c55ea18f7c8911d2d10668687f95748442b/Pillow-7.1.2-cp38-cp38-macosx_10_10_x86_64.whl
Collecting pytesseract==0.3.4 (from -r requirements.txt (line 6))
  Downloading https://files.pythonhosted.org/packages/1d/d8/521db389ff0aae32035bfda6ed39cb2c2e28521c47015f6431f07460c50a/pytesseract-0.3.4.tar.gz
Collecting six (from absl-py==0.9.0->-r requirements.txt (line 1))
  Downloading https://files.pythonhosted.org/packages/ee/ff/48bde5c0f013094d729fe4b0316ba2a24774b3ff1c52d924a8a4cb04078a/six-1.15.0-py2.py3-none-any.whl
Collecting numpy (from imagehash==4.1.0->-r requirements.txt (line 2))
  Downloading https://files.pythonhosted.org/packages/2f/c0/09c526b4167ed4dd3bcb6d6aa2103b4b50899e8eae89acde6455d43a37e4/numpy-1.19.1-cp38-cp38-macosx_10_9_x86_64.whl (15.3MB)
     |████████████████████████████████| 15.3MB 10.7MB/s
Collecting scipy (from imagehash==4.1.0->-r requirements.txt (line 2))
  Downloading https://files.pythonhosted.org/packages/8a/84/568ec7727bc789a9b623ec2652043ad3311d7939f152e81cb5d699bfb9b1/scipy-1.5.2-cp38-cp38-macosx_10_9_x86_64.whl (28.9MB)
     |████████████████████████████████| 29.0MB 11.5MB/s
Collecting PyWavelets (from imagehash==4.1.0->-r requirements.txt (line 2))
  Downloading https://files.pythonhosted.org/packages/77/fa/cd182609e276d8ea7315a084cf2acbd0f39751e56562555bd8e4a0131498/PyWavelets-1.1.1-cp38-cp38-macosx_10_9_x86_64.whl (4.3MB)
     |████████████████████████████████| 4.4MB 16.0MB/s
Installing collected packages: six, absl-py, numpy, scipy, Pillow, PyWavelets, imagehash, opencv-contrib-python, opencv-python, pytesseract
  Running setup.py install for absl-py ... done
  Running setup.py install for imagehash ... done
  Running setup.py install for pytesseract ... done
Successfully installed Pillow-7.1.2 PyWavelets-1.1.1 absl-py-0.9.0 imagehash-4.1.0 numpy-1.19.1 opencv-contrib-python-<IP_ADDRESS> opencv-python-<IP_ADDRESS> pytesseract-0.3.4 scipy-1.5.2 six-1.15.0
WARNING: You are using pip version 19.2.3, however version 20.2.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

Python is:
Python 3.8.2 (v3.8.2:7b3ab5921f, Feb 24 2020, 17:52:18)
[Clang 6.0 (clang-600.0.57)]

Any thoughts on this?  I also installed under ubuntu and get the same error with python 3.8.

I found the issue!
I uninstalled both opencv-python and opencv-contrib-python and then installed only opencv-contrib-python.
According to the opencv-contrib-python installation docs "There are four different packages and you should select only one of them. Do not install multiple different packages in the same environment. "
In your requirements you have both opencv-python and opencv-contrib-python. Because of the installation order the opencv-python gets precedence and the other is masked.
I suggest you remove opencv-python from requirements.txt.

Err, I somehow had my own repo set to "Unwatched" and completely missed this. Sorry about that and I'm glad you found the solution. And that you @rohm1 for the fix :)


ccim8x-sbc-pro.coffee: Add instructions for SD boot

The SBC has a boot microswitch that needs to be configured appropriately
to boot from either SD card or internal eMMC storage.
Change-type: patch
Signed-off-by: Alex Gonzalez<EMAIL_ADDRESS>

@balena-ci rebase

@balena-ci rebase

@balena-ci rebase

@balena-ci I self-certify!


[Error] Min relay fee not met

On a pretty sizable transaction, I received the error 'min relay fee not met'.
From the logs:

min relay fee not met, *** < ***
[...]
at com.sparrowwallet.sparrow@1.6.2/com.sparrowwallet.sparrow.net.BatchedElectrumServerRpc.broadcastTransaction(Unknown Source)
... 12 common frames omitted
Caused by: com.github.arteam.simplejsonrpc.client.exception.JsonRpcException: ErrorMessage{code=1, message=the transaction was rejected by network rules.

It was a segwit multisig transaction with a fee of 1.00 sats/vB.
Any idea what went wrong here? Would this be solved if the fee is higher than 1.0 sats/vB?

Would this be solved if the fee is higher than 1.0 sats/vB?

Yes, make it slightly higher and the transaction will work.
You haven't mentioned what is doing the signing here, but it's possible that it is not creating canonical signatures, which is increasing the size of the transaction slightly larger to that which Sparrow is estimating. See https://github.com/sparrowwallet/sparrow/issues/144#issuecomment-869560080 for details.


Maintenance status

We haven't been able to devote the effort to properly maintain this crate.
There are a few maintained alternatives to consider:

cargo-generate-rpm
rust2rpm

It would probably make sense to either deprecate this crate or hand it off to the maintainers of one of the above projects.
cc @cat-in-136 @ignatenkobrain

I've officially marked cargo-rpm as unmaintained: https://github.com/iqlusioninc/cargo-rpm/commit/be5204fdf4d82518cb3a95e24b986adc3f930dfd
The project is now archived.


iOS build faild

xcode: 11.4
macos: 10.15.4

LiquidCore version: 0.7.3

This is an incredibly strange set of symbols to be undefined (and just those?).  Very odd.
I cannot reproduce this.  What does your podfile look like?

@ericwlange Thank you for your response. This is happened on my office iMac, build is ok on myself macbookpro.
The content of Podfile sent as an screenshot.

Hi, there.
Thanks for developing a great library.
I had the same problem.
My environment is as follows.

  # Pods for LiquidCoreTest

  target 'LiquidCoreTestTests' do
    inherit! :search_paths
    # Pods for testing
  end

  target 'LiquidCoreTestUITests' do
    # Pods for testing
  end

end

I've also run into this issue, and I think I finally have a satisfactory reason why it failed in the first place and what to do about it.
I spotted this in the pod install --verbose log when attempting to use this module via a Flutter plugin, after a day or so of banging my head against the problem:
 > Running prepare command
   $ /bin/bash -c  set -e bash LiquidCore/src/ios/generate_node_javascript.sh
   bash LiquidCore/src/ios/generate_javascript_polyfills.sh bash
   LiquidCore/src/ios/copy_headers.sh
   Traceback (most recent call last):
     File "tools/js2c.py", line 365, in <module>
       main()
     File "tools/js2c.py", line 362, in main
       JS2C(source_files, [natives])
     File "tools/js2c.py", line 294, in JS2C
       (consts, macros) = ReadMacros(macro_lines)
     File "tools/js2c.py", line 167, in ReadMacros
       args = map(string.strip, macro_match.group(2).split(','))
   AttributeError: module 'string' has no attribute 'strip'
   generated: /Users/dd/Library/Caches/CocoaPods/Pods/Release/LiquidCore/0.7.10-fadf5/LiquidCore/src/ios/gen/node_javascript.cc
   Generated javascript polyfill: /Users/dd/Library/Caches/CocoaPods/Pods/Release/LiquidCore/0.7.10-fadf5/LiquidCore/src/ios/gen/polyfill.c
   Copied headers to: /Users/dd/Library/Caches/CocoaPods/Pods/Release/LiquidCore/0.7.10-fadf5/LiquidCore/src/ios/gen/include
  > Copying LiquidCore from
  `/Users/dd/Library/Caches/CocoaPods/Pods/Release/LiquidCore/0.7.10-fadf5` to
  `Pods/LiquidCore`

This looks to be a python 2.7 vs python 3 error being emitted from the prepare_command step in the Pod install script. Resolving it is simple - make sure you change to use a global python 2.7 version instead. If you're seeing this on macOS, this is probably (but not strictly) down to using pyenv to use a python 3 script environment; just switch to using the system version instead.
Doing so causes all the scripts in the prepare_command to be executed completely. As a suggestion for this issue, it would be good to get the pod installation to fail with a proper error message explaining the python environment isn't right - for anyone affected by it however, it is at least simple to work around.
You will probably need to clean the Cocoapods cache directory and rebuild the pod:
pod cache clean 'liquidcore'
pod cache clean 'liquidcore' --all
pod install

That's right！
Thank you, brother
#setting path for python 2.7 to .bash_profile
PATH="/Library/Frameworks/Python.framework/Versions/2.7/bin:${PATH}"
export PATH
alias python="/Library/Frameworks/Python.framework/Versions/2.7/bin/python"


Update german translation

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

Proposed changes
With this PR I update the German translation.
I've often replaced "Berechtigung" with "Anmeldeinformation", since "Berechtigung" stands for "permission" rather than "credential".
Otherwise, it's more minor adjustments or adding texts that have not yet been translated.
Maybe @ralphwetzel can take a look at the PR? :)
Checklist

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

Coverage increased (+0.03%) to 68.231% when pulling b50ba3e0e44c34034cb73603a4a9f81c152062d6 on Dennis14e:patch-de-2 into dc7fef63952548277d7759c327ce2909fdce0a3c on node-red:master.

As there seems to be no clever translation to German (that comes to my mind), I propose to stick to "Credentials" and treat this as a "terminus technicus". As a side effect, interested users will find additional info when net-searching for "credentials" - which is not the case for the other terms.

I agree, neither "Berechtigungen" nor "Anmeldeinformationen" is a really good translation of "credentials". Personally, I like the suggestion to simply use the term "Credentials".

@knolleary is this PR good to go? Has been over checked by @ralphwetzel


Fix URLs of Swift files that were pointing to the forked repo

What does this PR do?
This PR updates some of the URLs in the design docs that were pointing to the forked repo. Now they point to the tensorflow branch on the main repo.

Thank you!


diff -y does not work

The useful -y option for column-based diff seems to be unavailable in prezto’s diff function:
 ~  diff -y a.txt b.txt
diff: conflicting output style options
diff: Try 'diff --help' for more information.

You have probably Git installed on your host, in this case the diff command will use git diff.
See https://github.com/sorin-ionescu/prezto/blob/master/modules/utility/functions/diff and it is also described in this issue https://github.com/sorin-ionescu/prezto/issues/1215

Yes, colordiff is installed. The problem seems to be that prezto calls it with --difftype diffu even though -y is given, which specifies a different output style.

Yes, you are right. It should use the arguments you're passing to it. Needs to be fixed I would say.

The problem is diff doesn't accept -y and --unified at the same time.
The easiest way to solve this is to remove the --unified on this line, but I'm not sure why the option's there in the first place.

I think it's there to match up with git diff but it's not worth keeping it there if it's going to break options when actually using the command.

I've removed --unified from the diff function (as well as the workaround which uses git because it doesn't support --unified or -y in the same way) because this breaks things. There has also been a new alias added (diffu) which will give a unified diff, similar to before.

Great, thanks!


Component Parameters with dashes generate invalid Schemas

Description
An invalid schemas.ts file is generated.
The provided OpenAPI example will generate the following broken typescript.
(Dashes in declaration names are not valid)
export const $x-App-Request-Correlation-Id = {
    name: 'x-App-Request-Correlation-Id',
    in: 'header',
    required: true,
    schema: {
        type: 'string',
        example: '83a37bff-b5a3-43b6-8628-7afb2565dbe7',
        format: 'uuid'
    },
    description: 'Correlation Id'
} as const;

OpenAPI specification (optional)
{
  "openapi": "3.0.1",
  "info": {
    "title": "APi",
    "description": "description",
    "contact": {
      "url": "https://develop.example.com/contact-us"
    },
    "license": {
      "name": "Example",
      "url": "https://develop.example.com"
    },
    "version": "1.0"
  },
  "externalDocs": {
    "description": "Developer Portal",
    "url": "https://develop.example.com"
  },
  "servers": [
    {
      "url": "https://localhost:1002/mock/v1/",
      "description": "API Sandbox"
    }
  ],
  "tags": [
    {
      "name": "baas",
      "description": "Conversational Form APIs"
    }
  ],
  "paths": {
    "/form/{form-type}/{form-instance-id}": {
      "get": {
        "tags": ["baas"],
        "summary": "Restart conversation - reads existing application data",
        "operationId": "readApplicationId",
        "parameters": [
          {
            "name": "form-type",
            "in": "path",
            "required": true,
            "schema": {
              "type": "string"
            }
          },
          {
            "name": "form-instance-id",
            "in": "path",
            "required": true,
            "schema": {
              "type": "string"
            }
          },
          {
            "$ref": "#/components/parameters/Authorization"
          },
          {
            "$ref": "#/components/parameters/x-App-Request-Correlation-Id"
          }
        ],
        "responses": {
          "200": {
            "description": "Successful Evaluation",
            "content": {
              "application/json": {}
            }
          },
          "500": {
            "description": "Internal error occurred",
            "content": {
              "*/*": {
                "schema": {
                  "$ref": "#/components/schemas/StatusString"
                }
              }
            }
          }
        },
        "description": "Restart conversation - reads existing application data"
      }
    }
  },
  "components": {
    "schemas": {
      "StatusString": {
        "type": "object",
        "properties": {
          "status": {
            "type": "string"
          },
          "count": {
            "type": "integer",
            "format": "int32"
          },
          "cause": {
            "type": "object",
            "additionalProperties": {
              "type": "object"
            }
          }
        }
      }
    },
    "parameters": {
      "x-App-Request-Correlation-Id": {
        "name": "x-App-Request-Correlation-Id",
        "in": "header",
        "required": true,
        "schema": {
          "type": "string",
          "example": "83a37bff-b5a3-43b6-8628-7afb2565dbe7",
          "format": "uuid"
        },
        "description": "Correlation Id"
      },
      "Authorization": {
        "name": "Authorization",
        "in": "header",
        "required": true,
        "schema": {
          "type": "string",
          "example": "Authorization"
        },
        "description": "Authorization Header"
      }
    }
  }
}

Configuration
No response
System information (optional)
Mac 14.x
npm: 10
node: 21

@seriouslag Thanks! Which openapi-ts version are you on?

@seriouslag Thanks! Which openapi-ts version are you on?

0.38.1

I want to tell you how hard I worked on chasing down this bug and finally fixing it, but... turns out it's already fixed in 0.39.0. We will release it and then you can simply upgrade for more happiness. 🚀

I want to tell you how hard I worked on chasing down this bug and finally fixing it, but... turns out it's already fixed in 0.39.0. We will release it and then you can simply upgrade for more happiness. 🚀

Thank you 🙏 I am looking forward to the release.


Duplicate module instead of exporting

:construction:  Troubleshooting PR only  :construction:

Hey @danberindei @diegolovison Can I close this PR? Did you figure out if this was causing the cluster to fall apart?

Closing for now...


feat: stacktrace plugin

This can be done for apollo plugin the same model as https://github.com/Escape-Technologies/graphql-armor/blob/main/packages/graphql-armor/src/plugins/block-field-suggestion.ts#L7

https://www.apollographql.com/docs/apollo-server/data/errors/#omitting-or-including-stacktrace

https://www.apollographql.com/docs/apollo-server/data/errors/#example-redacting-the-error-message


Export .vhd and Creation of Managed Disk from .vhd failing

I observed a certain behavior and would appreciate clarification on whether there are any aspects in the documents below that require review.
1 - Copy a managed disk to a storage account - CLI - Azure Virtual Machines | Microsoft Learn
2 - Create a managed disk from a VHD file in the same account - CLI sample - Azure Virtual Machines | Microsoft Learn
I wish to keep long-term backups of .vhd files from decommissioned VMs in Azure. This ensures that the .vhd files are available in case any revisions are needed.
I can export the .vhd to the specified storage account as outlined in article 1. However, when following the instructions in documentation 2, although successfully creating a managed disk, I encountered difficulties creating a VM after that. This issue stems from the command [az disk create --resource-group $resourceGroupName --name $diskName --sku $storageType --location $location --size-gb $diskSize --source $vhdUri], which mistakenly designates the managed disk as a data disk, I run some tests to understand this behavior.
When creating a managed disk via the Azure Portal, additional parameters are essential for the proper configuration of the managed disk, ensuring the subsequent successful creation of a VM.
Example using the command from article 2:

However, my colleague using the same command obtained a different result that made us question whether it is necessary to add other flags such as [[--os-type {Linux, Windows}] | [--hyper-v-generation {V1, V2}]] or whether the commands in the articles should comply with what is necessary.
One of the things that we noticed was that when my colleague did the export, the .vhd received some metadata information, which in my situation did not happen.
Colleague example:

My example:

That's why when he ran the commands in the second article, he was able to successfully create the Managed Disk and be able to create the VM after that.
In my case, because I don't have this metadata, I can't have an OS Managed Disk to create a VM.
NOTE: we both use the same command and structures exposed in the commands in the article
We've identified a solution by incorporating additional flags [[--os-type {Linux, Windows}] | [--hyper-v-generation {V1, V2}]]  to create the managed disk successfully. However, a crucial question arises:
Can we continue using the existing articles commands, or is there a need for modification and review to ensure the accuracy of the commands?
And
Why does the preservation of metadata during the export process for the .vhd happen sometimes and not at other times? (I tried several exports and none of them managed to obtain the necessary metadata, several distro OS with the same result).

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

ID: e2513473-bb3f-04f5-d947-a9777e0c2e90
Version Independent ID: 99eb79de-2b7a-6b05-1f92-eee9c4cfb9c4
Content: Copy a managed disk to a storage account - CLI - Azure Virtual Machines
Content Source: articles/virtual-machines/scripts/copy-managed-disks-vhd-to-storage-account.md
Service: azure-disk-storage
GitHub Login: @ramankumarlive
Microsoft Alias: ramankum

#please-close
Closing as this has been taken offline.

@roygara Thanks for the quick responses and working on it.


Using pdf_viewer with Angular CLI (pseudo-webpack)

Hello,
I am developping an Angular 2+ application with angular-cli (so not a full Webpack) and pdfjs-dist.
I would like to use the pdf_viewer.js component as demonstrated in this example: https://github.com/mozilla/pdf.js/blob/master/examples/components/simpleviewer.js
Successful use of the core
I successfully used pdfjs-dist alone to render pages "manually" (without the PDFViewer component), like this:
import { Component, OnInit } from '@angular/core';

var PDFJS = require('pdfjs-dist');

@Component({/* ... */})
export class PdfViewerComponent implements OnInit{

	ngOnInit() {
		PDFJS.workerSrc = "../node_modules/pdfjs-dist/build/pdf.worker.min.js";
		var pagesWrapper = document.getElementById('ghsPV-pages-wrapper');
	}

	private renderPdf(pdfString: string) {

		PDFJS.getDocument({ data: pdfString }).then(pdf => {

			var pagesWrapper = document.getElementById('ghsPV-pages-wrapper');

			for (let p = 1; p <= pdf.numPages ; p++) {
				pdf.getPage(p).then(page => {

					var svgHolder = document.createElement('div');
					svgHolder.classList.add('ghsPV-svgHolder');
					svgHolder.style.backgroundColor = 'white';
					svgHolder.style.margin = '1em';

					var viewport = page.getViewport(1);
					svgHolder.style.width = viewport.width + 'px';
					svgHolder.style.height = viewport.height + 'px';

					page.getOperatorList().then(opList => {
						var svgGfx = new PDFJS.SVGGraphics(page.commonObjs, page.objs);
						svgGfx.getSVG(opList, viewport).then(svg => {
							pagesWrapper.appendChild(svgHolder);
							svgHolder.appendChild(svg);
						});
					});
				});
			}
		});
	}
}

First fail of importing both scripts
However, I didn't manage to use the pdf_viewer correctly, this is my last try:
import { Component, OnInit } from '@angular/core';

require('pdfjs-dist');
var PDFJS = require('pdfjs-dist/web/pdf_viewer.js').PDFJS;

@Component({/* ... */})
export class PdfViewerComponent implements OnInit {

	private pagesWrapper: HTMLElement;
	private pdfViewer: any;
	private pdfLinkService: any;

	ngOnInit() {

		PDFJS.workerSrc = "../node_modules/pdfjs-dist/build/pdf.worker.min.js";

		this.pagesWrapper = document.getElementById('ghsPV-pages-wrapper');

		// Hyperlinks:
		this.pdfLinkService = new PDFJS.PDFLinkService();
		this.pdfViewer = new PDFJS.PDFViewer({
			container: this.pagesWrapper,
			linkService: this.pdfLinkService,
		});
		this.pdfLinkService.setViewer(this.pdfViewer);

		// Scale :
		this.pagesWrapper.addEventListener('pagesinit', function () {
			this.pdfViewer.currentScaleValue = 'page-width';
		});
	}

	private renderPdf(pdfString: string) {
		PDFJS.getDocument({ data: pdfString }).then(pdf => {
			this.pdfViewer.setDocument(pdfString);
			this.pdfLinkService.setDocument(pdfString, null);
		});
	}
}

Here, I have this error message, probably because my PDFJS variable lacks the core features:
ERROR Error: Uncaught (in promise): TypeError: pdfDocument.getPage is not a function
TypeError: pdfDocument.getPage is not a function
    at PDFViewer.setDocument (pdf_viewer.js:2470)
    at eval (ghs-pdf-viewer.component.ts:123)
    at ZoneDelegate.invoke (zone.js:392)
    at Object.onInvoke (core.js:4629)
    at ZoneDelegate.invoke (zone.js:391)
    at Zone.run (zone.js:142)
    at eval (zone.js:873)
    at ZoneDelegate.invokeTask (zone.js:425)
    at Object.onInvokeTask (core.js:4620)
    at ZoneDelegate.invokeTask (zone.js:424)
    at PDFViewer.setDocument (pdf_viewer.js:2470)
    at eval (ghs-pdf-viewer.component.ts:123)
    at ZoneDelegate.invoke (zone.js:392)
    at Object.onInvoke (core.js:4629)
    at ZoneDelegate.invoke (zone.js:391)
    at Zone.run (zone.js:142)
    at eval (zone.js:873)
    at ZoneDelegate.invokeTask (zone.js:425)
    at Object.onInvokeTask (core.js:4620)
    at ZoneDelegate.invokeTask (zone.js:424)
    at resolvePromise (zone.js:824)
    at eval (zone.js:876)
    at ZoneDelegate.invokeTask (zone.js:425)
    at Object.onInvokeTask (core.js:4620)
    at ZoneDelegate.invokeTask (zone.js:424)
    at Zone.runTask (zone.js:192)
    at drainMicroTaskQueue (zone.js:602)
    at <anonymous>

Second fail with .angular-cli.json
I also tried to include both JavaScript files via .angular-cli.json:
{
	"apps": [
		{
			"assets": [
				"assets",
				"manifest.json"
			],
			"styles": [
				"styles.scss",
				"../node_modules/pdfjs-dist/web/pdf_viewer.css"
			],
			"scripts": [
				"../node_modules/pdfjs-dist/build/pdf.js",
				"../node_modules/pdfjs-dist/web/pdf_viewer.js"
			]
		}
	]
}

And just declare PDFJS in my component:
declare var PDFJS: any;

In this case, I have no error message, but the PDFJS.getDocument() promise is never executed, so nothing happens.
[TL;DR] Question
So my question is: what is the correct method of importing both pdf.js and pdf_viewer.js scripts in Angular?
I did check the webpack example but this example only uses the core pdf.js, not pdf_viewer.js.
As a side note, and I think it's related to how I should use PDFJS with Angular: my PDFJS.workerSrc does not work either (404 Not Found), so if anyone has an idea...

@LeoDupont If interested, I've built a wrapper for angular 2+ apps https://github.com/VadimDez/ng2-pdf-viewer

Even though the situation described here isn't identical to the one in issue #9239, that one might still be relevant/helpful here.
However, as explain in CONTRIBUTING.md, this issue isn't currently valid without a complete (and runnable) example; please refer to the quote below.

If you are developing a custom solution, first check the examples at https://github.com/mozilla/pdf.js#learning and search existing issues. If this does not help, please prepare a short well-documented example that demonstrates the problem and make it accessible online on your website, JS Bin, GitHub, etc. before opening a new issue or contacting us on the IRC channel -- keep in mind that just code snippets won't help us troubleshoot the problem.

@LeoDupont Could you achieve to implement pdfjs viewer in your angular 2.x app?

@MstfTkrsln I decided to use @VadimDez 's wrapper : https://github.com/VadimDez/ng2-pdf-viewer.
It's not as complete or flexible as using pure pdfjs, but it works at least.

@LeoDupont but it does not use web/viewer.html template according to demo.
I would like to use this template but i couldn't find a way how can i import this prepared template in my angular component.

@MstfTkrsln  did you found any solution on howw to integrate pdf.js in angular 2+ ??

I copied prebuilt  version in my assets folder. Then i navigate ..\assets\viewer.html?file=mypdf.pdf with file parameter then it's working. I couldn't find another way to accomplish this. the documentation for angular 2.x was not enoughf.

@MstfTkrsln  Thanks sir, i will try this.


Configure light/dark mode via Appearance API

https://docs.expo.io/versions/latest/sdk/appearance/

Closing this as a duplicate of https://github.com/tasitlabs/tasit/issues/294


[Suggestion] Support hybrid inline-extract mode ?

emotion version: latest
react version: latest

Problem Description:
Extract mode is great, however for browsers that don't support css-vars, keeping styles in JS for rules that don't have any dynamic part is a compromise. They don't require css-vars to be extracted out.
Suggested solution:
Proposal is to use a hybrid of extract and inline for the case where css-vars aren't supported. We shall extract the rules out in a file if they are idempotent (no dynamic part), and keep them inline otherwise. This will ensure even better performance for slower / older browsers by ensuring smaller JS bundle, even if they lack css-vars support.

This is essentially how the version 7 beta works. Inline mode is the default and you can opt into having static styles extracted to files. There are no css vars.


create a forum for Saddle so we can ask questions

There is a google group you can join, this is the right forum -
https://groups.google.com/forum/#!forum/saddle


Future Roadmap

Hi. Is there a timeline for when the rest of the ES6 features will be supported ?

Apparently there's some sort of roadmap in the old xto6 site. It lists the following:

Convert commonjs module definitions
Convert var to let/const
For of loops
Convert arguments to rest parameters
Remove _this=this for arrow functions

Of these the let/const transform has been implemented, but is quite buggy. Instead of these some other transforms have been implemented:

Default arguments instead of a = a || 2
Function properties in objects to Object methods
Object property shorthands

I guess any roadmap should be taken with a good grain of salt.


Registry of tag name and style mapping

The default should be:

json: Comma
binding, validate: CommaEqSpace
gorm: SemiColon

This registry is used as strategy of parsing as-is tags, for further name/key/value lookup.


Firestore compound range query with missing index (no warning, double callback)

Label: Firestore Plugin
Desired Outcome:

Show warning when missing a compound index
This situation should not result in a double callback (once with data, once without)

Possibly relevant
I was performing the range query on a String field assuming lexicographical ordering (also, the string is of a bastardized date e.g. "2018-06-29")
Background
Using the Flutter Cloud Firestore Plugin, I have run into the 'compound query' issue.

However, to combine the equality operator (==) with a range comparison (<, <=, >, or >=), make sure to create a custom index.

This messages take you to the Managing indexes in Cloud Firestore docs:

If you attempt a compound query with a range clause that doesn't map to an existing index, you receive an error. The error message includes a direct link to create the missing index in the Firebase console.

In my case, I saw no such error message or link
My issue
I naively ran into this issue but was confused when I was seeing the handler callback (listening to the query snapshot) was being fired twice. Even stranger is that it first first with the correct data (well, what I assume to be the correct data) and then a second time with an empty list. Thus my flutter application gets a flash of data then poof!
This takes us back to the expected outcome of:

Can we show the compound index warnings with link to create the correct index
What's up with the double callback once with the data and then without?

Once I added the compound query (manually on the two fields) everything worked as expected and the handler function was only called once per update.
Below is basically my query (I'm including the wonky date as a string details rather than concealing this terrible truth from the world):
static StreamSubscription streamFooIdsForBar(String barId,
      String startDateStr, String endDateStr, onData(List<String> fooIds)) {
    return Firestore.instance
        .collection(SOME_COLLECTION_CONST)
        // equality clause on barId
        .where(
          'barId',
          isEqualTo: barId,
        )

        // range clauses on a funky date as string...
        .where(
          'someDateAsString',
          isGreaterThanOrEqualTo: startDateStr,
        )
        .where(
          'someDateAsString',
          isLessThanOrEqualTo: endDateStr,
        )
        .snapshots()
        .listen((QuerySnapshot query) {

      onData(query.documents
          .map((DocumentSnapshot doc) => doc.documentID)
          .toList());

    });
  }

Notes
flutter analyze -> nothing
flutter doctor -v
[✓] Flutter (Channel master, v0.5.6-pre.61, on Mac OS X 10.13.5 17F77, locale en-US)
    • Flutter version 0.5.6-pre.61 at /Users/ashton/development/flutter/flutter
    • Framework revision 2e559584e2 (7 days ago), 2018-06-22 16:32:32 -0700
    • Engine revision 549c855e89
    • Dart version 2.0.0-dev.63.0.flutter-4c9689c1d2

[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at /Users/ashton/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-27, build-tools 27.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.4.1, Build version 9F2000
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.0

[✓] Android Studio (version 3.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 25.0.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

[✓] VS Code (version 1.24.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 2.14.0

[✓] Connected devices (1 available)
    • iPhone 5s • 139775FA-03A3-4426-A335-C89AAF2BFA87 • ios • iOS 11.4 (simulator)

• No issues found!

This is a pretty annoying issue.
I did find a workaround though. Query.getDocuments() actually fails with an error which contains link for the custom index. Still if you don't know much about indexes it would be hard to discover this problem.

@pulyaevskiy, ah so calling getDocuments() rather than adding a snapshot listeners gives you the correct index link?
Yeah, my worry is that this will leave a lot of people scratching their heads

calling getDocuments() rather than adding a snapshot listeners gives you the correct index link?

Correct. It works this way in my tests at least.

@ashtonthomas
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/774. Any further collaboration will be done there.


leptos-router,  crates.io, missing README.md

This is a minor DX issue
I just thought you should know the leptos-router pages is looking a little bare
This page
Your solution to this problem in leptos/leptos/Cargo.toml is to add this line to the [package] block
readme = "../README.md"

It is also missing in a few other crates lepto-config, but I have not done an extensive search.
Anyway love the project ....

Thanks! For my future self, or for anyone who wants easy credit for a PR: the leptos_router Readme should ideally be basically the same as the module-level doc comment, and the ones for leptos_core, leptos_reactive, leptos_dom, leptos_server, and leptos_macro (did I miss any?) should be the same as the main Readme.

I will create a PR.... development is so rapid,at the moment, and the issue so minor  -  I assumed it would be rolled in with the torrent  ....one sec.

#328


[Bug]:   I can skip the restricted mode

Version

[X] I'm using version 1.15.1

Known issues

[X] I've checked Known issues

Existing issues

[X] I've checked Existing issues

Advanced Preferences

[X] I've checked Advanced Preferences

What operating system are you using?
macOS
Operating System Version
MacOS ventura
Reproduction steps
I appreciate the strict mode in your app as it encourages me to take necessary breaks. However, I found a way to bypass this restriction by putting my iMac to sleep using the power button and then waking it up again. This allows me to terminate the break prematurely.
Expected Behavior
The strict mode feature in the app should enforce break periods without allowing users to bypass the restriction. Putting the iMac to sleep and waking it up again should not terminate the break prematurely. The app should maintain the break period regardless of the device's sleep status, ensuring that users take the necessary breaks as intended.
Actual Behavior
When using the strict mode feature in the app, I discovered a way to bypass the enforced break periods. By putting my iMac to sleep using the power button and then waking it up again, the app prematurely terminates the break. This allows me to resume work without completing the required break period.
Relevant log output
No response
Preferences
No response
Additional information
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi, by default, the breaks get reset when user closes the lid. You can change that behavior with advanced preferences, specifically with Pause breaks on Suspend/Lock. It is not that reliable, though.

Thank you, that was really helpful!

great, I will close this, then :)


Add save_model file

Breakout_DQN.py does not have a file called save_model, so the code does not work.

thank you :)

Thank you!


Make HTTP client swappable for LSP+Prometheus clients

Signed-off-by: Julius Volz<EMAIL_ADDRESS>

@Nexucis I pushed a commit to change things from axios to fetch... and also abstracted the fetch-based Prometheus API access a bit (just inside the HTTPPrometheusClient). I didn't manage to test the LSP changes yet, as I would need to set up an nginx or something to allow for CORS access to my locally running LSP (adding proxying to package.json somehow didn't work).

I'm not super comfortable with this approach, but I guess that's the simpler way. I'm a bit sad by saying goodbye to axios, the code looked a bit more cleaner when using it :(

Yeah, I get that. On the other hand, now with fetch() we have one less (small, but not tiny) npm library dependency that is forced on users, by just using native browser interfaces :) And its interface is simpler, so it's generally easier to swap out.

Looking into LSP error handling a bit more now, and gonna rebase and add the proxying stuff we discussed.

Pushed the proxying + LSP error handling, check again :)

awesome thanks :)


fix(trusted-sync): Follow tip with head updates

Overview
Currently the trusted-sync binary follows tip by continuously attempting to advance the cursor, fetching the next block. If the cursor is at tip, this will just cause the loop to spam logs. Instead, the binary should subscribe to head updates to avoid busy waiting, and advance the cursor on head update. This will allow the service to run persistently and expressively in our infrastructure.
We can do this most ergonomically by splitting the trusted sync control flow in two stages. The first stage is when the starting l2 block number origin to sync from is before tip. When this is the case, we perform the iterative looping over pipeline attributes creation and origin advancing. Once L1 tip is reached, trusted-sync advances to the next stage where it subscribes to new head updates and only drives the pipeline on head advancement.

Moving to nice to have since this is not critical - trusted-sync follows tip well, despite a bit more verbose logging.

trusted-sync is dead, long live trusted-sync https://github.com/anton-rs/kona/pull/621


Add links to readme?

As discussed here https://discourse.julialang.org/t/how-do-i-know-if-a-package-is-good/82133, it would be nice if this package's Readme linked to some alternatives: CSV.jl, DelimetedFiles.jl
I realised everyone likes to advertise what their package is good at, but sometimes users find the wrong one for their needs first. This package's name is close to Matlab's dlmread, so some people may find it who really just need the standard library's DelimetedFiles.jl.
Cc @juliohm from discourse thread.

I am ok with adding links to other packages. Please go for it. thanks.


Failed purchase error codes - Billing response codes instead of IAB Helper ?

Hello
It seems that error codes returned by purchaseFailedEvent, in unity plugin, is about IAB Helper error codes. How can i get "Billing response codes" instead of IAB Helper in unity?
IAB Helper error is not enough accurate for reach my goal. I would like to catch error like  "ITEM_ALREADY_OWNED"
Regards,

I'm pretty sure you can get this error from IabResult:BILLING_RESPONSE_RESULT_ITEM_ALREADY_OWNED = 7;

I'm not sure that IAB result is directy accessible from purchaseFailedEvent in unity plugin. How can i access it?
Here my purchaseFaildeEvent function, that always retuns me an -1005 error code when item is already owned.
private void purchaseFailedEvent(int errorCode, string errorMessage) {

	// if sku has already been purchased (error code 7)
	if (errorCode == 7) {

		/* unconsumable SKU */

		if (_SKU_temp == SKU_NOADS) { SetNoAds(true, null); }
		else if (_SKU_temp == SKU_PREMIUM) { SetPremium (true, null); }

		/* consumable SKU */

		else if (consumable_skuNames.Contains(_SKU_temp)) {

			if (inventory.GetPurchase(_SKU_temp) != null) {
				OpenIAB.consumeProduct (inventory.GetPurchase(_SKU_temp));
				ShowMsg ("Consuming item");
			}

			else {
				ShowMsg ("Unable to find purchase entry. Retry later.");
			}

		}
	}

	else {
		ShowMsg ("Purchasing product error (" + errorCode + ")");
	}

	// clear vars
	_SKU_temp = null;

	Debug.LogError("purchaseFailedEvent: " + errorMessage);
}


Fix typo in metaregistry

Partially addresses #41, by fixing a typo in synonyms.

Thank you. I was so confused by this.

PyCharm is adding the newlines at the end of the file automatically, I didn't do that on purpose. I just figured out how to turn that off.

Ehh i think we're going to run into this problem a lot. I guess we will just have to live with one extra line of diffs for whitespace popping up here and there