text:
MUI integration not working in production build

"@mui/material": "^5.10.14",
"tss-react": "^4.4.4"
So, here's the deal boys, per your docs, mui theme integration is supposed to work out of the box, but this doesn't seem to be the case. Here's a simple example showcasing the issue.
import { useTheme, ThemeProvider, Theme } from '@mui/material';
import { makeStyles } from 'tss-react/mui';

const useStyles = makeStyles<Theme>()((tssTheme, muiTheme) => {
  console.log(tssTheme, muiTheme, tssTheme === muiTheme);
  // spoiler alert: tssTheme !== muiTheme, what's more, there's barely any similarity between the two
  return {
    ...some styles
  }
})

const ChildComponent = () => {
  const theme = useTheme();
  const { classes } = useStyles(theme); // I passed the mui provided theme as props for easier comparison.
  console.log(theme);
}

const ParentComponent = () => <ThemeProvider theme={{ makeStyles: 'Wont load me in production', useTheme: 'Will load me in production' } as unknown as Theme}>
    <ChildComponent />
  </ThemeProvider>

The theme in makeStyles seems to be the default mui theme.

Problem solved?

I'm having this exact same problem, where tss-react's makeStyles's version of theme is the default MUI theme, while MUI's useTheme returns the actual/correct theme that was set in <ThemeProvider />. @raegen did you figure out a fix or workaround for this?
If not, @garronej, do you have any ideas why this would happen? My setup is fairly similar to the example above, where my test app simply does <ThemeProvider theme={theme}>...</ThemeProvider>, and it's installing and importing my package that used tss-react/mui's makeStyles separately. My test app does not have its own version of tss-react. I followed the package definitions suggested here https://docs.tss-react.dev/publish-a-module-that-uses-tss. (My package is not yet published, but I hope to publish it soon, and this would be a blocker for it rolling it, of course.) Thanks in advance!

Hello @sjdemartini,
The issue you're experiencing might stem from your module not utilizing the same MUI distribution. MUI, akin to tss-react, provides both ESM and CJS distributions. It's likely that your module uses node_modules/@mui/material while the main module operates on node_modules/@mui/material/esm.
The concurrent existence of these two module systems often poses challenges for NPM module publishers. A viable solution is to publish your module in both ESM and CJS formats.
It's crucial to specify the exports for both ESM and CJS (for require/import). You can refer to this example here:
https://github.com/garronej/tss-react/blob/f12238858b401a1c5a14538c5148ea1fd2fa9845/package.json#L9-L51
Alternatively, you can use a wildcard as demonstrated here:
https://github.com/garronej/tsafe/blob/6d08839c3b0695edbc3443d21b256043cd98787b/package.json#L67-L78
Remember to compile for both ESM and CJS:
https://github.com/garronej/tss-react/blob/f12238858b401a1c5a14538c5148ea1fd2fa9845/package.json#L54
A recommended approach is to maintain a separate tsconfig.json file for CJS and a tsconfig.esm.json for ESM, where the latter extends the former. Refer to these examples:

CJS
ESM

For your convenience, I have a project starter specifically designed for bootstrapping NPM modules:
https://github.com/garronej/ts-ci
I hope this guidance proves useful. Please let me know how it works out for you.

Hm, I take it back, it's still not working properly in my test app that uses link: to install my package that uses tss-react. The theme is correct/consistent with MUI's useTheme function, when called from inside my app and from inside my imported package in my app. (i.e. both the app code and external package code both match the theme used with <ThemeProvider />.) But for tss-react's makeStyles styles specifically, the theme is always the default, for the usage of makeStyles in the imported package. The tss-react styles do not update when I change the theme passed to the ThemeProvider, though other MUI styles do.
I am using ES modules for both my test app and my package. Compiling to CJS didn't seem to make a difference, and I've had the TS esModuleInterop option set to true as well. 😕

Understanding the Implications of Using Vite/Rollup for Library Building

While bundling a module might appear to be a good strategy, it's generally seen as less than ideal. The best practice is to reserve bundling for the final application, not the libraries. It appears there might be a complication with your current bundle, possibly due to the inclusion of MUI. This could result in duplicate copies of MUI within your final application. If this is happening, they won't be sharing the same context.
Bundling is primarily the responsibility of the final application. When a library is bundled, it restricts the end-user's ability to selectively choose components from your library. Moreover, it can also lead to unnecessary inclusion of dependencies that could have otherwise been deduplicated.

Module-level Directives and Bundling Issues: "use client"

The error message you've encountered is a clear indication that you're bundling tss-react. If you are getting this message while building your library, we have our explaination.

Hm, I take it back, it's still not working properly in my test app that uses

However, there's no need to feel disheartened. We will work through this together. If you could provide a link to your project, I'd be able to better diagnose the problem.
Please don't take my comments as overly critical. I've known many skilled developers who have made similar errors when first attempting to publish modules. The reality is that there's a scarcity of comprehensive resources that effectively explain how to publish NPM modules. Most of us, including myself, have had to learn through a process of trial and error.

Thanks again garronej, super helpful comments, and you were correct about the issues! I have a clearer understanding now of how the building/bundling/publishing processes work. For what it's worth, I was thinking the Vite+rollup-based bundling approach was sensible based on a couple other examples I'd seen (such as mui-datatables which uses tss-react, and react-hook-form which is a fairly popular library I've used), but it makes sense to simplify and generate the publishable code using tsc alone, leaving bundling for the final application.
The bundling was one issue with my approach, but the other was that I was using "my-package": "link:../" to install my package from my separate test application (with pnpm). I didn't realize that link: does not "install" the package, but rather links the entirety of the project and its underlying node_modules, which contributed to having two instances of MUI (and two of React as well, which I'd previously worked around by also linking React, which should have been a red flag!). I've simplified to use file:../ instead (or can get equivalent behavior with pnpm's workspace:../ along with dependenciesMeta.*.injected).
So with a build step similar to yours (packaging cjs and es separately using tsc), and with file: based install in my separate app, it's now working properly. 🙇

Onward and Upward! 🚀
I'm extremely pleased that we managed to resolve this issue. Congratulations on assembling all the pieces!
I will reference this discussion in the TSS documentation.
Here's an additional note for those wishing to publish a module compatible with all environments (this doesn't specifically pertain to your library, @sjdemartini).

If you intend for your library to function with node in module mode, there's an additional step you need to undertake. This involves renaming all .js files from the esm distribution to .mjs.  Also, all imports must be executed using the .mjs extension (import "./foo" -> import "./foo.mjs"). This is the function of the js2mjs script.

Furthermore, you may wish to publish a native distribution for Deno. For this purpose, you can utilize Denoify.

@garronej I just wanted to say thank you again for your help in getting the above issues with building/packaging/publishing resolved. I've now published several early versions of my package https://github.com/sjdemartini/mui-tiptap which is using tss-react, and I'm using it in an external application, and it's been working great! Really appreciate you taking the time to provide guidance! 🙏

Thanks a lof for the feedback!
tiptap looks great!

authors: garronej raegen sjdemartini

repo: garronej/tss-react


text:
makeStyles in material-ui allows for passing a classes object

We've been making styles extendable by something like this:
export type UseStyles<T extends (...args: never[]) => unknown> = {
  classes?: Partial<ReturnType<T>['classes']>
}
const useStyles = makeStyles({ name: 'FixedFab' })((theme: Theme) => ({
  root: {
    width: '100%',
  },
}))

type ComponentProps = UseStyles<typeof useStyles>

function Component(props: ComponentProps) {
  const { classes } = useStyles(props)

  return
asdf

}

function ExtendingComponent() {
  return <Component classes={{ root: 'foo' }} />
}

It currently isn't possible to pass the classes prop, might this be something that can be added?

Ok let me have a look.

I have released a new utility useMergedClasses in v3.3.0. Hope if fits your needs.
Could you please refer me where this property of makeStyles was documented in material UI v4, couldn't find it?

Wooo that was fast! 🎉
It was documented here: https://v4.mui.com/styles/advanced/#makestyles

Thank you for pointing this missing feature out. I wasn't aware of its existence but it's a nice addition.
The migration guide should be updated soon.
Best

source: gharchive/issue

authors: garronej paales

license: MIT

license_type: permissive

license_source: github-api


text:
Set location to admin's default on meal create page

When manually creating 63 meals at a time, it can be really helpful to have to think about selecting fewer options.
I'd like to see the location field filled in by default, picked up by the person who is creating the meal.
Originally created by Willie Northway at 2015-12-30 14:04, migrated from redmine-#3890

Given that we now have multiple locations per meal (dining room and kitchen)
this becomes more difficult. I'd rather put energy toward a batch import
feature.
By Tom Smyth at 2016-05-14 05:43

Status changed from New to Cancelled

By Tom Smyth at 2016-05-14 05:43

repo: gather-community/gather


text:
How to access reference file from Cloud Storage

Should I download reference files locally or is it possible to access them remotely? In that case, how can I do that?

If you plan to run the workflow locally then you'll need to download the files. If you plan the run the workflow on the google cloud platform then you wont need to download the files. It might be possible to use gatk4 NIO but that would require some edits to the workflow, if your intersted in NIO please ask your question in the wdl/cromwell forum. And in general please direct questions to the Gatk forums (GATK, Firecloud, WDL+Cromwell)
Link to (How to) Execute Workflows from the gatk-workflows Git Organization tutorial
Hope this helps

Thank you, I'll post further questions there.

authors: bshifaw romagnolid


text:
Ability to modify Graphite metric path

Hi,
Is there an ability to modify Graphite metric path? I'm running several Gatling processes in parallel and due to that my results are being overwritten. I'd like to add some unique value for each process.
Thanks.

Hi,
Please use our community google group for such questions, not the bug tracker.
Thanks

authors: kamsz slandelle

repo: gatling/gatling


text:
Allow to change the escapeChar of a csv feeder

This should do the trick. However, I must say that being fully compliant with the RFC as the default would have make more sense but would break backward compatibility.
Also, it might be possible that specifying no escape char instead of using \0 is cleaner.

Your code doesn't compile... :)
Then, you didn't get me:

I'm fine with sticking to RFC as the default behavior. We'll just have to mention it in 2.2.
Please:

change separatedValues to accept a new parameter of type Option[Char]
overload other methods such as csv with to it can also take a new parameter of type Char. You'll probably have to overload several times because of the rawSplit default value (can't have more than one).
compile and pass the tests

I made it compliant with the RFC by default. I've also started to implement it with an Option but found myself blocked by my lack of Scala knowledge. So I'm sorry but I'll have to let you fill the holes.

@henri-tremblay Back from travel.
Now that I can see the whole code, I realize that passing an Option would make duplicating all DSL methods many times because of the parameter default values. And we can't expect standard users to pass an Option themselves.
It would be cleaner to have a builder pattern for passing all those options, but sadly, it would break some other use cases, for example people using a parser to gain direct to parsed data (records field). So, it would make them change their code and explicitly call the final build method. That's maybe something we'll do in a future major version if proven useful, but we'll now stick with the current design.
I'm going to pick from your PR, and direct pass a Char, with a 0 default value (which is the noop default value Jackson uses underneath).
Thanks

Closed by #2833

source: gharchive/pull-request

authors: henri-tremblay slandelle


text:
Without Node

some topic  has a this without node tag.what does this mean?

The Without Node label was just a reminder for me. Since it only works with a specific naming convention, I'll remove it soon.

repo: gaug-cns/ros-control-center

license_source: bigquery


text:
Improve signal handling

🦟 Bug fix
Summary
This mainly deals with the problem where a signal is ignored if it occurs right before ServerPrivate::Run is called because we generally rely on the running variable to know when to stop, but that variable is set to true at the beginning of ServerPrivate::Run.
Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.
🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸

checking what's a good way to test this? Launch gazebo then verify ctrl + c signal is handled right away?

This mainly improves signal handling when Gazebo starts up. So the best way to test it would be to start Gazebo in server mode (gz sim -s empty.sdf) and type ctrl+c in the first few seconds. Without this PR, I noticed the signal would sometimes be completely ignored.

That can be addressed separately.

I'm hoping some of the remaining issues are related to https://github.com/gazebosim/gz-common/pull/618, but there might be other instances of timing.

repo: gazebosim/gz-sim


text:
Many optional sections in the metadata are marked with *

The * implies they are required, but they are not.
e.g.
Geographic Coverage → Descriptoin
Associated Parties → Position, Organization
Project Data → Title
Sampling Methods → Study Extent, Sampling Description, Step Description
Citations → Resource Citation
I think in several of these cases the fields are required once part of the section is filled in, e.g. the project must have a title.  Can this be expressed in Javascript or with the HTML form validation that didn't exist when these forms were originally designed?

Thanks Matt.
We can just remove those asterisk if we want to. IPT EML validation will be working fine as before

We are getting error messages if Geographic description is not filled out. Is it required?

Ping @sannegovaert

repo: gbif/ipt


text:
Add support for CP437

Adds support for Code Page 437 character encoding.
I wasn't entirely sure what the best name to describe it by was.

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

Hi @riconnon, unfortunately you've just added this to the list of encodings, but not implemented actual support for it. I'll close this PR for now, but please feel free to resubmit with an implementation of this character encoding.

authors: CLAassistant n1474335 riconnon

repo: gchq/CyberChef


text:
Provide ability to remove a whole group from an instance of a schema

In order to change which groups certain users are able to see, we would like to remove whole groups from schema's used in specific REST service deployments.  I.e. the schema overall could contain:
Group A, Group B, Group C
But in one specific REST deployment we only want the schema to contain:
Group A, Group C - there-by hiding Group B

Merged into develop.

repo: gchq/Gaffer


text:
Add additional tests around merging schemas with intersections

#2449 Allowed merging of schemas that overlap each other. More tests should be done around edge cases with aggregation to confirm we are happy with the behaviour before release 1.18.0.
Examples tests:

Test aggregation when graph1 has prop1 but graph2 has prop1 and prop2. Currently, aggregation is not tested.
Test this aggregation scenario with an aggregation method which fails when one property is empty.
Test his scenario when graph1 also has a count but graph2 has two counts. How do these counts differ? Is it counter intuitive?

Also improve variable names such as a:
https://github.com/gchq/Gaffer/blob/768f83f392dd57ff4d27c537fe3612a866db26b7/store-implementation/federated-store/src/test/java/uk/gov/gchq/gaffer/federatedstore/FederatedStoreSchemaTest.java#L131


text:
🛑 ARAPI Autisme is down

In 21e6b19, ARAPI Autisme ($ARAPI_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ARAPI Autisme is back up in be0d45d after 21 minutes.

repo: gcommeuneidee/upptime


text:
analysis of branding focus group results

Notes from three focus group sessions need to be combined and analyzed to write a brief report and provide recommendations for continued work on branding elements.
Additional focus groups or research may be required.

Results and recommendations sent to communications team.

repo: gctools-outilsgc/design-system


text:
Wercker don't automatic deployment html

Hello, I have a werkker to automate the deployment of my hugo, but after I added it to the werkker, the werkker just deployed the xml automatically, but did not deploy the html in the public, can I ask you? thanks，this my github：https://github.com/haoming1100/haoming1100.github.io

For support issues, please post on the support forums. Thanks.

repo: gcushen/hugo-academic


text:
Use ReverseDiff tape when constants are provided?

At the moment I don't record a tape when there are constants, just in case the control flow depends on them.

I remember now why it is impossible: the values of the constants are embedded in the tape


text:
Stop testing against HMMBase

This forces StatsBase v0.33 in the test environment, which is lower than the latest version v0.34, so we might get a different behavior of Distributions

Solved by #111


text:
Copy URL to Clipboard feature does not work on recent versions of Chrome

Supposedly new ClipboardEvent('copy') works on Firefox, but it does not work on Chrome 40ish+.
Details here.
TypeError: Illegal constructor
at TypeError (native)
at Scope.scope.copyUrl (http://localhost:9000/components/footer/footer.directive.js:19:22)
at fn (eval at <anonymous> (http://localhost:9000/bower_components/angular/angular.js:1:0), <anonymous>:4:316)
at callback (http://localhost:9000/bower_components/angular/angular.js:23298:17)
at Scope.$eval (http://localhost:9000/bower_components/angular/angular.js:15846:28)
at Scope.$apply (http://localhost:9000/bower_components/angular/angular.js:15945:23)
at HTMLButtonElement.<anonymous> (http://localhost:9000/bower_components/angular/angular.js:23303:23)
at HTMLButtonElement.jQuery.event.dispatch (http://localhost:9000/bower_components/jquery/dist/jquery.js:4435:9)
at HTMLButtonElement.elemData.handle (http://localhost:9000/bower_components/jquery/dist/jquery.js:4121:28)

ClipBoard API support is really bad across browsers. I don't think that it is even worth using for this use case. All we're doing is allowing the user to copy the URL to the ClipBoard, but they can just do that in the URL bar of the browser.
I think that we should just remove this field and button from the footer to eliminate this issue.

Makes sense to me.
On Fri, Oct 2, 2015, 5:34 PM Michael Prentice notifications@github.com
wrote:

ClipBoard API http://caniuse.com/#feat=clipboard support is really bad
across browsers. I don't think that it is even worth using for this use
case. All we're doing is allowing the user to copy the URL to the
ClipBoard, but they can just do that in the URL bar of the browser.
I think that we should just remove this field and button from the footer
to eliminate this issue.
—
Reply to this email directly or view it on GitHub
https://github.com/gdg-x/firefly/issues/49#issuecomment-145040832.

Closed by 61b549cb9343ae4c2b4a93734451250ce90ce187.

authors: Splaktar tasomaniac

repo: gdg-x/firefly


text:
Added face indexes to Vertex

I added face indexes to entity - its based on documentation, but I dont know where at this time, i'm just pushing it.

Thanks for the commit, I hope to merge this in very soon!

authors: bzuillsmith trubit

repo: gdsestimating/dxf-parser

license: mit


text:
fix yaml load

fixes https://github.com/gdsfactory/gdsfactory/issues/3188
fixes https://github.com/gdsfactory/gdsfactory/issues/3296
Thank you
@edelmanjm
@95-martin-orion

Oh, was the only reason for this that we couldn't use lists before?

Yes, now luckily Kfactory supports lists :)

authors: joamatab sebastian-goeldi

repo: gdsfactory/gdsfactory


text:
🛑 COM GURU is down

In 09d2cb7, COM GURU ($SITE_COM_GURU) was down:

HTTP code: 0
Response time: 0 ms

Resolved: COM GURU is back up in 2573a08 after 7 minutes.

repo: gedesco-git/uptime


text:
Android 7 can not open red packets automatically

It can successfully detect red packets appearing, but can not automatically opened the packet, i have to click the open button by myself.
My device is Nexus 6, System is Android 7.0.
Thanks 😄

@BigDipper7 It's a known issue in Android 7.0. Waiting for solutions.

出售扫雷外挂QQ2860968898

出售扫雷外挂需要的话加我QQ2860968898

这个问题原因应该是7.0的通知栏驻留时间较长，导致了无法找到开这个button.
尝试使用反射的方法去收起状态栏，但是没有效果 - -！

是啊,能弹出红包界面,但无法自动拆开,会慢人一步.希望早日能解决.
开发者辛苦了.

nexus5x 7.0貌似无法每次都弹出红包。。。

authors: 458448420 BigDipper7 ChuShouWaiGa DavidLiuwl geeeeeeeeek hellworld huanglongyu

repo: geeeeeeeeek/WeChatLuckyMoney


text:
High CPU usage on zombie agetty processes when using with molecule

This is an issue I noticed with the docker-ubuntu1804-ansible, docker-ubuntu1604-ansible, docker-debian8-ansible and docker-debian9-ansible images. When launching multiple containers at the same time with molecule create, the four distros I mentioned have very high CPU usage caused by the agetty process:
top - 09:56:06 up 7 min,  0 users,  load average: 18.23, 6.93, 2.59
Tasks:  11 total,   6 running,   5 sleeping,   0 stopped,   0 zombie
%Cpu(s): 41.7 us, 58.3 sy,  0.0 ni,  0.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem :  2046748 total,    93972 free,   308028 used,  1644748 buff/cache
KiB Swap:  1048572 total,  1048032 free,      540 used.  1490492 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
   66 root      20   0   13020   1792   1656 R  21.9  0.1   0:29.76 agetty
   64 root      20   0   13020   1804   1672 R  21.2  0.1   0:30.83 agetty
   67 root      20   0   13020   1764   1628 R  21.2  0.1   0:31.02 agetty
   65 root      20   0   13020   1812   1684 R  18.9  0.1   0:30.20 agetty
   68 root      20   0   13020   1876   1748 R  18.2  0.1   0:30.11 agetty
   78 root      20   0   36644   3044   2612 R   0.3  0.1   0:00.01 top
    1 root      20   0   37040   5048   3988 S   0.0  0.2   0:00.13 systemd
   23 root      20   0   35268   6764   6480 S   0.0  0.3   0:00.06 systemd-jo+
   31 systemd+  20   0  100320   2504   2296 S   0.0  0.1   0:00.01 systemd-ti+
   37 syslog    20   0  256388   3100   2692 S   0.0  0.2   0:00.01 rsyslogd
   76 root      20   0   13020   1804   1676 S   0.0  0.1   0:00.00 agetty

This issue seems to have popped up around the internet in various places:

https://github.com/ansible/molecule/issues/1104
https://github.com/moby/moby/issues/4040
https://bugzilla.redhat.com/show_bug.cgi?id=1046469

Environment
macOS 10.14 (18A391)
Docker Desktop for Mac Version 2.0.0.2
Docker Engine 18.09.1
Steps to reproduce
Create an empty role with molecule init and edit the default molecule.yml to include platforms like this:
# molecule/defaults/molecule.yml
...
platforms:
  - name: debian9
    image: "geerlingguy/docker-debian9-ansible:latest"
    command: ""
    volumes:
      - /sys/fs/cgroup:/sys/fs/cgroup:ro
    privileged: true
    pre_build_image: true
  - name: debian8
    image: "geerlingguy/docker-debian8-ansible:latest"
    command: ""
    volumes:
      - /sys/fs/cgroup:/sys/fs/cgroup:ro
    privileged: true
    pre_build_image: true
  - name: ubuntu1804
    image: "geerlingguy/docker-ubuntu1804-ansible:latest"
    command: ""
    volumes:
      - /sys/fs/cgroup:/sys/fs/cgroup:ro
    privileged: true
    pre_build_image: true
  - name: ubuntu1604
    image: "geerlingguy/docker-ubuntu1604-ansible:latest"
    command: ""
    volumes:
      - /sys/fs/cgroup:/sys/fs/cgroup:ro
    privileged: true
    pre_build_image: true
  - name: centos7
    image: "geerlingguy/docker-centos7-ansible:latest"
    command: ""
    volumes:
      - /sys/fs/cgroup:/sys/fs/cgroup:ro
    privileged: true
    pre_build_image: true
  - name: centos6
    image: "geerlingguy/docker-centos6-ansible:latest"
    command: ""
    volumes:
      - /sys/fs/cgroup:/sys/fs/cgroup:ro
    privileged: true
    pre_build_image: true
...

Run molecule create and once the containers have been launched, the com.docker.hyperkit process will max out all CPUs allocated. Running top on the Debian-based containers (u1804, u1604, d9, d8) shows multiple agetty processes chewing up CPU.
Note that this issue only seems to happen when the number of platforms is >2 and includes Debian-based images.
Expected behavior
It should be possible to launch all those containers with molecule create without the high CPU usage.
Proposed solution
I tested one of the proposed solutions from this comment:

Here's one workaround for this.  Sharing what I've learned.
Adding the following to the docker file
rm -f /lib/systemd/system/systemdudev ;
rm -f /lib/systemd/system/getty.target;
causes both the runnaway agetty and the spike in systemd-udevd processes to go away.  I understand there is no need for udev or getty in containers.
I did also try:
RUN systemctl disable getty.target
RUN systemctl disable systemd-udevd.service
and although the Dockerfile built fine, all the getty and udev services were still running as they were previously.  So those two "systemctl disable" appear to be no-ops.  Perhaps they get run before /sbin/init (systemd) is invoked.

I added a Dockerfile.j2 to the default scenario:
# molecule/default/Dockerfile.j2

FROM {{ item.image }}

RUN rm -f /lib/systemd/system/systemd*udev* \
  && rm -f /lib/systemd/system/getty.target

Then updating the molecule.yml to use pre_build_image: false:
# molecule/default/molecule.yml
...
platforms:
  - name: debian9
    image: "geerlingguy/docker-debian9-ansible:latest"
    command: ""
    volumes:
      - /sys/fs/cgroup:/sys/fs/cgroup:ro
    privileged: true
    pre_build_image: false
  - name: debian8
    image: "geerlingguy/docker-debian8-ansible:latest"
    command: ""
    volumes:
      - /sys/fs/cgroup:/sys/fs/cgroup:ro
    privileged: true
    pre_build_image: false
  - name: ubuntu1804
    image: "geerlingguy/docker-ubuntu1804-ansible:latest"
    command: ""
    volumes:
      - /sys/fs/cgroup:/sys/fs/cgroup:ro
    privileged: true
    pre_build_image: false
  - name: ubuntu1604
    image: "geerlingguy/docker-ubuntu1604-ansible:latest"
    command: ""
    volumes:
      - /sys/fs/cgroup:/sys/fs/cgroup:ro
    privileged: true
    pre_build_image: false
  - name: centos7
    image: "geerlingguy/docker-centos7-ansible:latest"
    command: ""
    volumes:
      - /sys/fs/cgroup:/sys/fs/cgroup:ro
    privileged: true
    pre_build_image: false
  - name: centos6
    image: "geerlingguy/docker-centos6-ansible:latest"
    command: ""
    volumes:
      - /sys/fs/cgroup:/sys/fs/cgroup:ro
    privileged: true
    pre_build_image: false
...

If I run molecule create with the platforms above, it completely resolves the high CPU usage issue.
I tested running molecule test with these 6 images concurrently on your ansible-role-ntp Galaxy role and everything passed.
This issue most likely won't affect your Travis CI setup for your Ansible roles, since the concurrency is coming from multiple Travis runners calling molecule on a single platform. However, this issue may present itself for anyone using these images with platforms >2, such as rapid local development running molecule converge against multiple distros.
I'm happy to test this change against your other roles and create a PR if it's something that you think is acceptable.
Thanks

Fixed via PR #10

authors: geerlingguy percygrunwald


text:
Add composer.json, add Drupal VM to Packagist

Instructions: https://getcomposer.org/doc/01-basic-usage.md
We can add Drupal VM to Packagist and allow people to add it as a project dependency. Will be awesome, especially in tandem with https://github.com/geerlingguy/drupal-vm/issues/506

So, https://github.com/geerlingguy/drupal-vm/pull/378 already added a composer.json...

Woohoo!! https://packagist.org/packages/geerlingguy/drupal-vm

repo: geerlingguy/drupal-vm


text:
提名

http://localhost:8090/updates
描述啊

带动

repo: gefangshuai/ultralist


text:
🛑 www.goliads.com is down

In d0db724, www.goliads.com (https://www.goliads.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: www.goliads.com is back up in aee1060.

repo: gelokatil/upptime-ceu


text:
🛑 www.ceualumni.com is down

In 07d93a1, www.ceualumni.com (https://www.ceualumni.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: www.ceualumni.com is back up in 971f364.


text:
Correct exit on 'SIGHUP', 'SIGINT' or 'SIGTERM'

/cc @j0tunn @sipayRT

тесты пока не смотрел

Ревью делать рано, буду доделывать.

@j0tunn
🆙 , please :)

/ok

repo: gemini-testing/gemini


text:
Test ssl off

Tested with ssl off.

@kltm
Fixed ssl and pushed geneontology/go-devops-base:tools-jammy-0.4.1 that allows "apt-get dist-upgrade" using jammy 22:10 instead of 22:04. Please pull this image ...

repo: geneontology/amigo


text:
obsoletion: GO:1900401 regulation of meiosis by regulation of transcription from RNA polymerase II promoter

obsoletion: GO:1900401 regulation of meiosis by regulation of transcription from RNA polymerase II promoter
and descendants
During previous changes this was re-defined as regulation of "meiotic cell division",
but the paper  which is used to define the term is not for the "regulation of meiotic division", it is
"regulation of meiotic cell cycle"
I'm not sure that meiotic division is regulated transcriptionally...(it's causally upstream).
experimental annotations
PomBase 5
SGD 2
these annotations should be rehoused under:
GO:0010672 regulation of transcription from RNA polymerase II promoter involved in meiotic cell cycle

OK for SGD as well:

Hi Pascale,

I took a look at those annotations and the publication and I agree that they should be rehoused. I moved them to child terms underneath GO:0010672 regulation of transcription from RNA polymerase II promoter involved in meiotic cell cycle as suggested. No objection here to obsolete that term.
Regards,
Edith

On Mar 13, 2017, at 2:21 PM, sgd-helpdesk-bounces@lists.stanford.edu wrote:
From: Pascale Gaudet pascale.gaudet@sib.swiss
Subject: obsoletion: GO:1900401 regulation of meiosis by regulation of transcription from RNA polymerase II promoter
Date: March 13, 2017 at 8:24:03 AM PDT
To: sgd-helpdesk@mailman.stanford.edu
Dear SGD curators,
I am working on a issue brought up by Val, in which she requests the obsoletion of GO:1900401 regulation of meiosis by regulation of transcription from RNA polymerase II promoter. The reason is that "During previous changes this was re-defined as regulation of "meiotic cell division”, but the paper which is used to define the term is not for the "regulation of meiotic division", it is "regulation of meiotic cell cycle"
I'm not sure that meiotic division is regulated transcriptionally...(it's causally upstream).
SGD has 2 experimental annotations
these annotations should be rehoused under:
GO:0010672 regulation of transcription from RNA polymerase II promoter involved in meiotic cell cycle”.
If it’s OK with you I’ll go ahead with the obsoletion.
Thanks,
Pascale

Hello, I am ready to do this. Looks like @mah11 created the term
https://github.com/geneontology/go-ontology/issues/9370
just wanted to notify her of the obsoletion.
Thanks, Pascale

@ValWood @mah11
I just noticed this term has annotated children:
GO:1900475 	positive regulation of meiosis by negative regulation of transcription from RNA polymerase II promoter 1 SGD/2 Pombase
Is a 	GO:1900476 	positive regulation of meiosis by positive regulation of transcription from RNA polymerase II promoter: 1 SGD/1 Pombase
I will also obsolete these two (it seems like they were included in your request since the total number of annotations corresponds to what you have there).
Thanks, Pascale

Yep we will fix if not done already....its probably just because of our current crazy long release cycle. This will be fixed soon...

Hi,
To avoid recreating the same terms I did a merge, adding the old terms as narrow synonyms:
GO:1900475
positive regulation of meiosis by negative regulation of transcription from RNA polymerase II promoter
-> merge with GO_0010674 negative regulation of transcription from RNA polymerase II promoter involved in meiotic cell cycle
GO:1900475   positive regulation of meiosis by negative regulation of transcription from RNA polymerase II promoter
-> merge with GO_0010674 negative regulation of transcription from RNA polymerase II promoter involved in meiotic cell cycle
GO:1900476 positive regulation of meiosis by positive regulation of transcription from RNA polymerase II promoter
-> merge with GO_0010673 positive regulation of transcription from RNA polymerase II promoter involved in meiotic cell cycle
Thanks, Pascale

Changed in the OBO file are now merged, see #13165

authors: ValWood pgaudet

repo: geneontology/go-ontology


text:
Temporarily revert "Add exclude-tautologies option to reason commands."

This reverts commit 709b88ee84bd7896f258509b3f6449adcd41d4f6.
Need to wait until pipeline upgrades ODK version.

cc @kltm @dougli1sqrd

@balhoff This matches what I'd expect for our old ODK.
Noting:
https://github.com/geneontology/pipeline/issues/135
https://github.com/geneontology/pipeline/issues/136

authors: balhoff kltm


text:
convert abstract and title text of GO_REF:0000096 to describe new preprocessing pipeline here instead of MGI curation process

also make sure we should be using GO_REF:0000096 for both human->mouse and rat->mouse ortholog annotations?

Note that GO_ref:0000096 corresponds to both J:164563 (human ISO load) and J:155856 (rat ISO load).
The human abstract at MGI is currently:
Experimental data from the human  gene association files are downloaded from the GO Consortium website (http://www.geneontology.org/). Human  annotations with experimental evidence codes (IDA, IMP IPI, IGI, and EXP) are automatically associated with the orthologous mouse genes with an evidence code of ISO (Inferred from Sequence Orthology; for more information about GO evidence codes, their meaning and how they are used, go to the GO Consortium evidence code documentation at http://www.geneontology.org/GO.evidence.shtml).  The original reference PubMed ID that provides the source data for the human annotation is maintained in the MGI system. The laboratory mouse is used as models for the study of human diseases. Both the Mouse Genome Database (MGD) and HGNC  have extensive procedures in place, overseen by expert curation, to establish orthology relationships between their genes. Both MGI and GO Annotation at EBI (UniProtKB-GOA) engage in curated Gene Ontology (GO) annotation using the experimental literature available for each organism and adhering rigorously to the guidelines set forth by the GOC.
The rat abstract at MGI is:
Both the Mouse Genome Database (MGD) and the Rat Genome Database (RGD)  have extensive procedures in place, overseen by expert curation, to establish orthology relationships  between their genes. Furthermore, each database engages in curated Gene Ontology (GO)  annotation using the experimental literature available for each organism, and adhering rigorously to the guidelines set forth by the GOC. Experimental data from the rat gene association files are downloaded from the GO Consortium website (http://www.geneontology.org/).  Rat annotations with experimental evidence codes (IDA, IMP IPI, IGI or IEP) are automatically associated with the orthologous mouse genes with an evidence code of ISO (Inferred from Sequence Orthology; for more information about GO evidence codes, their meaning and how they are used, go to the GO Consortium evidence code documentation at http://www.geneontology.org/GO.evidence.shtml). The original reference PubMed ID  that provides the source data for the rat annotation is maintained in the MGI system.
GO_REF:0000096 is: Automated transfer of experimentally-verified manual GO annotation data to close orthologs.
Mouse Genome Database (MGD), The HUGO Gene Nomenclature Committee (HGNC), and Rat Genome Database (RGD) have extensive procedures in place, overseen by expert curation, to establish orthology relationships between their genes. The Experimentally based annotations annotated by each group (IDA, IMP IPI, IGI, and EXP) are used to provide annotations to the respective mouse and rat orthologs, and given the ISO evidence code and an entry in the inferred_from field to indicate the orthologous entity.
Note that the GO_REF covers both rat and human. I suggest that we retain the GO_REF and modify its text to reflect the new methodology using The Alliance Orthology calls and sequence assignments made in MGI.

Draft new GO_REF:0000096
Automated transfer of experimentally-verified manual GO annotation data to close orthologs.
Mouse Genome Database (MGD) and The Alliance of Genome Resources have extensive procedures in place to establish orthology relationships between genes. The experimentally-based annotations provided by model-organism groups (IDA, IMP IPI, IGI, and EXP) are used to provide annotations to the respective orthologs, and given the ISO evidence code and an entry in the inferred_from field to indicate the orthologous entity.

@LiNiMGI Is there a current state on this?

@sierra-moxon
Would you please double check the abstracts for the GO_REFs that are being used to make sure they reflect how the pipeline is working? thanks, Li

@pkalita-lbl - what to I do here?  :)

@pkalita-lbl For context, we want to make some changes to the GO_REFs for this project, but don't want to weird what you have going on. Would it be better to just stick to the old SOP, or do the old and new at the same time to save you the trouble of syncing later?

With https://github.com/geneontology/go-site/pull/2253 being merged in, I'd appreciate that if you need to an update an abstract that you update it in both the metadata/gorefs/goref-NNNNNNN.md and metadata/gorefs.yaml file. If you only update the Markdown file it’s not the end of the world, I’ll get them sync’d up later. We’re just in a bit of a multiple-sources-of-truth situation until this project wraps up.

@pkalita-lbl After you review the PR (and merge) for the yaml file, this ticket can be closed.

I reviewed and merged https://github.com/geneontology/go-site/pull/2259

authors: LiNiMGI kltm pgaudet pkalita-lbl sierra-moxon ukemi

repo: geneontology/gopreprocess


text:
Replace the environment variables management with Doppler.

Check Doppler and note the scalability of this approach.

That looks cool, but overkill for the scope of this tutorial imho

That looks cool, but overkill for the scope of this tutorial imho.

Cannot disagree - this app is the closest of RedwoodJS sample applications that has enough "meat on the bones" to illustrate the use of Doppler. This is of course your call and I appreciate your focus on Stripe.

repo: generalui/redwood-stripe


text:
Ek/5978 add status command

Added status command for getting information about application loading, for more details see: #5978
Command output now looks like this:
genestack/qiime-report   failed

Application jar was not loaded due to the following errors:
genestack/qiime-report JS error: this language feature is only supported for ECMASCRIPT6 mode or better: class. Use --language_in=ECMASCRIPT6 or ECMASCRIPT6_STRICT or higher to enable ES6 features.
Script loading error: unable to find script dose_response.r
genestack/qiime-report JS error: this language feature is only supported for ECMASCRIPT6 mode or better: member declaration. Use --language_in=ECMASCRIPT6 or ECMASCRIPT6_STRICT or higher to enable ES6 features.

genestack/report-viewer   loaded

Also changed interface of install command.
Note: don't merge this branch until main repo branch will be finished (consult me on any questions).
Pull request in main repo: https://github.com/genestack/genestack/pull/3269

About Use --language_in=ECMASCRIPT6: i looked to closure compiler sources and it seems that there is no way to change error messages. It uses ErrorReporter and there are several implementations, but only one can report meaningful error messages.

Please bump version to '0.15.0a2'

authors: ekozobrodov genestack-solomatin

repo: genestack/python-client


text:
docs: fix hyperlinks in README #57

Summary
Fixed hyperlinks in README. Issue #57
Type of Change
Please mark the relevant option(s) for your pull request:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Code refactoring (improving code quality without changing its behavior)
[x] Documentation update (adding or updating documentation related to the project)

Checklist
Please ensure that your pull request meets the following criteria:

[x] I have read the Contributing Guide
[ ] My code follows the project's coding style and best practices
[ ] My code is appropriately commented and includes relevant documentation
[ ] I have added tests to cover my changes
[ ] All new and existing tests pass
[x] I have updated the documentation, if necessary

Testing
Please describe the tests you have added or modified, and provide any additional context or instructions needed to run the tests.

[x] Clicked the links on Github and they work

Thanks @eddex!

authors: eddex sourabhxyz

repo: geniusyield/smart-order-router


text:
add favicon

This should set the icon on the website when you e.g. bookmark to the new logo
I used: https://realfavicongenerator.net/

Codecov Report

Merging #290 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #290   +/-   ##
=========================================
  Coverage     19.02%   19.02%
  Complexity      137      137
=========================================
  Files           163      163
  Lines          2013     2013
  Branches        258      258
=========================================
  Hits            383      383
  Misses         1597     1597
  Partials         33       33

Continue to review full report at Codecov.

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

authors: codecov-io inodb

repo: genome-nexus/genome-nexus


text:
Kopie einer Bohrung

Diese Funktion im Editor funktioniert nicht. Muss wohl neu aufgesetzt werden. Hier sehe ich den Vorteil wenn man Bohrungen in verschiedene Workgroups kopiert werden könnten oder eine sehr ähnliche Bohrung existiert und so eine Kopie angepasst werden kann

Wie muss beim Kopieren mit den Feldern CreatedBy, Created (Datum), UpdatedBy und Updated (Datum) umgegangen werden?

@patrickackermann Es soll eine vollständige 1:1-Kopie sein. Selbst Created und CreatedBy soll beim alten belassen werden. Einzig die Titelerweiterung (copy) ist ok und weicht somit von der 1:1-Kopie ab.

Test Version: 2.0.57+782f061:
→ Es wird keine Kopie erstellt. Dialog geht bis zur Bestätigung "Create a Copy", dann passiert einfach nichts.

Der Fehler tritt auf, da die Spalte borehole.contact_id manuell aus der Datenbank gelöscht wurde und nicht mit einem Skript. Wird mit #146 erledigt.

cool, danke für das fixen!

authors: RBordoni danjov gysimichael patrickackermann

repo: geoadmin/suite-bdms


text:
Dynamically determine node version

https://github.com/geoffrich/svelte-adapter-azure-swa/pull/47 updated the adapter to target Node 16 instead of 12. This is good, but it would be better if we could allow the user to specify which node version to use. Otherwise, they'll be tied to the adapter Node version.
Here's how adapter-vercel does it:
https://github.com/sveltejs/kit/blob/3dae8e702641b5ee762b1892b7b7aa90e1c19a7c/packages/adapter-vercel/index.js#L388-L399

This could be solved using route-level config like the Vercel adapter: https://kit.svelte.dev/docs/adapter-vercel#deployment-configuration

Any news on this? I'd like to use node18 in SWA. Would it be possible to extend the customization level of the staticwebapp.config.json as proposed in #66 ?

Thanks for the bump @BernhardAuer - this was a quick feature add that is available in 0.17.

authors: BernhardAuer geoffrich

repo: geoffrich/svelte-adapter-azure-swa


text:
住所データ追加のリクエスト

リクエストの種類(必須)

[x] 追加
[ ] 修正
[ ] 削除

対象となる住所(必須)

長野県上伊那郡南箕輪村の市区町村コード13件が抜けていました

参考情報・URL(オプション)
おそらく上記の市区町村コードは下記より「20385」になると思います

https://www.e-sale24.com/

備考(オプション)
その他補足情報が必要であればご記入ください。

特になし

@sakisaitomn ご指摘ありがとうございます。修正して、長野県上伊那郡南箕輪村の市区町村コードを入れるようにしました。

@champierre ご対応ありがとうございました！ 🙇

authors: champierre sakisaitomn

repo: geolonia/japanese-addresses


text:
To remove the tooltip of textMarker when its enabled

I have a button tool for textMarker . How can I remove the tooltip of text marker when the button is clicked?
@codeofsumit

You can disable the tooltip by setting tooltips: false:
map.pm.enableDraw('Text', {tooltips: false})

https://jsfiddle.net/n6yfm8xk/

authors: Falke-Design agishk

repo: geoman-io/leaflet-geoman


text:
Add OMPT callbacks for thread progress API

ompt_callback_task_schedule_t (See OpenMP 5.0, Section 4.5.2.10)
ompt_callback_work_t (See OpenMP 5.0, Section 4.5.2.5)

https://review.gerrithub.io/c/geopm/geopm/+/467688/

Wrong issue in commit message :(

repo: geopm/geopm


text:
add temporal extent support to WMS harvesting

For WMS layers which support Extent/@time, map to pycsw:TempExtent_begin and pycsw:TempExtent_end in support of temporal GetRecords queries.

Fixed in master and 1.10 branch.

repo: geopython/pycsw


text:
fix safe file handling in unit tests

Description
Unit tests in a Python 3 environment yield ResourceWarning warnings like:
/home/travis/build/geopython/pywps/tests/test_inout.py:64: ResourceWarning: unclosed file <_io.FileIO name='/tmp/tmpwbpvbq0c' mode='rb'>

Environment

operating system: Ubuntu
Python version: 3.4
PyWPS version: master
source/distribution
[x] git clone
[ ] Debian
[ ] PyPI
[ ] zip/tar.gz
[ ] other (please specify):
web server
[ ] Apache/mod_wsgi
[ ] CGI
[x] other (please specify): unit test runner

Steps to Reproduce
# in a Python 3 virtualenv
python -m unittest tests

Additional Information
Initial discussion in #106.
Example can be found in current travis builds: https://travis-ci.org/geopython/pywps/jobs/111190874#L360

Can I take this bug?

Sounds good @mishravikas!

@mishravikas go for it, but I'm not sure it's easy to be fixed. Have a look in it and in case, you are not sure how to approach, just move on with your tasks

Line 160 in inout/basic.py, in the method get_stream() save a reference to the file object. CLose this file object after the handler is called - Process class, _run_process() method.

https://docs.python.org/3/reference/datamodel.html del object destroyer should do it

#175 fixes this

authors: jachym ldesousa mishravikas tomkralidis

repo: geopython/pywps


text:
Performance fix: move replacePublicMFieldRefs to beforeProgramTranspile

The NodeClass.replacePublicMFieldRefs() method is currently being called for every nodeclass on every transpile. This is extremely wasteful, and is probably a mistake.
Changes:

moves the NodeClass.replacePublicMFieldRefs loop and calls to beforeProgramTranspile.
removes unnecessary duplicate this.shouldParseFile() call in beforeFileTranspile()

excellent spot . thanks!

authors: TwitchBronBron georgejecook

repo: georgejecook/maestro-roku-bsc-plugin


text:
🛑 NYCResistor Wiki is down

In a04b57f, NYCResistor Wiki (https://wiki.nycresistor.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NYCResistor Wiki is back up in b4ba73b.


text:
Incorrect BTC price when converted to DKK?

Hi.
I just started using Crypto Bar and I am really liking it.
Unfortunately, it seems as if the BTC price is incorrect when converted to DKK currency.
Please check this image: https://imgur.com/a/sQx4OyU
As you can see, it is not the same price listed on Coinbase as in Crypto Bar. I don't think Crypto Bar is updating the price. The price seems to be stuck.
I hope you can fix it :)

https://imgur.com/gallery/sQx4OyU

I just realized that you're not working on the project anymore... :(

repo: geraldoramos/crypto-bar


text:
Использование проверки кода в VSCode

Для проверки кода используются такие программы, как линтеры. Линтеры автоматически находят ошибки в оформлении и не только. Мы будем использовать линтер Pylama, потому что он легковесный и выполняет нужную нам задачу: форматирование кода и недопущение ошибок.
Установка линтера
Для начала, у вас должен быть установлен плагин Python

Подсказка: в строке команд необязательно вводить команду целиком, можно лишь начать ее писать, а затем, в открывшемся списке выбрать нужную команду

Нажимаем Ctrl + Shift + P (откроется строка команд) и вводим Python : Enable/Disable Linting, выбираем "Enable"
Снова открываем строку команд и вводим Python : Select Linter, выбираем Pylama из предложенных вариантов.
VSCode предложит установить линтер, соглашаемся
Готово! Линтер должен заработать сразу после установки

Все написал, а как пользоваться линтером не написал 🥇

Не ну я считаю интеллектом и умом

такой штуки кстати нет 'Python : Enable/Disable Linting'

authors: Lukedam Nickonson germanFid

repo: germanFid/FieldAveraging


text:
feat: Charge order matching fee through the margin

This feature deducts the order matching fee from the margin instead of having to trust the app to pay an order matching fee invoice.

Removes the 5 seconds delay before submitting an order
Adds fee and pnl to the trade walltet history item

Notes

The fees will only get paid into the lightning channel once the position is closed. In other words in a collaborative settlement of a position we are substracting the opening fees and the closing fees from the accepted_settlement_amount.
The CETs are only generated with the opening fees and do not include a closing fee.

TODO:

[ ] Test if fees are properly deducted in case of a force closure

I'll review this once you've attempted to do it by modifying the collateral in ContractInput instead (i.e. without changes to rust-dlc).
(Submitting this to get rid of the pending review.)

Thanks for the suggestion! It works just fine with simply adding the fee to the initial collateral of the accepting party. However, I am wondering if this truly has the same semantics, as with the change in rust-dlc we would always get the order matching fees, while in this solution we'd put the fees up into the trade.


text:
[疑惑]：Android9存储到外部提示Permission denied

问题描述【必填】
大佬你好，我遇到了如下的问题，我的targetSdk版本为33，在申请权限时我用的是Manifest.permission.READ_MEDIA_IMAGES这个权限，在打开APP的时候申请的时候我执行了拒绝的操作，而后在下载图片的时候我执行了同意的操作，此时我在onGranted中开始了保存图片到 ---Environment.getExternalStorageDirectory().absolutePath + File.separator 文件夹中，会一直提示我Permission denied，但是不管如何申请权限都是通过的
当我重启APP之后，再进行保存的操作则能正常保存
所以是因为什么导致的，我拒绝之后再同意权限会一直报错Permission denied，必须重启之后才能正常保存
烦请大佬指导下

框架文档是否提及了该问题【必答】
否
是否已经查阅框架文档但还未能解决的【必答】
是
issue 列表中是否有人曾提过类似的问题【必答】
否
是否已经搜索过了 issue 列表但还未能解决的【必答】
是

小伙子，该 issue 被打回，打回的原因如下：

这个问题属于 bug，不能提疑问 issue 单，请提 bug issue 单

请重新提一个 issue 并纠正以上问题

repo: getActivity/XXPermissions


text:
Add "withdraw" button to savings balance

It should open withdraw onchain page, placed there for easier access and increasing feeling of control of funds for users

@stackingsaunter, it looks ugly when there are four balance boxes, should we use icons?

the hosted balance should be migrated, it's not planned to always show. Maybe this card can be displayed differently in a follow-up?

EDIT: anyway in a few months we can remove that card.

authors: im-adithya rolznz stackingsaunter

repo: getAlby/hub


text:
Add swr caching for selected account

Describe the changes you have made in this PR
Replace custom caching code in lib/api and lib/cache to get account info with SWR(https://github.com/vercel/swr)
Uses the useSWR hook for getting data on accountId change. Uses mutate to revalidate and refetch from other components to update balance.
I was interested in this issue and started debugging and testing. I got it working at some point, that's why i share it here. I'm not sure if this is how it was intended however. Feel free go give me any suggestions on how to modify or improve. In case it doesn't help at all, I'm not bothered by discarding the whole PR in favour of other implementations.
Link this PR to an issue [optional]
Fixes #1923
Type of change

feat: New feature (non-breaking change which adds functionality)

How has this been tested?
Manually so far
Checklist

[ ] My code follows the style guidelines of this project and performed a self-review of my own code
[ ] New and existing tests pass locally with my changes
[ ] I checked if I need to make corresponding changes to the documentation (and made those changes if needed)

@rolznz I will probably clean this up and might change again tomorrow. Please have a look and let me know what you think. Thanks.

@rolznz I will probably clean this up and might change again tomorrow. Please have a look and let me know what you think. Thanks.

Thanks for your changes @lujakob !
I think some parts of this PR are more complicated than necessary. I hope my comments help.

@rolznz I addressed all of your comments and added three more questions for you. Do you have any further suggestions?

@rolznz I addressed all your concerns. I created the useSelectAccount hook and the AccountContext and TestConnection are even leaner now. Please have another look at it.

@rolznz @escapedcat thanks for reviewing. I updated accordingly.

@rolznz do you get why the e2e test doesn't succeed? Seems like problem with loading a dependency?

@rolznz do you get why the e2e test doesn't succeed? Seems like problem with loading a dependency?

Yes, I think it is related to some changes that were recently merged into master. Hopefully it will be fixed soon.

@rolznz do you get why the e2e test doesn't succeed? Seems like problem with loading a dependency?

Yeah, no worries, no your fault. Restarting these helps. Did that now.

Some improvements in this PR:

Instant account switching for accounts you have already connected to
When switching account, it shows correct account icon & name
When switching to a new account, it will show a loading component (needs work, and is only shown in the popup right now)
Account context is a lot simpler (extracted status )

I am wondering now if we should have a loading screen for switching to a new connector rather than showing some skeleton loaders (we are not sure the connector can be connected to or not). For switching back to a connector you already connected to, it's now instant (because it uses SWR) but we should still check if the connection succeeds, otherwise show the connection failed screen.
CC @lujakob @reneaaron

Some improvements in this PR:

Instant account switching for accounts you have already connected to
When switching account, it shows correct account icon & name
When switching to a new account, it will show a loading component (needs work, and is only shown in the popup right now)
Account context is a lot simpler (extracted status )

I am wondering now if we should have a loading screen for switching to a new connector rather than showing some skeleton loaders (we are not sure the connector can be connected to or not). For switching back to a connector you already connected to, it's now instant (because it uses SWR) but we should still check if the connection succeeds, otherwise show the connection failed screen.
CC @lujakob @reneaaron
I wonder if it makes more sense to show a loading screen instead of skeleton loaders (#2456)

This PR is already 5 months old and interferes with a few current ones (account loading, error cases). I think we should finish the current ones and then in case re-address this one. Otherwise it gets even more confusing as it already is (we have several different issues on the topic of account loading/switch, error handling). Additionally this PR has a lot of changes and also has probably quite a few merge conflicts with master due to its age.

@lujakob I already addressed the merge conflicts. I don't know if the existing loading screen with skeleton loaders is the best way to do it, and does not work for the first account load (only switching accounts).
But I see what you mean - let's leave this issue for now and keep the discussion in the other tickets.

authors: escapedcat lujakob rolznz

repo: getAlby/lightning-browser-extension


text:
Update documentation ( taiko screencast not on npm )

Expected behavior
Should be able to install taiko-screencast
Actual behavior
taiko-screencast not found in npm
Steps to reproduce
See issue in taiko-screencast repo here: https://github.com/getgauge-contrib/taiko-screencast/issues/6

npm install --save-dev taiko-screencast`
Get error from npm that the package doesn't exist

Would recommend reaching out to the package maintainer or removing that package from the taiko documentation. I've created the above GH issue to notify the package maintainer that it doesn't appear to be published to npm

@cmbirk We will be releasing taiko-screencast to npm. Please track it as part of the issue you raised. Hence closing this.

authors: Apoorva-GA cmbirk

repo: getgauge/taiko


text:
update line-awesome to 1.3.0 (fixes #151)

Had to recompile scss, hence the changes.

How did you recompile the line awesome source? To me it looks like you need to change some variables in the scss to make it work. Also I am wondering why fa is still working, shouldnt it be fas now?

Right, the fa prefix has been deprecated in font-awesome in version 5. The new default is the fas solid style and the fab style for brands. However I included line-awesome, not font-awesome, just like it was before. Just udpated the version.
line-awesome uses the la prefix, however alternatively supports also the fa prefix for compatibility reasons: https://github.com/icons8/line-awesome/tree/master/dist/font-awesome-line-awesome
I didn't recompile the line-awesome source. Just embedded the source from the link.
I had to recompile the quark scss, because the line-awesome.min.css changed.

I see but the link you provided has 1.2.0 icons, not 1.3.0

Yeah, I most likely used the download from their website: https://maxst.icons8.com/vue-static/landings/line-awesome/line-awesome/1.3.0/line-awesome-1.3.0.zip
Can't say for sure, as this PR happened months ago...
To be sure, someone should check hashes. However, I would be surprised if I hadn't used 1.3.0 and still wrote so in the PR.

I tried it again, and it is really confusing to me. Details here:
https://github.com/icons8/line-awesome/issues/33#issuecomment-715900721

So I managed to update the font properly. There was a lot of files and information missing front line-awesome. I hope they will fix that. I managed to get support for almost every usecase now: fa, fas, las. So it should be almost safe to upgrade, even without modifying the theme icons or an of the plugins, that use the theme icons.
https://github.com/icons8/line-awesome/issues/33#issuecomment-715913183
https://github.com/NicoHood/grav-theme-quark/tree/magerquark

I hope the getgrav team will merge this PR and make a new release soon - icons are a big part of the features module.

authors: NicoHood o-pteron sal0max

repo: getgrav/grav-theme-quark


text:
function toggle()

Hi,
Whenever I go in the admin panel I see the following error on right side of the screen:
Notification: File Type

    	function toggle() {
    		var el = document.getElementById('session-data');
    		el.style.display = (el.style.display != 'none' ? 'none' : '' );

    		var c = document.getElementsByClassName('session-data-title');
    		for (var i = 0; i < c.length; i++) {
    			c[i].style.display = (c[i].style.display != 'none' ? 'none' : '' );
    		}
    	}

Any idea what it might be? I cant see any problems with any toggle on the screen.
Thanks

The issue disappeared :/
Thanks

repo: getgrav/grav


text:
Use images for all services

https://github.com/getodk/central/pull/676 builds nginx and service images. The enketo and secrets services can use stock base images instead.

I gave some thought to the enketo and secrets images and I'd rather leave them as-is.
For secrets, we could remove secrets.dockerfile and change the Docker compose block to something like:
  secrets:
    image: node:20.12.2-slim
    volumes:
      - ./files/enketo/generate-secrets.sh:./generate-secrets.sh:ro
      - secrets:/etc/secrets
    command: './generate-secrets.sh'

We could do something similar for Enketo (use volumes instead of COPY directives in the dockerfile, specify the script from docker compose) but I don't see much advantage.
For someone who wants to do their own orchestration, it makes no real difference as far as I can tell. They'll use the base image and then decide how they want to define the secrets volume, get the config files in the right place, and run the config and launch scripts.
The tradeoff that I see is between making the base versions really clear in the docker compose file vs. keeping everything about a service more contained in a Dockerfile. I have a slight preference for the latter (status quo).
@spwoodcock @tobiasmcnulty does that sound reasonable? Anything I might be missing?

It's nice from my perspective to have all the configuration and start-up files needed by Enketo bundled nicely into its own image. Furthermore, as long as the Central install requires a package to be installed that's not in the base image, I don't think there's any way to get around it.

the Central install requires a package to be installed that's not in the base image

I haven't tried this yet but I believe it should be possible to do an apt-get call in a shell script if needed.
The only part that's not in the Enketo base image is the config templating. The reason it's not in there is to give flexibility as to how that's done based on the deployment strategy. For example, the default Central install uses a shared volume to generate and persist secrets but in a specific deployment context it might make more sense to generate the secrets and then persist them in whatever deployment platform's secrets repository and template the configs from there.

Thanks for the quick replies!

I haven't tried this yet but I believe it should be possible to do an apt-get call in a shell script if needed.

Maybe I misunderstand, but in case this is the thought...please don't install packages during the container startup. Apt could fail or parts of the internet could be inaccessible (a real issue in our use case!), slowing or preventing the container launch. Even for people with fast and reliable connections, it leads to a (slightly) slower start, and confusing behavior when the container is executed with some other startup command and a package is missing.

The only part that's not in the Enketo base image is the config templating. The reason it's not in there is to give flexibility as to how that's done based on the deployment strategy. For example, the default Central install uses a shared volume to generate and persist secrets but in a specific deployment context it might make more sense to generate the secrets and then persist them in whatever deployment platform's secrets repository and template the configs from there.

Honestly I feel like what you have already is great. Startup scripts that modernize legacy applications by reading configuration from the environment provide real value. Sure, someone could sort out how to configure it by hand (and having these files in the image doesn't prevent that), but why bother when you've already done the hard part? 🙂
One nice-to-have might be to separate the startup script into its ENTRYPOINT and CMD components, so the command could be overridden while still getting the benefit of the configuration steps. But I can't say I've run into a need for that for this image yet, just raising it in case it seems useful!

please don't install packages during the container startup

Ah yes, that makes sense. It was too half baked of an idea!
We maintain the Enketo image so maybe we can just have it install gettext and then putting the files in the right place and doing the templating can be in the docker compose file. How does that sound?

Sounds good to me 👍
Another option could be to add an additional container to the stack that has the gettext dependency, mount the required files, and run the command on start. The enketo container could have a depends_on service_completed_successfully before it starts and mounts the same files. The additional container would shut down after.
Not ideal, but possible if the source enketo image cannot be modified!
It adding the extra dependency isn't a big deal, then that's definitely the way to to 😄

We maintain the Enketo image so maybe we can just have it install gettext and then putting the files in the right place and doing the templating can be in the docker compose file. How does that sound?

Oh, I missed this, and I can see why you might prefer to maintain only one Enketo image! Adding at least the gettext package to the source image sounds good to me. It'd be nice if it came with an entrypoint to create the configuration file based on the environment, but I can see how you might want to keep that in this repo, too.
If the configuration files are not in the image, we would need to mirror them in our helm chart. But I believe that's easily scripted and a small price to pay if we can run an official image directly.

Possibly of interest: Enketo can be configured directly using environment variables. That might be most appropriate for your context.

It'd be nice if it came with an entrypoint to create the configuration file based on the environment, but I can see how you might want to keep that in this repo, too.

The primary reason we took that work out of the Enketo image is because it felt like it overlapped with the direct configuration through env variables and because there's variation in what's defaulted vs. exposed for configuration across Enketo consumers. Central doesn't use the environment var based configuration because we wanted to specify a mix of defaults and templated configs and it felt nice to do that all in an Enketo-specific file. Do those seem like reasonable reasons? We can certainly revsit if not!

If the configuration files are not in the image

And here you mean the Central templated Enketo config, right? There is a base config with default values there but indeed the templated one is something Central-specific. Again, the reasoning is that for stock Central installs we have certain things we want to set as defaults and others we want to explicitly make configurable.

Cool! I didn't know about the environment variable option in Enketo proper.
I'll probably just mirror whatever you do here, so if it's a configuration file that sounds good, or if it's environment variables, that sounds good too! Thanks for talking through this, I appreciate it.

Thanks so much for the good discussion! I'll let this simmer a couple days to see if any other thoughts come in.
In the mean time, I'd also really appreciate thoughts on the versioning issue I've outlined at https://github.com/getodk/central/pull/678. Maybe someone knows of another project that builds images and publishes an orchestration file from the same repo? I wonder whether they use different tags for the images as for the orchestration file. Any ideas very welcome!

authors: lognaturel spwoodcock tobiasmcnulty

repo: getodk/central


text:
Nanopi bootstrap on senicOS

not quite finished, but this already installs our hub onto the current dev-version of senicOS ;)
TODO: adjust the homeassistant role, too

This PR is now good to merge IMHO. i'd be curious to see whether either one of you can bootstrap their instance using this

I'd like to see the dead code removed before merging

authors: larsblumberg tomster

repo: getsenic/senic-hub


text:
Perform issue

It takes more than 5s for landing page, when takes only 2s without sentry installed.  Do you have any suggestion?
Env:
"react": "15.4.2",
"react-native": "0.42.3",
"react-native-sentry": "0.8.1",

Try to set deactivateStacktraceMerging: true, depending on how much is sent over the javascript bridge, this can be very demanding.
But before doing that, try to update to the latest react-native-sentry version, we added several performance improvements.
https://docs.sentry.io/clients/react-native/config/

@HazAT I am using latest react-native-sentry and have the same issue.
set deactivateStacktraceMerging: true solves the prolem.

Thank you for the quick reply @HazAT. In my case, disabling stacktrace merging makes my application go from being unusable to pretty performant. It's a night and day difference 😳

@HazAT , Thanks, I will try.

Does anyone here have their app open source?
I am curious to debug it and see what's the bottleneck.
Also feel free to write me directly to daniel@sentry.io

Sadly our app is not open source and is quite large, so it would be hard to use to find the root cause. I can ask if I would be allowed to email you directly with the source though.

I don't think I'm going to be able to send our app 😞 Sorry about that

authors: HazAT damoguyan8844 hasLandon messense

repo: getsentry/react-native-sentry


text:
Session Replay crashing iOS application

Platform
Flutter Mobile
Obfuscation
Enabled
Debug Info
Enabled
Doctor
[✓] Flutter (Channel stable, 3.24.2, on macOS 15.0 24A335 darwin-arm64, locale en-US)
    • Flutter version 3.24.2 on channel stable at /Users/alexbouma/sdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4cf269e36d (13 days ago), 2024-09-03 14:30:00 -0700
    • Engine revision a6bd3f1de1
    • Dart version 3.5.2
    • DevTools version 2.37.2

Version
8.9.0
Steps to Reproduce

Enable Session Replay:..experimental.replay.sessionSampleRate = 0.0
..experimental.replay.onErrorSampleRate = 1.0,

Open application, not observed when debugging yet only on Testflight

Expected Result
No crash and replays 😄
Actual Result
Sometimes: https://recommendly.observ.app/share/issue/be0bb992d3d24c9cb1cf95c7b4621c4d/
Doesn't seem to be consistent. No replays sent yet either. Disabled the feature for now.

cc @vaind

Thanks for reporting this, I'll have a look into reproducing this.
@stayallive any device logs available?

Okay this gonna sound a bit daft maybe but I have a screenshot 🙈

I also do have a Crash Point File but unsure how useful that might be to you since I'm assuming it's specific to my application.
I have no logs from the device other than this as far as I can find.
Hopefully this is helpful, but if not please let me know what I should do to help out!

@stayallive thanks for reporting this, a fix will come in the next release.

authors: buenaflor stayallive vaind

repo: getsentry/sentry-dart


text:
[OTel] Improve Span attributes for Messaging events

Extracted from https://github.com/getsentry/sentry-go/issues/557 and https://github.com/getsentry/team-webplatform-meta/issues/32.
Re-evaluate how we set operation/description for messaging spans: https://sentry-sdks.sentry.io/performance/otel-demo-checkoutservice:3a93068eca0d4acb9c7865f68ba5183f
According to https://develop.sentry.dev/sdk/performance/span-operations/#messagesqueues, we should set topic.* attributes.

Related discussion here https://github.com/getsentry/sentry-go/discussions/639

authors: tonyo yolkhovyy

repo: getsentry/sentry-go


text:
Migration chokes on .d.ts files

Environment
just npx @sentry/migr8@latest,
sentry right now:
"@sentry/nextjs": "7.117.0",
Steps to Reproduce

have a project with .d.ts file:

declare namespace NodeJS {
	interface ProcessEnv {
		readonly FOO: string;
	}
}

Expected Result
I can migrate to v8
Actual Result
migration dies with
/index.d.ts Transformation error (A 'const' initializer in an ambient context must be a string or numeric literal or literal enum reference

I tried running it like so:
npx @sentry/migr8@latest --ingoreFilePatterns ["**/*.d.ts"]
npx @sentry/migr8@latest --ingoreFilePatterns "**/*.d.ts"
npx @sentry/migr8@latest --ingoreFilePatterns **/*.d.ts
but these broke in the same way
Also, every time I run it, I have to look at the intro messages for half a minute, can they be skipped?

Hi @MonstraG sorry for the late reply! Unfortunately, this repository slipped through our GH issue monitoring solution which is why we didn't leave a reply in time.
Is this still affecting you in the sense that you're blocked on upgrading to version 8 of the SDKs? Or did you follow the manual migration steps

I already migrated manually, but if course this might be a problem for someone else

Closing as we decided to archive migr8 and its unlikely that we'll further spend time on open migr8 issues.
We're already working on the next major version for the SDK which will feature way less breaking changes, rendering a codemod/migration tool like migr8 unnecessary. Sorry for anyone who's running into this issue. Please follow the manual migration guide.


text:
Disable sending Spans with attribute Sampled=False

Problem Statement
Span attribute sampled is ignored and on Transaction finish all collected Spans inside Transaction will be send, if all transaction is Sampled.
I want to use feature-flags for disabling tracing of some parts of my code dynamically for reducing usage on production environment (for example when I've many fast request to another service).
Solution Brainstorm
Modify condition  https://github.com/getsentry/sentry-python/blob/b7c0dc412a1505fff382732f567952c8a9572b60/sentry_sdk/tracing.py#L646 to
if span.timestamp is not None and (span.sampled == True or span.sampled is None)

@andrewchernyh how do you plan to use this even if we add this condition?

@sl0thentr0py
I'm using tracing decorators, and can easy add something like this
....
        def wrappee(*args, **kwargs):
            sampled = is_feature_enabled("tracing", context: { "op": decorator_self.op } )
            with start_span(decorator_self.op, decorator_self.description, sampled=sampled):
                return original_func(*args, **kwargs)

Another usage of unsampled spans is filtering them out on some condition, for example with duration less them 1ms

Right now sampling as a concept only exists on the transaction level. Changing APIs like this needs to be discussed internally and synced across SDKs, so we won't be moving fast on this but I'll bring it up. But it's not clear to me that this is a good idea and fits into the rest of the performance UX.

Second, modifying
https://github.com/getsentry/sentry-python/blob/b7c0dc412a1505fff382732f567952c8a9572b60/sentry_sdk/tracing.py#L646
is after the span is recorded/instrumented already, so it doesn't really lower your overhead.

Third, if you already have that decorator, you could just move the sampling logic for spans to your decorator and do it yourself. This will probably unblock you sooner than waiting for us. For instance,
        def wrappee(*args, **kwargs):
            sampled = is_feature_enabled("tracing", context: { "op": decorator_self.op } )
            if sampled:
                with start_span(decorator_self.op, decorator_self.description):
                    return original_func(*args, **kwargs)
            else:
                    return original_func(*args, *kwargs)

repo: getsentry/sentry-python


text:
[DEP-267] Release 2.8.1

Description
SDK Release 2.8.1

Upgrade SDK libraries version to 2.8.1
Update CHANGELOG to include main features included in this release.
Update README.md with references to the latest version
Update project set up (gradle version, target SDK, etc...)

References
DEP-267
Testing

[ ] Complete 3 steps flow with Zoom liveness.
[ ] Complete 3 steps flow with face capture.

Checklist

[X] I have added documentation for new/changed functionality in this PR or in auth0.com/docs
[X] All active GitHub checks for tests, formatting, and security are passing
[X] The correct base branch is being used, if not master

QA approved.

authors: Zzhelyaz mariasenosiain

repo: getyoti/yoti-doc-scan-android


text:
Support for Google Dialogflow

Add support for natural language/conversations using Dialogflow.
There's currently a "natural" plugin but it does nothing interesting. It would be interesting to have an actual natural language agent tied to it.
Using dialogflow through NodeJs is trivial:
https://www.npmjs.com/package/dialogflow

This is complete.

repo: gfaraj/super-bot


text:
Respect markdown quote blocks

We should't wrap these

This seems like it's addressed by #7

I don't think so. I think the parser rules will be subtly different. For code blocks it's "stop wrapping when you see 3 backticks, start when you see the next 3 backticks". This is basically just "don't wrap lines that start with >"

Oops, you're right. I read them as the exact same issue wording. My mistake.
Sent from my iPhone

On Mar 25, 2016, at 7:53 AM, Gordon Fontenot notifications@github.com wrote:
I don't think so. I think the parser rules will be subtly different. For code blocks it's "stop wrapping when you see 3 backticks, start when you see the next 3 backticks". This is basically just "don't wrap lines that start with >"
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

authors: gabebw gfontenot

repo: gfontenot/hfold


text:
Matlab Scheduler

Added a convenience class for loading/saving results and scheduling with ASAP. It comes with a documented example.

Thanks a lot for this additional functionality

authors: mantiuk mikhailiuk

repo: gfxdisp/asap


text:
Filetype option for listing directories like find -type d?

I noticed there isn't a directory/folder type in --list-file-types. I want to list directories like you would with find -type d, is this possible with ag?

Would it be of any use?

Definitely @forgottenswitch. One great use case would be to allow ag to replace the default ALT-C command for FZF (which uses find) to quickly search and switch directories with cd.
See https://github.com/junegunn/fzf for more info - replacing the main command CTRL-T is already doable with export FZF_DEFAULT_COMMAND='ag -g ""'

So you want something like find | ag ... ?

#!/bin/sh

files=$(ag -g "$@")
dirs=$(echo "$files" | sed -e 's:/[^/]*$::' | uniq)

echo "$files"
echo "$dirs"

And why fzf cannot do the above on its input?

fzf already can - it uses find for it by default, something like find -type d.
That workaround might end up being too slow and would ignore empty folders.
I'm asking to see if it would be possible to do the same with ag, though it seems maybe it won't be possible since it does not print directories.

But the script above does just that.

Not that it is not possible, but matching on directory names is something ag wasn't meant for :)

See https://github.com/forgottenswitch/the_silver_searcher/tree/gdirs
Reopening the pull once it is OK.

Go has filepath.Walk; use that in either fzf or helper binary.

To rephrase the request:

--dirs for printing directories with -g
--dirs-only for not printing files with -g
--dirs-nonempty for ignoring empty directories with -g
And if that is implemented, then why not:
--dirs-with-files-matching
--dirs-with-filenames-matching
--dirs-with-dirnames-matching

Maybe --dirs, --dirs=nonempty, and --dirs=only shold be added.

+1

+1

Worth noting that fd a similar project already does this pretty well.  It's probably unnecessary for ag to do this

authors: acannon828 forgottenswitch kevinzwhuang marcelpaulo shtanton


text:
FF 66.0.4 and security.nocertdb=true [1549344]

Hello.
I think everyone knows about the problem with addons for firefox. Mozilla released version 66.0.4 yesterday that should fix this problem. But I was faced with the fact that even on the new version of Firefox add-ons did not work. I began to find out why. It should be said that I use the hardening version user.js. As it turned out the problem lay with pref security.nocertdb.  If a intermediate certificate caching off then addons are not installed even on FF 66.0.4. I always thought that intermediate certificate caching huge fingerprint which raise entropy. I have not experienced any difficulties after disable. Tor Browser also always disables it. How to be now I do not know. I need addons but I don’t want to increase my entropy.
What do you think about that?

I had the same issue, I have it set to false for now. There will be more updates.

So far I`m use FF 66.0.4rc1. Addons work fine (except https-everywhere) and security.nocertdb "true" too. FF 67b17 have same problem as well as stable.

It should be said that I use the hardening version user.js

Just to be super clear: We don't have a hardened user.js. And the pref is inactive in our only user.js template. So I assume you mean you hardened it yourself

https://bugzilla.mozilla.org/show_bug.cgi?id=1549344
The hotfix added a new "temp" cert, and thus would not persist. I had no expectations about the dot release, but seeing as it's a "temp" cert (I haven't looked at it's expiry date) and that they are looking the whole mechanism and will be making other changes - that the dot release would probably do the same - i.e it is just the hotfix but rolled into an update to cover all those who didn't have Normandy on (which is exactly what they said they would do).
It's affecting Tor Browser (security.nocertdb = true at all slider settings), so I am sure they will. I wonder where the old one used: must have been hardcoded

Just to be super clear: We don't have a hardened user.js. And the pref is inactive in our only user.js template. So I assume you mean you hardened it yourself

I know it. :) Just unfortunately every year you become softer and softer, trying to please ALL users. Therefore, I have long been making my own user.js based on yours. Change some prefs from "true" to "false" and "false" to "true". Make active pref etc. Add some.

https://bugzilla.mozilla.org/show_bug.cgi?id=1549344
The hotfix added a new "temp" cert, and thus would not persist. I had no expectations about the dot release, but seeing as it's a "temp" cert (I haven't looked at it's expiry date) and that they are looking the whole mechanism and will be making other changes - that the dot release would probably do the same - i.e it is just the hotfix but rolled into an update to cover all those who didn't have Normandy on (which is exactly what they said they would do).
It's affecting Tor Browser (security.nocertdb = true at all slider settings), so I am sure they will. I guess the one loaded into memory wasn't patched? The one that gets created on new profiles? I wonder if that's a bug as well? IDK

That is, there is hope that mozilla will fix this in the next stable version? It's good.

Just unfortunately every year you become softer and softer, trying to please ALL users. No offence.

None taken. But there is nothing "soft" about what I change - there is always a reason. This is still a very hardened setup. Sure it can be further hardened - but that's on the end user

I do not want to flood, but... For example, one of the latest changes regarding the work of Netflix with their DRM video.
https://github.com/ghacksuserjs/ghacks-user.js/issues/709
Was it really so necessary? People who need Netflix don't care about security and privacy. But you made concessions. I am sure that three years ago you would never do such a thing. Ah-h, golden years. :)

WTF are you talking about? The user.js, as is, does not allow cdm or eme, or the openh264 gmp (because only WebRTC uses it and that's disabled), and AFAICT the only pref I made inactive to do with gmp/cdm/eme i.e. pref 1820, doesn't do anything except hide plugins in about:addons and thereby also hides those plugins' options (such as always/never activate, and updates of them). In effect, there has been no change.

People who need Netflix don't care about security and privacy

Most people have no idea, and just want the web to work. That doesn't mean they don't care about these. And for it is entirely possible to use Netflix with both of those: security risk of the codecs is very low - just using a browser is a security risk. Privacy, their streams are encrypted. But like any service /platform on the internet - they have to decide if they want it and how to use it. I'm not a NF user, but you used to be able to use a VPN, you used to be able to pay with non-traceable methods (prepaid cards, bitcoin? IDK), use a thowaway account. But at the end of the day to say they don't CARE about privacy is a load of hogwash.

I am sure that three years ago you would never do such a thing

Here is a quote "Once is an accident. Twice is a coincidence. Three times is enemy action."  Just stop digging that hole... and making assumptions about why I do something.

You do a good job @Thorin-Oakenpants , your efforts are appreciated. It all seems like a lot of information and confusing at times, so thanks for being thorough.

The more unnecessary services running, the wider the vector to attack from the outside. Over the past year you have done a lot of things inactive or removed. To tell the truth, I have already begun to think about the fact that Mozilla has set on lawyers against you. That's why you give up positions one after another. I still can not believe that you enable "safebrowsing". You gave &%$*$ google the right to dispose of which sites the user can enter, and which not. It`s wrong. I do not need to tell tales that it is important for security reason. I know how they work. This is nothing more than a means of control. They have long considered itself the masters of the Internet. And I remind you that safebrowsing has been inactive in ghacks-user.js for a long time before you enable it.
Forgive me for being straightforward. Just already boiling.

Seems fair @Shadymerlin
I think it's more a question of broadening the user-base as much as possible, a lot of people probably don't feel as safe without safebrowsing. I disable it as well, but I also have a good firewall.

That SB is also fishy to me.
@Shadymerlin why do you wait to boiling point? IMHO @Thorin-Oakenpants would never avoid constructive debate and others opinion.
But I think here goes first as security and then as privacy.

You gave &%$*$ google the right to dispose of which sites the user can enter, and which not.

Good point

The more unnecessary services running, the wider the vector to attack from the outside.

Prefs are neither services, nor they necessarily enable or disable services. Prefs control specific functionality of the browser, and their names aren't always descriptive or even accurate. Moreover, that statement of yours is nothing more and nothing less than a heuristic. Heuristic approaches usually lead to sub-optimal solutions. That's not to say they're not useful or that Pants doesn't use them. We all make decisions in our everyday lives based on heuristics without even noticing. But why resort to such decisions when you can, on a case-by-case basis:

consult the experts, ask for opinions
analyze the source code yourself to see how things really work
test stuff yourself to see what changes take place when you toggle a pref on or off

From what I've seen so far, Pants and earthlng avoid making decisions based on heuristics whenever they can.

Over the past year you have done a lot of things inactive or removed.

Again, that is not necessarily a bad thing. There were well-grounded reasons to remove or make inactive all those things. That does not equate to Pants and earthlng becoming softer. If in your books disabling stuff leads to better security and privacy, then all you're doing is leaving everything to heuristics (and making very wrong assumptions about Pants' decisions in the process).

To tell the truth, I have already begun to think about the fact that Mozilla has set on lawyers against you.

...Really? Mozilla spending money on lawyers to accuse a user... of what, exactly? of changing a bunch of settings they made available in the first place? of sharing the info on GitHub? If Mozilla didn't want you to have the freedom to make those choices, they would simply not give you that freedom. It would mean less work for them (and they wouldn't need lawyers for that!)

That's why you give up positions one after another.

Give up positions?... Is Pants not entitled to change his mind? Besides, many of the changes to the user.js only happen because the browser is getting updates all the time, and some of the things that used to make sense no longer make sense (and so on).
As for the rest of the rant: IMHO It's not constructive. The only thing you've done here is voice your distrust of Mozilla, of Google and of Pants. You're free to choose whom to trust, but if you don't even trust Pants, what are you even doing here? Does Pants owe you anything?
Consider this some criticism of my own. And in case you're still boiling, try to remember that all of us here are humans (except me, I'm a cat). We all make mistakes. Let's be civil.

https://bugzilla.mozilla.org/show_bug.cgi?id=1549249 ... hard-code new add-on signing intermediate so it's always available

I still can not believe that you enable "safebrowsing"

I didn't enable anything, stop lying. It was inactive. I actually removed most of it recently, because of idiotic statements like yours. I'm sorry now I ever provided the info. And lastly, I do actually actively block a part of it. Stop drinking the kool-aid bro! You seem to only look at things in black and white. Learn to see shades of grey.
:small_red_triangle_down: Point 1: The SB contents
Google is the only one capable of providing such a list (Safe Browsing) - or at the very least the best one. Look, call them evil, and they do shitty things .. but they also do good things, especially in the field of security (because they have to: this is not some BS IoT company). They do not fuck around when it comes to security.
Google couldn't fucking care less about what is on that list, unless it has to do with security etc. It's not a mechanism they would use for censorship: they already control that in their search engine - censorship actually goes against their model (they want diversity). And also consider the fallout and backlash if this was used to e.g say block FoxNews. And SB is used by more than just google/chrome, it's not just a google product: it's a global service provided by google. Like any list, false positives can slip in, as can one or two contentious items.
:small_red_triangle_down: Point 2: Default
Consider that the web is crawling with 5billion people (and at least one cat) , of which 4.8billion have NFI. What's more important here: catering to your wild accusations, or as a default, protecting most users.
:small_red_triangle_down: Point 3: There is no privacy risk
I'm sick of pointing this out time and time again. Read the section header, take the link. No F privacy risk with using the local SB lists or updating them.
:small_red_triangle_down: Point 4: Real time binary checks are disabled
enough said

And I can defend every single change I have made to the user.js (that doesn't mean I don't make mistakes). You keep saying I have made things "softer": but the I actually haven't, or where something actually is, e.g HTTP2, there are solid reasons - there is always a trade-off. You just keep looking at things in black and white, and in isolation.
That's twice now you have provided two examples of my "softness": cdm/eme and SB, and both times nothing was actually changed with them. Both examples you called me out on, you were wrong. Seriously dude, stop wasting my time.
I appreciate the fact that you brought up this issue, which I was already aware of: that sort of participation is welcome. But leave all your other baggage at the door

authors: Shadymerlin Thorin-Oakenpants aesthicc claustromaniac crssi