Update LICENSE file

In the course of reviewing PR #77, we opted not to update the LICENSE file (see: jgarber623/microformats-ruby@6778565) since it wasn't a terribly valuable change.
I happened upon some additional resources around how GitHub recognizes LICENSE files:

https://help.github.com/articles/licensing-a-repository/
https://choosealicense.com
https://choosealicense.com/licenses/cc0-1.0/

This PR adds the text from choosealicense.com's CC0 page which should expose the project's license to GitHub so that it can be surfaced in search results and displayed in the GitHub UI similar to:

It's a small thing, but potentially useful. Thanks for taking a look!

@dissolve Circling back around to this after too many months. Any objection to merging this one?

@dissolve Awesome, thanks!

Success! 🎉


Same class names in css in both development and production?

Hello,
I have a question regarding the class names used in development and production.
The documentation (https://material-ui.com/customization/css-in-js/#class-names) says:
Instead, you have to use the classes property of a component to override them. On the other hand, thanks to the non-deterministic nature of our class names, we can implement optimizations for development and production. They are easy to debug in development and as short as possible in production:

development: .MuiAppBar-root-12
production: .jss12
If you don't like this default behavior, you can change it. JSS relies on the concept of class name generator.

How would I get the same behaviour both in development and in production including the html-structure and names for classes easiest? I would be happy to use the short names in development as well for example.
Problem I'm facing is that in development the names and structure is different so as i'm develpoing I always have the check the GUI in both develpoment and production modes (in webpack) which is time consuming and prone to errors.
Thank you for your advice and comments, there probably is something I'm missing here.. :)

[ ] This is a v1.x issue (v0.x is no longer maintained).
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

Your Environment

Tech
Version

Material-UI
v1.?.?

React

browser

etc

@mikkopori I don't understand your problem. What's your workflow?

Thank you for your reply.
My workflow is in development flow to run:
./node_modules/.bin/webpack --config webpack.config.js --watch -d --watch-poll
and in production:
./node_modules/.bin/webpack --config webpack.config.js -p
and depending on this Material UI and webpack handle html and css differently. I would like to have them handle these similarily so developing the GUI would be easier.

@mikkopori Reading between the lines, I think perhaps you should be in the Overriding with classes section of the documentation.? If so, then perhaps we should link there from the section you were quoting.

Yeah, something is off with this question. Either use the classes property for overriding the style or use the global CSS option.

Okay, thank you for the guidance.
What I mean by the difference between development and production css is this:

So you are happy to design the the elements in development mode, but once you place them in production there appears new css-properties that have to be designed again.
For example the ::before and ::after pseudo-classes.
How could I the same css-properties already visible in development mode?
I do not believe the overriding solves this issue..

@mikkopori It's hidding something else. You have a class name generator duplication issue.

This could be it! So I'm not supposed to have for example the jss1 in several different components at the same time? Any tips on where to solve this?

@mikkopori I'm not sure I can help more than linking: https://material-ui.com/getting-started/faq/#how-to-fix-a-class-names-production-build-conflict-


fix(input): fix input blur event trigger error

Types of changes

[ ] New feature
[x] Bug fix
[ ] Enhancement
[ ] Component style change
[ ] Typescript definition change
[ ] Documentation change
[ ] Coding style change
[ ] Refactoring
[ ] Test cases
[ ] Continuous integration
[ ] Breaking change
[ ] Others

Background and context

https://github.com/arco-design/arco-design-vue/issues/1954
Solution

How is the change tested?

fix input blur event trigger error
Changelog

Component
Changelog(CN)
Changelog(EN)
Related issues

Checklist:

[x] Test suite passes (npm run test)
[x] Provide changelog for relevant changes (e.g. bug fixes and new features) if applicable.
[x] Changes are submitted to the appropriate branch (e.g. features should be submitted to feature branch and others
should be submitted to main branch)

Other information

@LadyChatterleyLover 这是一个 change 事件逻辑错误产生的问题，在 https://github.com/arco-design/arco-design-vue/pull/1990 中整体修复了下，这个问题也同时解决了。这个 PR 就先关闭了


Contributes Android Injector support.

This is just a rebased jakew/contributes-android-injection/2019-02-21. Works for us and our codebase!

Rebased and reformatted and merged to master as dcd05ff


Object value strings have extra quotes.

I use the extended webpack plugin as such:
      new ExtendedDefinePlugin({
        GlobalKey:  {
              numberKey: 1234,
              stringKey: "foo",
          },
      }),

But when the output I get is:
console.log(GlobalKey.stringKey,  typeof GlobalKey.stringKey);
// Outputs ""foo"" string

UPDATE:
So after wasting a good 2 hours, I find out its happening because I'm using multiple webpack configs — server and client, and the unexpected behaviour always occurs in the second config.
This is because this library is directly modifying the params sent to it (which are passed by
reference). Ouch. Use ESLint no-param-reassign maybe?

I recommend using EnvironmentPlugin instead of this.
Sorry for your troubles. When I wrote this, webpack didn't include the EnvironmentPlugin, but now it's best to use this one as I don't maintain this project anymore.

EnvironmentPlugin seems to work best with environment variables.
I've raised a small pull request #2 to fix this behaviour — might be helpful for people using multiple webpack config objects.


TrueOS-Desktop-2016-08-31-x64-USB.img black/blank screen instead of TrueOS Installation Menu

TUXEDO InfinityBook
Intel Core-i Prozessor, Skylake: Intel Core i7-6500U: 2x 2.5-3.1GHz Dual-Core, 4 Threads, 4MB Cache
Intel HD Graphics 520
When booting from USB I get the used FreeBSD start messages until something like
Intel graphics detected
Using Intel video driver
and some (about 8) drm messages with an drm error
(that I can't read because of the blackend screen)
After that nothing happens, but the system (freebsd) seams to run, at least it is possible to shutdown it regulary by pressing the power-button for a second.
I guess there is a problem with the intel-video-driver so I tried the 'Failsave VESA-mode', unfortunately with the same result.
I was able to install PCBSD11.0-CURRENTJUNE2016-06-10-2016-x64-USB.img in SCFB-Mode, but wasn't able to start the installed system afterwards (xorg is trying to start (a lot of 'Please wait ... Starting xorg' messages for some time) but ends up in a black screen too).
I would be glad to help with further information, please let me know how to attain these if needed.
Kind regards
Martin

It sounds like you are not getting to the installation menu due to the i915kms loading when the video detection routine runs ahead of the installer menu.  I resolved this for the next image which should come out sometime later this week.  It will not load i915kms until the either auto detect, or intel is selected.  This will allow use of VESA, or SCFB on unsupported graphics cards.
Especically since you have skylake I would report the drm errors here where that is being developed specifically for further investigation:
https://github.com/FreeBSDDesktop/freebsd-base-graphics/issues


Add location URL to calendar invite

This PR is about adding the location URL to the calendar invites (session and fullevent)

@jakearchibald Please review


chore: Bump GO version

This PR
GO 1.19 is deprecated https://endoflife.date/go, this PR bumps the version to 1.21.

@thomaspoignant should we also bump the min go versions in the project go-mods? Or is it common practice to keep them on lower (deprecated) versions.
We could increment them all to Go 1.20.

I also had a similar idea proposed through this PR - https://github.com/open-feature/go-sdk-contrib/pull/377
This is a blocker for Flipt provider PR - https://github.com/open-feature/go-sdk-contrib/pull/376
Per my knowledge, we can use any latest version of Go and each provider vendor can choose their version of choice for the minmum supported version through go.mod file. However, CI should support the latest stable version so vendors can stay at most recent version if they like.

@Kavindu-Dodan do you think I can remove this PR and we can merge yours instead?

Closing this one since the one from @Kavindu-Dodan has been merged


Broken link

Link broken on this page, this is the good one.

Thanks, will be fixed in the next doc deploy.


Cayenne is evaluating Sepolia access conditions based on data from the Ethereum mainnet.

**Before reporting, I have already ***

checked LIT Protocol developer docs and/or the lit-js-sdk.
searched for other open issues.

Describe the bug
I am using the encryptString and decryptToString functions with unified access conditions for handling token-gated access to information. I did my testing on the Sepolia Testnet (chain ID: 11155111). However, I keep receiving errors indicating
"Invalid name: please ensure the contract and method you're calling exist! failed to decode empty bytes. if you're using jsonrpc this is likely due to jsonrpc returning 0x in case contract or method don't exist"
I tried switching my testing to the contracts deployed on Ethereum mainnet, and the error disappeared. I went further to run the test on the same Ethereum contract "0xD4416b13d2b3a9aBae7AcD5D6C2BbDBE25686401", while specifying the chain as Sepolia, and surprisingly the condition evaluation is working. Please see the unified access condition I used for verifying the Ethereum contract's condition on Sepolia network.
{         conditionType: "evmContract",         contractAddress: '0xD4416b13d2b3a9aBae7AcD5D6C2BbDBE25686401',         functionName: "balanceOf",         functionParams: [':userAddress', '1234'],         functionAbi: {           type: "function",           stateMutability: "view",           outputs: [             {               type: "uint256",               name: "",               internalType: "uint256",             },           ],           name: "balanceOf",           inputs: [             {               type: "address",               name: "account",               internalType: "address",             },             {               type: "uint256",               name: "id",               internalType: "uint256",             },           ],         },         chain: 'sepolia',         returnValueTest: {           key: "",           comparator: '>',           value: '0',         },       }
This indicates that the Sepolia chain access conditions are evaluated based on the data from the Ethereum mainnet. I went down to the SDK code and the error seems to be coming from the Node instead of the client code.
To Reproduce
Steps to reproduce the behavior:
Please use the above unified access condition for encrypting and decrypting strings. Note that the contractAddress points to a contract on Ethereum.
Expected behavior
The above condition should evaluated to some meaningful result, while any contracts deployed on Sepolia should throw errors.
Environment:

Lit SDK version 3.2.2 for nodejs, on the "cayenne" network
Node version 18

This issue has been solved by the Lit Protocol team


Update bower.md to prefer LibMan

@guardrex  did I get rid of the right smarty quote?

@guardrex  never mind, missed your comment.

You did! You did! That quote really wasn't all that smart ... I was smarter than that quote ... so how smart could it really have been?? 😀


Update composer.json

Fix to not install it on wrong php versions
What are you changing/introducing
Fixed versiono of php
What is the reason for changing/introducing
Fix to not install it on wrong php versions
QA

Q
A

Is bugfix?
yes

New feature?
no

Breaks BC?
yes/no

Tests pass?
yes/no

Fixed issues
comma-separated list of tickets # fixed by the PR, if any

dear @giuseppealtomonte i made a mistake, i need to revert the changes which required php 7.4, its a BC break. But i will do a 2.0 release für 7.4. Thanks for pointing out that problem

I just tagged 1.3.1 (https://github.com/luyadev/yii-helpers/releases/tag/1.3.1), could you tests again with a lower php version? I assume you had that problem.

minimum tested php level is now again 7.2


Using "Import Project" in the test csproj (embedding the test framework in props) stops auto detection

Installed product versions

Visual Studio: VS 2019 V16.6.0
This extension: 2.4.0

Description
Looks like after VS16.6.0 update that the boilerplate:

Using "Import Project" in the test csproj (embedding the test framework in props) stops auto-detection

Steps to recreate

Create a central project props file
import the props file to the test csproj
Try to generate a test using boiler plate

Current behavior
It cannot "collect" the test and mock framework from the project import
Expected behavior
The auto discover still works.
OR, is there an attribute or something we can add to the CSPROJ so it discovers the framework  + sub?
Thanks for WONDERFUL extension

Just released 2.4.5, which should fix your issue. I added a step to check the references on the loaded project in the Visual Studio API, which catches references loaded by props files.
Give the extension a nice review if you like it!


[Table] New generic slots.

Description
Currently, we have slots named <column>-header and <column>-data. However, in some scenarios, it may be necessary to intercept all cells, regardless of the column name.
It would be beneficial to introduce generic header and data slots.
<UTable>
  <template #data="{ row }">
    Now, all data cells are equal.
  </template>
</UTable>

Additional context
No response

I'm also looking for a way to manipulate the header because I would like to display icons there

I'm also looking for a way to manipulate the header because I would like to display icons there

@migro1982 you can do something like this.
It's not as obvious as proposed in the issue, but it solves the problem.
<template
  v-for="header in headers"
  :key="header.key"
  #[`${header.key}-header`]="{ column }"
>
  Slot of "{{ column }}"
</template>

This would be so helpful... this is my current set up
`

`
I would really prefer it if I could indicate a condition for when the row is selected and present the complete form with validation else default to the table data... This is my implementation of utable with form input

An I deal situation for me is something similar to what primevue did here
https://tailwind.primevue.org/datatable/#cell_edit

@Nyantekyi I'll keep this in mind when building the Table component for v3 😊

Duplicate #818.

Reading the issue you commented above, it doesn't seem to be the same topic. Anyway, I hope it's available in #2139.

@caiotarifa It's implicit, all component in Nuxt UI v3 implements generics 😊


Future-proof view test against signaling NaNs

As currently written, the view test may lead to failures if the random seed generating test cases is changed, and it ends up generating bits that indicate a signaliing NaN. This should future-proof the test against such failures.

Tests pass internally.


[Suggestion] make option to keep alpha channel surrounding image upon download

This is definitely something that could be done in photoshop after downloading the file, but if there was an option to have plain backgrounds turn into alpha channel it would make for a smoother workflow going from the app to an image editor.

Maybe we could have a 'color' that has the ai paint in.. transparency?

Could we get information on this? Has it been added already?

SEPA will have an AI-driven matting system to independently resolve all alpha problems.


[RFC] options about low-bit GEMM kernels contribution on x86 CPUs

Hi, here is Zhe from Intel AI software engineering team. Thank you for creating this amazing project AutoAWQ.

Motivation
My colleagues have done some pretty good work on low-bit GEMMs (e.g. int4). We have developed a kernel template library called BesTLA, which is similar to Cutlass. BesTLA is highly optimized for x86 CPU hardware and supports the most advanced ISA(e.g. AMX, VNNI). It has shown significant performance benefits in recent MLPerf submissions.We would like to help optimize the performance of AutoAWQ on x86 CPUs. We need some advice from the community on how to best contribute to this project.

Options
We can contribute these kernels in two different ways:

Option 1: Through a Python package
Currently, BesTLA kernels are packaged as Torch extended ops in the Intel-Extension-for-Transformers (ITREX) Python package. AutoAWQ can use these Torch extended ops directly by adding ITREX to the requirements list in its setup.py file. ITREX depends on the Torch version at build time. AutoAWQ can specify the version of ITREX via PyPI to ensure that the Torch version it depends on is consistent with the Torch version that ITREX depends on.If users need to build from source, we can also add specific commit from the ITREX repo main branch in autoAWQ requirements, like
requirements = [
    "torch>=2.0.1",
    "ITREX @ git+https://github.com/intel/intel-extension-for-transformers.git@commit"
]

The advantages of this approach are:

It has minimal impact on the existing AutoAWQ project structure.
It makes it easier to maintain and update the CPU-side kernels. You can update the kernels by simply changing the ITREX version in setup.py.

Option 2: Through source code
We can also integrate BesTLA directly into the AutoAWQ_kernels project. However, the process of building BesTLA into Torch extended ops is quite complex. It requires using CMake to build the extension, so we need to rewrite build_ext class from setuptools to make it compatible with both Torch's BuildExtension class and CMakeBuild class. This will add a lot of content and make major changes to AutoAWQ_kernels.setup.py.The advantages of this approach are:

It does not introduce third-party dependencies.
AutoAWQ maintainers can have better control over their project.

We welcome any suggestions. feel free to comment so that we can find the most proper manner to contribute:)

@casper-hansen Thanks, very useful😄

Thanks @casper-hansen. We briefly discussed this on X about adding CPU optimizations to AutoAWQ, and we are going to create a PR soon as you suggested.


Add Scala-Native examples (500USD bounty)

From the maintainer Li Haoyi: I'm putting a 500USD bounty on this issue, payable by bank transfer on a merged PR implementing this.

We already have Scala-Native support in scalanativelib, but it is not very discoverable and is not covered in the docsite. We should add example tests with explanations and include them in the docsite so people can read the docs and learn how to get started with a simple scala-native project.
This ticket is to add the following examples to a new example/scalalib/native folder:

[ ] example/scalalib/native/1-simple: a simple hello-world Scala native project, similar to example/scalalib/basic/1-simple: build, test, run of a trivial one-module project with some trivial thirdparty dependencies

[ ] example/scalalib/native/2-interop: a Scala-native project that interops with native C code that is compiled as part of the build, similar to example/javalib/module/15-jni

[ ] example/scalalib/native/3-multi-module: a version of example/scalalib/basic/3-multi-module except the two modules are scala-native modules each with their own C code, and with both Scala- and C-level dependencies between the two modules

[ ] example/scalalib/native/4-common-config: a version of example/scalalib/module/1-common-config but giving an overview of the important Scala-Native config specific overrides rather than the generic-Scala config overrides

These should be included in a new page in the documentation docs/modules/ROOT/pages/scalalib/native-examples.adoc titled Scala Native Examples, similar to docs/modules/ROOT/pages/scalalib/web-examples.adoc.
All the scala-native integration code should already be there, this ticket is just about documenting it and making it discoverable

Paypal ?

Bank transfer, as stated in the description

Do I understand correctly from https://github.com/com-lihaoyi/mill/pull/3583 that it would make those automatically available from mill init ? If so, that's brilliant :)

@rom1dep yes these can become automatically available from mill init. That's the whole point of #3583 after all!


Dark Theme

This is my proposal for a dark theme such as requested in #49
I took a very simple approach using the media query prefers-color-scheme to toggle between light and dark. When dark mode is detected, which is determined by the users system settings, the css rules override some of the colors. Browser compatibility is fairly good for any versions from the last 2-3 years. OS compatibility is good as well, Ive tested on Android, Windows, Manjaro, and Fedora with Chrome and Firefox. I havent tested Mac or IOS but I understand they should be on par.
The benefit of using the media query is there's no js changes needed, which made it much easier to do. However if you prefer to have a dedicated switch in the settings then it would be possible to use the same styling as a starting point.
Did not change any of the defaults so the light theme should remain the same.
Color-wise I just used colors off of Github's dark theme and tweaked it until I think it looks reasonable.  My screenshots look fine so its something that github did to them.

@SuiriuS Thanks for the effort, however I decided not to go ahead with your solution and implemented the dark theme myself (#100). I saw several issues with your solution:

In general the color scheme was not optimal. The contrast for many elements was way too low which made them hard to read. Also many of the colors did not match very well and were way off from the original Spectre.css color scheme.
I felt your approach of overriding styles per page would not scale very well. Instead I decided to compile two different theme files, which allowed me to just redefine the existing Spectre.CSS variables instead of duplicating existing style rules. That in turn makes most of the components work out-of-the-box, also the ones that are not used yet but might in the future.

Closing.


Error: MSSQL - Cannot Read Property Rowcount of Undefined

Why that message when I try to execute this select statement?

Does this problem occurs without the brackets? By the way, what is the reason of the brackets, I guess I have never seen brackets in a SQL query before :smile: .

This problem still occurs without the brackets :(
I just did double clicked the table name. After that, the select statement appeared.
Btw it's a common practice to use brackets, maybe because Microsoft SQL Server Management Studio use brackets as default.


Sync of GitHub repositories within 2024.10.14-20

The aim is to synchronize GitHub repositories in the given period.

Repositories are synchronised. Goal is achieved.


Update constructor docs to include context

The docs previously did not indicate that it was necessary to call super(props, context) if you are using context within components, which could cause confusion. Opening this PR to start discussion around a change to make this more obvious (I searched and could not find a previous issue)

We intentionally don't use context in the API docs anywhere except the Context page because it's still considered experimental and people should minimize its direct usage. Even though we won't remove it we do plan to change it. Most people shouldn't attempt to use it directly.
It would make sense to me to instead add a caveat about this to the Context doc itself, and leave others as they are.

Ok, I can make an update to that page then :)
On Mon, Oct 16, 2017 at 17:04, Dan Abramov<EMAIL_ADDRESS>wrote:

We intentionally don't use context in the API docs anywhere except the
Context page because it's still considered experimental and people should
minimize its direct usage. Even though we won't remove it we do plan to
change it. Most people shouldn't attempt to use it directly.
It would make sense to me to instead add a caveat about this to the
Context doc itself, and leave others as they are.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/reactjs/reactjs.org/pull/168#issuecomment-337078457,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA5hFmWvHHtLwdcdEBlHoMzBKZCF6awZks5ss-72gaJpZM4P7ZX2
.

I looked, the page on context already has some documentation about the constructor.
Would you be open to adding a warning to the component docs page about avoiding using context directly, which links to the context docs page? It seems like since this page doesn't mention context in the constructor, it would be easy for someone to mistakenly exclude it, which would break using a library like react router, correct?

I'm open to adding a second "Note" in the constructor doc that mentions context linking to its doc and shows the different signature.

I would honestly recommend rest/spread-ing the constructor args.
class Foo extends Component {
    constructor(...args) {
        super(...args);
        // ...
    }
    // ...
}

A component author generally shouldn't be fiddling with any of the arguments to the constructor, and writing your constructors this way also future-proofs the component: if React team decides for whatever reason to radically change the constructor arguments, a constructor declared as above will be unaffected by the change. The same argument also applies to migrating a project into react-router, or any other framework which similarly uses context. Existing components should Just Work™ regardless of the structure of the constructor arguments.

Ok, the wording has been updated

I'm a little uneasy about this wording. It's not technically required that you call super with context (or even props for that matter) since React has your back in case you forget. The only time it matters, in practice, is if you call this.context within the constructor function.
I'm wary that this change could influence people to bulk-modify their code unnecessarily in order to change super(props) to super(props, context) and that this could in turn make changes to context slightly less convenient down the road. (Although that kind of change would also be pretty easy to code mod away so maybe I'm just over-thinking it.)
I'm also a bit nervous that this note might confuse people unnecessarily (eg "How do I know if any of the libraries I'm using rely on context?") when in practice, it only matters in a very specific (and probably not super common) situation.
Either way, thanks so much for the proposal and the discussion. I could be wrong - and I'd love for people to speak up if they disagree with this decision - but I think it's best to leave this note out for now.

Ok, thanks for taking the time to reply. :)
On Fri, Nov 17, 2017 at 08:04, Brian Vaughn<EMAIL_ADDRESS>wrote:

I'm a little uneasy about this wording. It's not technically required
that you call super with context (or even props for that matter) since React
has your back in case you forget
https://github.com/facebook/react/blob/b5e4b45a1036e3587415ae395f9d62a0229ed7e2/packages/react-reconciler/src/ReactFiberClassComponent.js#L446-L449.
The only time it matters, in practice, is if you call this.context
within the constructor function.
I'm wary that this change could influence people to bulk-modify their code
unnecessarily in order to change super(props) to super(props, context)
and that this could in turn make changes to context slightly less
convenient down the road. (Although that kind of change would also be
pretty easy to code mod away so maybe I'm just over-thinking it.)
I'm also a bit nervous that this note might confuse people unnecessarily
(eg "How do I know if any of the libraries I'm using rely on context?")
when in practice, it only matters in a very specific (and probably not
super common) situation.
Either way, thanks so much for the proposal and the discussion. I could be
wrong - and I'd love for people to speak up if they disagree with this
decision - but I think it's best to leave this note out for now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/reactjs/reactjs.org/pull/168#issuecomment-345284628,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA5hFoZ5EyaVPYkTYs-7EIi-MslQTNXJks5s3a5FgaJpZM4P7ZX2
.


Fix dependent job not run if it got updated

This fixes an issue where a job that depends on two or more parent jobs
is not executed if it was updated while some of the parent jobs
have finished while others are still running.

Some more background information.
Given the following dependency graph:

parent runs for five seconds. It's just there to trigger the other jobs.
layer1-job1 takes 60 seconds to complete
layer1-job2 takes 30 seconds to complete
layer2-job1 is just there to be triggered by its parent jobs

Without this fix, this happens:

parent starts
parent finishes and triggers layer1-job1 and layer1-job2
layer1-job2 finishes but layer1-job1 is still running
A user updates the configuration of layer2-job1
layer1-job1 finishes
layer2-job1 is not executed

This happens because DependentJobResource.handleRequest first calls JobGraph.removeDependency and then JobGraph.addDependency. Doing so resets the value of edgeInvocationCount  for the edge between layer1-job2 and layer2-job1 to 0 which leads to count and min not being equal here.
I would expect that the job is executed if the parents of a job have not changed during an update and that is what this PR fixes.

:+1:

Thanks for reviewing this so quickly.


Use a Justfile instead of a Makefile

This is a pretty silly PR, but I thought you might find it interesting.
I wrote a program called just which is basically just make for running commands.
Some advantages over make:

It can be called in any subdirectory. It will cd up until it finds a file called justfile or Justfile and run commands from any directory.

It gives very helpful error messages when you mess up the syntax of the justfile, as opposed to the super cryptic error messages that make gives

It is written in rust, so you can cargo install just and be done with it. It relies on sh from the host system, but that's it.

It supports a lot of options, like recipes with parameters, etc, documented in the readme.

No .PHONY recipe necessary XD

Feel free to close if you're not interested.

Thanks for the PR but I don't see the value in this.


Can't find BackgroundBeaconMonitoring

@stephenrob
I have added your plugin, i can see it in my package.json but when I try to find it in my typescript code like : "console.log(cordova.plugins);" i don't see BackgroundBeaconMonitoring class and its method. How do you call BackgroundBeaconMonitoring  in your app ??

I've currently not looked into typescript and angular2. The application we are developing with Ionic is still Ionic v1 and Angular 1.5.3 (I'm just cleaning up some of the code before open sourcing this).
Below is an extract from one of our AngularJS services that uses the BackgroundBeaconMonitoring Plugin.
Once you have added the plugin the javascript files should be available to use, they are auto included like all other plugin files, make sure you have android added to your project as this plugin currently only works for android. At this stage you can just call the plugin methods documented in the README.
In most cases you will need to customise the code in this plugin, generally the BeaconLoggingMonitorNotifier and BeaconLoggingRangeNotifier to suit your individual application needs, not just adding the plugin.
angular.module('myJourneys.services').service('BeaconMonitoringService', function($rootScope,
                                                                                $ionicPlatform,
                                                                                $cordovaBeacon,
                                                                                $cordovaLocalNotification,
                                                                                $cordovaDevice,
                                                                                BEACON_UUID,
                                                                                BEACON_GLOBAL_MAJOR,
                                                                                BEACON_GLOBAL_MINOR,
                                                                                BEACON_REGIONS,
                                                                                API_SERVER_URL,
                                                                                API_VERSION,
                                                                                PreferencesService,
                                                                                RegionEventsService,
                                                                                BeaconEventsService,
                                                                                AuthService,
                                                                                $timeout) {

  var BeaconMonitoring = function() {};

  ...

  var requestPermissions = function() {
    $cordovaBeacon.requestAlwaysAuthorization();
    $cordovaLocalNotification.promptForPermission();
    BackgroundBeaconMonitoring.requestPermissions();
  };

  var initAndroidService = function() {

    $ionicPlatform.ready(function() {

      var device_id = $cordovaDevice.getUUID();

      BackgroundBeaconMonitoring.startService(AuthService.token(), AuthService.email(), device_id, API_SERVER_URL, API_VERSION, PreferencesService.readSendMovement(), function() {

        BEACON_REGIONS.forEach(function(region) {

          var identifier = region.identifier;
          var uuid, major, minor = "";

          if (region.uuid === undefined) {
            uuid = BEACON_UUID;
          } else {
            uuid = region.uuid;
          }
          if (region.major === undefined) {
            major = BEACON_GLOBAL_MAJOR;
          } else {
            major = region.major;
          }
          if (region.minor === undefined) {
            minor = BEACON_GLOBAL_MINOR;
          } else {
            minor = region.minor;
          }

          BackgroundBeaconMonitoring.startMonitoringRegion(identifier, uuid, major, minor, function() {}, function() {});
          BackgroundBeaconMonitoring.startRangingRegion(identifier, uuid, major, minor, function() {}, function() {});

        });

      }, function() {});

    });

  };

  BeaconMonitoring.prototype.init = function() {

    $ionicPlatform.ready(function() {

      requestPermissions();

      ...

      initAndroidService();

    });

  };

  return BeaconMonitoring;

});


Add handling for additional error codes that shouldn't be considered a permanent failure

This PR makes SDWebImageManager handle the error codes NSURLErrorInternationalRoamingOff, NSURLErrorCallIsActive or NSURLErrorDataNotAllowed on iOS 7 so that the URL that triggered the error isn't put in the failed URL anymore, as the URL can be tried again once the conditions are right (Since the error doesn't come from the server)

@stephanecopin why did you add his check
NSFoundationVersionNumber <= NSFoundationVersionNumber_iOS_6_1 in your if statement?
if (shouldBeFailedURLAlliOSVersion && (NSFoundationVersionNumber <= NSFoundationVersionNumber_iOS_6_1 || shouldBeFailedURLiOS7)) {

@mythodeia indeed, my mistake, I'll update it

This PR breaks offline image support. @mythodeia

@jstart this https://github.com/rs/SDWebImage/commit/60cab8b74cb59a79c69957368628c48a3f82a454 fixed this issue


Fix for issue 3349 - Package name should be el7, not el7.centos

#3349 reference Centos is over specific. It should be simply el7 which is more inclusive

@joeyaiello and @SteveL-MSFT please review to see if the name change is good.

We won't delay beta.1 for this change.

I think I have them all now

The changes to markdown files and dockerfiles will break our users, because we currently don't have the package named powershell-6.0.0_beta.1-1.el7.x86_64.rpm.
The changes to files other than build.psm1 would be reverted, and those changes should be done in the next release.

@daxian-dbw so your recommendation is that we stage these changes: change build.psm1 so that our next release will have the correct file name, then update all the readme/scripts to use this new filename after the release, correct?

ok - pulled first commit, running through CI now


Pass delimiter to fsspec in bag.read_text

[x] Closes #7293
[x] Tests added / passed
[x] Passes black dask / flake8 dask

Interesting that this fails on windows ("\r\n"). We should check that the test was, in fact, correct!

Looks like it should work, but when I wrote a test it did not pass with blocksize passed:
        longstr = 'abc\ndef\n123\n$$$$\ndog\ncat\nfish\n\n\r\n$$$$hello'
        with filetexts({'.test.delim.txt': longstr}):
            assert read_text(".test.delim.txt",linedelimiter='$$$$').count().compute() == 3
            assert read_text(".test.delim.txt",linedelimiter='$$$$',blocksize=2).count().compute() == 3
            vals = read_text(".test.delim.txt",linedelimiter='$$$$').compute()
            assert vals[-1] == 'hello'
            assert vals[0].endswith('$$$$')
            vals = read_text(".test.delim.txt",linedelimiter='$$$$',blocksize=2).compute()
            assert vals[-1] == 'hello'
            assert vals[0].endswith('$$$$')

What do you expect to happen if the separator is larger than the blocksize??
It actually seems to work, except that you get [""] from an empty block. With the tests changed as in the last commit, it passes. Is this reasonable? I don't know how to distinguish between two successive separators and an empty block.

(still fails windows line ending)

I think you still get empty blocks with a blocksize of 6 though, so it isn't just the relationship between the delimiter length and blocksize.  I thought empty blocks got cleaned up somewhere (they do with the newline case).

I hope everyone appreciates that I had to boot into Windows to get this right!

@jsignell , want a look?


bug fix: get correct attribute when commitment mapping is there

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

Comparison is base (62e70fe) 71.05% compared to head (eccad89) 71.05%.

Files
Patch %
Lines

apps/sage300/exports/base_model.py
0.00%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #129   +/-   ##
=======================================
  Coverage   71.05%   71.05%
=======================================
  Files          79       79
  Lines        3517     3517
=======================================
  Hits         2499     2499
  Misses       1018     1018

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


[Removal]: Real Cloud Cheetah

Hotspot Name
real-cloud-cheetah
Hotspot b58 Address
112ugmWTjnrR9uh9Kde82x3e63H27H3yE8a8cEJWFxikhXQcLJ3a
Discord Handle
Merikon#6484
Hotspot Manufacturer
PantherX
Removal Reason
The location and its actual place used to be not coincide with each other to reach a larger coverage. That's probably why my hotspots appear on the denylist. However, the problem has been fixed now and the hotspots appears at where they should be.
Modifications
No
Extra forwarders
No
Extra antennas
No
Additional Information
Hi Helium manage team, thanks for all the effort you have done to build an effective and honest network. I'm an officer of a local wlan & IoT service firm. Many of the residents in my town got involved into the Helium network and community by deploy the hotspots at their home last September. Most of them are using indoor hotspot while some of them deploy extra antennas (maybe hand-made). We were impressived by this genius idea of people's network.  From my prospective as a IoT industry participant, this network definity lower the total IoT infrasturcture cost and must grow in a rapid way. Some of residents in the coverage region also tried the rak WisNode Senser and they really work well.
However, in order to reach a larger coverage and increase the reward scale, some of the hotspots were located a small distance deviate from where it should be. We realized this attempt lead to the inclusion to the denylist so we correct this mistake by moving hotspots and relocate them on the Helium map. By far all of the hotspots appears at the right place (no more than 300m deviation).
Also, I found that there were some hotspots locate near our town by they really shouldn't be at there. These virtual hotspots are included in the denylist either. I wonder if those gaming hotspots that never interact with us made all of us into the denylist? If so please update your algrothim in order to avoid this situation again.  Thanks

.

If you have any questions of need more information, please contact me in discord at any time!

We have taken into account this removal request in the next iteration of the denylist. It may take some time before it's processed. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.


4 side-drawers in BasicNFT lesson are not rendering

There are four pieces of content from the Fundamentals Track, and they are called/used in NFT Track - Build a Basic NFT lesson (lesson 2):
academy-turbo/apps/academy/src/pages/tracks/nft-solidity
/2.mdx
Unfortunately they aren't rendering.
Where to find it on the page. Here are the first two:

What it looks like after clicking on the button, i.e. the inside of the side-drawer:

There are another three Fundamentals in the lesson. And one more edge case 👇🏼
Is there an MVP fix that I could do? E.g.

convert the < sidedrawer > components in the lesson 2 .mdx to < lessonInformationalModal >
copy all the relevant .mdx from each Fundamental lesson into lesson 2's new  < lessonInformationalModal > s
create four sub-directories in public/assets/lessons/2 to store the images for each of the four fundamentals, e.g. public/assets/lessons/2/cli_lesson; public/assets/lessons/2/install_npm
change the paths of the images in the .mdx to reflect the above change?

The edge case is also in Lesson 2. It's the "Longer Path...."  < lessonInformationalModal >

And it's a Fundamental about Decentralised Storage:

We could get away with the edge case for mVP, but the other four are going to be quite obvious.
I guess we could also just add a hyperlink and a little bit of text on what it is and why (IMO, a faster approach, but as far as learner flow goes, messy)

Thanks @Markkos89 for solving this Issue in your PR: https://github.com/Developer-DAO/academy-turbo/pull/114


cabinets are indestructible

these

fixed by #5141

also for clarification, it wasn't actually indestructible, it just had an insane dmg modifier, so anything with less than 30 brute dmg, would not be able to dmg it


Cannot use useUserSession when setting imports scan on false

When you enable
  imports: {
    scan: false,
  },

in your nuxt.config.ts file useUserSession stops working (not importing).
I also can't find a way to manually import it.
Other modules like useI18n keep working when doing this.
When removing scan: false, it works as intended.
Is it possible to support this feature?

Have you try to import from #imports ?
import { useUserSession } from '#imports'


Add Acronym exercise

Awesome, thanks @isaacvando!
I only have a few comments (see the code review):

have you run roc format on all the .roc files (including acronym-test.roc, unfortunately it looks like the generate_test.py script doesn't do it, I'll fix that)? I just run find . -name "*.roc" -exec roc format {} \; from the project root.
Please use {{ case["input"]["phrase"] | to_roc }} instead of "{{ case["input"]["phrase"] }}", as it will properly handle escaping (e.g., in the bob exercise, one of the test cases involves a string containing $(, which would fail without to_roc.
Please run bin/fetch-configlet followed by bin/configlet fmt -u to format the config.json file.

Also, I see that you've used result = ... and expect result == .... I didn't know it made a difference, but it looks like it does display the value of result when a test fails, so that's great, I'll update all the other tests! 👍
You've also included type annotations. One of the things that I like about Roc is the fact that these are totally optional, but I suppose it's best practice to include them for important / top-level functions (and when debugging)? Perhaps we could get that point across by not including type annotations in the stub code (i.e., Acronym.roc) but including type annotations in the solution (i.e., .meta/Example.roc), but only for top-level functions. What do you think?

The tweaks were fairly minor so I merged this PR and did the tweaks in PR #35
Thanks again!

Thanks for the comments and fixes @ageron!
The norm is to annotate top level definitions for readability and to improve error messages. I think at a minimum the stubs should be annotated so that it is clear to the user what types they are working with and to minimize the possibility of confusing error messages. I lean towards annotating top levels in the example solutions also, because that's usually what I do once I'm ready to polish and publish my code, but I think it's okay for there to be variation there. The example solutions seem like a better place to communicate that annotations are optional to me.

That being said, if we want the examples to be as idiomatic as possible, we should annotate top levels.

Thanks for your feedback, sounds good to me. I'll update the existing examples to add top-level annotations.


Image source binding not working

In my view, I tried to bind image source to a string and it didn't work, despite the exact same code works in a project of a friend of mine. Both of us tried to find the cause of it but we didn't find anything.
<!-- MainWindow.xaml -->
<Image Source="{Binding ImagePath}"/>

// MainWindowViewModel.cs
public string ImagePath => "/Assets/image.png";

Note that writing path directly into the view like below does work.
<!-- MainWindow.xaml -->
<Image Source="/Assets/image.png"/>

Also, I've tried to bind it by Bitmap (with a custom string to bitmap converter too) but couldn't find a way to load AvaloniaResource from code.
Everything was tried on multiple versions of Avalonia, nothing worked.

Type converters don't work for bindings. It's the common behavior across XAML frameworks.
You need to use a Converter for the binding manually.

I have tried but didn't find a way to load AvaloniaResource.
Additionally, binding Image Source to string did work for a friend of mine in another project, but we haven't been able to find why

Umm, I downloaded the friend's program and after I compiled it, the image binding didn't work. It did, though, with the exe compiled by the friend.

Can you attach reproducible sample?

Oh, and now when my friend compiled his own program, it doesn't work either

I'll try to do something quickly @FoggyFinder

Seems like it's not implemented yet:
#853
#2208

It did work when my friend compiled it, though. I've got a working sample and he didn't change its code, but it doesn't work anymore and it's not a public program

Here you can see that binding doesn't work

TestAvaloniaImageBinding.zip

There might be a mistake with it working. I think that version was made in WPF.
On Avalonia, it just doesn't work but additionally, I can't find a way to make it work using a custom converter. Any idea of how to do so?

var assets = AvaloniaLocator.Current.GetService<IAssetLoader>();
return new Bitmap(assets.Open(new Uri("avares://TestAvaloniaImageBinding/Assets/github-logo.png")));

seems to work. I'll try to post a working converter there in case anyone has a similar issue and then I'll close it

Note that Bitmap under the Avalonia.Media.Imaging namespace is used instead of Bitmap under System.Drawing


fix(lexer): wrong interpreter parsing

Here I found this strange code, and I think that this is the correct implementation.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add back unique icons

Added back the unique icons used for Research Duplication, Research Expertise, and Research Mastery in older versions of Thaumcraft.
Research Mastery now gives minor warp like in older versions of Thaumcraft.

I love this thank you!


Program gets stuck attempting to swap Subs

The following program gets stuck displaying True once the mouse is clicked instead of the expected 'True on mouse down, False on mouse up' behaviour.

module Main exposing (..)

import Html
import Html.App as App
import Mouse
import Debug exposing (log)

main =
    App.program
        { init = False ! []
        , view = Html.text << toString
        , update = \msg model -> msg ! []
        , subscriptions = subscriptions
        }

subscriptions : Bool -> Sub Bool
subscriptions isDown =
    if isDown then
        log "ups" <| Mouse.ups <| always False
    else
        log "downs" <| Mouse.downs <| always True

Interestingly enough if you change the False in the init to True it manages to go from True to False then get stuck on True again.

Issue https://github.com/elm-lang/html/issues/58 is the same, issue https://github.com/elm-lang/elm-compiler/issues/1426 is the same, issue https://github.com/elm-lang/core/issues/628 is the same, and issue https://github.com/elm-lang/animation-frame/issues/7 is the same.
My findings about the root cause on the javascript side, it appears to be caused by tasks/subs/process being killed 'while' they are in the workQueue.  My overall findings below from the mailing list and other issue:
As per the mailing list at:  https://groups.google.com/forum/#!topic/elm-discuss/JJaWcxKy6L4
This might be a bug in core or even the compiler who knows, but here it happened.
I am still trying to reduce it, but so far in my giant application if I use animation-frame then it randomly dies in Chrome.
Do note, I subscribe and unsubscribe fairly rapidely to AnimationFrame via code kind of like:
subscriptions model =
        Sub.batch
            [ if List.isEmpty model.onNextFrame then
                Sub.none
              else
                AnimationFrame.times HelpersMsg_Frame
            ]

So I am guessing that something is not being cleaned up or so in the right order maybe?  I really really do not want to keep it always subscribed when there are no updates that need to be done...
I tested it by removing the conditional subscription and instead always subscribing (ohcrapmylog) and I've not hit the issue yet.  I need to switch it back though as this constant polling is hurting the site performance...
Here is the overall message, lot of hairy Elm internals, do not know enough about it to simplify yet:
The message that contains the one that gets wiped is id: 38 as stated before, it is a "_Task_andThen" with a task of what will become id: 39.
When id: 38 gets processed it enqueues id: 39, at this time the cancel key on the task that becomes Process id: 39 is null, but walking back up the parent stack of id: 38 shows it calls the callback on id: 4 while creating the cancel key in the step function when if (ctor === '_Task_nativeBinding') {.
Traced through the entire id: 38 path, it ends up creating id: 39 when it calls Native_AnimationFrame native callback on rAF, which then ends up calling the callback given to requestAnimationFrame, which then calls callback(_elm_lang$core$Native_Scheduler.succeed(timeNow));, which then calls "_Task_succeed" to be called on id: 38, which then calls the callback on its 'stack' key, which ends up calling sendToSelf with the animation frame time value, and id: 38 gets called more times on the work loop because it ended up getting queued up a few times earlier, but these next ones do not do anything of importance since its stack is null (it early breaks).  Process id: 4 appears to get fed the message to queue up the task for the animationframe callback.
When id: 39 does work and there is no exception in a run it is filled with the animation frame callback succeed task and then message.
When id: 39 does not work, I.E. root is null during the 'work' call, root is not null and is assigned an object when id: 39 is initially created, and that object is a "_Task_andThen" that will do a "_Task_nativeBinding" to the animation frame "callback' function.
It gets cleared during the step of id: 4, which involves a "_Task_succeed", that then calls the callback on the stack, which is a "_Task_andThen", which then immediately gets called in the step loop again (did not exit as it was via the internal loop), which then process as a "_Task_andThen" this time, which then bumps on a "_Task_succeed", which calls the list 'Cons' operator (empty list and a tuple0) and gives the result back as a "_Task_succeed", which then gets called via the id: 4 loop to get wrapped up in a 'Just', sent to the animation frame native code that then packages up the time information into another "_Task_succeed", which then loops again and passes that value into the main application spawnLoop loop function and stuffs things into a ready to handle onMessage, then id: 4 loops again to handle the "_Task_andThen" that the loop put into it just now, which then stuffs the loop callback back onto itself and loops again to handle the "_Task_receive" for the onMessage callbacks (the id: 4 process at this point has 3 things in its mailbox), the first message is the animationframe callback, which ends up calling down to _elm_lang$animation_frame$AnimationFrame$onEffects of which is passed in is a subscription object that holds id: 39 (whoo found it!  ow...), which stuffs our id: 39 object into a return object on the request._0 key, which all gets bundled into a "_Task_succeed", and processed via the loop for id: 4 and passing that to the main loop callback again that stuffs a "_Task_receive" onto id: 4 (the elm compiler could really optimize a LOT of this, maybe translate elm to llvm, optimize it, then translate to javascript as a start, like holy heck..., hmm webassembly is not a bad idea for elm at all...), so then id: 4 handles the "_Task_andThen" which then puts on then handles the "_Task_receive", then it pops the second of the originally 3 messages on id: 4 and gives it to the callback that then calls onMessage with the animationframe time stuff again, which calls back into _elm_lang$animation_frame$AnimationFrame$onEffects again and OhHeyLook id: 39 Again (>.>), which stuffs it into the request._0 key again on the return object so we loop around id: 4 a couple more times again while a "_Task_receive" shuffles to the top yet again (really, elm compiler, optimization, maybe llvm to output to both javascript and webassembly for options...), and we receive the last message on the mailbox which is all the same stuff through _elm_lang$animation_frame$AnimationFrame$onEffects yet again except this last time instead of returning a "_Task_succeed" it instead goes down the other path where a kill function is called's callback for a native binding within the process of id: 39 (Oh hey there it is again!), which is then pushed on to be called so yet again id: 4 gets looped around again to handle a "_Task_andThen" that then handles the prior "_Task_nativeBinding" that builds the cancel function on the root via the callback function on that same root (which is the prior kill returned callback function that was on id: 39), this function does:
		function kill(process) {
			return nativeBinding(function (callback) {
				var root = process.root;
				if (root.ctor === '_Task_nativeBinding' && root.cancel) {
					root.cancel();
				}

				process.root = null;

				callback(succeed(_elm_lang$core$Native_Utils.Tuple0));
			});
		}

Where 'process' is the process with id: 39, so you see here the function (callback) function that was passed into a nativeBinding function (that returned the nativeBinding task message that is 'now' being processed) is being called, so first it does var root = process.root, so far so good, it then calls root.cancel if root.ctor === '_Task_nativeBinding', which it is not (it is a "_Task_andThen"), so it skips that if entirely and continues on down to process.root = null, and BOOM there id: 39 was just corrupted, so when id: 39 is run through later then its root being null causes it to die when it is trying to figure out what to do.
So yes, this is a bug, probably in AnimationFrame (maybe in core, I don't know).
And this hurts...  How do I work around this bug for the time being until it is fixed?
On Wednesday, August 3, 2016 at 12:28:47 PM UTC-6, OvermindDL1 wrote:
Sometime between when id: 39 and id: 40 is created during rawSpawn the root key in the object goes null.  Still trying to find what code is wiping it...
On Wednesday, August 3, 2016 at 12:21:18 PM UTC-6, OvermindDL1 wrote:
The task object with id: 39 does not have a null root at the time it is put into workQueue.  At the time it is put into the workQueue it is:  {callback : function(b), ctor: "_Task_andThen", task: {callback: function(callback), cancel: function(), ctor: "_Task_nativeBinding"}}
The root.task.callback function seems to have one interesting closure that has a key/value of navStart:1470247637381, and there is another link in the cancel to the process with id: 38 so it appears to be a continuation of that one.  I am not sure of the internal structure of Elm so I am not sure what Native Binding it is called, and I use no Native Bindings in my project (only what comes with Elm core libraries is what exists here at all).
A little further digging and I am seeing _elm_lang$animation_frame$Native_AnimationFrame in the stack, further digging makes it seem (although I am unsure) that the root.task.callback is the same function as defined at:  https://github.com/elm-lang/animation-frame/blob/master/src/Native/AnimationFrame.js#L13
I am not yet seeing how the root key on this "_Process" object is getting cleared yet before it has a chance to be processed, still tracing...
On Wednesday, August 3, 2016 at 11:59:23 AM UTC-6, OvermindDL1 wrote:
Debugged into it and caught the exception at the point to get the stack values:
numSteps = 403
process = Object {ctor: "_Process", id: 39, root: null, stack: null, mailbox: Array[0]}

So root is null, why would it be trying to access a null value without checking if null?
Any ideas how to work around this in this project so I can at least keep working in chrome?
On Wednesday, August 3, 2016 at 11:52:36 AM UTC-6, OvermindDL1 wrote:
I keep getting this exception thrown from inside Elm, so far only from Chrome Version 51.0.2704.103 m
elm.js:2417  Uncaught TypeError: Cannot read property 'ctor' of null

Where that line and the surrounding context is purely Elm generated code, and is:
// STEP PROCESSES  // Line 2411

function step(numSteps, process)
{
	while (numSteps < MAX_STEPS)
	{
		var ctor = process.root.ctor;  // Line 2417 -- This is the error:  Uncaught TypeError: Cannot read property 'ctor' of null

		if (ctor === '_Task_succeed')
		{
			while (process.stack && process.stack.ctor === '_Task_onError')
			{
				process.stack = process.stack.rest;
			}
			if (process.stack === null)

The same javascript seems to run fine in firefox, IE, and edge, this only seems to happen in Chrome and only 'sometimes'.  It seems to happen pretty quickly during loading and if it does not happen at the start then it does not seem to happen.  I've not been able to find code to whittle down that lets my app still do anything while still causing this error.
The 'step' function is being called from the 'work' function of (and with context):
javascript

		// WORK QUEUE

		var working = false;
		var workQueue = [];

		function enqueue(process) {
			workQueue.push(process);

			if (!working) {
				setTimeout(work, 0);
				working = true;
			}
		}

		function work() {
			var numSteps = 0;
			var process;
			while (numSteps < MAX_STEPS && (process = workQueue.shift())) {
				numSteps = step(numSteps, process); // This is the place in the callstack before step
			}
			if (!process) {
				working = false;
				return;
			}
			setTimeout(work, 0);
		}

Chrome is not reporting anything in the stack below work so this appears to be during the setTimeout callback set a few lines prior to work that calls work.
Any thoughts as to the cause?

Managed to reduce a program, it happens for me quite reliably in Chrome, just click On then Off a few times and you will eventually see
Main.elm:2417 Uncaught TypeError: Cannot read property 'ctor' of null
step @ Main.elm:2417
work @ Main.elm:2533

pop up into your javascript console fairly quickly and the entire Elm app will stop functioning, thus killing the page.  If you attach a debugger in chrome to the javascript and have it stop on unhandled exceptions then you will see exactly where.
The simplified code is (add a dependency on elm-lang/animation-frame as it supplies a wonderfully easy way to reproduce this):
port module Main exposing (..)

import AnimationFrame
import Html
import Html.App
import Html.Events

main =
  Html.App.program
    { init = init
    , view = view
    , update = update
    , subscriptions = subscriptions
    }

init = (0, Cmd.none)

type Msg
  = On
  | Off
  | Tick Float

update msg model =
  case msg of
    On     -> if model == 0 then (1, Cmd.none)       else (model, Cmd.none)
    Off    -> if model >= 1 then (0, Cmd.none)       else (model, Cmd.none)
    Tick t -> if model >= 1 then (model+1, Cmd.none) else (model, Cmd.none)

subscriptions model = if model >= 1 then AnimationFrame.times Tick else Sub.none

view model = Html.div []
  [ Html.text (toString model)
  , Html.button [Html.Events.onClick On]  [Html.text "On"]
  , Html.button [Html.Events.onClick Off] [Html.text "Off"]
  ]

https://github.com/elm-lang/core/commit/9320969bf47082b902d4511ef8a48a93612d7bf0 should have fixed this issue too.  It did for me.  Can anyone else check their issues too, such as @Ryan1729 ?

Better to follow in #628


Remove argparse in requirements

I suggest removing argparse from the requirements.txt since it is included in the standard library.
Acceptable ?

@koslambrou thanks for the suggestion. I've removed argparse and am now removing other requirements too. If I shift all those requirements just needed for Falcon server implementations - beautifulsoup4, falcon & gunicorn - to a new file requirements.server.txt then `requirements.txt shrinks to just:
jinja2
markdown
rdflib>=5.0.0
rdflib-jsonld>=0.5.0
requests

I can't remove requests since that's required by certain rdflib functions but that's being worked on by the RDFlib maintainers (me and others!!). If we can remove that, and fold rdflib-jsonld into rdflib within the next month or so, then the dependencies will shrink further to just:
jinja2
markdown
rdflib>=6.0.0

where rdflib>=6.0.0 contains rdflib-jsonld.

I've tidied up the requirements.txt and implemented requirements.server.txt and the Dockerfile builder's adding in the extra packages from there so requirments.txt is now just:
jinja2
markdown
rdflib>=5.0.0
rdflib-jsonld>=0.5.0
requests


Push to NPM

Any plans to push this to NPM?
Thanks!

+1

+1

Hi there, I've "forked" this project, and it's available on npm here: https://github.com/gamestdio/websocket.js
My implementation is way different, so maybe it's behaviour is not exactly the same.

This library is on npm: https://www.npmjs.com/package/reconnectingwebsocket

+1. This is on npm, but not the latest version.

+1, push latest release

@joewalnes, can you please push this library to npm because npm install ReconnectingWebSocket doesn't work.


Improved tts command and updated documentation

Files changed: ./src/cogs/fun.py, ./src/cogs/help.py, ./src/bot.py, ./docs/commands.md.
Contributing under hactoberfest 2022.

Done, please check!


WIP: Revert "Revert "fixes #133: same task runner for platform&render""

Reverts go-flutter-desktop/go-flutter#421

As this is an hotfix, I'm merging this into master.


Update maps and cleanup

Updated maps and unified naming
New woods map, updated other maps, renamed maps to have the same naming
Solves: #237 #238 #239
Note:
I opted to add suffixes to all maps because with the current naming, to add woods 3d I needed first to rename the current woods in woods-2d and only then add woods, the same can happen with interchange that would need to be renamed before adding the 3d version. This PR solves this at the root for all current and future maps.

lgtm, but we need to update stash bot to use [key]-2d for the map command

I think it's even safer to simply use the first map from the array of the object that matches the key, because e.g. factory is only 3d, and interchange is only 2d.

.deploy


IntrospectionQuery is causing huge memory consumption after the latest updates

Component(s)
router
Component version
0119c2d656674c07dde45372298a7b6ab625e70f
wgc version
0.58.5
controlplane version

router version
0119c2d656674c07dde45372298a7b6ab625e70f
What happened?
Description
After one of the recent Cosmo updates, there is an abnormal increase in memory consumption when calling IntrospectionQuery (e.g. in the Playground refresh button).
Our schema (config.json), from which we get this result, weighs 13.7M. On older versions of cosmo we didn't have this problem.
Occurs after executing err = t.loader.LoadGraphQLResponseData(ctx, response, t.resolvable) in resolve.go<EMAIL_ADDRESS>Steps to Reproduce

Prepare a huge scheme
Prepare a config from that schematic
Run the cosmo with this config
Press the refresh button in Playground

Expected Result
Consume the normal amount of memory for this request)
Actual Result
Brutal memory consumption)
https://github.com/user-attachments/assets/4793a6be-76a3-4647-91e3-667967081b5d
Environment information
Environment
OS: (e.g., "Ubuntu 20.04") macOS / Linux
Package Manager: npm
Compiler(if manually compiled): go version go1.22.3 darwin/arm64
Router configuration
version: "1"

# General router options
graph:
  name: "production"
  token: ""

log_level: "info"
listen_addr: "localhost:3002"
playground_enabled: true
introspection_enabled: true
json_log: true
shutdown_delay: 15s
grace_period: 20s
poll_interval: 10s
health_check_path: "/health"
readiness_check_path: "/health/ready"
liveness_check_path: "/health/live"
router_config_path: "config.json"

cors:
  allow_origins: ["*"]
  allow_methods:
    - HEAD
    - GET
    - POST
  allow_headers:
    - Origin
    - Content-Length
    - Content-Type
  allow_credentials: true
  max_age_minutes: 5m

# Config for custom modules
# See "https://cosmo-docs.wundergraph.com/router/custom-modules" for more information
modules:
  myModule:
    # Arbitrary values, unmarshalled by the module
    value: 1

Router execution config
No response
Log output
No response
Additional context
No response

Does the same behavior happen when you make a introspection query from e.g. curl while disabling brotli? We've got a suspicion that the brotli Middleware is responsible, which gets usually activated by browsers.

OK, 50MB –<EMAIL_ADDRESS>Memory running out, 10GB+ –<EMAIL_ADDRESS>Video of work using<EMAIL_ADDRESS>https://github.com/user-attachments/assets/7a052cea-6069-4c8a-9e08-b4b25eb1133a
I haven't figured out how to disable brotli on this version, hint? I couldn't find it in the doc. I can cut it in the code if you tell me where)

Could it be?
https://github.com/wundergraph/graphql-go-tools/pull/845/files

8d7f20a7f43c29a1a0e80510afb6e7c318fcd080 in cosmo increased memory consumption in this scenario

Just in case. That PR https://github.com/wundergraph/cosmo/pull/968 didn't solve the problem
Since it seems to be consuming memory in graphql-go-tools/v2

Hi, I tried<EMAIL_ADDRESS>the result is the same
Please note my recent posts
https://github.com/user-attachments/assets/26cd1c75-6b7c-4d78-ba00-88937fdd8665

Hi, thanks for the test. Could you attach your router config here or send me via<EMAIL_ADDRESS>Thank you!

Same on my side, 4gb has always be enough memory but since a few releases introspection has been failing and pods restarting:

The spikes timestamps match with introspection queries.

@flymedllva please send me your router config. https://cosmo-docs.wundergraph.com/cli/router/fetch

Hi @StarpTech, sent it to your email<EMAIL_ADDRESS>

I tried https://github.com/wundergraph/cosmo/pull/986, no problems on it, thanks!


Use of Object.assign disallows deep merge e.g. changing the arrow classNames only

This is a trivial issue but I'd rather not duplicate any default config externally.
Using Object.assign makes use of the defaults for arrow impossible if you want to customize.
Codepen test case
I don't think it is a big piece of code to add, I have used node-extend for this and it works well (and you don't need to add jquery)

BTW - this I ran into this because of a common SCSS lint rule:
SelectorFormat: Selector popper__arrow should be written in lowercase with hyphens
Perhaps a default class change to popper-arrow wouldn't hurt?

I'm flowing the BEM convention for the class names.
I think we should find a better polyfill which supports deep merging.

@rosskevin please may you try the object-deep-assign branch and let me know if it fixes the problem?

@FezVrasta this test case was updated with your branch and still doesn't work.

Ok I'm sure now it works :)
I've changed arrow.classNames with arrowClassNames so there's not an additional level of deepness and everything works fine.
All the "deep merge" functions I have found was buggy and very big.


No commands to delete locations

This is aggravated by the fact that location-put with no arguments will generate an ID and create a location. You can create a location with a random ID that you then can't remove, just by typing the name of the command.

Affects #109


ZMQ Client Library

Currently ZMQ functionality is tightly coupled to the sigfinder module. This functionality should be abstracted out into a separate library.

Closed by #664


workaround for IE model + clipping planes shader bug

Fixes https://github.com/AnalyticalGraphicsInc/cesium/issues/6575

@likangning93, thanks for the pull request! Maintainers, we have a signed CLA from @likangning93, so you can review this at any time.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Thanks @likangning93. I don't have any comments to add, the bug is fixed.


Problem with click and locale

I'm having a locale-related problem with Click (I think). Not sure how to remedy this, setting LANG to en_US.UTF-8 didn't seem to work.
I installed mgefinder using the conda instructions (install.sh)
I'm guessing there's something wierd about my environment, but I'm not sure where to start.
$ mgefinder --help
#### CHECKING DEPENDENCIES ####
Current version of snakemake: 3.13.3
Expected version of snakemake: 3.13.3
Current version of einverted: EMBOSS:<IP_ADDRESS>
Expected version of einverted: EMBOSS:<IP_ADDRESS>
Current version of bowtie2: 2.3.5
Expected version of bowtie2: 2.3.5
Current version of samtools: 1.9
Expected version of samtools: 1.9
Current version of cd-hit: 4.8.1
Expected version of cd-hit: 4.8.1
###############################
Traceback (most recent call last):
  File "/panfs/pan1.be-md.ncbi.nlm.nih.gov/gpipe/home/aprasad/mydata/PD-3134/miniconda3/envs/mgefinder/bin/mgefinder", line 8, in <module>
    sys.exit(cli())
  File "/panfs/pan1.be-md.ncbi.nlm.nih.gov/gpipe/home/aprasad/mydata/PD-3134/miniconda3/envs/mgefinder/lib/python3.6/site-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/panfs/pan1.be-md.ncbi.nlm.nih.gov/gpipe/home/aprasad/mydata/PD-3134/miniconda3/envs/mgefinder/lib/python3.6/site-packages/click/core.py", line 696, in main
    _verify_python3_env()
  File "/panfs/pan1.be-md.ncbi.nlm.nih.gov/gpipe/home/aprasad/mydata/PD-3134/miniconda3/envs/mgefinder/lib/python3.6/site-packages/click/_unicodefun.py", line 124, in _verify_python3_env
    ' mitigation steps.' + extra
RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Consult https://click.palletsprojects.com/en/7.x/python3/ for mitigation steps.

This system lists a couple of UTF-8 supporting locales that
you can pick from.  The following suitable locales were
discovered: aa_DJ.utf8, aa_ER.utf8, aa_ET.utf8, af_ZA.utf8, am_ET.utf8, an_ES.utf8, ar_AE.utf8, ar_BH.utf8, ar_DZ.utf8, ar_EG.utf8, ar_IN.utf8, ar_IQ.utf8, ar_JO.utf8, ar_KW.utf8, ar_LB.utf8, ar_LY.utf8, ar_MA.utf8, ar_OM.utf8, ar_QA.utf8, ar_SA.utf8, ar_SD.utf8, ar_SY.utf8, ar_TN.utf8, ar_YE.utf8, as_IN.utf8, ast_ES.utf8, ayc_PE.utf8, az_AZ.utf8, be_BY.utf8, bem_ZM.utf8, ber_DZ.utf8, ber_MA.utf8, bg_BG.utf8, bho_IN.utf8, bn_BD.utf8, bn_IN.utf8, bo_CN.utf8, bo_IN.utf8, br_FR.utf8, brx_IN.utf8, bs_BA.utf8, byn_ER.utf8, ca_AD.utf8, ca_ES.utf8, ca_FR.utf8, ca_IT.utf8, crh_UA.utf8, cs_CZ.utf8, csb_PL.utf8, cv_RU.utf8, cy_GB.utf8, da_DK.utf8, de_AT.utf8, de_BE.utf8, de_CH.utf8, de_DE.utf8, de_LU.utf8, doi_IN.utf8, dv_MV.utf8, dz_BT.utf8, el_CY.utf8, el_GR.utf8, en_AG.utf8, en_AU.utf8, en_BW.utf8, en_CA.utf8, en_DK.utf8, en_GB.utf8, en_HK.utf8, en_IE.utf8, en_IN.utf8, en_NG.utf8, en_NZ.utf8, en_PH.utf8, en_SG.utf8, en_US.utf8, en_ZA.utf8, en_ZM.utf8, en_ZW.utf8, es_AR.utf8, es_BO.utf8, es_CL.utf8, es_CO.utf8, es_CR.utf8, es_CU.utf8, es_DO.utf8, es_EC.utf8, es_ES.utf8, es_GT.utf8, es_HN.utf8, es_MX.utf8, es_NI.utf8, es_PA.utf8, es_PE.utf8, es_PR.utf8, es_PY.utf8, es_SV.utf8, es_US.utf8, es_UY.utf8, es_VE.utf8, et_EE.utf8, eu_ES.utf8, fa_IR.utf8, ff_SN.utf8, fi_FI.utf8, fil_PH.utf8, fo_FO.utf8, fr_BE.utf8, fr_CA.utf8, fr_CH.utf8, fr_FR.utf8, fr_LU.utf8, fur_IT.utf8, fy_DE.utf8, fy_NL.utf8, ga_IE.utf8, gd_GB.utf8, gez_ER.utf8, gez_ET.utf8, gl_ES.utf8, gu_IN.utf8, gv_GB.utf8, ha_NG.utf8, he_IL.utf8, hi_IN.utf8, hne_IN.utf8, hr_HR.utf8, hsb_DE.utf8, ht_HT.utf8, hu_HU.utf8, hy_AM.utf8, ia_FR.utf8, id_ID.utf8, ig_NG.utf8, ik_CA.utf8, is_IS.utf8, it_CH.utf8, it_IT.utf8, iu_CA.utf8, iw_IL.utf8, ja_JP.utf8, ka_GE.utf8, kk_KZ.utf8, kl_GL.utf8, km_KH.utf8, kn_IN.utf8, ko_KR.utf8, kok_IN.utf8, ks_IN.utf8, ku_TR.utf8, kw_GB.utf8, ky_KG.utf8, lb_LU.utf8, lg_UG.utf8, li_BE.utf8, li_NL.utf8, lij_IT.utf8, lo_LA.utf8, lt_LT.utf8, lv_LV.utf8, mag_IN.utf8, mai_IN.utf8, mg_MG.utf8, mhr_RU.utf8, mi_NZ.utf8, mk_MK.utf8, ml_IN.utf8, mn_MN.utf8, mni_IN.utf8, mr_IN.utf8, ms_MY.utf8, mt_MT.utf8, my_MM.utf8, nb_NO.utf8, nds_DE.utf8, nds_NL.utf8, ne_NP.utf8, nhn_MX.utf8, niu_NU.utf8, niu_NZ.utf8, nl_AW.utf8, nl_BE.utf8, nl_NL.utf8, nn_NO.utf8, nr_ZA.utf8, nso_ZA.utf8, oc_FR.utf8, om_ET.utf8, om_KE.utf8, or_IN.utf8, os_RU.utf8, pa_IN.utf8, pa_PK.utf8, pap_AN.utf8, pl_PL.utf8, ps_AF.utf8, pt_BR.utf8, pt_PT.utf8, ro_RO.utf8, ru_RU.utf8, ru_UA.utf8, rw_RW.utf8, sa_IN.utf8, sat_IN.utf8, sc_IT.utf8, sd_IN.utf8, se_NO.utf8, shs_CA.utf8, si_LK.utf8, sid_ET.utf8, sk_SK.utf8, sl_SI.utf8, so_DJ.utf8, so_ET.utf8, so_KE.utf8, so_SO.utf8, sq_AL.utf8, sq_MK.utf8, sr_ME.utf8, sr_RS.utf8, ss_ZA.utf8, st_ZA.utf8, sv_FI.utf8, sv_SE.utf8, sw_KE.utf8, sw_TZ.utf8, szl_PL.utf8, ta_IN.utf8, ta_LK.utf8, te_IN.utf8, tg_TJ.utf8, th_TH.utf8, ti_ER.utf8, ti_ET.utf8, tig_ER.utf8, tk_TM.utf8, tl_PH.utf8, tn_ZA.utf8, tr_CY.utf8, tr_TR.utf8, ts_ZA.utf8, tt_RU.utf8, ug_CN.utf8, uk_UA.utf8, unm_US.utf8, ur_IN.utf8, ur_PK.utf8, ve_ZA.utf8, vi_VN.utf8, wa_BE.utf8, wae_CH.utf8, wal_ET.utf8, wo_SN.utf8, xh_ZA.utf8, yi_US.utf8, yo_NG.utf8, yue_HK.utf8, zh_CN.utf8, zh_HK.utf8, zh_SG.utf8, zh_TW.utf8, zu_ZA.utf8

$ echo $LANG
en_US.UTF-8

Ok, I answered my own question. Fixed by setting LC_ALL to en_US.UTF-8:
export LC_ALL=en_US.UTF-8

Ok, I answered my own question. Fixed by setting LC_ALL to en_US.UTF-8:
export LC_ALL=en_US.UTF-8


After update to 1.0.16 Warning in all files WTF?

Line 1: Definition for rule 'jsx-a11y/href-no-hash' was not found jsx-a11y/href-no-hash
But at all i have this rule!
in my .eslintrc "jsx-a11y/href-no-hash": "off",

Can you fill the issue template please? It exists for a reason because we are not mind readers 😉
In particular, we need a project reproducing this.

in my .eslintrc

Not sure what you mean. CRA comes with its own linting configuration. It is not supported to customize it.

@gaearon node 8.8.1 npm 5.5.1 yarn 1.2.1  my package.json
"bootstrap": "^3.3.7",
"google-map-react": "^0.25.0",
"husky": "^0.14.3",
"moment": "^2.18.1",
"prop-types": "^15.6.0",
"react": "^16.0.0",
"react-addons-shallow-compare": "^15.6.0",
"react-animated-number": "^0.4.3",
"react-bootstrap": "^0.31.2",
"react-dates": "^15.0.0",
"react-dom": "^16.0.0",
"react-notification-system": "^0.2.15",
"react-notification-system-redux": "^1.2.0",
"react-number-easing": "^0.0.4",
"react-redux": "^5.0.6",
"react-router": "^4.2.0",
"react-router-dom": "^4.2.2",
"react-scripts": "1.0.16",
"react-select": "^1.0.0-rc.10",
"recharts": "^1.0.0-alpha.4",
"redux": "^3.7.2",
"redux-devtools-extension": "^2.13.2",
"redux-thunk": "^2.2.0",
"styled-components": "^2.1.2",
"whatwg-fetch": "^2.0.3"
},
"devDependencies": {
"babel-cli": "^6.26.0",
"babel-polyfill": "^6.26.0",
"babel-preset-env": "^1.6.0",
"eslint": "^4.5.0",
"eslint-config-airbnb": "^16.0.0",
"eslint-config-prettier": "^2.3.0",
"eslint-plugin-import": "^2.7.0",
"eslint-plugin-jsx-a11y": "^6.0.2",
"eslint-plugin-prettier": "^2.2.0",
"eslint-plugin-react": "^7.3.0",
"prettier": "^1.7.4"
rm -rf node_modules/ && yarn cache clean && yarn install && yarn start
after start i have this warnings in all files

if i use 1.0.14 all works!


Support for notes about clients

Setting in Web UI, multiline is supported

Note in the wg.conf

There is no note for this client, nothing is written

Finally no more notes in the name
Notes are only visible for admins and managers
You can search by notes

LGTM. Thank you for adding it.

Great work! Tested already.
It would be great if between DNS enabled and IP Allocation a note (or just the first line of the note) will be displayed on the "user square".

You can search by notes

Also noticed that search by notes is case sensitive, while search by other fields are not. I think it should be altered for convinience.


Connections and Saving Failures

Type: Bug
There are 2 issues with clicking on Connect in a query window.

No matter what I do the connection is not added to the Recent list.
Even though Trust Server Certificate is TRUE, when I try to choose a database I get the pop-up asking if I should Enable Trust Server Certificate.

I have seen issue #1 as both a reported bug and as resolved, but IT IS NOT RESOLVED. I couldn't find issue #2 anywhere.
Azure Data Studio version: azuredatastudio 1.49.1 (2f696aa95a13ccabd7e0a4431d1d759e3a7b8cfd, 2024-08-13T18:12:38.831Z)
OS version: Windows_NT x64 10.0.19045
Restricted Mode: No
Preview Features: Enabled
Modes:

System Info

Item
Value

CPUs
Intel(R) Xeon(R) CPU E3-1230 v5 @ 3.40GHz (8 x 3408)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.92GB (8.05GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (13)

Extension
Author (truncated)
Version

newdatabase
kev
1.0.0

admin-pack
Mic
0.0.2

admin-tool-ext-win
Mic
0.1.3

agent
Mic
0.49.0

import
Mic
1.6.1

profiler
Mic
0.14.0

query-history
Mic
0.5.3

schema-compare
Mic
1.21.0

sql-database-projects
Mic
1.4.3

schema-visualization
R0t
0.9.1

db-snapshot-creator
sea
0.1.0

simple-data-scripter
sea
0.1.6

vscodeintellicode
Vis
1.3.1

I get the same with version 1.50.0.
Version: 1.50.0 (user setup)
Commit: 49c73a84388731fec941dac8d938345ac16bd470
Date: 2024-11-17T22:41:05.327Z
VS Code: 1.82.0
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22631


HELP - Running outside of Docker

Hi There,
I am trying to get this app running on a Nginx server already on a Raspi,
The docker images aren't compatible for some reason as I keep getting exec format errors,
Therefore, I install all the python modules needed to run the app proxied through Nginx
However, every time I go to run the main.py script I get this error
sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) could not connect to server: Connection timed out
Is the server running on host "db" (<IP_ADDRESS>) and accepting
TCP/IP connections on port 5432?
I have no idea where this IP Address is coming from and it seems to  be mapped to the domain www.db.com
Is there a way I can change this, I suspect it is something to do with the metadata.py script?

Never mind, I ended up finding out it was a line of code in the model.py script,
I just had to fine tune a couple of other things as well in the uwsgi.ini file,
Now I'v got this bad boy up on my raspi!
Thanks again for the awesome project


Uncaught ReferenceError: browser is not defined

[Enter steps to reproduce below:]

...
...

Atom Version: 1.12.6
Electron Version: 1.3.9
System: "Fedora release
Thrown From: atom-webbrowser package, v2.1.4
Stack Trace
Uncaught ReferenceError: browser is not defined
At /home/motz/.atom/packages/atom-webbrowser/lib/toolbar-view.coffee:33

ReferenceError: browser is not defined
    at ToolbarView.module.exports.ToolbarView.initialize (/home/motz/.atom/packages/atom-webbrowser/lib/toolbar-view.coffee:33:36)
    at ToolbarView.View [as constructor] (/home/motz/.atom/packages/atom-webbrowser/node_modules/space-pen/lib/space-pen.js:184:25)
    at new ToolbarView (/home/motz/.atom/packages/atom-webbrowser/lib/toolbar-view.coffee:8:7)
    at new Toolbar (/home/motz/.atom/packages/atom-webbrowser/lib/toolbar.coffee:10:24)
    at atom-workspace.atom.commands.add.web-browser:toggle (/home/motz/.atom/packages/atom-webbrowser/lib/web-browser.coffee:34:25)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/usr/share/atom/resources/app.asar/src/command-registry.js:259:29)
    at /usr/share/atom/resources/app.asar/src/command-registry.js:3:59
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/usr/share/atom/resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:587:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/usr/share/atom/resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:382:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeyEvent (/usr/share/atom/resources/app.asar/src/window-event-handler.js:106:36)
    at HTMLDocument.<anonymous> (/usr/share/atom/resources/app.asar/src/window-event-handler.js:3:59)

Commands
     -3:43.8.0 core:save (atom-text-editor.editor.is-focused)
     -3:31.3.0 settings-view:open (atom-text-editor.editor.is-focused)
     -3:21 core:confirm (atom-text-editor.editor.mini.is-focused)
  5x -3:20.1.0 core:backspace (atom-text-editor.editor.mini.is-focused)
  2x -3:19.1.0 core:confirm (atom-text-editor.editor.mini.is-focused)
  3x -1:54.3.0 gpp-compiler:compile (atom-text-editor.editor.is-focused)
     -1:40.3.0 core:copy (atom-text-editor.editor.is-focused)
     -1:39 core:paste (atom-text-editor.editor.is-focused)
     -1:38.7.0 core:save (atom-text-editor.editor.is-focused)
  2x -1:37.5.0 gpp-compiler:compile (atom-text-editor.editor.is-focused)
     -1:09.8.0 tree-view:toggle-focus (atom-text-editor.editor.is-focused)
     -0:52.5.0 settings-view:open (atom-text-editor.editor.is-focused)
     -0:48.5.0 core:select-all (atom-text-editor.editor.mini.is-focused)
     -0:45.6.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -0:14.7.0 core:select-all (atom-text-editor#atom-webbrowser.homepage.editor.mini.is-focused)
     -0:00.1.0 web-browser:toggle (atom-text-editor#atom-webbrowser.homepage.editor.mini.is-focused)

Config
{
  "core": {
    "telemetryConsent": "limited"
  },
  "atom-webbrowser": {
    "homepage": "https://www.google.de"
  }
}

Installed Packages
# User
atom-webbrowser, v2.1.4 (active)
gpp-compiler, v3.0.7 (active)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.45.0 (inactive)
base16-tomorrow-dark-theme, v1.3.0 (inactive)
base16-tomorrow-light-theme, v1.3.0 (inactive)
one-dark-ui, v1.6.2 (active)
one-light-ui, v1.6.2 (inactive)
one-dark-syntax, v1.5.0 (active)
one-light-syntax, v1.5.0 (inactive)
solarized-dark-syntax, v1.0.5 (inactive)
solarized-light-syntax, v1.0.5 (inactive)
about, v1.7.0 (active)
archive-view, v0.62.0 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.13.1 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.4 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.42.0 (active)
bracket-matcher, v0.82.2 (active)
command-palette, v0.39.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.40.0 (active)
find-and-replace, v0.202.2 (active)
fuzzy-finder, v1.4.0 (active)
git-diff, v1.1.0 (active)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.2 (active)
image-view, v0.60.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.2 (inactive)
markdown-preview, v0.158.8 (active)
metrics, v1.1.2 (active)
notifications, v0.65.1 (active)
open-on-github, v1.2.1 (inactive)
package-generator, v1.0.1 (inactive)
settings-view, v0.243.1 (active)
snippets, v1.0.4 (active)
spell-check, v0.68.4 (active)
status-bar, v1.4.1 (active)
styleguide, v0.47.2 (active)
symbols-view, v0.113.1 (inactive)
tabs, v0.103.0 (active)
timecop, v0.33.2 (active)
tree-view, v0.210.0 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.35.1 (active)
whitespace, v0.35.0 (active)
wrap-guide, v0.38.2 (active)
language-c, v0.54.0 (active)
language-clojure, v0.22.1 (active)
language-coffee-script, v0.48.0 (active)
language-csharp, v0.13.0 (active)
language-css, v0.40.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.43.0 (active)
language-html, v0.47.1 (active)
language-hyperlink, v0.16.1 (active)
language-java, v0.24.0 (active)
language-javascript, v0.122.0 (active)
language-json, v0.18.3 (active)
language-less, v0.29.6 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.37.0 (active)
language-php, v0.37.3 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.1 (active)
language-ruby, v0.70.2 (active)
language-ruby-on-rails, v0.25.1 (active)
language-sass, v0.57.0 (active)
language-shellscript, v0.23.0 (active)
language-source, v0.9.0 (active)
language-sql, v0.25.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.29.1 (active)
language-toml, v0.18.1 (active)
language-xml, v0.34.12 (active)
language-yaml, v0.27.1 (active)

# Dev
No dev packages

also affecting me

The issue is mentioned here https://github.com/gstack/atom-browser-webview/issues/33


Howto set Footer text size

This is a really amazing tool, thanks for creating it!
I have been using this regularly, but have struggled with the template file when it comes to the slide footer
For the following footer, how would one set the text size?
leftFooterText: Left Text
middleFooterText: My presentation
rightFooterText: Right Text

Is there a way to also set the page number size?

Thanks for your kind words. I will investigate what we can do. (I'm assuming I didn't already provide metadata terms for these two - pseudofooter and page number text sizes.)
Question: Does it make any sense for the three pseudofooter sizes to be different?
(And I emphasise pseudo as md2pptx does not use the standard footer and page number fields. The reason for this is mainly to allow flexibility the standard ones don't allow. I'm also receptive to ideas for further flexibility in the pseudofooters.)

So I can confirm this function doesn't yet exist. So tagging as new function.

A single size metadata terms would be sufficient for all three footers and page number. I personally like the fact that the footer are separate from the standard ones.

My thinking is 1 for footers - which really ought to be the same size as each other (as you say) - and 1 for slide numbers.
How urgent is this @yamsu?

Take your time, i'm happy to wait.

Thank you. The code needs some repair right now - with enhancements that aren't yet ready. None of these changes have been pushed.
By the way, do you clone the repo or just download a release? (Affects how you might test the enhancements you need.)

Turns out the code has no regressions that I can see - even if my new features don't work well enough for me to advertise them.
Just pushed
footerFontSize: 12
and
`numbersFontSize: 24'
where the 12 and 24 values are floating point and you can obviously change them.
Will write up soon and hope to ship 4.1.1 with these in and documented.

Documented and released as v4.1.1.
Closing. Please reopen or, preferably, create another issue if you want this tweaked / extended.

Nice! Thank you


aten::view error

❓ Question
During conversion, it seems like I found an incomplete support of the torch.view function:
Error as follows:
at most one dimension may be inferred
The function it is trying to convert is this:
out.view(out.shape[0], -1, 4)

Can you provide more info ? maybe your model/example ? The info is insufficient. Where is this error coming from ? conversion phase from TRTorch or libtorch or from TensorRT libraries?

Can you provide more info ? maybe your model/example ? The info is insufficient. Where is this error coming from ? conversion phase from TRTorch or libtorch or from TensorRT libraries?

Very strange... I decided to start from the untraced model and retraced it from the same code before conversion and this problem disappeared. I had this problem when I loaded this model from a previously saved traced state. Now my issue is that the results from my converted model differ quite a bit from the original running in full fp32:
Time for total prediction pytorch = 0.1059262752532959
Time for total prediction TRTorch = 0.052992820739746094
sum of differences: tensor(767.9413, device='cuda:0')
max difference: tensor(0.0203, device='cuda:0')
Average difference percentage: 2.7372%

Very strange... I decided to start from the untraced model and retraced it from the same code before conversion and this problem disappeared. I had this problem when I loaded this model from a previously saved traced state. Now my issue is that the results from my converted model differ quite a bit from the original running in full fp32:
Time for total prediction pytorch = 0.1059262752532959
Time for total prediction TRTorch = 0.052992820739746094
sum of differences: tensor(767.9413, device='cuda:0')
max difference: tensor(0.0203, device='cuda:0')
Average difference percentage: 2.7372%

There still seem to be a problem in spite of the conversion having completed. The output dimensions are incorrect which makes me suspect that the view function conversion failed but it could also be something else.
The inference time improvement is also minimal (~20%) compared to using mix precision inference+JIT trace.
Time for total prediction pytorch JIT AMP = 0.06222057342529297
Time for total prediction TRTtorch = 0.05096912384033203
2nd output shape pytorch: ([1, 129024])
2nd output shape TRTorch: ([129024, 1])
Sum of difference: tensor(2005.3442, device='cuda:0')
Max difference: tensor(0.0545, device='cuda:0')

There still seem to be a problem in spite of the conversion having completed. The output dimensions are incorrect which makes me suspect that the view function conversion failed but it could also be something else.
The inference time improvement is also minimal (~20%) compared to using mix precision inference+JIT trace.
Time for total prediction pytorch JIT AMP = 0.06222057342529297
Time for total prediction TRTtorch = 0.05096912384033203
2nd output shape pytorch: ([1, 129024])
2nd output shape TRTorch: ([129024, 1])
Sum of difference: tensor(2005.3442, device='cuda:0')
Max difference: tensor(0.0545, device='cuda:0')


Feature: create a generator of strings matching context-free grammar

There are type of programs that accept data matching context-free grammars: compilers, parsers etc.
These programs can be easily tested using property-based approach with generator of strings matching context-free grammar accepted by program. There is such functionality exist in Hypothesis python module, see [1].
I found at least two Lua modules that generates parsers using PEG syntax, see [3] and [4].
It would be nice to create a generator that accepts grammar and produce a string matching this grammar.

https://hypothesis.readthedocs.io/en/latest/extras.html#hypothesis-lark
https://pypi.org/project/hypothesis-grammar/
https://github.com/andremm/lua-parser
https://github.com/vsbenas/parser-gen

LGen - the Lua Language Generator (LGen) is a sentence (test data) generator based on syntax description and which uses coverage criteria to restrict the set of generated sentences. This generator takes as input a grammar described in a notation based on Extended BNF (EBNF) and returns a set of sentences of the language corresponding to this grammar.

https://bitbucket.org/chentz/lgen/src/master/


Is there a way to install all these custom actions without going through the manual clicks on SourceTree?

Hi
I'm looking for adding the custom actions that can be installed in multiple machines.  I don't want each user to go through the steps of going to Options menu and adding each custom actions, is there a way to write bash script for this purpose?
OS: Windows 10
Regards,

Good idea! Let me see if there is a feasible method.

In MacOS, the configuration of actions is located in ~/Library/Application Support/SourceTree/actions.plist, but it can't be changed easily with the shell.
There should be a similar file in Windows, but I don't have one at hand.
You can make a PR if possible.

Found a C:\Users\[User Folder]\AppData\Local\Atlassian\SourceTree\customactions.xml that actually has all custom actions in the format below.
<?xml version="1.0" encoding="utf-8"?>
<ArrayOfCustomAction xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <CustomAction>

Prune Tags

    <Target>C:\Users\[User Folder]\Downloads\git prune.bat</Target>
    <OpenInSeparateWindow>false</OpenInSeparateWindow>
    <ShowFullOutput>true</ShowFullOutput>
    <IsSilent>false</IsSilent>
  </CustomAction>
  <CustomAction>

Git Tag - Fix

    <Target>\\EI-Data1\Users3\[User Folder]\My Documents\git tag fix.bat</Target>
    <Parameters>$SHA</Parameters>
    <OpenInSeparateWindow>true</OpenInSeparateWindow>
    <ShowFullOutput>true</ShowFullOutput>
    <IsSilent>false</IsSilent>
  </CustomAction>
</ArrayOfCustomAction>

It looks like on Windows, the configuration file can be easily modified using a scripting language( Javascript, Python, php, etc.)


Documentation: add diagrams from self-hosted document

Port from https://docs.google.com/document/d/1VNp4CMjPPHevh2_JQGMl-hpz9JSLq3s7HlI87CTjl-8/edit#

I was planning to create a "how it works" document containing the images from my kubecon presentation -- this goes over self-hosting the control plane & self-hosting etcd. Does that seem reasonable in lieu of adding these?

cc @lukemarsden

I opened an issue to track creating a "how it works section" in favor of adding these 3 images - with the plan being to use my existing kubecon slides: https://github.com/kubernetes-incubator/bootkube/issues/302