Error when using symlinked docs folder: Module parse failed: Assigning to rvalue

🐛 Bug Report
Tried to run the 'classic' template following the getting started steps https://v2.docusaurus.io/docs/installation
npx @docusaurus/init@next init my-website classic

Failed when running npm run start. Lots of errors. (only showing partial log)
c:\Users\karl\firkin-www>npm run start

><EMAIL_ADDRESS>start c:\Users\karl\firkin-www
> docusaurus start

Starting the development server...

× Client
  Compiled with some errors in 3.36s

i ｢wds｣: Project is running at http://localhost:3000/
i ｢wds｣: webpack output is served from /
i ｢wds｣: Content not from webpack is served from c:\Users\karl\firkin-www
i ｢wds｣: 404s will fallback to /index.html

c:/users/karlp/firkin-www/docs/doc1.md 1:2
Module parse failed: Assigning to rvalue (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> ---
| id: doc1
| title: Style Guide
 @ c:/users/karlp/firkin-www/.docusaurus/registry.js 1:3494-3536 1:3394-3471
<EMAIL_ADDRESS> @ c:/users/karlp/firkin-www/.docusaurus/routes.js
<EMAIL_ADDRESS> @ multi c:/users/karlp/firkin-www/node_modules/react-dev-utils/webpackHotDevClient.js c:/users/karlp/firkin-www/node_modules/@docusaurus/core/lib/client/clientEntry.jsc:/users/karlp/firkin-www/docs/doc2.md 1:2
Module parse failed: Assigning to rvalue (1:2)

Your Environment

Docusaurus version used: 2.0.0-alpha.61
Environment name and version: node 12.8.3
Operating system and version: Windows 10

I have no idea what's going on but it works for me.
Can someone reproduce this consistently?
Maybe it's specific to your env.
Can you try with yarn instead of npm?
Have you modified anything at all of the generated project?
Are you sure you are in the correct directory? I see you created my-website, yet the logs show you are in firkin-www

Hey @slorber
I just tried this on another machine (also Windows) and it worked fine. So you may be right - it might just be my env.
To answer your questions, though - I didn't modify anything in the generated project. And I was in the correct directory (the initial command using my-website was wrong).

Ok great to know.
Not sure what I can do about this issue, so I'm closing, but let's reopen it if other users are affected and we get more info.

Hi @slorber
I`m trying to use version feature with docusaurus v2 (2.0.0-alpha.61) and get the same error:

× Client
  Compiled with some errors in 150.24ms

./versioned_docs/version-1.1.0/doc1.md 1:2
Module parse failed: Assigning to rvalue (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> ---
| id: doc1
| title: Style Guide
 @ ./.docusaurus/registry.js 1:4301-4368 1:4145-4253
<EMAIL_ADDRESS> @ ./.docusaurus/routes.js
<EMAIL_ADDRESS> @ multi ./node_modules/react-dev-utils/webpackHotDevClient.js<EMAIL_ADDRESS>1:2
Module parse failed: Assigning to rvalue (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> ---
| id: doc2
| title: Document Number 2
 @ ./.docusaurus/registry.js 1:4746-4813 1:4590-4698
<EMAIL_ADDRESS> @ ./.docusaurus/routes.js
<EMAIL_ADDRESS> @ multi ./node_modules/react-dev-utils/webpackHotDevClient.js<EMAIL_ADDRESS>1:2
Module parse failed: Assigning to rvalue (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> ---
| id: doc3
| title: This is Document Number 3
 @ ./.docusaurus/registry.js 1:5373-5440 1:5218-5325
<EMAIL_ADDRESS> @ ./.docusaurus/routes.js
<EMAIL_ADDRESS> @ multi ./node_modules/react-dev-utils/webpackHotDevClient.js<EMAIL_ADDRESS>1:2
Module parse failed: Assigning to rvalue (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> ---
| id: mdx
| title: Powered by MDX
 @ ./.docusaurus/registry.js 1:5809-5875 1:5657-5762
<EMAIL_ADDRESS> @ ./.docusaurus/routes.js
<EMAIL_ADDRESS> @ multi ./node_modules/react-dev-utils/webpackHotDevClient.js<EMAIL_ADDRESS>

Hi @slorber
I`m trying to use version feature with docusaurus v2 (2.0.0-alpha.61) and get the same error:

× Client
  Compiled with some errors in 150.24ms

./versioned_docs/version-1.1.0/doc1.md 1:2
Module parse failed: Assigning to rvalue (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> ---
| id: doc1
| title: Style Guide
 @ ./.docusaurus/registry.js 1:4301-4368 1:4145-4253
<EMAIL_ADDRESS> @ ./.docusaurus/routes.js
<EMAIL_ADDRESS> @ multi ./node_modules/react-dev-utils/webpackHotDevClient.js<EMAIL_ADDRESS>1:2
Module parse failed: Assigning to rvalue (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> ---
| id: doc2
| title: Document Number 2
 @ ./.docusaurus/registry.js 1:4746-4813 1:4590-4698
<EMAIL_ADDRESS> @ ./.docusaurus/routes.js
<EMAIL_ADDRESS> @ multi ./node_modules/react-dev-utils/webpackHotDevClient.js<EMAIL_ADDRESS>1:2
Module parse failed: Assigning to rvalue (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> ---
| id: doc3
| title: This is Document Number 3
 @ ./.docusaurus/registry.js 1:5373-5440 1:5218-5325
<EMAIL_ADDRESS> @ ./.docusaurus/routes.js
<EMAIL_ADDRESS> @ multi ./node_modules/react-dev-utils/webpackHotDevClient.js<EMAIL_ADDRESS>1:2
Module parse failed: Assigning to rvalue (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> ---
| id: mdx
| title: Powered by MDX
 @ ./.docusaurus/registry.js 1:5809-5875 1:5657-5762
<EMAIL_ADDRESS> @ ./.docusaurus/routes.js
<EMAIL_ADDRESS> @ multi ./node_modules/react-dev-utils/webpackHotDevClient.js<EMAIL_ADDRESS>

Hi,
Can you give us more infos on your env?
Are you both on Windows?
Wonder if you use a fs path with spaces in it or something? That can lead to issues sometimes.

I'm running into the same issue, when trying to use files that a symlink in from another directory.  Are you aware of any issues with symlinks?

It almost seems that docusaurus isn't finding the files and compiling them from markdown into js files?  Or maybe webpack can't handle symlinks?  I don't have enough background to really say.

It may have something to do with this https://github.com/webpack/webpack/issues/1643

Yes! @CyborgMaster this is what fixed it for me.
For me, my user folder c:\users\karl is actually a symlink to c:\users\karlp. If I try run npm run start from the symlink folder it fails but it works from the actually one!
I assume what you're thinking is correct - that webpack doesn't understand symbolic links. Somehow some of the files are not being found.

Thanks for reporting this.
Do you think we can do anything about it?
Note we have this resolve.symlinks: true in config (https://webpack.js.org/configuration/resolve/#resolvesymlinks).
By using a local site plugin + configureWebpack you should be able to override any default setting we set, so maybe it's worth checking if you find a final config that works for your usecase?

Not sure how to fix this. I've tried creating a webpack.config.js locally and setting the config you mention, @slorber , but it has no effect. Not sure how to create a local site plugin as you suggest either.

@kewp we don't read any webpack.config.js file.
The doc to create a local plugin is very simple:
https://v2.docusaurus.io/docs/using-plugins#creating-plugins
https://v2.docusaurus.io/docs/lifecycle-apis#configurewebpackconfig-isserver-utils
I think something like that:
module.exports = function (context, options) {
  return {
    name: 'custom-docusaurus-plugin',
    configureWebpack(config, isServer, utils) {
      return {
        resolve {
          symlinks: false
        },
      };
    },
  };
};

Hi @slorber . Yup that worked too :)

@slorber, that worked for me too.  I added the plugin you provided in your comment and now the symlinked files work.
I'm obviously not understanding something here, but it feels completely backwards to me that in order to get docs that are symlinked in to work we have to set resolve symlinks: false in the webpack config.  But hey, it works.
Thanks for you help!  This may be super specific to our setup so I don't know if it belongs in the docusaurus docs or not, but it was certainly tricky to find.

Also saw this webpack setting and found it confusing, but as far as I understand it, true means webpack will try to "replace" the symlink by its real location, not that it will enable some kind of mode that works with symlinks.
I don't know either why in Docusaurus we have symlinks: true exactly, not sure we'll be able to know now

Another issue with this symlinks error: https://github.com/facebook/docusaurus/issues/3579
Maybe we should consider switching symlinks to false by default. Not sure about the impact of this, so we'd rather be prepared to revert if users report bugs after release

Set resolve.symlinks: false is works. But when I modify the docs, the local site does not auto refresh and display the new modified content.

I'm running into the same error now, with docusaurus 2.0.0-beta.0 and symlinks out to ../site/* for my docs, src and static folders.
The above workaround does not appear to work any longer.  Might that be due to the updates for v5.x?  Does anyone know of a workaround for the current docusaurus?

To clarify: the plugin workaround does work for npm run build and serving the static site, but does not work for npm run start.

Maybe worth trying updating the watchOptions.followSymlinks option mentioned by @BiosSun
You can edit the file locally. here and restart your server: node_modules/docusaurus/lib/commands/start.js

@slorber it does not seem to work, sadly.

FWIW I just had the exact same issue after upgrading to 2.0.0-beta.0.
Removing node_modules followed by a yarn install solved it for me.

I have the same problem and symlinks: false solve it, add this to docusaurus.config.js and you are ready to go on symlinked folders:
plugins: [
  function (context, options) {
    return {
      name: 'webpack-configuration-plugin',
      configureWebpack(config, isServer, utils) {
        return {
          resolve: {
            symlinks: false,
          }
        };
      }
    };
  },
],

Also HMR works ok.

yes, we can now pass plugins as inline config functions :)
I'm not sure to understand why we have symlink: true in our webpack config anymore, so I think we could just remove that and see if anyone complains. Just be aware that I may have to revert it if any significant bug is reported about that change.

FYI I coudn't find any reason to use symlink: true.
The code introducing this is very old and does not explain this setting (https://github.com/facebook/docusaurus/commit/2ab412e563e4aa7ac87d05edaa05ebbfb4c7d8d1)
Going to revert to false in https://github.com/facebook/docusaurus/pull/5126
Using a symlinked folder as source docs seems to work fine (in dev/watchmode + prod)
Using symlinks inside the regular docs folder does not really work, and probably require more work so that features such as auto-generated sidebars etc work as intended.
Do you all have the same use-case to create a single symlink for the root docs folder?

FYI I coudn't find any reason to use symlink: true.

I see it the same way, users should be able to use symlinked docs folder.

Do you all have the same use-case to create a single symlink for the root docs folder?

I'm going to use it this way, I hope that this was only one problem which I come across. I'm going to use it this way because I want to have documentation to be a part of the main project and create a new repository for the docusaurus.
So I will have two repos, main project eg. xyz and second repo xyz-github.io which will generate documentation with docusaurus and deploy to github.io. xyz-github.io will have symlinked docs folder to xyz/docs folder.

Going to revert to false in #5126

Nice thank you 🙏 For me it makes sense.

So I will have two repos, main project eg. xyz and second repo xyz-github.io which will generate documentation with docusaurus and deploy to github.io. xyz-github.io will have symlinked docs folder to xyz/docs folder.

That's very much like my use case as well.

great, we'll figure out later if using symlinks inside the docs root folder is necessary.
If you have this need please explain your usecase.
I've added a new docs plugin instance using a root symlink so that we keep this behavior working over time. CI builds fine on linux/windows: https://deploy-preview-5126--docusaurus-2.netlify.app/docs-tests

Unfortunately, I have to revert the change I made (https://github.com/facebook/docusaurus/pull/5164).
There is a bug in Webpack 5 caching and using resolve.symlinks: false lead to deploying a Docusaurus site with stale cache entries.
If you implement a Docusaurus plugin as part of a monorepo and change some UI code, your new deployment (dev + prod) may not see your changes. Not many sites will be affected by this in practice (theme components should be fine fine), but it's particularly painful for ourselves: Docusaurus PR Netlify deploy previews show stale UI components.
If you decide to stick to using webpack.resolve.symlinks = false in your site for symlinks reasons, and have some monorepo UI lib symlinked, I recommend to run docusaurus clear to be free of nasty side-effects.
Also, I'm not sure using symlinks: false is a good solution, and webpack contributors do not seem to agree it's a good idea to use false either.
I'd like to recommend another workaround to try: instead of using symlinks: false, you can try to resolve the symlink to the real location, directly in your config:
    [
      '@docusaurus/plugin-content-docs',
      {
        routeBasePath: 'docs',
        sidebarPath: 'sidebars.js',
        path: fs.realpathSync('docs-symlink'),
      },
    ],

Please let me know if this workaround works for your site.
We'll only try to apply symlinks: false again if some come up with a case where it does not work and we can't find any other solution (repros / linked repos appreciated)

Hello everyone

@slorber it does not seem to work, sadly.

Can confirm on this. With { symlink: false} HMR does not work. Tried using the { followsymlinks: true} option in devServer conf, but it does not work as intended. The app recompiles on changes but the browser does not refreshes the content.

If one has a docs multi-instance and wants to share a directory with partials between two docs instances, would the symlink approach work?

@leograba the canary now allows putting mdx docs anywhere (https://github.com/facebook/docusaurus/pull/5299) so you shouldn't need symlinks anymore: just import the mdx files where you want to use them.
However keep in mind the link resolution in those partials is "simpler", it doesn't resolve relative md file paths but only regular relative/abslute links. Also there's a TOC limitation (https://github.com/facebook/docusaurus/issues/3915)

@slorber thanks! I have tested it with the canary release 0.0.0-3900 and it worked well.
About the link resolution, I have previously noticed that that the "simpler" link resolution also affects referring to a different doc in a multi-docs setup, so I've been already using relative links. I'll keep in mind the limitations of relative links instead of relative file paths.
About the TOC, keeping an eye on (#3915) :)

Yes, only the docs plugin resolve relative md file paths currently and it's limited to the scope of a single instance. We need some additional infrastructure so that plugins can expose to each others a filePath => absolute url mapping. But anyway if 2 instances have different version schemes you'd rather avoid such links because it won't play well with versioning, as the versined docs would be in a totally different folders. In such case we'll probably need to support something like<EMAIL_ADDRESS>to make those links easier to version.

The Webpack 5 caching bug should be resolved in https://github.com/webpack/webpack/pull/14019
Using symlinks: false should be safe again in webpack 5.51.0


Can't perform a React state update on an unmounted component.

Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in a useEffect cleanup function.

Only happens at the first unmount, not sure why, but I'm basically using a templating system, which requires switching between 2 or more components as templates.

Hi @artpumpkin,
Can you share a reproducible sample?


Draggable debug window

I am working on this currently, I just wanted to add it as an issue because I forgot to do it earlier

This is now done


bats_print_failed_command: Include $output if available.

Checking $status right after a run seems to be a quite regular use case:
@test "run will fail" {
    run blahblah
    [[ "$status" -eq 0 ]]
}

With this change, the $output of run is included in case of failure, which makes debugging much easier:
 ✗ run will fail
   (in test file broken.bats, line 7)
     `[[ "$status" -eq 0 ]]' failed
     bats/libexec/bats-exec-test: line 58: blahblah: command not found

/cc @vieux @ehazlett

Yes!

LGTM

Nice!
On Monday, May 4, 2015, Victor Vieux<EMAIL_ADDRESS>wrote:

LGTM
—
Reply to this email directly or view it on GitHub
https://github.com/sstephenson/bats/pull/101#issuecomment-98928121.

:+1: Applied this today locally, looks cool.

Definitely I need this merged

Ping @sstephenson :)

:+1:

Bump @sstephenson

Anyone who wants to get feedback when a test fails should take a look at the discussion in #110 and the libraries that resulted from it.

This so needs to be merged and released. It's impossible to understand why the test failed on a build server otherwise. @sstephenson

@aluzzardi was there a reason to close this? Is this PR perhaps merged into some official fork (in the context of #150)?


2.4-fix-ans

Awaiting the org rename change in https://github.com/openshift/release/pull/24927 to be merged.
https://github.com/stolostron/backlog/issues/17130

/retest

/test pr-test-image-mirror

/test pr-image-mirror

/test pr-test-image-mirror

/test e2e-cluster

/test e2e-cluster

/test e2e-cluster

Part of https://github.com/stolostron/application-ui/pull/1404
Closing the issue


DAQ's GetErrorString() should remove trailing NULL characters in the error_string

Since we know this parameter is a string, we should remove trailing NULLs for this and all strings in the API.
AB#1560643

I'm planning to address this by making these functions use the IVI dance.


[BEAM-7954] Validate beam modules to disable guava imports from vendored gRPC

R: @lukecwik

The idea is good but there are likely other occurrences as well since the checkstyle in the java precommit is failing. Will wait on an update to fix other offending locations before merging.
Also, we may need to revert the checkstyle check in the future if a gRPC API ever requires its own guava type to be passed into it. For now it doesn't seem to be the case but it might be worthwhile to add a comment to this regard.

Oups my local regex did not work, fixing now. Yes I thought about the eventual case when guava versions won't be happy but I think is better to try to keep it constrained as much as possible. We'll see when it happens.

Run Portable_Python PreCommit


Add 'Wrap Input in SEQUENCE' to Parse ASN.1 hex string

This will parse extra tags concatenated to the first tag.
For example, the following ASN.1 encoded public key consists of multiple top-level tags:
300d06092a864886f70d010101050003818d0030818902818100d88280e8d619027d1f85183925a2652be1bfd405d3bce6363baaf04c6c5bb6e7aa3c734555b2f1bdea9742ed9a340a15d4a95cf54025ddd907c132b2756cc4cabba3fe56277143aa63f5303e9328e5faf1093bf3b74d4e39f75c495ab8c11dd3b28afe70309542cbfe2b518b5a3c3af9224f90b202a7539c4f34e7ab04b27b6f0203010001

Without the option:

With the option enabled:

Another solution would be to overload the substr function, capturing the last accessed offset by the library, and re-start parsing from that,
or to search if there is a 'length' function inside the library that can be used, and re-start parsing after that.


virtcontainers: wait until process exited before RemoveContainer

RemoveContainer is called right after SignalProcess(SIGKILL), the container
process might be still running and container Destroy() will fail, thus it's better
to wait on this process exited before to issue RemoveContainer.
Fixes: #690
Signed-off-by: fupan<EMAIL_ADDRESS>

The PR the comment is referring to is https://github.com/kata-containers/agent/pull/344 which has just landed.
It's a shame we can't add a test here for this change but it's possible as it can't be unit-tested.
lgtm

@lifupan @egernst This one is a bug fix, but unfortunately cannot be backported since we need the agent to support multiple WaitProcess() calls, and this is not part of the agent 1.1 or 1.2, right ?

@sboeuf Yes, you are right. And the fix is only required for containerd-shimv2 so stabe 1.1 and 1.2 do not need it either.


switch to OSDI-API-Token header for auth in person signup helper

made change or person signup helper.  TODO generalize for other operations

:+1: - minor note: we can remove the require('auth') part from line 6
not-blocking-this-PR-note: we should apply the same change to this

Hi there, I'm closing this PR because it was written against feature/clientRefactor, but the code that's "live" on osdi.ngpvan.com is in the develop branch.  However, I did port Josh's changes to the develop branch, tested them locally, and pushed just now, so they should be live shortly.
For the near-term future (next few weeks) PRs intended to affect osdi.ngpvan.com should be written against the develop branch.

PR updated as requested

ahh.  ok


Decode Error with unexpected "produced_mana" value

In the upcoming set "The Big Score," we are encountering a new card named "Fomori Value" with a produced_mana value of "[1]." This presents an issue for our decoder, as it encounters an unexpected enum value and was anticipating a produced_mana value of "[C]" instead.
API URI - https://api.scryfall.com/cards/a5433b98-4657-4bbe-9e72-d3c94c6aa8ef

Issue resolved by Scryfall


feat!: Migrate to new Client; Setup Testing Workflow with Voyage API Key; Rename model_name to model

Related Issues:
fixes: #18
fixes: #19
fixes: #20
Proposed Changes:
Migrate to voyageai.Client:

Refactor code to use the new voyageai.Client instead of the deprecated get_embedding and get_embeddings method of the global namespace.
Support for the new truncate parameter has been added.
Default embedding model has been changed to "voyage-2" from the deprecated "voyage-01".
The total number of tokens used are returned as part of the "total_tokens" in the metadata.
Bump voyageai to "0.17" and pin haystack-ai to "2.0.0b5"

Setup Testing Workflow with Voyage API Key

Added VOYAGE_API_KEY environment variable to testing workflow.

[Breaking Change] Rename model_name to model:

Both VoyageDocumentEmbedder and VoyageTextEmbedder now accept the model parameter instead of model_name.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

-1 of 70 (98.57%)  changed or added relevant lines in 4 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.1%) to 99.333%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/voyage_embedders/voyage_document_embedder.py
17
18
94.44%

Files with Coverage Reduction
New Missed Lines
%

src/voyage_embedders/voyage_document_embedder.py
1
97.14%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
236

Relevant Lines:
238

💛  - Coveralls


Enable 'native query' for the connector

As seen here:
https://learn.microsoft.com/en-us/power-query/native-query-sdk

Made changes, updated readme.md.
Submitted and accepted.


Add billing

Fixes #668.
Changes proposed in this pull request:

Added the billing icon
Added icon to StoryBook
Added Jest test for icon

Note: See this link for an example https://github.com/HospitalRun/components/pull/506/files. Also, the updates to the libraries came from the updates to the head components repo from HospitalRun.

This looks great! The one thing you may want to revert is the new npm module version changes unless they are intentional.

Hey Drew! I think this happened when I did "git pull." Comparing the package.json files of my branch and the remote master shows no conflicts. Thanks!


feat(recipes): export VariantDefinitions

Hi. I REALLY love vanilla-extract!
I wanted to use VariantDefinitions not being exported.
I can calculate it from the type of recipe but it's useful if exported.
Here's my use case.
// Button.css.ts
const size = {
  small: {
    height: "24px",
  },
  medium: {
    height: "32px",
  },
} as const satisfies VariantDefinitions;

export type Size = keyof typeof size;

export const button = recipe({
  base: {/* */},
  variants: {
    size
  }
})

// Button.tsx
import * as styles from './Button.css'

export const Button: React.FC<{ size: styles.Size }> = ({ size }) =>
  <button className={styles.button({ size })}>/* */</button>

Hey, would you be able to clarify the use case here? From looking at your example, would the RecipeVariants utility work for you?

Sorry, I didn't know that.
RecipeVariants can extract the variant type and that was one of my points, you know.
However, VariantDefinitions can also make it easier to separate variant definitions because the type checker can help you by using the satisfies operator.

As a general rule, we try to minimise the API footprint as it makes us less vulnerable to breaking changes in the future. In this case we would prefer not to export internal types unless there's a use case that cannot be achieved without it.

I understood your point! Thank you for your explanation.


Is it possible to list the additional properties that cause the additonalProperties error?

Currently if we have a schema like:
{
  type: "object"
  properties:{
    foo:{}
  },
  additionalProperties: false
}

And we validate against something like:
{
  foo: "foo",
  bar: "bar",
  baz: "baz"
}

We will get an error like:
{
  keyword: "additionalProperties"
  path: ""
}

This doesn't explain the failure very well though. You can't easily tell which property is additional. Ideally I would like an error result like:
{
  keyword: "additionalProperties"
  path: "",
  values: ["bar", "baz"]
}

or
[
{
  keyword: "additionalProperties"
  path: "",
  value: "bar"
},
{
  keyword: "additionalProperties"
  path: "",
  value: "baz"
}
]

Is this extra detail available?

Hey, thanks for the feedback, @DavidGrinberg. This request is implemented for v0.6.2. It works in the way given by your second example (every excessive key in its own error object), and is documented in the README


Feedback stephan

Dear Yifang,

your derivations of the baseline model look perfect!
the code for the baseline model works excellent!
the derivations for your extension make absolutely sense and look great!
-I just added the definition of the error term $\epsilon_t = x_t'A$
your code for the extension looks pretty nice!
-I proposed a solution to implement the error term structure within your loop and new representations of lambda and sigma

Looking forward to work with you on implementing the sampling step of nu and potentially the metropolis-hastings algorithm.
Best, Stephan

Hi Stephan
Thank you for your kinda review. Unfortunately, due to some technical conflict I haven't been able to merge your pull request to my master index.qmd file. I do manually adopt some of your advice:

Using N = rcol(Y)
Adding your definition of epsilon
Citation of Chan

About the omega/lambda issues, we both have our methods and I'd like to compare when we have time. Thank you again for going through my code and add what I have neglected. Looking forward to keep working with you in the future!
Best,
Yifang


hide some debug echos

echo outputs where visible in release builds, so I used when defined to hide them.

sry unrelated changes...

i will try again.


[FEAT] Implement heredoc without handle process

The Github Action works now, including a diff of the results.

I should not merge main branch into it, I will rebase and force update tomorrow

I merged the gh-actions branch into this branch already, that's why there are no changes from merging main.
If you prefer, you can revert the merge from main and it will look okay on the history graph, I think.

I already merged the gh-actions branch into main, need to rebase and force push this branch again


Fixes image deletion failing in subdirectory.

Fixes #1092
I was unable to test it on a sub-directory, since while setting up was getting an issue stating -
[Sun Nov 25 00:14:25.175814 2018] [core:error] [pid 30398] [client ::1:50186] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.

But I'm fairly certain that this will fix the issue. Tested on the PHP localhost server.
Signed-off-by: Abijeet<EMAIL_ADDRESS>

@Abijeet Good find, Have merged in now, Thought I'd put together a little patch release tonight. Thanks again!


issues: mongodb models not well configured

some test cases had issues with MongoDB models.
mainly type errors or geo-spatial errors.
resources.js had a validation error for the email
it could also use more enum values.
ex:- for categories, types, etc.

encountered an issue with the admin logs model. It lacks the necessary target types to log all admin actions.

I added the necessary fixes for the adminLogs.js model.
issues with the resources.js model are still not patched

I came across some issues with the notification.js and subscriptions.js models, too. check those too


npm install error

 npm install angular-redux/form --save

><EMAIL_ADDRESS>postinstall \node_modules\@angular-redux\form
> npm run build

><EMAIL_ADDRESS>prebuild \node_modules\@angular-redux\form
> npm run clean

><EMAIL_ADDRESS>clean \node_modules\@angular-redux\form
> rimraf dist

><EMAIL_ADDRESS>build \node_modules\@angular-redux\form
> ngc

Error at ......../node_modules/@angular-redux/form/source/state.ts:221:25: Type 'string' does not satisfy the constraint 'object'.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `ngc`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script 'ngc'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the @angular-redux/form package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     ngc
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs @angular-redux/form
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls @angular-redux/form
npm ERR! There is likely additional logging output above.

<EMAIL_ADDRESS>has been released with a number of toolchain fixes - can you try upgrading?


[Pylint] Update Version to 2.14.5

@l0lawrence is this to pick up the version with the "Const is not iterable" fix?

@l0lawrence is this to pick up the version with the "Const is not iterable" fix?

Yes! I am hoping that with this change it will prevent any breaking of CI on build of api stub gen - like anomalydetector


Migrate to v1.0-rc

What kind of changes does this PR include?

Changes to the docs site code

Description
Docs migration to v1.0-rc! 🥳
Note: The <TableOfContents> component is throwing console errors and it isn't being updated properly, this is a bug/regression introduced unrelated to the migration (only now discovered but was already happening in the docs). Thanks Hippo for the fix!

Whoops, after all this testing, we still found something - a strange issue on mobile Safari on iOS!
Algolia search doesn't work there. It works fine in astro dev --host, but stops working when doing astro build and astro preview --host. Same goes for the Netlify preview.

Issue is fixed! LGTM again! 😂

Thank you @hippotastic for all the amazing testing and bug fixing! Everyone, please sit in your seats because we are about to lift off!


Fix DisplayToastAsync throws exception even if not awaited

Description of Change
Added await to async page extensions, so the exceptions from them are thrown only if returned task is awaited.
This way those methods can be used in combination with "fire and forget" methods.
Bugs Fixed

Fixes #972

API Changes
None
Behavioral Changes
None
PR Checklist

[ ] Has tests (if omitted, state reason in description)
[x] Has samples (if omitted, state reason in description)
[x] Rebased on top of main at time of PR
[x] Changes adhere to coding standard

[ ] Updated documentation

@pictos Could you take a look at this please?

@brminnick can you review this one?

This doesn't change or improve the methods.
The two implementations are operationally the same, with returning Task (the existing implementation) being slightly more performant.

The two implementations are operationally the same

@brminnick They are not the same though.. Could you please take a look to the issue description and issue demo? If we use await exceptions from those are wrapped inside the task that they are returning. If we don't use await exceptions are thrown immediately (even if we don't await the result from DisplayXxx). This makes them unusable with "fire are forget" methods.

Your solution is two-fold:

Don't pass in null values
Wrap your call to the API in a try/catch block:

try
{
    MyPage.DisplayToastAsync("Some string").Forget();
}
catch(ArgumentNullException e)
{
    /// Handle exception
}

Don't pass in null values

I don't pass null values, but method still throws NullReferenceException (#959), and Forget cannot handle it, because method is not wrapped into single task.

@brminnick We also can resolve this issue like this: https://github.com/xamarin/XamarinCommunityToolkit/pull/973/commits/73f147ce89c6939c7515ba38fd49406217d0f4c1
This way argument validation exceptions will be thrown immediately, but exceptions from the method itself will be thrown only when returned task is awaited


Add webhook support

Hi!
While we're here, can we add post as json too?
Because new twitter events accepts post only as json .
Check here: https://developer.twitter.com/en/docs/direct-messages/sending-and-receiving/api-reference/new-event.html
Something like this maybe? https://github.com/NKudryavka/cowitter/commit/081cdc97a87d5ad6014acabb455b7a6145b62ac9
Thank you.

@mpyw any update?
Thank you!

@sololance Sorry, I don't feel like keep maintaining this project nowadays. Twitter has already started locking out 3rd party developers by strictly limiting API. Also I'm busy for my work at office. It's very hard for me keeping motivation.
Would you take over this project? I'll assign you as a collaborator

@mpyw sure, no problem I will maintain this repo because it's used in last project. Thank you ;)

Closed in favor of #19


PHP Parse Error – yii\base\ErrorException  syntax error, unexpected ';' (T_STRING)

I dont understand.
Can someone tell me how i can slove this problem?

That's error in your application. Update to master code and error page will give you more details.

but how update to master?

In your composer.json you can change Yii version to dev-master@dev and do composer update. Note that 2.0.6 will be released soon and when it happens it's better to switch back to ~2.0.0.

@AndruAlex there is a missing semicolon on line 42 $params['name'] = $this->username


Frontend With Framework - React Hooks

Description 📜
I will describe(documentation including code) different Hooks and their use.

Domain of Contribution 📊

[ ] Android Dev (Flutter, Java, Kotlin)
[ ] Backend Dev (Java, .NET, Python)
[ ] C/CPP
[ ] Competitive Programming
[ ] Cyber Security
[ ] DSA
[ ] Database
[ ] Datascience with Python
[ ] Datascience with R
[ ] Frontend Dev (HTML, CSS, JS)
[x] Frontend Dev (React, Angular, Vue)
[ ] Golang
[ ] Interview Prep
[ ] Java
[ ] JavaScript
[ ] MERN
[ ] Machine Learning
[ ] Open Source
[ ] Python
[ ] Rust
[ ] Statistics
[ ] UI/UX

/assign

I would love to contribute in React Hooks


No metrics to display

Please help me

config maps: argocd-cm

logs extension-metrics

+1

@bomtan2000 resolved? did you solve this problem?

@autokilla47
I haven't solved it yet

I am experiencing same issue, let me if you resolve it

For me it works with this fix: https://github.com/argoproj-labs/argocd-extension-metrics/pull/65/files

Please double check if the typo fix in the doc provided by @mcanevet address the issue

I'm facing same issue. I'm almost give-up do configure it. Did someone solve the problem?

i change file config maps: argocd-cm
Tabs metrics argocd

I already put this line. Yet, I have the following error
server time="2024-07-30T22:28:48Z" level=info msg="unauthorized extension request: unauthorized to invoke extension \"metrics\": rpc error: code = PermissionDenied desc = permission denied: extensions, invoke, metrics, sub: admin, iat: 2024-07-30T22:21:40Z"

What I am missing in my configs. I am using helm values
configs:
  cm:
    create: true
...
    extension.config: |-
      extensions:
        - name: metrics
          backend:
            services:
              - url: http://argocd-metrics-server:9003```
@bomtan2000

Just figured my issue. Permissions wasn't set correctly for metrics extension
Now I am facing different issue

I'm still receiving error trying to access metrics!!! I did all the tips and configs above, but didn`t solve it.

I have to point /extensions/metrics to metrics-server in my ingress configuration?

When I set enableTLS: false on metrics-server, I cant't even see GET connections on pod, and receive error 502 Bad Gateway on UI interface.
If I set enableTLS: true, I get GET logs connections on pod, and receive 404 Not Found on UI interface.

It seems when calling with uri /extensions/metrics is not working. When I call without that uri the metrics are ok.

+1

@r-pag have u enable extension enable: true on argocd-server param ?


Cannot insert a value for auto-increment primary key

I'm getting the error Cannot insert a value for auto-increment primary key (...) when I'm trying to write a row to a MySQL database table with the primary key field pre-defined. I've always been under the impression MySQL allows this by default. Contrary to MSSQL which requires to set IDENTITY_INSERT to ON first.
Is this a 'bug' in Propel, or have I gone full retard with my limited MySQL knowledge?

Calling the setter on an autoincremented PK will throw an exception as soon as you try to save the object. You can allow PK inserts on such columns by setting the allowPkInsert attribute to true in the <table> tag of the XML schema.

Reference: http://propelorm.org/documentation/reference/active-record.html

Ah, didn't know that, thanks!


Get-DbaFile Test - makes test universal

Looks good to me, tested against a couple of instances

omg appveyor is totally lying, im gonna have to do some more tests this is weird

@potatoqualitee : you create "dbatoolsci_getfile$random" ... search for that file mask only (rather than dbatoolsci), probably other tests leave something behind.

i did - in this case, it was returning some files instead of true/false. i guess it's evaluated differently for som reason? i see why but wished it'da failed locally


Bug: Setting a pending format at end of text before beginning a (Japanese) composition in Safari errors with "Lexical node does not exist in active editor state"

Lexical version:
Steps To Reproduce

Open the lexical playground in Safari (desktop)
Select all the text and delete it
Switch to Japanese input
Press a followed by Enter to commit あ
Press ⌘+B to set bold on the collapsed selection
Press a to begin a new composition

The current behavior
An error is produced and the candidate window shows up with an "a" and no candidate text in the editor.
In the current version of the playground which uses the production version of Lexical, the error is:
Error: Minified Lexical error #69...

Using a similar setup with a dev build of Lexical, the error is:
Error: Lexical node does not exist in active editor state. Avoid using the same node references between nested closures from editor.read/editor.update.

The expected behavior
It should not error.
This appears to come about from this block:
https://github.com/facebook/lexical/blob/82bb692f221b813d9702b3c8a83aebff0788f92a/packages/lexical/src/LexicalEvents.ts#L391-L419
It looks like the reference to node used inside the setTimeout is now stale.

This doesn't seem to be a safari-only bug, it can also be reproduced in chrome.

Thanks @LuciNyan!

I have the same problem with my English-language-based CustomNode in a RichTextEditor plugin format #3938 Error: Lexical node does not exist in active editor state. Avoid using the same node references between nested closures from editorState.read/editor.update.

I get the same error when I try to use MaxLengthPlugin https://github.com/facebook/lexical/blob/d4b192289d3714b34614b411d40e513d1f86f413/packages/lexical-playground/src/plugins/MaxLengthPlugin/index.tsx#L43.
Uncaught Error: Lexical node does not exist in active editor state. Avoid using the same node references between nested closures from editorState.read/editor.update.

@vlysytsia Did you figure out the solution yet?
I'm seeing the exact same issue on my end too.


Shader params that are arrays of unspecified length

You could previously declare OSL functions that have parameters that are arrays of unspecified length (like 'float foo[]'), but there was not an effective way to make shader parameters like that.
This patch, mostly the work of Max Liani from Animal Logic (with a little touch-up from LG), more or less fully enables shader parameters that are arrays of unspecified length. When an instance value is provided, which must itself be of definite length, it fixes the length of the shader parameter. Or, within a shader group, when an upstream shader's output parameter (of definite length) is connected to a downstream shader's parameter of unspecified length, it fixes the length. This provides some interesting new flexibility to write shaders that take arrays as parameters, without knowing the maximum length when you are writing or compiling the shader.
It's still a little dicey to alter one of these parameters for "re-rendering". Even if you mark it as "lockgeom=0", once the length becomes fixed, it's fixed, and you can't (without redeclaring the shader group and starting over) change its length again. So beware of situations like that.
Max - I hope you approve of my changes. The overall logic is still as you had it, I just fixed a couple edge cases to address some bugs that I noticed when I made the test cases, and added lots of comments.

LGTM


Firebird is updated to EFCore 5.0

https://twitter.com/cincura_net/status/1364886579353972740
https://www.nuget.org/packages/FirebirdSql.EntityFrameworkCore.Firebird/8.0.0-alpha3

@mariuz the nuget you're pointing at is an alpha prerelease... We should probably wait until there's a non-preview release.

@roji Ok then we can wait until then , all looks green in the testing area
https://github.com/FirebirdSQL/NETProvider/runs/1977984662

@cincuranet This change advertises 5.0 of your provider. We don't usually do this until the 5.0 version is released. If you wish to have this updated before then, then it probably should indicate that the 5.0 version is prerelease. What would you prefer?

I'm finishing few other pieces and will release final version in a week or two. Therefore I would prefer to wait and update when final version is out.

Closing this for now per @cincuranet's response.


StreamAllMessage and Groups create inconsistent results

When streaming Groups & StreamAllMessages at the same time sometimes stream all messages receives the welcome message first and writes it to the database. This means when groups receives the stream it think it already exists and doesn't stream the message.

From andrew

We could probably just:
Keep a list/keep the last streamed group
if we get the error that welcome id exists, silence the error and stream the group anyway if it's a newer group than the last known streamed group


ceph_bootstrap: Modify PyYAML prereq

It's currently not possible to run ceph-bootstrap on Tumbleweed because the setup.cfg requires a version < 5.1, but 5.3 is installed on Tumbleweed.
Signed-off-by: Volker Theile<EMAIL_ADDRESS>

@votdev when you hit this problem, were install ceph-bootstrap from package or from source?

Is this still valid?

Closing in favor of https://github.com/ceph/ceph-salt/pull/117


This adds handlers for the following:
block
blocks
dimensions
hatch
insert
layer
ltype
lwpolyline
spline
style
text
tables
Solves issues #3 #4 #5 and adds SVG Path and File generation #6.

There are quite a few jshint failures - there should be none.
$ npm test

Also, tabs for this library is 2 spaces

Ah sorry, I was not aware of using npm test.
I will try to fix that if I can get time to do so.

Cool. Or “grunt test”, but “npm test” should point to whichever build system you’re using
On Friday, 24 April 2015 at 10:06, Liam Mitchell wrote:

Ah sorry, I was not aware of using npm test.
I will try to fix that if I can get time to do so.
—
Reply to this email directly or view it on GitHub (https://github.com/bjnortier/dxf/pull/7#issuecomment-95844445).

Okay I managed to get some time to fix the jshint errors.
Sorry about that.

Thanks!

Also published to npm as 0.5.0


Enable to ability to apply filters to dashboards that limits the current result set

For example, have a Markdown tile that allows data entry. I have several tiles that are built around applications...Apdex by application table, Apdex by application graph, application count, etc. These tiles show data for all applications in my tenant. I can then enter in an application name into the Markdown tile, click apply and then PU removes all the applications in my tiles that don't meet my application filter. It could look something like this...
Before Filter:

After Filter:

Would this apply only to USQL data?

Think that and explorer data as well. If that’s too much, then we can start with USQL for now.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Lucas Hocker @.>
Sent: Wednesday, September 29, 2021 4:19:41 PM
To: dynatrace-oss/DynatraceDashboardPowerups @.>
Cc: Kelly, John @.>; Author @.>
Subject: Re: [dynatrace-oss/DynatraceDashboardPowerups] Enable to ability to apply filters to dashboards that limits the current result set (#103)
Would this apply only to USQL data?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdynatrace-oss%2FDynatraceDashboardPowerups%2Fissues%2F103%23issuecomment-930513043&data=04|01|john.kelly%40dynatrace.com|4795ddc0f38e48eb96a308d983867a1f|70ebe3a35b30435d9d677716d74ca190|1|0|637685435866713994|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=BCd9BEC36qfDOEoGRA5KzdtpyB0ufoIqcGOzMrTJHO4%3D&reserved=0, or unsubscribehttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFCTOM422OPO4LJDYKY234DUENYF3ANCNFSM5FAQKFGA&data=04|01|john.kelly%40dynatrace.com|4795ddc0f38e48eb96a308d983867a1f|70ebe3a35b30435d9d677716d74ca190|1|0|637685435866723939|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Aabo2IkH3Ect5nWk295OuDfSNDoywQLqNGOrH%2FoSQfI%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|john.kelly%40dynatrace.com|4795ddc0f38e48eb96a308d983867a1f|70ebe3a35b30435d9d677716d74ca190|1|0|637685435866733891|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=KbZimMoPWvTRTyYer%2FQauOg7ecZd6AViMo1gsuK3lAU%3D&reserved=0 or Androidhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|john.kelly%40dynatrace.com|4795ddc0f38e48eb96a308d983867a1f|70ebe3a35b30435d9d677716d74ca190|1|0|637685435866733891|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=2BQVp7cN2DPq6aSLPRzNhr%2BNiZE%2BzK1QXBQO1aJN%2Bik%3D&reserved=0.


filter_on_attributes raises KeyError on unknown attribute

If the request contains unknown attribute (not registered in any attribute map) the filter_on_attributes raises KeyError.
I do believe that the error should be expected and the attribute removed from the request.

Hi,
This was caught and raised in #441, and is now fixed in #442 . You can try to install from head or wait a little bit until the new release is tagged.


fix(abg): Make pair building pretty again

#1617
#1616
#1615
#1614
#1613
#1612
#1611
#1610
#1609
#1608
#1602
#1601
#1600
#1599
#1598
#1603
#1618  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

 Maybe you recall how we could reproduce the problems? If in doubt, we can leave the uglier code just in case.

Just almost :-)
And yes I tested with the exact case that failed previously.
Now there are not spaces around the to but mid-dots which tell the poet to put spaces there but not break on those.
If you replace the mid-dots with spaces again, the compile error is back.

Oh OK, so like a non-breaking space. Clever!


GEODE-7414: Added Client Hello extension

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[*] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[*] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[*] Is your initial contribution a single, squashed commit?

[*] Does gradlew build run cleanly?

[*] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

This is only solution with updated config parameter. Start working on Jens proposal.

Idea is that ssl-server-name-extension will contain generic string value which will be passed as Server Name extension in Client Hello message.  Could you clarify your idea. What will be content of ssl-parameter-extension parameter?

If the user wishes to manipulate SSLParameters (say in order to add their own SNI value) they would need to implement an interface something like:
public interface SSLParameterExtension {
  SSLParameter modify(SSLParameter, SSLConfig);
}

On starting Geode, they would provide the following parameter:
ssl-parameter-extension=com.example.ssl.MySSLParams.class

When the SSLConfig class is created it would also create (and hold a reference to) an instance of this class. At the point where SSLParameters need to be adjusted, this class' modify method could be called in order to perform whatever changes the user wants.
Depending on your particular use case you may need to also have the interface provide an init() method with whatever parameters are necessary for modify to do what you want - perhaps Cache or DistributionConfig - something fairly general so that additional use cases would likely also be satisfied in the future.


Just a thought

Great work, we love the idea.
Just a thought...
On the 'DEMO' page for this H5P widget on the H5P.com site, ow about putting it into 'Design mode' so that we can try out the demo during the other 11 months of the year...
https://h5p.org/content-types/advent-calendar
Nick

@SirClickALot Great idea! Unfortunately, that's out of my control. I am not part of the H5P core team and didn't create that demo content, so you'd have to contact them.

I will do just that!
On Thu, 17 Jun 2021 at 19:55, Oliver Tacke @.***> wrote:

@SirClickALot https://github.com/SirClickALot Great idea!
Unfortunately, that's out of my control. I am not part of the H5P core team
and didn't create that demo content, so you'd have to contact them.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/otacke/h5p-advent-calendar/issues/7#issuecomment-863486230,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJCU6ISBF7TAMMTOVFEOKTTTJAIZANCNFSM464HSJOQ
.

--
http://sirclickalot.co.uk


Optional checkbox style

When doing a checkbox, the toggle style widget from Semantic UI is used (the element has a toggle class). I think it is quite a presumption, using that style as the default – please consider changing it.
In the meantime, how can I render the form with a normal style checkbox? Will I have to hack it via a rendered hook?

To answer my last question, I think the best way is with the template-extension package. All helpers and events are inherited – it works like this:
<template name="myAtCheckboxInput">

      <input type="{{type}}" id="at-field-{{_id}}" name="at-field-{{_id}}" {{disabled}}>
      {{displayName}}

</template>

Template.myAtCheckboxInput.replaces("atCheckboxInput");

Yeah, that's the quicker solution...
In principle it wouldn't be difficult to add some other configuration options to select the checkbox style...
...but this would be hard to work for all availble front-end.
@meteor-useraccounts/semantic-ui, what do you think?
Should we change the default style to the normal checkbox?
We might also think about adding front-end-specific options, but I'd keep this reasoning for the v2.0 milestone.

It would be nice to have a property for addField – like custom: – which could be an object that is passed on to the templates.
Right now I'm looking into getting extra options that I set on my fields into the templates. For instance, I would like to be able to tell the template to put a divider before this or that field or to make a field 50 % width.

How would you like the whole thing to be?
...for the divider I think we could make it to add a special field type divider.
Feel free to make a PR about this, I'll accept it without concerns...
for the width, and in general for the layout, it might be trickier to achieve.
But, again, we can discuss this and see if there's a way to put it in a simple way adding another few configuration options.

Before going any further, I wonder whether there are any bad implications of having an options (or similarly named) property that is passed on to the templates untouched?
The names of the various options, as long as they only relate to layout and such, might be chosen freely by different UIs – including custom options for when a developer is using template overrides, e.g. with the template-extension package.
Something like a divider consists either of additional markup (like an
) or a special class – it should be up to the UI of choice.
(P.S. Should we move this discussion to the core repo?)

Yeah, I think it is better to continue on the core repo.
P.S. I'm not following what you mean with options. Some additional classes to be added to the form elements?
At the moment all the templates for the input fields, for example, are defined here.
The separator might be simply another templated shaped as needed for each framework...


GUI is white bar

After a forced update, the GUI appears as an empty white bar for one of my characters.  Its working fine for my other characters.  Removing and reinstalling the GUI doesn't help.  Here's how it appears when installed:

Here's how it appears when removed (but only after I close and reopen the mudlet window):

And reinstalled using the gmcp gui command:

I have to admit, that is certainly a new one. 🤔
I am noticing the characters being cut off for the time and devotion, though. Do you have the HDPI fix applied here?

Also, when you say it's only doing this on one character, are other characters also on 4.1.0?

They are all on mudlet 4.18.5.  Deleting the profile and creating a new one (copied from another profile) fixed the problem.

Sorry, I was referring to the version of the GUI (4.1.0). Are other profiles also on this version and they are not having the problem?

Got it a moment after posting.  All are using GUI 4.1.0.   Mudlet updated to 4.18.5 when I first connected a profile.  Each time I connect another profile it forces an updated to GUI 4.1.0 (unless the GUI is already updated).

Here's how it looks when the GUI updates.


Terminus TTF Font not rendering properly at certain sizes

Windows Terminal version
1.16.2523.0
Windows build number
10.0.19044.1826
Other Software
Terminus TTF font installed from https://files.ax86.net/terminus-ttf/
WSL, running Ubuntu 20.04.1 LTS, SSHing into an Arch Linux machine
Steps to reproduce
In the Font configuration menu, select "Terminus (TTF) for Windows"
Select a font size that doesn't correspond to a native bitmap size (eg. 14 pt)
Expected Behavior
Terminus TTF Font renders as it does at a size corresponding to a native bitmap size
See example from Windows Terminal 1.14.2281.0

Actual Behavior
Font renders with visible artifacting

@fizz125 the latest terminal release has the AtlasEngine enabled by default. If you turn if off Terminus will look better.
Size 14 with AtlasEngine on:

and with AtlasEngine off:

I'm noticing similarly weird rendering with CaskaydiaCove Nerd Font.
New engine:

Old engine:

The old engine makes the letters look rounder, fuller.

@elsaco Thanks for the comparison!
The old text renderer rounds the font size to match the column width in pixel which appears to just so happened to have worked with Terminus TTF. The new text renderer doesn't do that anymore - if you specify 14pt you'll get exactly 14pt. But Terminus TTF doesn't support 14pt. It only supports 13.5pt.
As such the solution to me seems like we should simply allow users to specify fractional font sizes. To test this idea I ran AtlasEngine with Terminus TTF at 13pt and 100% display scale. Then I replaced the requestedSize.Y with the fractional font size 13.5f here:
https://github.com/microsoft/terminal/blob/e2b2d9b92cf75d7841c80b222be9100eabe093ac/src/renderer/atlas/AtlasEngine.api.cpp#L617-L618
Et voilà (Old = Windows Terminal 1.16, New = patched AtlasEngine)!

@jedieaston I'm not convinced that the old version is better (Old = Windows Terminal 1.15, New = 1.16):

@elsaco Sure, that's the obvious workaround. But since this behavior isn't the same in the old engine, I wasn't sure if this was a regression or not.
@lhecker The documentation for the TTF font calls out that there may be issues with using the font at sizes for which there aren't bitmaps available, so if the answer is "Don't use Terminus TTF at non-bitmap-available sizes" then that's fine with me and this bug can be closed. But I wanted to make sure it wasn't a regression or an issue with the new engine
Thanks!

FWIW #6678 does have a lot of traction, so if it's "trivial" to just fix that, then maybe we should.

I wasn't sure if this was a regression or not.

I personally would consider it a regression, because even if it just randomly happened to have worked before, it definitely doesn't work now. I'm currently finishing a PR that will close #6678. Additionally it'll also fix some other issues in respect to your issue which will then definitely remove those gaps and draw pixel-perfect bitmap line drawings.

@jedieaston I'm not convinced that the old version is better (Old = Windows Terminal 1.15, New = 1.16):

Yeah, I just started looking into it because it was different. My eyes have adjusted now though, thanks for looking into it!

An upcoming version of Windows Terminal Preview will break the rendering for Terminus again. Instead you need to add a "cellHeight" override. Something like this for instance:
{
    "profiles": {
        "defaults": {
            "font": {
                "face": "Terminus (TTF) for Windows",
                "size": 10,
                "cellHeight": "14px"
            }
        }
    }
}


Adding Getting started client overview for Java

@kovrus You're now the JDBC driver owner!
This is a very quick overview page for the 'Getting Started' area of the documentation, it's just meant to cover getting the client and connecting to a cluster.
I struggled to get the current instructions for the driver to work, but I'm not sure if this was due to my own Java ignorance or if there is something wrong with the driver. Could you double check that these steps work for you and let me know if there any other things you want changed?

Merging elsewhere.


[1.12.2] No CraftTweaker integration

Hey!
When I try to make CraftTweaker scripts for NuclearCraft machines, I get the error message "nuclearcraft is not a module" - Is it not yet implemented in this version? I used the syntax from the CraftTweaker doc in the root of this git.
Minecraft 1.12.2
Forge 1.12.2 - <IP_ADDRESS>6
NuclearCraft-2.5a--1.12.2

Turns out that there was some extra code necessary to register the recipe addition and removal methods which I was not aware of - this has been fixed by TheGuyRunningSouth in a pull request :)

Cool, thanks the both of you :D


Add a mail catcher app

Purpose
In non-production environments, we don't want  to send real emails but we want to easily consult the emails sent to anyone.
Proposal
The solution for this is to use a mail catcher. There are several solutions available and we chose https://github.com/sj26/mailcatcher because it is easy, good enough and distributed as a Docker image.

[x] Add a separate mailcatcher app not subject to blue/green deployments
[x] Configure edxapp to send its emails to mailcatcher

@jmaupetit not weird: I forgot to add it to the list of jobs...

I should have seen this... well, know it works! :tada:


merge from konsum-frontend-svelte

.github/workflows/codeql_analysis.yml

chore: add<EMAIL_ADDRESS>(jobs.analyze.steps.uses)

.github/workflows/browser_ci.yml

chore: add<EMAIL_ADDRESS>(jobs.test.steps.uses)
chore: add<EMAIL_ADDRESS>(jobs.release.steps.uses)

:tada: This PR is included in version 1.31.14 :tada:
The release is available on:

v1.31.14
npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


add new params and other fixes

add new param ProfileMatch, update the way how we get new SDK minor verison

Branch was renamed


Wrong axis label for equipment "Kinds" plot

X-Axis is labeled "Year" instead of "Kind". See #201

You didn't have to create both a bug for the pull request. The pull request alone is also just fine. Thanks for the contribution!


Add apostrophe

Let's look at how momentum accelerates convergence with a concrete example.
You mean "Let us" not "Allows".

Thank you.


Update API to accept date and time parameters

TL;DR
Added support for departure/arrival time selection in trip planning
What changed?

Extended the trip planning API to support departure and arrival time preferences
Added new parameters for date (YYYYMMDD) and time (HHMM) in the trip planning service
Introduced a DepArr enum to handle departure/arrival preferences
Added utility functions in DateTimeSelectionItem to format date and time
Updated TimeTableViewModel to incorporate user-selected date/time preferences

How to test?

Set a departure or arrival time in the date/time selector
Plan a trip between two stops
Verify that the returned journeys respect the selected time preference
Test both departure and arrival scenarios
Verify date/time formatting matches the required format (YYYYMMDD for date, HHMM for time)

Why make this change?
To provide users with more control over their journey planning by allowing them to specify whether they want to arrive by or depart at a specific time, rather than only showing current departure times.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#402  👈 (View in Graphite)
#401
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Nov 30, 12:37 AM EST: A user merged this pull request with Graphite.


'Local Development' part of the README file needs to be modified.

Describe the bug
When I followed the steps of the "Local Development" part of README file, I got an error like below:

That's because when I did yarn build-dev, the dist directory was incomplete.

And there was another warning like this:

But when I followed the 'Getting set up' part of 'CONTRIBUTING.md' file, everything was okay.

To Reproduce
Steps to reproduce the behavior:

Clone the project by "git clone".
yarn install
yarn build-dev
yarn start

Expected behavior
So, I recommend to modify the 'Local Development' part of the 'README file' like 'Getting set up' part of 'CONTRIBUTING.md' file,
or rewrite simply like "Please refer to 'CONTRIBUTING.md' file."
Desktop (please complete the following information):

OS: Windows 10
Browser: Chrome

@DigitalBard (cc. @martijnrusschen )
It looks like the PRs have already been merged, are there any other issues?


Fix typos

Found via typos --format brief

Quite a few.. awesome!

:partying_face: :partying_face: :partying_face: :partying_face: :partying_face:


Document how Hexatomic is modularized

E.g., when to create a new Eclipse plugin (more general software engineering, SOC, etc.), when to create a new Eclipse feature, e.g., every editor/view gets its own feature (apart from the one in #40).

This should include a discussion of terminology, e.g., bundles vs plugins vs modules, etc.


Integrate slither and mythril

https://github.com/trailofbits/slither
https://github.com/ConsenSys/mythril-classic
Should be relatively straightforward to call both of these from Brownie when running tests.

Hey man! I'm Dominik from the ConsenSys Diligence team. I do core development on Mythril and MythX (a SaaS that runs tons of security analysis services in the backend). Just today I actually published a stable version of PythX. I tried to make it stupidly simple for devs to integrate the MythX API.
I'd actually love to help build a plugin for Brownie that allows the user to analyze their code for vulnerabilities (something like brownie analyze), or a standalone tool. Hit me up at<EMAIL_ADDRESS>if you wanna have a chat about it. Maybe we can push the Python ecosystem in Ethereum a bit more if we combine efforts! :rocket:


Enhancement: Remove database streaming when extracting table schema.

Reported by Michael Mortensen, RepoDb is doing multiple round-trips Opening-Closing of the database connection, that leads the application to crash, when connecting to Azure.
This is an already known behavior by the author, but have to revisits the implementation. The fix is simple as removing the "yield" keyword in the  DbHelper.GetFields() method.

FYI: @gimlichael

Fixed applied in the master branch. The fix will be available in builds and releases > v1.9.8.

Will be available at >= v1.9.9-beta1. Closing this ticket now.


Support for generators

This adds support for mix-like generators.

[x] Create spin configuration file after generating the template
[x] List available generators
[x] Generate new files for generators

The first implementation is done. There is still a bit of work needed, especially for argument handling, but I will revisit later when I create more advanced generators.


[Storage] Fix Queue account SAS generation with latest service version

In a previous change the value of X_MS_VERSION was updated to use the latest supported service version rather than the version from the generated code (this was done to reflect what our clients do by default). This also updated the version used for SAS generation by default and therefore broke account SAS generation due to the not including the recent change to account SAS generation that only affects later service versions.
This change adds that required change to SAS generation as well as updates our version tests to use the X_MS_VERSION constant.

API change check for azure-storage-queue
API changes are not detected in this pull request for azure-storage-queue


Proxy coonection

Hi,
When I tried connect to one of the AMQP with the proxy it doesn't work. When I checked wire shark it's not really connecting via the proxy. It would be great if this could be fixed.
I get below error and its connecting directly without proxy
params = {"http_proxy": {"proxy_hostname": "http://<IP_ADDRESS>", "proxy_port": 9000}}
ServiceBusClient("ServiceBusNamespace", token_credential,  **params)
Please confirm target hostname exists: b'elexon-iris.servicebus.windows.net'
Thanks
Jay

Thank you for the feedback @jay-iyengar . We will investigate and get back to you asap.

Hi @jay-iyengar, could you share what version of the package you are using, as well as logs if you have them? Was this working for you previously?

Hi,
Apologies, I was using the this version azure-servicebus==7.8.0, just now upgraded to azure-servicebus==7.12.2 and thats seems to be working fine.
Thanks for looking into it.
Kind Regards
Jay

Thank you for confirming @jay-iyengar


Mysql2::Error: Can't connect to local MySQL server through socket '/tmp/mysql.sock' error occurred on CircleCI

This gem works fine on local environment, thanks.
But, when I run rake db:create db:migrate on CircleCI, it failed to connect to local MySQL server...
I couldn't resolve this error.
The error log is below:
CircleCI logs `rake db:create db:migrate`export RAILS_ENV="test"
export RACK_ENV="test"
bundle exec rake db:create db:migrate --trace
warning: parser/current is loading parser/ruby23, which recognizes
warning: 2.3.3-compliant syntax, but you are running 2.3.0.
warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
** Invoke db:create (first_time)
** Invoke db:load_config (first_time)
** Execute db:load_config
** Execute db:create
#
Couldn't create database for {"database"=>"circle_ruby_test", "adapter"=>"mysql2rgeo", "pool"=>5, "charset"=>"utf8mb4", "encoding"=>"utf8mb4", "collation"=>"utf8mb4_general_ci", "username"=>"ubuntu", "socket"=>"/tmp/mysql.sock", "host"=>"localhost"}, {:charset=>"utf8mb4", :collation=>"utf8mb4_general_ci"}
(If you set the charset manually, make sure you have a matching collation)
Created database 'circle_ruby_test'
** Invoke db:migrate (first_time)
** Invoke environment (first_time)
** Execute environment
** Invoke db:load_config
** Execute db:migrate
rake aborted!
Mysql2::Error: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/mysql2-0.4.5/lib/mysql2/client.rb:89:in `connect'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/mysql2-0.4.5/lib/mysql2/client.rb:89:in `initialize'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/activerecord-mysql2rgeo-adapter-1.0.4/lib/active_record/connection_adapters/mysql2rgeo/create_connection.rb:38:in `new'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/activerecord-mysql2rgeo-adapter-1.0.4/lib/active_record/connection_adapters/mysql2rgeo/create_connection.rb:38:in `mysql2rgeo_connection'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/activerecord-5.0.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:729:in `new_connection'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/activerecord-5.0.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:773:in `checkout_new_connection'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/activerecord-5.0.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:752:in `try_to_checkout_new_connection'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/activerecord-5.0.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:713:in `acquire_connection'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/activerecord-5.0.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:490:in `checkout'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/activerecord-5.0.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:364:in `connection'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/activerecord-5.0.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:883:in `retrieve_connection'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/activerecord-5.0.1/lib/active_record/connection_handling.rb:128:in `retrieve_connection'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/activerecord-5.0.1/lib/active_record/connection_handling.rb:91:in `connection'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/activerecord-5.0.1/lib/active_record/migration.rb:1100:in `initialize'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/activerecord-5.0.1/lib/active_record/migration.rb:1006:in `new'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/activerecord-5.0.1/lib/active_record/migration.rb:1006:in `up'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/activerecord-5.0.1/lib/active_record/migration.rb:984:in `migrate'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/activerecord-5.0.1/lib/active_record/tasks/database_tasks.rb:161:in `migrate'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/activerecord-5.0.1/lib/active_record/railties/databases.rake:58:in `block (2 levels) in '
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/lib/rake/task.rb:248:in `block in execute'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/lib/rake/task.rb:243:in `each'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/lib/rake/task.rb:243:in `execute'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/lib/rake/task.rb:187:in `block in invoke_with_call_chain'
/opt/circleci/ruby/ruby-2.3.0/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/lib/rake/task.rb:180:in `invoke_with_call_chain'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/lib/rake/task.rb:173:in `invoke'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/lib/rake/application.rb:152:in `invoke_task'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/lib/rake/application.rb:108:in `block (2 levels) in top_level'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/lib/rake/application.rb:108:in `each'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/lib/rake/application.rb:108:in `block in top_level'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/lib/rake/application.rb:117:in `run_with_threads'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/lib/rake/application.rb:102:in `top_level'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/lib/rake/application.rb:80:in `block in run'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/lib/rake/application.rb:178:in `standard_exception_handling'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/lib/rake/application.rb:77:in `run'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/exe/rake:27:in `'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/bin/rake:23:in `load'
/home/ubuntu/joinus-black-server/vendor/bundle/ruby/2.3.0/bin/rake:23:in `'
/opt/circleci/.rvm/gems/ruby-2.3.0/gems/bundler-1.14.6/lib/bundler/cli/exec.rb:74:in `load'
/opt/circleci/.rvm/gems/ruby-2.3.0/gems/bundler-1.14.6/lib/bundler/cli/exec.rb:74:in `kernel_load'
/opt/circleci/.rvm/gems/ruby-2.3.0/gems/bundler-1.14.6/lib/bundler/cli/exec.rb:27:in `run'
/opt/circleci/.rvm/gems/ruby-2.3.0/gems/bundler-1.14.6/lib/bundler/cli.rb:335:in `exec'
/opt/circleci/.rvm/gems/ruby-2.3.0/gems/bundler-1.14.6/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/opt/circleci/.rvm/gems/ruby-2.3.0/gems/bundler-1.14.6/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/opt/circleci/.rvm/gems/ruby-2.3.0/gems/bundler-1.14.6/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
/opt/circleci/.rvm/gems/ruby-2.3.0/gems/bundler-1.14.6/lib/bundler/cli.rb:20:in `dispatch'
/opt/circleci/.rvm/gems/ruby-2.3.0/gems/bundler-1.14.6/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
/opt/circleci/.rvm/gems/ruby-2.3.0/gems/bundler-1.14.6/lib/bundler/cli.rb:11:in `start'
/opt/circleci/.rvm/gems/ruby-2.3.0/gems/bundler-1.14.6/exe/bundle:32:in `block in '
/opt/circleci/.rvm/gems/ruby-2.3.0/gems/bundler-1.14.6/lib/bundler/friendly_errors.rb:121:in `with_friendly_errors'
/opt/circleci/.rvm/gems/ruby-2.3.0/gems/bundler-1.14.6/exe/bundle:24:in `'
/opt/circleci/.rvm/gems/ruby-2.3.0/bin/bundle:23:in `load'
/opt/circleci/.rvm/gems/ruby-2.3.0/bin/bundle:23:in `'
/opt/circleci/.rvm/gems/ruby-2.3.0/bin/ruby_executable_hooks:15:in `eval'
/opt/circleci/.rvm/gems/ruby-2.3.0/bin/ruby_executable_hooks:15:in `'
Tasks: TOP => db:migrate
export RAILS_ENV="test"
export RACK_ENV="test"
bundle exec rake db:create db:migrate --trace
returned exit code 1
Action failed: rake db:create db:migrate

activerecord-mysql2rgeo-adapter: v1.0.3
Ruby: 2.3.0
Rails: 5.0.1

i guess that's wrong settting at test environment.
because we are using this gem at production, all enviroment.
can u connect via socket on circle-ci? maybe you have to use tcp connecting

i guess that's wrong settting at test environment.
because we are using this gem at production, all enviroment.
can u connect via socket on circle-ci? maybe you have to use tcp connecting

Okay, thanks.
It seems that the error occurred due to my setting.
I'll continue to investigate.
But only this change occurred the error...
-  adapter: mysql2
+  adapter: mysql2rgeo

can i know project's link?

can i know project's link?

Sorry, the project's source code is private...

I suspect that CircleCI's default MySQL version is old.
I'm investigating...

I suspect that CircleCI's default MySQL version is old.

This document and the log says MySQL version is 5.7.17, so version is okay.
Ubuntu 14.04 (Trusty) - CircleCI

current, that's result on TravisCI
https://travis-ci.org/stadia/activerecord-mysql2rgeo-adapter/builds/221975851
all test is okay. and connected on mysql and execute sql command.
this is settings on test environment.
https://github.com/stadia/activerecord-mysql2rgeo-adapter/blob/master/test/database.yml

I'm investigating and the error not resolved, but it seems that the problem is CircleCI's environment or configuration, so I close this.
Thanks!

Thanks!


Question: How do I set up corpus and dictionaries?

Can you please elaborate on what exactly you want to do?


tf.layers.conv3d with "channels_first" does not accept batch dimension to be None

code to reproduce:
import tensorflow as tf
x = tf.placeholder(dtype=tf.float32, shape=[None, 1, 32, 32, 32])
y = tf.layers.conv3d(x, 32, 9, data_format='channels_first')

traceback
Traceback (most recent call last):
  File "/usr/local/Cellar/pyenv/1.2.0/versions/3.6.3/envs/mrtoct/lib/python3.6/site-packages/tensorflow/python/framework/tensor_util.py", line 468, in make_tensor_proto
    str_values = [compat.as_bytes(x) for x in proto_values]
  File "/usr/local/Cellar/pyenv/1.2.0/versions/3.6.3/envs/mrtoct/lib/python3.6/site-packages/tensorflow/python/framework/tensor_util.py", line 468, in <listcomp>
    str_values = [compat.as_bytes(x) for x in proto_values]
  File "/usr/local/Cellar/pyenv/1.2.0/versions/3.6.3/envs/mrtoct/lib/python3.6/site-packages/tensorflow/python/util/compat.py", line 65, in as_bytes
    (bytes_or_text,))
TypeError: Expected binary or unicode string, got None

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/Cellar/pyenv/1.2.0/versions/3.6.3/envs/mrtoct/lib/python3.6/site-packages/tensorflow/python/layers/convolutional.py", line 809, in conv3d
    return layer.apply(inputs)
  File "/usr/local/Cellar/pyenv/1.2.0/versions/3.6.3/envs/mrtoct/lib/python3.6/site-packages/tensorflow/python/layers/base.py", line 671, in apply
    return self.__call__(inputs, *args, **kwargs)
  File "/usr/local/Cellar/pyenv/1.2.0/versions/3.6.3/envs/mrtoct/lib/python3.6/site-packages/tensorflow/python/layers/base.py", line 575, in __call__
    outputs = self.call(inputs, *args, **kwargs)
  File "/usr/local/Cellar/pyenv/1.2.0/versions/3.6.3/envs/mrtoct/lib/python3.6/site-packages/tensorflow/python/layers/convolutional.py", line 185, in call
    outputs_shape[4]])
  File "/usr/local/Cellar/pyenv/1.2.0/versions/3.6.3/envs/mrtoct/lib/python3.6/site-packages/tensorflow/python/ops/gen_array_ops.py", line 3938, in reshape
    "Reshape", tensor=tensor, shape=shape, name=name)
  File "/usr/local/Cellar/pyenv/1.2.0/versions/3.6.3/envs/mrtoct/lib/python3.6/site-packages/tensorflow/python/framework/op_def_library.py", line 513, in _apply_op_helper
    raise err
  File "/usr/local/Cellar/pyenv/1.2.0/versions/3.6.3/envs/mrtoct/lib/python3.6/site-packages/tensorflow/python/framework/op_def_library.py", line 510, in _apply_op_helper
    preferred_dtype=default_dtype)
  File "/usr/local/Cellar/pyenv/1.2.0/versions/3.6.3/envs/mrtoct/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 926, in internal_convert_to_tensor
    ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
  File "/usr/local/Cellar/pyenv/1.2.0/versions/3.6.3/envs/mrtoct/lib/python3.6/site-packages/tensorflow/python/framework/constant_op.py", line 229, in _constant_tensor_conversion_function
    return constant(v, dtype=dtype, name=name)
  File "/usr/local/Cellar/pyenv/1.2.0/versions/3.6.3/envs/mrtoct/lib/python3.6/site-packages/tensorflow/python/framework/constant_op.py", line 208, in constant
    value, dtype=dtype, shape=shape, verify_shape=verify_shape))
  File "/usr/local/Cellar/pyenv/1.2.0/versions/3.6.3/envs/mrtoct/lib/python3.6/site-packages/tensorflow/python/framework/tensor_util.py", line 472, in make_tensor_proto
    "supported type." % (type(values), values))
TypeError: Failed to convert object of type <class 'list'> to Tensor. Contents: [None, 32, 576, 24]. Consider casting elements to a supported type.

The error source appears here and can be simply fixed by adding
if outputs_shape[0] is None:
  outputs_shape[0] = -1

however you might suggest a deeper fix?

As you pointed out, I think you'd better to use shape=[-1, 1, 32, 32, 32] or shape=tf.TensorShape([None, 1, 32, 32, 32]).

Thank you, @bodokaiser . I think the issue might have been resolved in  #14120, could you test it on tf-nightly?

issue still occurs with tf_nightly-1.5.0.dev20171222-cp36-cp36m-macosx_10_12_x86_64.whl

Sorry, my mistake. It looks like a different problem, I'd like to look into the issue later. Thank you, @bodokaiser

@martinwicke

The issue is not fixed apparently. Only Conv3DTranposed seems to be fixed, but the last nightly build still provides the same error with tf.layers.conv3d.
Can someone confirm the bug and reopen the issue?
The trick in the initial post solves the issue.

You are correct, sorry for closing. The code sample in the first post still has an error.
@fchollet can you fix this?

Please submit a PR.

Added a PR #18027 for the fix.


Tooltip is not displayed fully if its on the field inside a dialog near the dialog header.

Select one ...  (check one with "x")
[X] bug
[ ] feature request
[ ] enhancement

Expected behavior
Tooltip should be shown over the top.
Actual behavior
https://plnkr.co/edit/fJzlogPxqhDhR97zAiaP?p=preview
Click open dialog button and focus on the first field and tooltip is not displayed properly.
Reproduction of behavior

Environment details

Angular version: 2.0.X

Clarity version:

OS and version:

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

@snagar78 thanks for submitting an issue here. This seems to be the same issue being discussed in issue #37, right?

@jaffoneh Yes this looks similar and looking at the discussion i think i would just change tooltip orientation to bottom :)

@snagar78 thanks. I'll close this one as duplicate since the other issue is mentioned here. Feel free to add to that discussion there with opinions and/or feedback!


Forms: Optional vs. Required fields

As part of refining form feedback, should we denote optional vs. required?

to be addressed in #896


issue with cmake external project

we are having many issues with cmake external project and managing of dependencies. This also varies from different cmake version some times. maybe we should import back those third party sources into libkml/third_party/ and activate thse only if system libs are not found.
This will allows users a clean build on windows platforms and at the same time allows to use a custom version from debian or other packages.
Any thoughts?

steps:

avoid complete boost library and try boost bcp or something to update only required boost headers. libkml uses boost's header only libraries.
internal usage of expat, minizip, zlib should avoid symbol clash when used with other libs

also this change will follow single library file for libkml rather than 4 components and all are mandotory (current case).

I suggest to use git submodules to include 3rd party libraries. And replace boost shared pointers with the new stl ones.

yes alex. git sub modules is a good option.
regarding removing boost, i am not sure task is easy. boost equivalent of smart pointer are in c++11. so libkml cannot be compiled without a recent compiler.
i would also be interested to keep only boost's shared_ptr inside third_party or as a git submodule.
the main issue to change from boost shared ptr to those from stl are intrusive_ptr which is not in stl. i know it will not hard to acheive same behaviour with existing stl ones. but there is work and it is not trivial. Hey, volunteers welcomed :)

git submodules is not an easy option now. all third parties does not have git repo and i am reluctant to keep a mirror of them in github or anywhere else.

i did some work in the fork for including thirdparty sources.
https://github.com/rashadkm/libkml/tree/master/third_party

There are newer and better ways to handle this. Attempting to compile on Ubuntu 22 with default optoins when it tries to install boost in root owned directories.
Would you be open to accepting a set of PR's to get it to compile on Ubuntu 22?


Terminal crops wide character

My PS1 starts with ➜  (one arrow and one space). The space is there so there's enough space to render the arrow. But the new canvas terminal simply crops the arrow.

Apparently this is a particularly popular wide character (dupe in #34121), "wide" characters that take up single widths are now cropped as characters own only their cell(s). This arrow char is similar to an emoji, wherein it is a single width character followed by a space. Maybe it should be special-cased and treated like an emoji until a proper solution is devised, due to its popularity (default oh-my-zsh?).
Related: https://github.com/sourcelair/xterm.js/issues/942

It might be the PS1 of the default theme of oh-my-zsh.

Ran into #35102 on verification but the problem with the arrow character and other wide characters seems fixed


fix(sqllab): Remove update_saved_query_exec_info to reduce lag

SUMMARY
Currently, there is a significant bottleneck when executing queries in sqllab due to the delay in update_saved_query_exec_info.

According to #11391, the information obtained during the update_saved_query_exec_info was added for display on the homepage, but it has been confirmed that the recently changed_date is actually being used.
To facilitate smoother execution of sqllab queries, this commit removes the update_saved_query_exec_info part. Additionally, it changed the displayed label (from ran to modified) on the homepage to reflect the actual data.
TESTING INSTRUCTIONS
CI and specs
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

I would like to add more context to this change to facilitate review:

Currently, there is a significant bottleneck when executing queries in sqllab due to the delay in update_saved_query_exec_info.

update_saved_query_exec_info currently compares the executed SQL on SQL Lab with all saved queries to update when a saved query was last run. The cost of this operation can be really high depending on the SQL size and the number of saved queries that exist in the database. We also don't think the information of when a saved query was last run is worth that cost. In fact, the last changed information is way more important and it's what's displayed for the other entity types.
@rusackas @yousoph @villebro @dpgaspar @betodealmeida @mistercrunch

we could do an additional PUT

it didn't seem to me like the last run time isn't displayed anywhere is it? It's not in the "Saved Query" CRUD at least, couldn't see it surfaced anywhere else... If that's the case, and knowing that it's not maintained now, should be just delete the column?

it didn't seem to me like the last run time isn't displayed anywhere is it? It's not in the "Saved Query" CRUD at least, couldn't see it surfaced anywhere else... If that's the case, and knowing that it's not maintained now, should be just delete the column?

Good point 👍🏼


cherrypick-dbe192d : Modified TSTAT sep 21 #22800

Fixes #22648
Fixes issues: #561, #562
Modified scripts
TSTAT-2.1
TSTAT-2.2
ACL-2.2
APPLAUNCHER-3.8
AUDIOOUTPUT-1.8
Added auto generated files

@andy31415  this is one of the cherry picks for SVE-2 branch

Bypassing cirque failure for merge: this does not seem related to these PRs.


Lab 6 level 3

Im not sure how to edit this so that it can take into account the scenario above. Anyone can help?

i solved this by adding an additional statement when i = 0 to just compare the first 2 in the list

You can use conjunction with another condition in your filter function to account for the case when one of the repeating sequences starts from the first element.

Your stream has to account for the element at index 0.

I see okay i tried it and it works thank you!


chore: remove overly aggressive stale bot

Fixes #164.
IMO it would be better to have a dedicated label to indicate that an issue or PR is waiting on the author. In that case we could use the only-labels option instead of removing the action altogether.

I think it's okay to remove the stale workflow for now.
@MichaelDeBoey What do you think about this change?


Proposal: Merging tool to manually fix data

Hi,
I have noticed that some drives are split in 2 (without switching to Park).

Would it be possible to have a tool to merge 2 drives.
Maybe merging 2 charges might also be useful to someone else.
It might look like :
docker-compose exec teslamate bin/teslamate rpc \     "TeslaMate.Repo.get!(TeslaMate.Log.Drive, 864, 865) |> TeslaMate.Log.merge_drives()"
Maybe ?
Thank you for reading me :)
This tool is gorgeous.

Feature requests belong here: 💡 Ideas. I'll move it.


move k8s host and port to yaml conifg

move k8s host and port to yaml conifg

add runtime.yaml

@winebag  Please update the runtime.yaml to README.md


As a user, I want to be able to mark my data as private

...so that I can prevent unrelated people from seeing them.
Re-implement privacy fields for data:

[x] Name
[x] Address
[x] Phone
[x] Email

#37


feat: switch to eclipse-temurin:11 as runtime base image

feat: use eclipse-temurin:11 as runtime base image
workaround: force eclipse-temurin:11 as runtime base image for upgrade tests
feat: use eclipse temurin as java distribution for github actions

Release Note
Switched form AdoptOpenJDK to  adoptium/temurin as runtime base image

This one will need to be backported to 1.11 and 1.10 as well and we should make a release of all these to fix the openjdk error.


Bad link to "update-ref" page - should be "update-refs"

[Enter feedback here]
On this page, the link "Create, update, or delete" points to the "update-ref" page when it should point to the "update-refs" page.
The item in question is a bullet point in the "Common tasks" section. It's a very subtle difference (just the letter 's'), but it's an important difference.
Also note that the "update-ref" page does exist, just does a different thing.

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

ID: e9af3a77-939e-b65c-9e48-80b36d7a6638
Version Independent ID: 73d07604-0323-01ca-0f7d-db1545761c28
Content: Git REST API for Azure DevOps Services - Azure DevOps Services REST API
Content Source: docs-ref-conceptual/5.0/git/index.md
Product: devops
Technology: devops-ref
GitHub Login: @wnjenkin
Microsoft Alias: elbatk

@GaTechThomas Thanks for reporting. I agree that there should be refs I will forward your feedback to the team owning this API to fix the doc.


Introduce binary manifest format

You can translate build.ninja to build.ninja.bin by
$ ninja -f build.ninja -tcompile build.ninja.bin
and use it by
$ ninja -b build.ninja.bin
This change makes NULL build more than 3x faster for Android
build. See src/serializer.cc for the detail for the binary
manifest format.

Another solution to improve noop build times would be #1389.

Closing in favor of #1438.


Reduce code duplication: vispy _on_scale_change() & _on_translate_change()

Description

This PR is a refactor to reduce code duplication.
Currently, VispyImageLayer overrides the base layer methods _on_scale_change() and _on_translate_change(). But there's no reason this can't live in VispyBaseLayer instead, and this simplifies things a bit.
Type of change

[x] Refactor

References

Original discussion with jni here: https://github.com/jni/napari/pull/6#discussion_r383197606
How has this been tested?

[x] all tests pass with my change

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

Nice catch, looks good to me too - I will merge after all tests pass

@GenevieveBuckley looking at this again, I notice that the find_top_left function which is in VispyImageLayer is now referenced inside VispyBaseLayer. Do you think it should be moved over too? Fine to be in a follow-up PR now that this is merged

Though that function depends on a level_shapes property on the Layer which I'm not sure is on the Base layer ... Hmm need to think more about it

@GenevieveBuckley looking at this again, I notice that the find_top_left function which is in VispyImageLayer is now referenced inside VispyBaseLayer. Do you think it should be moved over too?
Though that function depends on a level_shapes property on the Layer which I'm not sure is on the Base layer ... Hmm need to think more about it

Ooh, well spotted! I don't like having this concept split across two classes like this...
I'd prefer we picked a side: does is_pyramid and all related attributes/methods live completely in the base layer, or does it live completely in the image layer. I'll let you think about it some more.

One question: what kind of support to pyramid label layers does napari have? That's probably something that will affect the decision here.

I don't remember where this concept came up last week, but we had the idea that is_pyramid would become is_multiscale and would apply across all layers (eg millions of points would get grouped into a single point if you zoom out enough, just like this happens with some mapping applications, for example). So, I think a lot of that logic should definitely go on the base layer.


Don't select Command Cards of immobilized servants in battle

Preparation

[X] No one has asked for this feature before in other issues (even the closed ones)

Describe the feature
Similar to how FGA avoid cards of stunned servants, which I assume works fine on NA.

Can you make a video of the situation you mean?

I'll get a video later. In the meantime, you can replicate this easily by using a support Oberon's 3rd skill on turn 1 to immobilized a servant, then let FGA auto attack next turn.

Now that I think about it, does FGA avoid Charmed servant cards?

I have taken a video here. It would be better if FGA can avoid useless cards.
https://drive.google.com/file/d/1VfAnu10SVt2fiPzYSZOF9MRCgrZuJ8UH/view?usp=sharing

Now that I think about it, does FGA avoid Charmed servant cards?

No it doesn't, it only checks for stun right now.


[Regression] ErbalT now requires 2 params

New Issue Checklist

[x ] Updated fastlane to the latest version
[x ] I read the Contribution Guidelines
[x ] I read docs.fastlane.tools
[ x] I searched for existing GitHub issues

Issue Description
With #11144, Fastlane:: ErbalT now requires two params where it used to require one previously. The 2nd parameter should have a default. There is at least one plugin that breaks due to this change.
Complete output when running fastlane, including the stack trace and command used
/.../.rvm/gems/ruby-2.4.1/gems/fastlane-2.82.0/fastlane/lib/fastlane/erb_template_helper.rb:21:in `initialize': [!] wrong number of arguments (given 1, expected 2) (ArgumentError)
	from /.../.rvm/gems/ruby-2.4.1/bundler/gems/fastlane-plugin-s3-a85f598f1ab4/lib/fastlane/plugin/aws_s3/helper/aws_s3_helper.rb:29:in `new'

Environment

Thank you @ctaintor for raising this so quickly! Already have a PR on this and I hope it'll get released as soon as possible.

And reviewed and merged. Thanks for the report @ctaintor, thanks for the PR @minuscorp. I think we can expect a release on Monday containing this change.