Empty string title at 0. Title strings must have a length greater than zero

puppet 3.8.2 stringify_facts = false parser = future
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Empty string title at 0. Title strings must have a length greater than zero. at /modules/mongodb/manifests/keyfile.pp:13:10
The file in question:
# = Class: mongodb::keyfile
#
# This class installs mongodb::keyfile. It's included by the main mongodb class
#
class mongodb::keyfile {

  exec { 'generate_mongo_keyfile':
    command => "openssl rand -base64 753 > ${mongodb::keyfile}",
    path    => '/usr/bin:/bin:/usr/sbin:/sbin',
    creates => $mongodb::keyfile,
    notify  => Service['mongodb'],
  }
  file { $mongodb::keyfile:
    ensure  => present,
    mode    => '0600',
    owner   => $mongodb::process_user,
    group   => $mongodb::process_user,
    require => Exec['generate_mongo_keyfile'],
  }
}

Uhm ,
it looks like keyfile variable or param is not set anywhere in the mongodb class.
Should be added there with a correct path


Make it possible to built with GTK 2.4

gtk_notebook_set_tab_reorderable() was newly added in GTK 2.10.
Based on the following comment: https://github.com/vim/vim/pull/3436#issuecomment-422613691
@tgc Could you try this on GTK 2.4 (RHEL4)?

This works on RHEL 4.
For reference this is what I use on top of this PR to build on RHEL 3:
$ cat vim-post-pr3436-fix-gtk22-support.patch
diff -up vim-8.1.0401/src/gui_gtk_x11.c.fixgtk22 vim-8.1.0401/src/gui_gtk_x11.c
--- vim-8.1.0401/src/gui_gtk_x11.c.fixgtk22     2018-09-18 12:51:34.000000000 +0200
+++ vim-8.1.0401/src/gui_gtk_x11.c      2018-09-18 12:52:53.911661022 +0200
@@ -6395,7 +6395,11 @@ theend:
 gui_mch_flush(void)
 {
     if (gui.mainwin != NULL && gtk_widget_get_realized(gui.mainwin))
+#if GTK_CHECK_VERSION(2,4,0)
        gdk_display_flush(gtk_widget_get_display(gui.mainwin));
+#else
+       gdk_display_sync(gtk_widget_get_display(gui.mainwin));
+#endif
 }

 /*


Typescript declarations not found

When trying to upgrade pact-node in the pact module and removing the custom typings I had results in the following issue (truncated for readability):
src/pact-web.ts(20,28): error TS7016: Could not find a declaration file for module '@pact-foundation/pact-node'. <EMAIL_ADDRESS>implicitly has an 'any' type.
  Try `npm install @types/@pact-foundation/pact-node` if it exists or add a new declaration (.d.ts) file containing `declare module '@pact-foundation/pact-node';`

I'm running the latest TypeScript (v2.6.1 at this time). Even though the advice from https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html says:

Also note that if your main declaration file is named index.d.ts and lives at the root of the package (next to index.js) you do not need to mark the "types" property, though it is advisable to do so.

Manually adding "types": "./src/index.d.ts", to package.json solves the issue.
Without this, I must use the non-TS const pact = require('...') declaration, losing the nice auto-completion etc. and benefits of TS.

@mefellows ah yeah, it needs to be in the root.  I believe the index.js used to be at the root level, but I moved it and it must have broken the typings.  Cheers for the fix.


Issue/21

#21

Use httpResponse to operate status code and body.
Fix content-type is "",GET request pop 'unsupported content-type'.

We already have an RPC based http request/response type and handler. You can find the protos in the proto directory and the handler in the api package.


feat: show next result image on hover

To test this, the x-components/src/views/home/result.vue component can be updated to something like this.
Keep in mind that the animation will not be applied correctly the first time, because the appear attribute of the animations is not configurable right now.
In this PR the animations are updated making it configurable.
In the meantime, the appear attribute of the animations used to test this can be set to false.
Also, in this PR I change the picture element of the component for a div. This is needed because Firefox and Safari browsers fire the load event of the images twice if they are inside a picture element.
Even if we don't consider this problem, I am not sure that a picture element should be used there, because the purpose of that element is to provide multiple sources to the same image, and let the browser decide which one to use depending on the format, the viewport, and so on.
BREAKING CHANGE: The base-result-image animation prop is now named loadAnimation.
EX-5970

Nice job!


fix: use-sync-external-store/shim import in ESM

ESM requires providing the file extension when importing - source
When importing the package as is, an error is thrown:

The request 'use-sync-external-store/shim' failed to resolve only because it was resolved as fully specified
(probably because the origin is a '.mjs' file or a '.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.

@fabioatcorreia Thanks for the pull request. While it does fix the problem, I think we can find other ways to fix it. I just pushed a new version with a few things, if possible, or when you can, try it out and tell me if that fixed your problem.

Just tried with the new version and, unfortunately, I still get the same issue

@fabioatcorreia This version should fix the error, changed all files and config, to include file extensions (including the shim). When you can check it out and tell me the results if possible.


[Proposal] View::prependLocation($path)

Hi,
is it possible to implement a View::prependLocation($path) (+ View::setLocation($path)) method?
Use Case:
You create a blog, you use the default location for views. Later you want to implement a "Themer" functionality to change some of the templates without touching/editing the original ones. Right now there is only the addLocation method to append a new location, BUT then only the original template would be loaded first.
Example:
Let's assume we have a blog. And we "make" a view:
View::make('posts.show')->withPost($post);
By default no theme is set, so this view should be called:
app/views/posts/show.blade.php
Now we apply a "Bootstrap" theme, now this file should be called:
app/Themes/Bootstrap/views/posts/show.blade.php
if there is no such file, the original should take place instead.
With View::prependLocation($path) + View::setLocation($path) you could offer a nice and easy way to tackle even deep nested Sub-Theming like:
Look for
app/Themes/Bootstrap/Christmas/views/posts/show.blade.php
Nothing found - look here:
app/Themes/Bootstrap/views/posts/show.blade.php
Nothing found - look here:
app/Themes/Default/views/posts/show.blade.php
Nothing found - look here:
app/views/posts/show.blade.php
(The setLocation method should replace all given view paths with a set of new ones)
Greetings from Munich :-)

prependLocation could be this:
    protected function prependViewNs($ns)
    {
        Config::set('view.paths', array_merge([$ns], Config::get('view.paths')));
        // Rebind finder
        View::setFinder($this->app['view.finder']);
    }

The problem with using namespaces is that they don't work with blade. So while I can successfully use namespaces to find the custom view paths, once I'm in the view @extends doesn't use the namespace so I'm back to square one


Fix NCSO functions for orgs with no prescribing data

At present, trying to load the homepage for a practice which has long
since closed triggers an error.

Merging myself as there's no one around to review


Makefile, style and linter

Standardize the code and the flow with these elements.
This includes type hints everywhere.
(and will also expose the leaky abstraction around the current vector mixin, eeeh)

shipped with 0.1.3


Input validation in the middleware (additional scope required in fieldWithHooks call)

After getting the example working thanks to #587 and searching here, I'm hitting a bump when trying to implement custom input validation in the middleware.  For various reasons, we would prefer not to do this in PG.  Ideally I'd like to be able to just intercept any update or create mutation and get a handle on the table/class name the mutation is targeting, and all the fields being sent in the patch.
The first half has been fairly straight forward after following along with the example using a bit of code like this:
if ((0 == fieldName.indexOf('update')) || (0 == fieldName.indexOf('create'))) { /* stuff */ }
I'm struggling to find a clean way to determine the name of the object/table being updated however.  Dumping the resolveParams (again, from the resolve method in the example) gives the patch pretty readily in the input field, but I need to know the class/table name, since it's named fooPatch.
Is there an easy way to get this information here, or am I taking the wrong approach entirely?

Sorry I cannot go into detail in this today, I can try and give some pointers though. When you hook up your override you have access to the Context object (the third argument passed to your hook) and within that is a field called “scope” which contains a field called “pgIntrospection” (or something like that, scan through the existing plugins for the correct name) which represents the entity (most likely table) the GraphQL object is being created for. This should tell you the table name, schema etc.
You should also be using this scope object to determine when to apply your resolve wrapper though I don’t know the fields to check for offhand

Actually it seems the fieldWithHooks call doesn’t add any context so it’s going to be harder to auto-detect. I’d consider a PR that adds pgIntrospection and isPgCreateField to the fieldWithHooks call so you can hook this more easily.
https://github.com/graphile/graphile-build/blob/master/packages/graphile-build-pg/src/plugins/PgMutationCreatePlugin.js

@benjie I'm looking through and poking at the code you mentioned but it's not really clear to me what I should be doing.  I don't really have any experience in this sort of JS development, as until a week or two ago my experience was limited to purely client-side stuff with jquery et al.
Adding another parameter around line 232 (after the getDataFromParsedResolveInfoFragment block) doesn't cause any errors in the lerna tests, so is that the right approach/place to do this?
Sorry for the newbie questions but I want to make sure I'm on the right path here before I rebuild postgraphile and then start trying to hook into things in my application, since a mistake on the graphile side will leave me pointlessly scratching my head when debugging the express server.

So basically, the field with hooks call:
https://github.com/graphile/graphile-build/blob/d2da24040a6a352679b5985b4829634f32396e7a/packages/graphile-build-pg/src/plugins/PgMutationCreatePlugin.js#L135-L140
...
https://github.com/graphile/graphile-build/blob/d2da24040a6a352679b5985b4829634f32396e7a/packages/graphile-build-pg/src/plugins/PgMutationCreatePlugin.js#L220-L223
Only uses the call signature fieldWithHooks(fieldName, spec). fieldWithHooks can be called with 3 arguments - the third one is scope:
https://www.graphile.org/graphile-build/context-object/#fieldwithhooksfieldname-spec-scope--
So if you were to insert an additional object just before line 222, the keys on that object would be available on the context.scope of the hook you write.
I would recommend passing pgIntrospection: table and maybe something like isPgCreateMutationField: true in a similar way to how the scope is passed to newWithHooks a few lines above:
https://github.com/graphile/graphile-build/blob/d2da24040a6a352679b5985b4829634f32396e7a/packages/graphile-build-pg/src/plugins/PgMutationCreatePlugin.js#L124-L130

It's a shame the GitHub code embeds don't work cross-repository!

 Ensure all fieldWithHooks calls declare the correct data on the third argument (scope)

The next release of PostGraphile will include more scope information on many fields, and thus better hooks can be written 👍

Benjie,
I'm revisiting this nearly a year later and without opening another ticket, I'm curious to know if any additional support for this sort of plugin has made it into the 4.0 branch?  An (over simplified) example of what I want to do would be to validate a value against a regex prior to the mutation making it to the DB.
TIA!

Yeah, sounds like you want to wrap the mutation resolvers:
https://www.graphile.org/postgraphile/extending/#wrapping-an-existing-resolver
Let me know what questions you have the docs don’t answer 👍

That link was a big help, got the example sorted.  Before I continue, is this ticket the right place to continue this discussion?
All I want now is an easy way to get the name of the table I'm working on without the calling context on it -- e.g. reliably getting the name "Foo" from a mutation like "updateFooBySomeField" or "createFoo" or whatever.  I didn't see the name anywhere in the available data in the resolver wrapper.

Sorry about the poor documentation on this (help fixing it would be greatly appreciated once you've figured it out!); plugin hooks take three arguments (thing, build, context); the context argument contains a scope property that tells you about the scope that the current hook is running in. This contains lots of useful information; I think you're either after pgIntrospection or pgIntrospectionTable which will tell you useful things about the thing that that field/type is based on. You're looking for one that has .kind === 'class', like this:
https://github.com/graphile/graphile-build/blob/69d7b1cbe48ea5f50e3121916e7b1e12d1c70008/packages/graphile-build-pg/src/plugins/PgIntrospectionPlugin.js#L46-L68
Here's an example from one of the built-in plugins:
https://github.com/graphile/graphile-build/blob/69d7b1cbe48ea5f50e3121916e7b1e12d1c70008/packages/graphile-build-pg/src/plugins/PgMutationPayloadEdgePlugin.js#L17-L35

If you are using white-listed queries/mutations using for instance express middleware, validating the variables based on the matched query/mutation should be trivial. Upside is validation that is not tied into PostGraphile/PG, downside is you may have to repeat validation for every white-listed query instead of reusable field-level validation.

https://www.graphile.org/postgraphile/plugin-gallery/#Mutation_wrappers__OverrideArgValuePlugin
Changing this, and possible create reusable args validation plugin ( not yet created though ).
return {
      ...field,
      resolve(mutation, args, context_2, info) {
        args.input.patch = editProfileSchema.validateSync(args.input.patch)
        console.log('\n\n\n\x1b[36m%s\x1b[0m', 'here should not be called\n\n\n') // here not called and

        return oldResolve!(mutation, args, context_2, info)
      },
    }

this returns
{
  "errors": [
    {
      "message": "username must be at most 10 characters",
      "locations": [
        {
          "line": 137,
          "column": 3
        }
      ],
      "path": [
        "updateUserById"
      ]
    }
  ],
  "data": {
    "updateUserById": null
  }
}

perfect!!


feat: allow stdin for sfdx-url

What does this PR do?

oclif has been updated to include a new option for flags: allowStdin
Enable this for the sfdx-url-file flag based on solution outlined here: https://github.com/oclif/core/issues/761

$ echo url | sf org login sfdx-url --sfdx-url-file -
However, there is one issue I hope to solve before this PR is merged. This allows the URL to be read from stdin but doesn't prevent someone from directly passing the value in. This is because the '-' value is replaced with the url after calling the parse method and I need an easy way to tell what the original value was.
So there is no difference between doing either of these:
$ echo url | sf org login sfdx-url --sfdx-url-file -
$ sf org login sfdx-url --sfdx-url-file url
I hope to discuss how to solve for this if needed, and then include tests.
What issues does this PR fix or reference?
closes: https://github.com/forcedotcom/cli/issues/2120
[skip-validate-pr]

@k-capehart Thanks for taking this on!
As you noted, this change would allow someone to pass the url directly to the flag. I just made a PR to oclif/core that adds an only option to allowStdin. I think we should create a separate flag for the stdin (--sfdx-url-stdin) and use allowStdin: 'only' to force users to supply the - value
That way we don't open up the possibility for people to provide the url directly

@k-capehart Thanks for taking this on!
As you noted, this change would allow someone to pass the url directly to the flag. I just made a PR to oclif/core that adds an only option to allowStdin. I think we should create a separate flag for the stdin (--sfdx-url-stdin) and use allowStdin: 'only' to force users to supply the - value
That way we don't open up the possibility for people to provide the url directly

Perfect! I'll update this PR to reflect that new change in oclif. Thanks.

@k-capehart FYI, I merged the oclif/core PR. Changes should be available in 3.16.0

@k-capehart FYI, I merged the oclif/core PR. Changes should be available in 3.16.0

@mdonnalley Thanks for your help. This PR has been updated to reflect the new changes and is ready for review now.

@mdonnalley @jshackell-sfdc I appreciate you both! It's exciting to get this one working.

QA
Setup:

pulled changes
linked to sf
put auth url into auth.txt and auth.json file

✅ echo <URL> | sf org login sfdx-url --sfdx-url-stdin -
✅ echo <URL> | sf org login sfdx-url --sfdx-url-stdin throws validation error
✅ sf org login sfdx-url --sfdx-url-file auth.txt
✅ sf org login sfdx-url --sfdx-url-file auth.json
✅ sf org login sfdx-url --sfdx-url-file auth.txt --sfdx-url-stdin throws validation error
✅ sf org login sfdx-url throws validation error
Great work @k-capehart 🏆

@k-capehart I'm going to merge this into a separate feature branch first so that all our integration tests can run. Once those pass I'll merge to main


fix: correct import_map attribute name in validation

Follow up to https://github.com/netlify/edge-bundler/pull/239, where the schema said importMapURL as the key name instead of import_map which is correct.

on my machine, I have do set FORCE_COLOR=0 for the snapshot testing to work correctly. Is it the same for you, @eduardoboucas? If I don't, it outputs a bunch of colour escape codes into the snapshot.

on my machine, I have do set FORCE_COLOR=0 for the snapshot testing to work correctly. Is it the same for you, @eduardoboucas? If I don't, it outputs a bunch of colour escape codes into the snapshot.

You can also use npm run test:dev:vitest:watch.

good to know! now I see that package.json also has FORCE_COLOR=0, that makes sense :)


Assign a service endpoint to the Key Vault in the spokes

Decided against doing this as current state of the Key Vault is more secure without public access enabled at all


[SDK Renaming] - New Carthage Version & Adjustments

Jira Ticket

ACCSEC-

Github Issue

ISSUE-

Description

Commit message

Screenshot

Testing

[ ] Added unit tests
[ ] Ran unit tests successfully
[ ] Added documentation for public APIs and/or Wiki

Code coverage
Total coverage: 95.13%

Powered by Slather

  Generated by :no_entry_sign: Danger

Code coverage
Total coverage: 95.18%

Powered by Slather

  Generated by :no_entry_sign: Danger

Code coverage
Total coverage: 95.13%

Powered by Slather

  Generated by :no_entry_sign: Danger


Enhancing Visibility: Updating Contributor Name Colors for Dark Mode Compatibility

Adjusting the color of project contributor names to enhance visibility in dark mode. This change improves readability and ensures consistent accessibility across both light and dark themes.

@vanshchauhan21 hey vansh what are you doing why did you give level 3 konw its every easy task


Problem with chunking (DITA OT 2.x development branch).

I uploaded a zip here:
http://www.oxygenxml.com/forum/files/ug.zip
If the usermanual DITA Map gets published to plain XHTML the "eppo-installation-linux" HTML file should contain inside it the content from the two subtopics but it no longer does that.
The used chunk method is:
  <topicref href="topics/eppo-installation-linux.dita" chunk="select-branch to-content" navtitle="Linux Installation" locktitle="yes">
    <topicref href="concepts/installation-installer-linux.dita" toc="no"/>
    <topicref href="concepts/installation-requirements-linux.dita" toc="no"/>
  </topicref>

@raducoravu are you able to verify whether this is a regression bug or something that's never worked?

select-branch is redundant since you're targetting the root topic in eppo-installation-linux.dita. Have you tried removing it, in case the problem is there?

Still does not work if I remove "select-branch". It works with DITA OT 1.8. But it seems that it does not work even with the stable DITA OT 2.1 release.

Ok, so it's a regression bug.

I tested the changes and I confirm Chris' commit fixes this issue. Thanks Chris :)


[KOGITO-5603] - Implement Kogito-Infra Improvement

Many thanks for submitting your Pull Request :heart:!
https://issues.redhat.com/browse/KOGITO-5603
Please make sure your PR meets the following requirements:

[ ] You have read the contributors' guide
[ ] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[ ] Pull Request contains a link to the JIRA issue
[ ] Pull Request contains a description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[ ] You've ran make before-pr and everything is working accordingly
[ ] You've tested the new feature/bug fix in an actual OpenShift cluster
[ ] You've added a RELEASE_NOTES.md entry regarding this change

@vaibhavjainwiz Infinispan truststore volume is not created. Reproducer:

install Infinispan

apiVersion: app.kiegroup.org/v1beta1
kind: KogitoInfra
metadata:
  name: kogito-infinispan-infra
spec:
  resource:
    apiVersion: infinispan.org/v1
    kind: Infinispan
    name: kogito-infinispan

apiVersion: app.kiegroup.org/v1beta1
kind: KogitoRuntime
metadata:
  name: example-quarkus
spec:
  image: 'quay.io/kiegroup/examples-process-quarkus-example-persistence-nightly:latest'
  infra:
    - kogito-infinispan-infra

Kogito Deployment doesn't contain any volume.

@sutaakar Could you please retest now.

/jenkins test

/jenkins test

@vaibhavjainwiz If user defines env variables both in KogitoInfra and KogitoRuntime then KogitoRuntime variables in Deployment are defined twice:
apiVersion: app.kiegroup.org/v1beta1
kind: KogitoInfra
metadata:
  name: kogito-infinispan-infra
spec:
  envs:
    - name: qqq
      value: www

apiVersion: app.kiegroup.org/v1beta1
kind: KogitoRuntime
metadata:
  name: example-quarkus
spec:
  env:
    - name: eee
      value: rrr
  image: 'quay.io/kiegroup/examples-process-quarkus-example-nightly:latest'
  infra:
    - kogito-infinispan-infra

When I create default Infinispan on OCP:
apiVersion: infinispan.org/v1
kind: Infinispan
metadata:
  name: example-infinispan
  namespace: ksuta-test
spec:
  replicas: 1
``
And basic KogitoInfra:

apiVersion: app.kiegroup.org/v1beta1
kind: KogitoInfra
metadata:
name: kogito-infinispan-infra
spec:
resource:
apiVersion: infinispan.org/v1
kind: Infinispan
name: example-infinispan
The operator gets into infinite loop trying to reconcile truststore, crashing.

Hi @sutaakar
I had fixed env issue and infinite reconcilation loop issue.
For other issue -
Next issue - when I delete env variable from KogitoRuntime then application is not redeployed. To refresh the Deployment I have to delete it and let operator create it again.

It was intentionally do so in https://issues.redhat.com/browse/KOGITO-3032.

Nitpick - Infinispan truststore password is passed using env variables. Ideally it should be part of secret.

Infinite reconciliation when file mode not defined for volume CM:
  configMapVolumeReferences:
    - name: example-cm

deployed
"spec":{"volumes":[{"name":"example-cm","configMap":{"name":"example-cm","defaultMode":420}}

requested
"spec":{"volumes":[{"name":"example-cm","configMap":{"name":"example-cm"}}

Otherwise it looks ok

Hi @sutaakar
I had incorporated your all review comments.

/jenkins test

I see reconciliation issues with truststore.p12 in BDD log, however I am not able to reproduce it locally. Rerunning
/jenkins test

Infinite reconciliation for volume CM is fixed.

@vaibhavjainwiz the PR needs rebase due to descriptor PR merge (sorry).


Side and margin notes à la Tufte CSS

Feature Request
Is your feature request related to a problem? Please describe.
Constantly going top to bottom to read footnotes is annoying.
Describe the solution you'd like
To have the possibility of easily adjust the margins to include side and margin notes in a responsive way, just like Tufte CSS does.
Describe alternatives you've considered
As seen in the example document, Tufte CSS successfully presents side and margin notes in a responsive way.
Additional context
Sidenotes in desktop

Sidenotes in mobile

I guess this feature doesn't have any fans 🙄😔

It would be nice to have, because I agree that going all the way to the bottom of the page is a pain. I'm still pretty new to Academic, but I really like how Distill and Tufte CSS solves these footnote problems.
A workaround that might at least partially solve the problem would be hoverable footnotes, as is implemented in Distill.

A workaround that might at least partially solve the problem would be hoverable footnotes, as is implemented in the Distill framework.

Thanks! I had never heard of those hoverable footnotes and indeed they seem to be the way to go. Searching the web I found this solution based on Bootstrap and also this jQuery plugin.

For anyone following this, this is my current solution, which is live in my website (this post for example has many footnotes). Happy for now.
@gcushen do you think this would be worthy of adding to Academic? It really improves the footnote experience.
Thanks!

For anyone following this, this is my current solution, which is live in my website (this post for example has many footnotes). Happy for now.

I have been looking for a Tufte CSS style for my website in Hugo Academic too!
This seems like a great working solution to the problem. Cheers!

FYI here is a great example of this idea in implementation: https://ingeveb.org/pedagogy/guidelines-for-yiddish-in-bibliographies


I cannot install MOBsuite to my environment

Hello,
I'm a newbie in programming and need help installing MOBsuite in my conda environment. I've opened a new environment to install the specific requirements. Here is what I installed before installing MOBsuite:
python=3.8
pandas=1.0.5
numpy=1.19.0
I also have the necessary channels. However, it gets stuck in the solving environment stage when I run conda install -c bioconda mob_suite -y (I've tried without -y too). It stuck for two days in this state, but I've never had any response. I am trying to figure out what is wrong. I have to solve it soon because I have to finish my thesis in a week and classify my plasmids for my result section. Can you help me?

Same problem here, installation via bioconda keeps getting stuck after launching
conda install -c bioconda mob_suite

(Executing transaction is endlessly loading).
Has anyone figured this out yet?

I can confirm there is a problem in solving the environment as well.

I successfully installed MOBsuite via pip :)

LibMambaUnsatisfiableError: Encountered problems while solving:

package pycurl-<IP_ADDRESS>-py36h5be270d_3 requires libcurl >=7.71.1,<9.0a0, but none of the providers can be installed

I'm pretty new to coding, so I'm not sure how to solve this specific error :') The thing that I did was create a new environment in conda with python=3.8 and open it. Then, I installed pandas=1.0.5 (the version was written wrong in the requirements section of MOBsuite) and numpy=1.19.0 (suggested by a developer in one of the issues here). Then, I installed MOBsuite via pip, and it worked. You could ask it to ChatGPT, too, if no one answers here.

@zeineppu97 This is great - it worked. Thank you so much!

I'm glad it did work ^^ Good luck with your analysis!

Hi,
I ran into the same issue, and it seems the conflict is mainly due to the version of pandas. By default, Conda installs a higher version than what MOBsuite requires. To resolve this, I created a new environment and first installed all the dependencies with their default versions, except for pandas, which I set to version 1.0.0. After that, running conda install -c bioconda mob_suite worked smoothly, and it automatically adjusted numpy to the required version.
Hope this helps!

@NerisGarcia Good to hear - will note that in my next installation attempt!

I run into a similar issue and also worked for me installing pandas 1.0.0 and biopython 1.84 from conda-forge (as the latest version from bioconda is  biopython 1.70).  So in a single command would be:
 conda create -n mob_suite mob_suite pandas==1.0.0 conda-forge::biopython

Thank you for looking into this. The new version 3.1.9 relaxed pandas requirement to 1.5.3 and should work without any extra hoops to jump. You can always check what are the minimum requirements at https://github.com/bioconda/bioconda-recipes/blob/master/recipes/mob_suite/meta.yaml and https://github.com/phac-nml/mob-suite/blob/master/setup.py. I also recommend using a new environment solver mamba instead of conda as it is faster. We will be looking into migration to pandas 2.0 in the future to avoid any issues. Also will need to bump python requirement to 3.9 as Biopython v1.84 requires it

For the life of me I cannot get this installed.
I have tried the workarounds above but always end up with dependency errors.
I can't even get the docker image running (I get errors about image not being found locally).
Any planned updates on installation instructions/updated versions that are easier to work with? As it stands, I can't get anything working.


.Net: [Agents] Add streaming to ChatCompletion agent

Add streaming to the agents abstraction and ChatCompletionAgent [confirmation required]

Agent streaming is quite a bit different from chat-completion streaming.  This is a task with some complexity, risk, and will require some time (around a week).

Really looking forward to this as well as the agent changes in general. We have a product that we are refactoring to this Agent framework and this is a blocker to releasing.


The message schedule, w, expands by one when we copy the chunk into the first 16 entries.

This fixes that.

Thanks!


Add a --cname option to create the CNAME file

Search Terms
CNAME GitHub pages
Problem
The repro for Gerrit0/typedoc-plugin-missing-exports#4 has a a build script which copies a CNAME file so that GitHub Pages works properly. We should make this extra build step easier.
Suggested Solution
Add an option --cname, which will result in TypeDoc creating a CNAME file with the contents of that option.

I've just seen this issue (and it refers to my project 🤣). I don't use this anymore since the docs folder is inside another website but it could be useful for someone else.
I think a cname string option could fit, that value will be written inside the CNAME file.


[release-4.4] Bug 1850112: Resolve only default channels

Non deterministic behavior was introduced where, in some cases, the
dependency resolver would select a channel entry from the registry
that was not part of the default channel and create a subscription
on that channel. This bugfix updates the registry client's filter
function to ignore non default channel entries.

/bugzilla refresh

/bugzilla refresh

/bugzilla refresh

/lgtm

/lgtm

/cherry-pick release-4.3


Unhandled Promise Rejection

Sentry Issue: KAP-7C9

macOS version:    High Sierra (10.13)
Kap version:      3.3.0
Unhandled Promise Rejection

TypeError: Cannot read property 'some' of undefined
    at /Applications/Kap.app/Contents/Resources/app.asar/main/common/settings.js:126:18

Fixed in #915
In the meantime you can get it to work by following this:

Requires macOS 10.12 or later. macOS 10.13 or earlier needs to download the Swift runtime support libraries.


no such package '@remotejdk11_linux//'

System information

**OS Platform and Distribution: Linux Ubuntu 20.04
**Apollo installed from: 软件包
**Apollo version :8.0

Steps to reproduce the issue:
When I run the command:
bazel test //modules/localization/rtk:rtk_localization_test
I meet the error:

ERROR: /apollo_workspace/.cache/bazel/679551712d2357b63e6e0ce858ebf90e/external/bazel_tools/tools/jdk/BUILD:490:6: no such package '@remotejdk11_linux//': BUILD file not found in directory '' of external repository @remotejdk11_linux. Add a BUILD file to a directory to mark it as a package. and referenced by '@bazel_tools//tools/jdk:remote_jdk11'

I check the /apollo_workspace/.cache/bazel/679551712d2357b63e6e0ce858ebf90e/external/bazel_tools/tools/jdk/BUILD' file： ![2023-11-15 11-59-35 的屏幕截图](https://github.com/ApolloAuto/apollo/assets/128605713/6ef23131-be2b-460c-9243-8ec25e1ad586) and I find them in the /apollo_workspace/.cache/bazel/679551712d2357b63e6e0ce858ebf90e/external` directory：

but there is no linux_x86_64.
Is this causing the error? If so, how do I fix it?

same as #15176, you can discuss the issue in there


Serialization for Transition & Section doesn't always work for variable widths

Describe the bug
When creating a variable width Transition or Section, if the user uses a function to return the custom width function, Pydantic will just serialize the width_function, offset_function (in the case of Section), and width_type (for Transition) as a string with the name of the width function.
In the example below, this results in the @gf.cell decorator seeing the same width_func when serializing the Section, s, though the actual function has been created using different num_periods arguments. As a result, all of the resulting extruded paths, p, are identical.
import numpy as np
import gdsfactory as gf

def get_custom_width_func(n: int = 5):
    def _width_func(t):
        return 3 + np.cos(2 * np.pi * t * n)
    return _width_func

c = gf.Component()

P = gf.path.straight(length=40, npoints=100)

for i, num_periods in enumerate([1, 5, 10]):
    width_func = get_custom_width_func(n=num_periods)
    s = gf.Section(width=0, width_function=width_func, offset=0, layer=(1, 0))
    X = gf.CrossSection(sections=(s,))

    c2 = gf.Component()

    p = c2 << gf.path.extrude(P, cross_section=X)
    label = c2 << gf.c.text(f"{num_periods=}", size=5)

    label.movex(label.xmin, p.xmax + 2)
    label.movey(label.y, p.y)

    c.add_ref(c2).movey(-i * 15)

c.show()

Which ends up creating 3 identical components:

Suggested Fix
I propose we fix this by serializing the output of the function, like so:
class Section(BaseModel):
    ...
    @field_serializer("width_function", "offset_function")
    def serialize_functions(self, func: Callable | None) -> str | None:
        if func is None:
            return None
        t_values = np.linspace(0, 1, 11)
        return ",".join([str(round(width, 3)) for width in func(t_values)])

and
class Transition(BaseModel):
    ...
    @field_serializer("width_type")
    def serialize_width(self, width_type: WidthTypes | Callable) -> str | None:
        if isinstance(width_type, str):
            return width_type
        t_values = np.linspace(0, 1, 10)
        return ",".join([str(round(width, 3)) for width in width_type(t_values)])

making these modifications, the behavior is as expected:

There is a bug with this fix. Overall, all somehow works but widths are returned 3 times from one function call using width_function. I have tried many ways to drop/ignore the extra two arrays but unsuccessfully. The below part of the code produces this issue - there should be only one array output but there are three.
def func(x):
    print('len(x)='+str(len(x)) + '; x='+str(x))
    y = np.sin(50*x)
    mpl.plot(x, y)
    return y

XS = gf.Section(width=0, offset=0, layer=(10,0), width_function=func)
gf.path.extrude(mypath, gf.CrossSection(sections=[XS]));

Example of the output:

By deleting the below code part from cross_section.py this issue is solved.
    @field_serializer("width_function", "offset_function")
    def serialize_functions(self, func: Callable | None) -> str | None:
        if func is None:
            return None
        t_values = np.linspace(0, 1, 11)
        return ",".join([str(round(width, 3)) for width in func(t_values)])

I.e., from the above example I get:

Can someone advise how to properly implement the fix such that there aren't these extra generated lists or what should be done?


Customizing of Table not fully functioning (reusable component)

[x] I have searched the Issues to see if this bug has already been reported
[x] I have tested the latest version

Steps to reproduce

Import and add table exactly as example with checkboxes: https://www.flowbite-react.com/docs/components/table#table-with-checkboxes
Copy the customization object according to documentation, and add it to the theme prop of Table. I used example from Option 3 from https://www.flowbite-react.com/docs/customize/theme
Change the classes from "root" and then from "head"

Current behavior
Only the classes from "root" will be rendered, and the ones from "head" will still be the default, as if nothing was changed on custom object.
Expected behavior
thead component should inherit the classes passed on "head" property from custom object.
Context
I'm trying to accomplish a customized Table, styling it with theme prop. It happens on any browser (tested on Safari, Chrome and Firefox), using MacOS Monterey.
Reproduction:
https://codesandbox.io/p/sandbox/unruffled-morning-kpq7r3
On this reproduction, it is possible to customize classes for root, but not for head.
IMPORTANT:
I have tested the Flowbite wrapper approach and it works, so this problem seems to be only occurring with reusable custom component approach.

After using the  approach, I've found another issue.
Even though it changes the classes, it seems to not apply the property.
You can reproduce it by customizing the Table wrapping it on a Flowbite component, and then applying the theme to that wrapper. After that, you can go to head > cell and change the background-color for example. It will render the component with the new class but not apply it. It will act as no bg was informed at all. The same for "group-first/head:first:rounded-tl-", if you change it to 2xl it will render with class "group-first/head:first:rounded-tl-2xl" but header will have no border on left side.

This issue is fixed by https://github.com/themesberg/flowbite-react/pull/1104, which is present in 0.7.0 release.


community[patch]: fix Azure AI search delete and improve documentation

This PRs includes the following changes:

Fix missing await initPromise when doing a delete with filter, causing race conditions
Set default search mode to hybrid to improve search results relevance
Add documentation on hybrid search and semantic ranking

@bracesproul We've answered your comment, is there anything else you need from our side?

@bracesproul We've answered your comment, is there anything else you need from our side?

Nope, lgtm and will get a release asap!


nfs-client provisioner pod keep in ContainerCreating state

Hi,
I need created a NFS client storage class in k8s network for Jenkins X usage.
My k8s has one master and one work node, the version is 1.11
helm version is (both client and server): v2.13.1
The command I created the nfs-client is (I also tried mount version 4, result is the same):
helm install --name my-release stable/nfs-client-provisioner --set nfs.server=<IP_ADDRESS> --set nfs.path=/home/ocsg/nfs/jenkinsx  --set storageClass.defaultClass=true --set nfs.mountOptions="{tcp,nfsvers=3}"
Helm doesn't report any error, and sc can be seen in k8s:
[root@bej312336 storageClass]# kubectl describe sc
Name:                  nfs-client
IsDefaultClass:        Yes
Annotations:           storageclass.kubernetes.io/is-default-class=true
Provisioner:           cluster.local/my-release-nfs-client-provisioner
Parameters:            archiveOnDelete=true
AllowVolumeExpansion:  True
MountOptions:
tcp
nfsvers=4
ReclaimPolicy:      Delete
VolumeBindingMode:  Immediate
Events:
But seen from the pod:
[root@bej312336 storageClass]# kubectl get pod
NAME                                                 READY     STATUS              RESTARTS   AGE
my-release-nfs-client-provisioner-5b98cd6d97-stpqd   0/1       ContainerCreating   0          14s
I also tried to mount the NFS locally in linux command and it also works for both V3 and V4.
Could anyone provide any instructions for the troubleshooting?

have the same error

Hi, i had the same error.
I solved this problem with also set the right path:
kind: Deployment
apiVersion: extensions/v1beta1
metadata:
  name: nfs-client-provisioner
spec:
  replicas: 1
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: nfs-client-provisioner
    spec:
      serviceAccountName: nfs-client-provisioner
      containers:
        - name: nfs-client-provisioner
          image: quay.io/external_storage/nfs-client-provisioner:latest
          volumeMounts:
            - name: nfs-client-root
              mountPath: /persistentvolumes
          env:
            - name: PROVISIONER_NAME
              value: fuseim.pri/ifs
            - name: NFS_SERVER
              value: <YOUR NFS SERVER HOSTNAME>
            - name: NFS_PATH
              value: <MY NFS SERVER PATH>
      volumes:
        - name: nfs-client-root
          nfs:
            server: <YOUR NFS SERVER HOSTNAME>
            path: <MY NFS SERVER PATH>

i hope it helps someone :-)

describe the pod to see the mount command that is failing


Catch exceptions, raise Plug.Conn.WrapperError

We have a Phoenix application that expects the [:phoenix, :endpoint, :stop] event to be executed, but I noticed that this was not happening when uncaught exceptions originated from this plug.
This is because Plug.Telemetry registers this event by using Plug.Conn.register_before_send, which, in turn, adds a key to conn.private.
When there is an uncaught exception, Phoenix catches the error to render a standard error response here. When this sends the response, the telemetry callback is run and the event is executed.
Notice that if there is a Plug.Conn.WrapperError, the conn from it is used, but if not, conn is what's in scope at the time the RenderErrors plug runs. This happens to be at the top of the middleware stack before Plug.Telemetry registers the callback. Thus, no [:phoenix, :endpoint, :stop] event is executed.
Note also that bug reporting plugs may also expect request parsers etc. to have surfaced important bits of info on the conn (we ran into this issue as well, but worked around it).
This issue can be solved by rescuing errors in call and using Plug.Conn.Wrapper.reraise/4

I should note that this likely only effects Phoenix applications without a router, since Phoenix Router wraps errors. As our application is solely a GraphQL server, we don't have/need a router.


Page Speed

Description:
The page speed of the website is good, but has a pretty good chance of improvement. General points on this are the format of the introductory video and general code practices. The detailed report is given below, with individual analysis for mobile and desktop.
Desktop:
https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fdoc2pen.smaranjitghose.codes%2F&tab=desktop
Mobile:
https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fdoc2pen.smaranjitghose.codes%2F&tab=mobile

I would like to work on this issue.

Go ahead with it. Mention the changes you have made and the enhanced website's pagespeed when making a PR.


CPP Client - Turning switch case warnings into errors.

Turning missing switch case handling warnings into errors and handled a few missing cases.

rerun integration tests

rerun java8 tests

rerun integration tests


resizeWidth and resizeHeight is not work

excuse me,I use resizeWidth and resizeHeight is not work..
what happen?
<dropzone ref="myUniqueID" id="VueBanner" :url="url"
              v-on:vdropzone-error="showError"
              v-on:vdropzone-success="showSuccess"
              :resize-height="500"
              :resize-width="500"
              :auto-process-queue="false"
              :max-number-of-files="1"
              :thumbnail-width="300"
              :maxFileSizeInMB="500"
              >
                <!-- Optional parameters if any! -->
                <input type="hidden" name="_token":value="csrf">
</dropzone>

What do you mean it doesn't work? Do you get an error?

@rowanwins
sorry, is not any error message

@niusmake Everything is working fine. I reproduced the same as you described, with different height and width. Se the output below.
I'd suggest please check the vue2-dropzone version you are using. It should be 2.3.1 or greater, as image resize feature was introduced in 2.3.1 track here

Image Height : 50, Width: 50

Image Height : 200, Width: 200


Validate config against a declarative JSON Schema

[!warning]
This is public repository, ensure not to disclose:

[ ] personal data beyond what is necessary for interacting with this pull request
[ ] business confidential information, such as customer names

What kind of PR is this?
Required: Mark one of the following that is applicable:

[x] kind/feature
[ ] kind/improvement
[ ] kind/deprecation
[ ] kind/documentation
[ ] kind/clean-up
[ ] kind/bug
[ ] kind/other

Optional: Mark one or more of the following that are applicable:

[!important]
Breaking changes should be marked kind/admin-change or kind/dev-change depending on type
Critical security fixes should be marked with kind/security

[x] kind/admin-change
[ ] kind/dev-change
[ ] kind/security
[ ] kind/adr

Release notes
The configuration files are now validated against a JSON Schema.
Platform Administrator notice
When validating config against the schema you may encounter cases where they disagree on what type a field should be and it may be necessary to tweak either the config or the schema

What does this PR do / why do we need this PR?

...

Fixes #1427

Additional information to reviewers
This adds a new tool, yajsv, written in Go, which needs to be installed (bin/install-requirements.bash). Since JSON Schema is an an open specification with multiple implementations, it could be replaced in the future. We could even write our own using one of the available libraries.
To try this, run e.g.:
./bin/ck8s validate sc

The schema is mostly generated from existing defaults and is not yet completely accurate. Notably there are several "set-me" that are currently guessed to be strings when they should be something else, as well as other issues. Perfecting it may take some iterations. Please comment where you know what types are correct.
Information about JSON schema can be found at https://json-schema.org/
The specifications themselves are found at

https://json-schema.org/draft/2020-12/json-schema-core (basics)
https://json-schema.org/draft/2020-12/json-schema-validation (definitions of many kinds of constraints)

Notes about certain common schema fields:

default can be used to describe a default value, which could be used in future tooling to actually fill in default values, but for now serves as documentation.
example and examples can contain one or many example values. This could be shown in future tooling to improve UX.
format allows specifying what kind of string to expect. Common usable values include hostname, uri (for URLs etc), email. Unknown values are ignored by the validator, so common formats could be described and potentially implemented in future tooling.
additionalProperties defines schema for a property of an object that is not covered by properties, setting this to false rejects unknown values, and thus detects things that might have been missed.

Screenshots
$ ./bin/ck8s validate sc
[ck8s] Validating sc config
[ck8s] Failed schema validation:
config-sc.yaml: nodeLocalDns.customConfig: Invalid type. Expected: string, given: null
config-sc.yaml: falco.driver.ebpf.path: Invalid type. Expected: string, given: null
config-sc.yaml: certmanager.tolerations: Invalid type. Expected: array, given: object
config-sc.yaml: certmanager.cainjector.tolerations: Invalid type. Expected: array, given: object
config-sc.yaml: certmanager.webhook.tolerations: Invalid type. Expected: array, given: object
config-sc.yaml: certmanager: Must validate all the schemas (allOf)
config-sc.yaml: networkPolicies.global.externalLoadBalancer: Invalid type. Expected: string, given: boolean
config-sc.yaml: networkPolicies.global.ingressUsingHostNetwork: Invalid type. Expected: string, given: boolean
1 of 1 failed validation
[ck8s] Do you want to abort? (y/n):

Can provide validation and help messages in e.g. VS Code:

Could also be used to generate documentation:

Checklist

[x] Proper commit message prefix on all commits

Change checks:

[x] The change is transparent
[ ] The change is disruptive
[x] The change requires no migration steps
[ ] The change requires migration steps

Metrics checks:

[x] The metrics are still exposed and present in Grafana after the change
[x] The metrics names didn't change (Grafana dashboards and Prometheus alerts are not affected)
[ ] The metrics names did change (Grafana dashboards and Prometheus alerts were fixed)

Logs checks:

[x] The logs do not show any errors after the change

Network Policy checks:

[ ] Any changed pod is covered by Network Policies
[ ] The change does not cause any dropped packages in the NetworkPolicy Dashboard

Pod Security Policy checks:

[ ] Any changed pod is covered by Pod Security Admission
[ ] Any changed pod is covered by Gatekeeper Pod Security Policies
[ ] The change does not cause any pods to be blocked by Pod Security Admission or Policies

Falco checks:

[ ] The change does not cause any alerts to be generated by Falco

Audit checks:

[x] The change does not cause any unnecessary Kubernetes audit events
[ ] The change requires changes to Kubernetes audit policy

Bug checks:

[ ] The bug fix is covered by regression tests

In the pipeline, where does this falco setting come from?
[ck8s] Failed schema validation:
wc-config.yaml: falco.alerts.enabled: Invalid type. Expected: boolean, given: string
1 of 1 failed validation

Please add yajsv into check_tools and into the tests/Dockerfile.

I've created a PR with a helper to regenerate the full diff that is used for the update-ips tests.

thoughts on split vs single schema file
split schema into multiple files
pro:

easier review with smaller files
easy to validate individual sections

con:

some tools don't support external references, e.g. that documentation generation tool
some tools have poor handling of multi-file schema, e.g. doesn't report which file to look in or reports a 404 error
breaks the symmetry-ish between config and schema
reference by URL seems needlessly complicated
tools may try to download resources over the internet

single schema
pro:

simpler references, just $ref: "#/path/somewhere" instead of a full URL and needing $id
a larger schema may work as a pressure towards smaller schema, and thus smaller config with more reuse

con:

harder to review
harder to navigate?

conclusion
tools vs tools tradeoff? I prefer single file. can always switch later.

thoughts on split vs single schema file

Yeah, the single schema sounds better in this case.

pro:

a larger schema may work as a pressure towards smaller schema, and thus smaller config with more reuse

And this I especially like :grin:
I assume the idea is to still have a separate one for secrets, as we don't merge that in?

thoughts on split vs single schema file
tools vs tools tradeoff? I prefer single file. can always switch later.

Very nice summary of the pros and cons. :+1:  I agree stick with a single file.

I assume the idea is to still have a separate one for secrets, as we don't merge that in?

Yeah, assuming secrets is its own thing. Different kind of thing having its own schema seems sensible. And given the sensitive nature, keeping them separate as long as possible to minimize exposure is probably good.

Would it be sensible to split the big schema into separate PRs (one per component or such?), leaving minimal top-level bits here with the scripts?

Would it be sensible to split the big schema into separate PRs (one per component or such?), leaving minimal top-level bits here with the scripts?

That would be interesting and maybe easier to review the config file. Im open to it :slightly_smiling_face:

Would it be sensible to split the big schema into separate PRs (one per component or such?), leaving minimal top-level bits here with the scripts?

Yes, that could be a way to handle it. But then we would have to make it so that it doesn't complain about extra fields while we're at it, and then enforce it once all parts are in.

There are about 40 top level things, that would be a lot of PRs, although I see some parts that could be grouped, e.g. various metrics related things (Prometheus, Grafana, variousMetrics, -Monitoring...).
Does this grouping make sense?
global: # this, the first PR, along with the tooling
  - global
calico:
  - calicoAccountant
  - calicoFelixMetrics
ingress:
  - certmanager
  - ingressNginx
  - issuers
logs:
  - fluentd
  - opensearch
monitoring: # metrics, exporters, dashboards
  - alerts
  - grafana
  - grafanaLabelEnforcer
  - kubeStateMetrics
  - metricsServer
  - openstackMonitoring
  - prometheus
  - prometheusBlackboxExporter
  - prometheusNodeExporter
  - prometheusOperator
  - s3Exporter
  - thanos
  - wcProbeIngress
policy: # security, auth
  - dex
  - gatekeeper
  - networkPolicies
  - opa
  - trivy
  - externalTrafficPolicy
  - falco
storage:
  - objectStorage
  - rookCeph
  - storageClasses
  - velero
others: # uncertain, fold into global?
  - clusterAdmin
  - clusterApi
  - harbor
  - hnc
  - kured
  - nodeLocalDns
  - user
  - welcomingDashboard # logs or monitoring?

✅ All checks have passed

🎉
Now to add more tests specifically for schema...

could you mention some were how to setup vscode to work with the validator? 🙂

As in, enabling it here or enabling it somewhere else where you have config?
I can write some extra words about it in .../schema/README.md, it should mainly be having an already recommended plugin and some references in .vscode/settings.json

I can write some extra words about it in .../schema/README.md, it should mainly be having an already recommended plugin and some references in .vscode/settings.json

Yeah, I think it is worth mentioning that, that plugin would enable validation/help in vscode. As you basically already done in this PR description.


Add "daily" and "weekly" net/gross volume reports to Stripe dashboard

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1929
Originally created by @DouweM on 2020-03-26 23:03:54

View 5 previous comments from the original issue on GitLab


[WFCORE-5648] Assertion arguments correct order (controller)

Fixes https://issues.redhat.com/browse/WFCORE-5648
as part of https://issues.redhat.com/browse/WFCORE-5644

Thanks @boris-unckel for this one and the others related


Does not return if the command is not executable by user's primary group

Steps to reproduce:

sudo chmod o-x /usr/bin/make
sudo chown root:sudo /usr/bin/make
Run a node-gyp build from a user who is a member of group sudo, but sudo is not his primary group

(Tested on Debian 6.0.8)
node-gyp will complain about missing make, even if make is in fact executable by current user.
Related SO

Yes, we need to check against all the results from process.getgroups() if the function is available.  Patch welcome.


Disable SMP for Arm cpus.

There is an RTS SMP bug in 8.6.x and earlier which affects Arm.
https://gitlab.haskell.org/ghc/ghc/merge_requests/734

bors r+

bors r+


Custom PS prelude for library users

I was thinking it might be nice to support a custom Purescript prelude for our users
Rationale:

The PS prelude exports far less than its Haskell counterpart. This might increase friction as users try to port their off-chain code
We can select certain common (non-Prelude) types/functions to re-export that differ from what a Haskell developer might reasonably expect (e.g. Data.Semigroup.Last vs Data.Maybe.Last)
We can also export effects, types, etc... that almost all off-chain code uses

this is nice to have, especially as a guideline for your default number types.

it may cause a problem with purescript-bridge shimming though, unless we have an equivalent prelude in haskell....


bug: release menu is absent in some cases

Describe the bug
For some, not all, of the website pages, the release menu does not appear when the selected release is main.  Contrast the two attached images of the syncer doc page.  The same thing happens for the "extended example" page.  It does NOT happen on the "details" page.

vs.

Steps To Reproduce
See above
Expected Behavior
I expected to always see the release menu.
Additional Context
No response

The problem is on the quickstart page.

this is only happening in 'main' on pages that have docs-ecutable metadata on the top.  Opened an issue with 'mike' - they closed it stating it is theme related.  I am chasing down the 'material' theme folks next.  The dropdown is in the html DOM.  The behavior of removing the dropdown happens when you scroll down any of our pages.  It seems that the metadata for the 'main' branch docs-ecutable pages is causing this "scroll down" effect on default load.  I am researching a solution.

Fixed. Required packages had extra open and close code blocks in the new WSL Linux section. I am going to have another swipe at the formatting of this specific section, but for now this issue should be fixed.


Sqmagopc 447 validation setup

Prototype pull request. Meant to trigger and test coding standard validation

Close test pull request


How to make a spaceship script? (And Documentation Suggestions/Feedback)

Question 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

Hey all, I've been reading and searching the docs for a long time, and I'm having trouble figuring out how to create a spaceship script.
The docs clearly show how to play around with it using "spaceship playground" - I.E. run "fastlane spaceship", which is great for figuring out commands, however I would love to create a script.
The docs even say that "as most fastlane users won't need the spaceship playground"...
So.. it would be amazing to have any info on how to script this. For example: can I login with the playground, then just run a bash script that starts with "fastlane spaceship" and the commands will run fine?
Thanks for any help or links - googling "create fastlane script" or "create fastlane spaceship script" are surprisingly useless.
Further helpful information on the main page would be:

how to pass in command line vars to a script.
How to create a new version (in addition to (or instead of) a new app which happens once ever) (app.create_version!("1.0.0"))
Links to the extended API docs located at: https://www.rubydoc.info/github/fastlane/spaceship
Put these links on the main page! lol - https://github.com/fastlane/fastlane/blob/master/spaceship/docs/README.md

If you can help me with some of my scripting questions, and/or provide feedback, I'd like to fix up the docs a bit to add more info that I would have found extremely helpful as a first time user. Seems like finding some simple stuff is a bit harder than it should be in my opinion (trying to figure this out for the first time).
Thanks! And I look forward to any reply!

✅ fastlane environment ✅
Stack

Key
Value

OS
10.15.2

Ruby
2.6.3

Bundler?
false

Git
git version 2.14.1

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.15.2 (19C57)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib

OpenSSL Version
LibreSSL 2.8.3

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
11.3

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:ios)

platform :ios do
  desc "Push a new release build to the App Store"
  lane :release do
    increment_build_number(xcodeproj: "PracticePlayer.xcodeproj")
    build_app(scheme: "PracticePlayer")
    upload_to_app_store
  end
end

`./Appfile`
app_identifier("com.MFE.PracticePlayer") # The bundle identifier of your app
<EMAIL_ADDRESS># Your Apple email address

itc_team_id("119057288") # App Store Connect Team ID
team_id("ZAR5QX7MAH") # Developer Portal Team ID

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.139.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.3.0

slack-notifier
2.3.2

atomos
0.1.3

claide
1.0.3

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.14.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.6.0

terminal-table
1.8.0

plist
3.5.0

public_suffix
2.0.5

addressable
2.7.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.7.0

tty-cursor
0.7.0

tty-spinner
0.9.2

babosa
1.0.3

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.71.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.13.1

fastimage
2.1.7

gh_inspector
1.1.3

mini_magick
4.9.5

multi_xml
0.6.0

rubyzip
1.3.0

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.7.5

bundler
1.17.2

naturally
2.2.0

simctl
1.6.7

jwt
2.1.0

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mini_mime
1.0.2

multi_json
1.14.1

signet
0.12.0

memoist
0.16.2

os
1.0.1

googleauth
0.10.0

httpclient
2.8.3

google-api-client
0.36.3

google-cloud-env
1.3.0

google-cloud-core
1.4.1

digest-crc
0.4.1

google-cloud-storage
1.25.0

emoji_regex
1.0.1

CFPropertyList
3.0.2

faraday
0.17.3

json
2.3.0

forwardable
1.2.0

logger
1.3.0

stringio
0.0.2

ipaddr
1.2.2

openssl
2.1.2

ostruct
0.1.0

strscan
1.0.0

date
2.0.0

fileutils
1.1.0

etc
1.0.1

io-console
0.4.7

zlib
1.0.0

libxml-ruby
3.1.0

rexml
3.1.9

psych
3.1.0

mutex_m
0.1.0

generated on: 2020-01-05

Spaceship is just the underlying ruby gem that most Fastlane actions use, what I've done in the past is just create a ruby script and importing the gem into my code, i.e:
require "spaceship"
While I agree with you that the documentation is rather limited and some stuff like in app purchases and the likes is present but undocumented, I've had no problem digging into the source code. Also to use Spaceship directly instead of Fastlane you should have a very specific use case, hence the lack of available information. Have you seen this documentation pages? While it might not seem to be too much, it's a really good starting point.

Cool thanks guys, figured it out.
My confusion from reading the docs was related to the intro - I.E. "It powers parts of fastlane".
It wasn't clear to me that this wasn't a plugin or something you have to add or use.
Might be cool to add something in like "To use this, you don't have to do anything! Just install and setup fastlane for your app: . You'd reference this library to make any custom or advanced workflows you want via fastlane's custom action feature for anything that isn't already built into fastlane for you.
Or "if you don't have fastlane, you're missing the point"
I dunno, just a few tidbits. It was definitely my misunderstanding, but sometimes the new guy's impression of confusions can help future comers.


[Fix #3475] Parsing the errorMessage metadata keys in end nodes

Fix https://github.com/apache/incubator-kie-kogito-runtimes/issues/3475
See example at https://github.com/apache/incubator-kie-kogito-examples/pull/1912

PR job #7 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
build-chain build full_downstream  -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-runtimes -u https://github.com/apache/incubator-kie-kogito-runtimes/pull/3491 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3491/7/display/redirect
Test results:

PASSED: 2912
FAILED: 1

Those are the test failures:

failsafe-summary.xml.[empty]
Test report file /home/jenkins/jenkins-agent/workspace/_jobs_kogito-runtimes-pr_PR-3491/kogito-pipelines/bc/apache_incubator-kie-kogito-runtimes/quarkus/integration-tests/integration-tests-quarkus-processes-persistence/integration-tests-quarkus-processes-postgresql/target/failsafe-reports/failsafe-summary.xml was length 0


Bug: issues with selection when there are 2 or more consecutive decorator nodes

Lexical version: 0.11.3
Steps To Reproduce

Add 3 or more decorator nodes one after the other
Try to move the cursor from right to left and from left to right
Try to select the nodes using the keyboard from right to left and from left to right
Have the cursor between the 2nd and 3rd decorator nodes and hit backspace
Have the cursor between the 1st and 2nd decorator nodes and hit delete

Link to code example:
repo: https://github.com/ifrim/lexical-selection-issue

clone the repo locally
run npm i
run npm run dev
open http://localhost:5173/

The current behavior
When moving the cursor from left to right and there are at least two decorator nodes one after the other the focus is lost (goes to the root). When moving from right to left it works as expected.
When selecting using the keyboard (SHIFT + RIGHT_ARROW) from left to right and there are at least two decorator nodes one after the other the selection stops after selecting the first decorator node. From right to left works as expected.
When the cursor is between the 2nd and 3rd decorator nodes and you hit backspace two decorator nodes are deleted.
When the cursor between the 1st and 2nd decorator nodes and you hit delete two decorator nodes are deleted.
The expected behavior
Moving the cursor from left to right doesn't lose the focus and "jumps" one node at a time. (And will be consistent with moving from right to left)
Selecting using the keyboard from left to right selects all decorator nodes one at a time. (And will be consistent with selecting from right to left)
Hitting BACKSPACE or DELETE when between decorator nodes deletes only one node.
Possibly related issues

https://github.com/facebook/lexical/issues/4499
https://github.com/facebook/lexical/issues/4214
https://github.com/facebook/lexical/issues/3748

Screen Recordings
Cursor movement
https://github.com/facebook/lexical/assets/5877494/d7d9e4c1-7b7d-4321-ba53-8df1d5d483d1
Selecting using the keyboard
https://github.com/facebook/lexical/assets/5877494/546f6e8e-20a7-4945-87a8-80e669cb71c8
Deleting nodes
https://github.com/facebook/lexical/assets/5877494/90304876-528d-4036-a78e-e1b363118e99
Behavior in firefox
https://github.com/facebook/lexical/assets/5877494/b5588209-e52b-4714-b4d2-0067a2e47313
In firefox the problem is even bigger because you can't "place" the cursor between decorator nodes.

I don't think this is reproducible anymore? At least not with the inline decorator present in the playground (equation nodes)


bench.zig: Re-open perf fds for each sample instead of re-using one for all samples

PERF_EVENT_IOC_RESET doesn't seem to work properly when the inherit bit is set (which is set when the benchmark uses a child process). To get around this, we now close and re-open perf fds for each sample.
Closes #17

Note: This seems to be the better approach. I tried reading the fds before each sample and then subtracting the initial values from the final values, but I was running into intermittent cases where the end - start would end up as zero. With the approach in this PR, I haven't run into that (yet?).

Thanks for the 2 PRs! Re-running the backfill script now. Will make a note here when the new results are live.

New data is live. Thanks for the fixes! I also made the Y axes start at 0.
https://ziglang.org/perf/


Fix httpmetrics deadlock cause by panic

Which problem is this PR solving?

fix #2944
buildTimer would panic, cause lock not being release.

Short description of the changes

put unlock in defer statement. so lock can release after panic.
put httpmetrics.Wrap inside recoveryHandler. just seems to be right.

Yes, this maybe not a perfect fit for the issue.
Although at least it's a safer way of using lock. And allow other correct requests being processed.

It may be safer, but it results in invalid metrics being reported, especially if requests fail for other reasons than the bad characters.

I think metrics would be droped after panic from promethues, not sure though.
I still think this could be usefull. I have being using jaeger collecting opentelemetry spans. And every few hours my service got a ileagle url ( from Network scanning which is not part of my services ). Then collector would stop responding http 202 to opentelemetry client causing timeout and drop spans. And collector memory useage increase over time.  Stay in this state untill OOM kill. Take me days to find this cause.
I would argure that this may save others some time locating this problem in a similar network environment.

It may be fixing one specific issue, but it's a dirty fix as it introduces other issues. I have a cleaner fix in #4051.


Master

Spatial Mapping updates (part 1).
This updates addresses issue #146. The SpatialMappingRenderer and SpatialMappingCollider components are now provided by Unity and do not need to be in the HoloToolkit.

Getting this into the build quickly to make room for the larger Spatial Mapping changes coming next....


Unhandled exception happened

safety version: 2.3.1
Python version: 3.7
Operating System: Linux archlinux 5.18.16-arch1-1

Description
Got this when decided to upgrade from safety:1.10.3. Any ideas why it happens?
What I Did
safety check -r requirements.txt
Unhandled exception happened: parse() got an unexpected keyword argument 'resolve'
ERROR: InvocationError for command /home/ar0ne/Codes/superpedestrian/sp-web-billing-service/.tox/py37/bin/safety check -r requirements.txt (exited with code 1)

Hi, probably you have the wrong dparse version. try with the latest dparse version and let me know the result.

Good catch! Thanks!


Rainbow and Sitecore 9

Do you want to request a feature or report a bug?
bug
What is the current behavior?
I'm working in a solution based on Sitecore 8.1 and I am trying to upgrade to Sitecore 9. In the Analysis process, I receive several warnings of Rainbow, for example:
<shortdescription>Type Rainbow.Settings.RainbowSitecoreSettings from assembly Rainbow uses the type that has got breaking changes.</shortdescription>

<description>The type Sitecore.Configuration.Settings defined in assmebly Sitecore.Kernel has got breaking changes. Custom type Rainbow.Settings.RainbowSitecoreSettings defined in assembly Rainbow uses the changed type in System.Int32 get_SfsSerializationFolderPathMaxLength() and might be affected.</description>

Is Rainbow compatible with Sitecore 9?
If yes, any reason why we are receiving these warnings? How we could avoid them?
In case we cannot overcome this we will remove Unicorn from our solution, install Sitecore 9 and then install Unicorn again but we would really prefer to solve this issue first.
What is the expected behavior?
There are no warnings in the Analysis result in the Update Installation Wizard
Please mention your Sitecore version, Rainbow version, and if also using Unicorn, your version of that too.
Sitecore 8.1
Unicorn 4.0.3
Rainbow 2.0.0

Yes it is compatible with Sitecore 9.

From: csoler46<EMAIL_ADDRESS>Sent: Thursday, June 14, 2018 4:07:36 AM
To: SitecoreUnicorn/Rainbow
Cc: Subscribed
Subject: [SitecoreUnicorn/Rainbow] Rainbow and Sitecore 9 (#23)
Do you want to request a feature or report a bug?
bug
What is the current behavior?
I'm working in a solution based on Sitecore 8.1 and I am trying to upgrade to Sitecore 9. In the Analysis process, I receive several warnings of Rainbow, for example:
Type Rainbow.Settings.RainbowSitecoreSettings from assembly Rainbow uses the type that has got breaking changes.
The type Sitecore.Configuration.Settings defined in assmebly Sitecore.Kernel has got breaking changes. Custom type Rainbow.Settings.RainbowSitecoreSettings defined in assembly Rainbow uses the changed type in System.Int32 get_SfsSerializationFolderPathMaxLength() and might be affected.
Is Rainbow compatible with Sitecore 9?
If yes, any reason why we are receiving these warnings? How we could avoid them?
In case we cannot overcome this we will remove Unicorn from our solution, install Sitecore 9 and then install Unicorn again but we would really prefer to solve this issue first.
What is the expected behavior?
There are no warnings in the Analysis result in the Update Installation Wizard
Please mention your Sitecore version, Rainbow version, and if also using Unicorn, your version of that too.
Sitecore 8.1
Unicorn 4.0.3
Rainbow 2.0.0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/SitecoreUnicorn/Rainbow/issues/23, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAGU_RNRgroR3e9vQBt9XqWtfmvwCOb5ks5t8kP4gaJpZM4Unwhs.

It's just a warning. As it says; "it might be affected". Key here is "might". I currently run and test Unicorn and Rainbow on Sitecore 9 without issue.


fix(state): state list on filter toolbar is fixed

Note: If there are pending changes to the PR, prefix the PR title with "WIP" and add the label "DO NOT MERGE"
Mandatory

[ ] What does this PR do?

[ ] What issue/task does this PR references?
https://github.com/openshiftio/openshift.io/issues/3441

[ ] Are the tests Included?

Optional

[ ] Is the documentation Included?

[ ] Are the Release Notes included?

[ ] @mention(s) to expected reviewer(s) included

[test]

@sanbornsen Your image is available in the registry. Run docker pull registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2613 && docker run -it -p 5000:8080 registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2613 and visit http://localhost:5000 to access it.


Implement _writev for the bunyan write stream

This adds support for _writev to allow bulk writing from the WritableStream.
Fixes: #2135

Coverage remained the same at 100.0% when pulling 5baf51b2ae93fd82408634e0f0146876c0fd30df on ofrobots:bunyan-writev into 021a97d2a6722e55a595ada3f1b83807e9c2af59 on GoogleCloudPlatform:master.

@ofrobots we have a broken system test:
1) LoggingBunyan should properly write log entries:

      Uncaught AssertionError: 0 === 4
      + expected - actual

      -0
      +4

      at system-test/logging-bunyan.js:122:16
      at node_modules/@google-cloud/logging/src/index.js:318:5
      at node_modules/@google-cloud/logging/node_modules/@google-cloud/common-grpc/src/service.js:318:5
      at onResponse (node_modules/@google-cloud/logging/node_modules/@google-cloud/common-grpc/node_modules/retry-request/index.js:120:7)
      at Object.callback (node_modules/@google-cloud/logging/node_modules/@google-cloud/common-grpc/src/service.js:307:11)
      at node_modules/@google-cloud/logging/node_modules/@google-cloud/common-grpc/node_modules/grpc/src/node/src/client.js:439:14

Would you mind taking a look?

Ack. Looking.

https://github.com/GoogleCloudPlatform/google-cloud-node/pull/2201. Apologies for not running the system test.


Cleanup double empty lines

It would be nice if there is a config about how many empty lines in a row are allowed.

duplicate of #63


 I want the iOS Swift packages to be able to pull any KMM module as a Swift package. I am using spm configuration for this:
kmmbridge {
  spm()
}

However this throws with:
You must apply an artifact manager! Call `artifactManager.set(...)` or a configuration function like `githubRelease()` in your `kmmbridge {}` block.

The plugin seems to require artifact and version managers even though I have no use for them. Is there any reason why we would not want to make them optional for a use case like mine?
Meanwhile adding github managers seems to work, though I am not use them:
kmmbridge {
  spm()
   githubReleaseVersions()
   githubReleaseArtifacts()
}

The intended use of the plugin is for managing published binaries. If you're not doing that, all you're really getting is package file generation. I'm going to close this for now but we're doing some thinking about local SPM development flow that might address the root need in the future.


Change number-type-mapping for AsnUint8Codec and AsnUint16Codec

In order to (de)serialize the CCP to/from ASN.1 OER, it is necessary for the Java codecs to support Uint16 datatypes (in order to (d)encode the identifier of a route-property).
This ticket proposes to do this by modifying the underlying Java data-type of AsnUint8Codec and AsnUint16Codec to be Short and Integer respectively.
In this way, if we want to write Java code (using the current codec framework) that emits an 8-bit number (in a single octet), we would use a Short. If we wanted to write Java code that emits a 16-bit number (2 octets), we would use an Integer, and so on. The following illustrates the new proposed mapping of ASN.1 OER datatypes to Java number types:

8-bit Fixed Length Number (1 octet) --> Short [changed]
16-bit Fixed Length Number (2 octets) --> Integer [changed]
32-bit Fixed Length Number (4 octet) --> Long [unchanged]
64-bit Fixed Length Number (8 octet) --> BigInteger (if X <= 2^64-1) [unchanged]
Var Octets Number --> BigInteger (if X > 2^64-1) [unchanged]

@adrianhopebailie Any thoughts on this one?

Makes sense. In considering your comments from #164 I wondered if we should have default mappings to native types at all?
Maybe we should encourage any project that uses the framework to create their own context and therefor their own codec -> type mappings?

Maybe we should encourage any project that uses the framework to create their own context and therefor their own codec -> type mappings

This is an interesting concept. I think we should probably keep a default mapping, but perhaps add better documentation around customization? I'm thinking that the change proposed by this ticket will allow us to support all use-cases, although we'll know more once I finish the CCP codecs.


fix: make order of annotations stable

range is iterating through map in random order. Switching to slice.

/approve


Read only fields not to focus on tab key.

Hello,
please guide me.
Read only fields not to focus on tab key. It only focus on Editable fields.

tabindex="-1"

@volkanceylan Please help me

@Zahar661 Not working tabindex="-1".
Please help me.

how did you use tabindex= "-1"? Works, I checked.

@Zahar661 In above figure. in dialog some of fields are readonly. so i have to make tab key not to focus on readonly fields. it have to focus on editable fields.

So have you tried the fields for reading add "tabindex='-1'"?

in editmode()
this.form.InvoiceNo.element.attr("tabindex", 1);
is this correct?
@Zahar661

No
protected updateInterface(): void {
            super.updateInterface();
            this.element.find('.readonly').attr("tabindex", -1);
        }

Suppose first field is readonly and second field is editable then?
@Zahar661

tabindex= '-1' will be set for all fields that are read

Ok


_CastError in EditableTextState._updateSelectionRects

Unfortunately, I don't have a reproduction scenario, but I'm seeing this exception >100k times in analytics. It appears to have started after upgrading from Flutter 3.3.2 to 3.3.7. It happens exclusively when Flutter is used without UI (in a geofence handler) on Android (versions 12, 13, 11, 10)
_CastError: Null check operator used on a null value
editable_text.dart in EditableTextState._updateSelectionRects.<fn> at line 2985

[!] Flutter (Channel unknown, 3.3.7, on macOS 12.5.1 21G83 darwin-arm, locale en-NL)
    ! Flutter version 3.3.7 on channel unknown at /Users/sander/Development/hue_blue2/dev/flutter
    ! Upstream repository unknown
    • Framework revision e99c9c7cd9 (3 weeks ago), 2022-11-01 16:59:00 -0700
    • Engine revision 857bd6b74c
    • Dart version 2.18.4
    • DevTools version 2.15.0

Hi @spkersten

It happens exclusively when Flutter is used without UI (in a geofence handler)

Can you share more information about this? It could be better if you can provide a snippet sample code to reproduce it.
Also, to be more precise, please provide the information indicated below:

A completed stack trace if any
The list of affected device info
The percentage occurrence of the crash

Thank you!

Affected devices seem to be Manu different Samsung devices and Pixel 6, Pixel 5 (seemingly the overal most popular devices).
The stack trace has only the single line I quoted unfortunately.

Thanks for providing more information. Labeling this issue for further investigation from the team.

@justinmc

CC @LongCatIsLooong

@spkersten Can you include any more details from the stacktrace?
I fixed a CastError recently but seems different: https://github.com/flutter/flutter/pull/112590

crash site: https://github.com/flutter/flutter/blob/3.3.7/packages/flutter/lib/src/widgets/editable_text.dart#L2985
I recently changed the implementation and the ! that caused the crash doesn't exist on master: https://github.com/flutter/flutter/pull/113425, so that probably fixed the crash too.
But the old code doesn't seem to be problematic, it should be safe to use ! there?
      ).where((SelectionRect? selectionRect) {
        if (selectionRect == null) {
          return false;
        }
        if (renderEditable.paintBounds.right < selectionRect.bounds.left || selectionRect.bounds.right < renderEditable.paintBounds.left) {
          return false;
        }
        if (renderEditable.paintBounds.bottom < selectionRect.bounds.top || selectionRect.bounds.bottom < renderEditable.paintBounds.top) {
          return false;
        }
        return true;
      }).map<SelectionRect>((SelectionRect? selectionRect) => selectionRect!).toList();

@spkersten are you still seeing the exception in analytics?


Enable custom cache key

I find the custom key is ignored.  The key is saved in the this._key, however it's not used in the getCacheKey.

Hey goodfind missed this one, but let's make some changes
if (this._key != null) return this._key

Will be fixed with: https://github.com/ilovepixelart/ts-cache-mongoose/pull/134

Released in: https://github.com/ilovepixelart/ts-cache-mongoose/releases/tag/v1.4.1


Earliest compatible node version is not 0.10

The README states that tap works on any version of Node.js back to v0.10.   In reality the library now uses const and fat arrow functions and does not work for node version prior to 4.
It might be helpful to update the  README to explicitly state the earliest node version supported (I think it's 4) and possibly provide a link to the latest possible version of tap that  that supports v0.10 and up.
Any library that wants to maintain v0.10 backwards compatibility tests will have to pin tap to an old version.
For example I'm not able to use the latest version here and will have to revert back to the old tap.

Yes, that is an oversight in the documentation. Node 0.10 is out of LTS, and insecure to continue using. Doc patch welcome, or I’ll fix soon.


Work in Progressive Web App

Hi!
Will this work in PWA?
I have tried some, but can't get it to work.

Hi, 5.1.8 adds the W3C WebShare API, that may help. Other than that I don't know what you'd like to see changed.


Flowistry outputs nonsense on Windows

Problem
after I download and install successfully. VS gave me the error.
Logs

OS: win32 (10.0.19043)
VSCode: 1.61.2
Error message
'D:\Program' �����ڲ����ⲿ���Ҳ���ǿ����еĳ���
���������ļ���

Full log: https://paste.rs/P3z

Oh my! That's quite the error.
I will note that Flowistry does not have first-class support for Windows yet. I tried it briefly on a VM and found a bunch of strange errors that don't show up in Linux or OSX. I will ping this issue though if I do get around to supporting Windows!

Hi @1221long, are you still having this issue? On current builds of the VS Code extension, I can't reproduce your problem.

This should be fixed now.


SCTO-11089: Release new enumerator-related translations in web forms (for 2.72)

@jkdamilola , @nabilahamdaou , could you please take a look at this one?
Thanks!

Thank you!


Typo ;)

Hey
Just found a typo in naming the corn.php which i guess should be cron.php ?

@alijafari-gd
Thanks, fixed it.


Querying by column values?

Thanks for this great tutorial. I only wish it would have shown how to query the data by specific column values. For example, show me a planet of a given name or all the planets with gravity > X.
Regards,
Alvaro

Hi @alvaro1728
Indeed these are important features of GraphQL. I personnally stopped to use Flask/Graphene and switched most of my projects to PostgreSQL and PostGraphile which automatically generates a feature complete GraphQL API. It includes in particular the features you mentioned above and even more. You should check this other tutorial ;) https://github.com/alexisrolland/docker-postgresql-postgraphile


Reduce size of Docker images

The Docker images are much larger than the official ones:
$ docker images | grep trino
docker.stackable.tech/stackable/trino        362-stackable0                 4a6cc6f9f9dd   2 weeks ago     4GB
trinodb/trino                                362                            8c4c3cc8b6b5   2 months ago    1.33GB

The size of the images should be decreased to speed up the download. This would also make the integration tests faster and decrease the chance of hitting timeouts.
One possible optimization is to not rename the installation directory in a separate layer:
RUN mkdir /stackable/trino-server && \
    mv /stackable/trino-server-${PRODUCT}/* /stackable/trino-server && \
    rm -rf /stackable/trino-server-${PRODUCT}

See also https://github.com/stackabletech/issues/issues/149
This ticket is only about fixing the immediate issue of having Docker images that are over twice the size they need to be.
There are more improvements to be made in the CI pipeline later but this is not the ticket for hat.


Replacement input system

Component to Improve
Core Engine
Describe Your Suggestion
The current input system is not very flexible and kinda sucks to work with. We should replace it with something else.
Here's a list of possible replacements I've found to handle inputs:

input_lib
SDL (yes this is extremely overkill but it IS still a valid option if all else fails)
and of course there's always the option of just rewriting what we have

feel free to add any other suggestions here this is just what I found from searching

I would rather rewrite what we have tbh
It would be best to make input mappings that aren't defined in code, but defined by the user I think
Handling input cannot be too hard compared to other engine tasks

We're going to use SDL once #39 is in, but we still need our own system on top of it to keep everything pretty looking
It would be great if we could just copy how Godot does it but mix it up a bit, where keys, buttons, joysticks, etc map to a single named action specified in a config and you can register/deregister hooks into that named action (or check if that action is being fired in the update function, which is also more like Godot and is probably more scripting-language friendly but might be slower depending how it's implemented)


Fix iPython breakage

Fixes https://github.com/Textualize/rich/issues/3013

Codecov Report
Patch coverage: 100.00% and project coverage change: -3.09% :warning:

Comparison is base (80e66aa) 98.29% compared to head (ea1129a) 95.21%.
Report is 1 commits behind head on master.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3065      +/-   ##
==========================================
- Coverage   98.29%   95.21%   -3.09%
==========================================
  Files          74       74
  Lines        8037     7981      -56
==========================================
- Hits         7900     7599     -301
- Misses        137      382     +245

Flag
Coverage Δ

unittests
95.21% <100.00%> (-3.09%)
:arrow_down:

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

Files Changed
Coverage Δ

rich/pretty.py
96.67% <100.00%> (+0.26%)
:arrow_up:

... and 10 files with indirect coverage changes

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


Frontpage updates

@forrestkim before merging, am just waiting on

card spacing tweak to make the three-line text as two lines
add a little bit of padding between news items

Hoping to get a bit of feeback from Vineet on this before our Thursday meeting.
The FAQ and Getting Started pages can go into a separate branch whenever they are ready for me to add some content to.

@jluebeck I've made the requested changes and added capability for using the CMS. I will add the documentation to the readme when it is ready. Otherwise it should be good to go


Fix panic on invalidPayloadError.Error()

Creates a new error for when SSE data has length == 0

Signed-off-by: Swetha Repakula<EMAIL_ADDRESS>

Thanks, @crhino and @swetharepakula! Makes sense, prioritizing for the Diego team to review.
Best,
Eric

Closing as accepted.


Synology - no hidraw support

Hi all
I am running Home Assistant in a Docker container on a Synology server running DSM 7 OS. Unfortunately, it does not support the hidraw interface, only the hiddev. Is it possible to add support for hiddev to your integration, beside to hidraw? Or maybe you konw a hack how to add the hidraw support to DSM OS?
Some details on my configuration
# uname -a
Linux synology 4.4.180+ #42661 SMP Mon Jun 27 15:08:06 CST 2022 x86_64 GNU/Linux synology_r1000_rs422+

# lsusb -Ie
|__usb1          1d6b:0002:0404 09  2.00  480MBit/s 0mA 1IF  (Linux 4.4.180+ xhci-hcd xHCI Host Controller 0000:04:00.3)
                   (EP) 00: Control  attr 00 len 07 max 040
 1-0:1.0          (IF) 09:00:00 1EP  () hub
                   (EP) 81: Interrupt (256ms) attr 03 len 07 max 004
  |__1-1         f400:f400:0100 00  2.00  480MBit/s 200mA 1IF  (Synology DiskStation 7F0025A35F3F6D46)
                   (EP) 00: Control  attr 00 len 07 max 040
  1-1:1.0         (IF) 08:06:50 2EPs () usb-storage host7 (synoboot)
                   (EP) 02: Bulk  attr 02 len 07 max 200
                   (EP) 81: Bulk  attr 02 len 07 max 200
  |__1-2         16d6:0008:0107 00  2.00   12MBit/s 100mA 2IFs (Jablotron ltd JA-100 Flexi xxxxxxxxxxxxxx)
                   (EP) 00: Control  attr 00 len 07 max 040
  1-2:1.0         (IF) 03:00:00 1EP  () usbhid
                   (EP) 81: Interrupt (1ms) attr 03 len 07 max 040
  1-2:1.1         (IF) 08:06:50 2EPs () usb-storage host8 (usb1 usb2)
                   (EP) 02: Bulk  attr 02 len 07 max 040
                   (EP) 82: Bulk  attr 02 len 07 max 040
|__usb2          1d6b:0003:0404 09  3.00 5000MBit/s 0mA 1IF  (Linux 4.4.180+ xhci-hcd xHCI Host Controller 0000:04:00.3)
                   (EP) 00: Control  attr 00 len 07 max 040
 2-0:1.0          (IF) 09:00:00 1EP  () hub
                   (EP) 81: Interrupt (12ms) attr 03 len 07 max 004

# lsmod | grep -i hid
hid_generic             1321  0
usbhid                 26319  0
hid                    90279  2 hid_generic,usbhid
usbcore               200140  9 etxhci_hcd,usblp,uhci_hcd,usb_storage,ehci_hcd,ehci_pci,usbhid,xhci_hcd,xhci_pci

# modprobe hidraw
modprobe: FATAL: Module hidraw not found.

# dmesg | grep usb
[   24.056711] usbcore: registered new interface driver usbfs
[   24.062220] usbcore: registered new interface driver hub
[   24.067551] usbcore: registered new interface driver ethub
[   24.073049] usbcore: registered new device driver usb
[   24.282429] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[   24.618048] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[   24.887089] usb 1-2: new full-speed USB device number 3 using xhci_hcd
[   32.353821] usb-storage 1-1:1.0: USB Mass Storage device detected
[   32.353880] scsi host7: usb-storage 1-1:1.0
[   32.353951] usb-storage 1-2:1.1: USB Mass Storage device detected
[   32.353997] scsi host8: usb-storage 1-2:1.1
[   32.354050] usbcore: registered new interface driver usb-storage
[   32.735644] usbcore: registered new interface driver usblp
[   32.762277] usbcore: registered new interface driver usbhid
[   32.762278] usbhid: USB HID core driver
[   32.772221] hid-generic 0003:16D6:0008.0001: hiddev0: USB HID v1.11 Device [Jablotron ltd JA-100 Flexi] on usb-0000:04:00.3-2/input0

Exactly same issue. I tried to enable support usb on synology, but no success.

It seems, that synology will never support hidraw. So I ended up with using HAOS virtual machine.


Homepage Layout

User Story
As a website visitor, I want to be able to access the homepage of the website with a clear and captivating layout so that I can access the latest information and learn about the mission of CSSA.
Acceptance Criteria

The homepage includes a hero image/banner upon entry to captivate the attention of visitors.
The homepage includes a highlight section for a description of CSSA, its latest news/events and other pertinent information.
The homepage includes a footer with links to CSSA social media and a newsletter signup field.

Priority
High
Story Points
8

Increased task size after reviewing.
Modified story points in consequence.

Designed


Does not work with chrome

Yesterday the extension worked, but today it no longer allows you to mark up more than 100 locations (and my already 132 marked up locations are lost). Can anyone check what happened?

It doesn't work on Firefox anymore either.
To be more specific, the extension use to work randomly. Sometimes do, sometimes don't. I keep pressing F5 to update the Elden Ring map genie page, and it doesn't work anymore. Yesterday it was working "fine", but now, map genie doesn't even recognise the extension installed.

I tested the latest version of my extension on Firefox and it still works for me.
Maybe if one of you guys can provide an error log?, Can help me find the issue.
And you can always check if your stored map markers are still saved in LocalStorage.
It should be saved under the key mg:game_<gameid>:user<userid>:v5.
The game id can be found by typing game.id in the browser console, And for the user id user.id.
(Make sure to check and remove vulnerable information before sending a screenshot!)
Also wanted to say that I'm currently rewriting the extension using manifest v3, So it could potentially fix the issue.
But I'm not able to tell when its gonna be finished at the moment.

So, let me explain:
As you can see in the image, sometimes when i open the Elden Ring map genie, the page doesn't even load. It keeps loading and never ends.

So, if i hit F5 a few times, the page loads but the addon doesn't work, as you can see here:

I learned that if i duplicate the current browser tab (by holding ctrl + drag left click), the addon loads and can fully work.
as you can see in the image, it's working:

Also, i wouldl ike to mention that my preset keeps being duplicated, and i don't know how:

Let me know if you need more screenshots.

I'm gonna close this issue in favor of the latest release. A new issue can always be posted if it turns out it still doesn't work as intented.