Didn't work with defaultLanguage different than en?

server.js
app.prepare().then(() => {
    const server = express();

    if (!dev) {
        server.use(compression({threshold: 0}));
    }

    nextI18NextMiddleware(app, server);
...

i18n.js
module.exports = new NextI18Next({
  defaultLanguage: 'mn',
  otherLanguages: ['en'],
});

My App starts with en not mn

@revskill10 you have full control over detection - just use no detector and pass lng: 'yourLng' on init options...https://www.i18next.com/overview/getting-started#basic-sample

@jamuhl No, what i mean is that 'yourLng' is a function from (req), not fix string ;)

https://github.com/i18next/i18next-express-middleware/blob/master/src/LanguageDetector.js#L47 but guess we drifting away from the issue here...so let's keep this here on the topic of the defaultLanguage setting not working.
It's a design decision to use the express middleware. I wouldn't say it's a fault. Support for koa, serverless,... can be sure taken into account but needs the contribution of the community using those stacks.

I added {lng: 'mn'} option it works. But first shows English texts.

@endigo that's for sure not the intended solution - let's wait for @isaachinman to have a look.

Hi @endigo, sorry to hear you are having problems. In my projects, English is always the default language, so I haven't run into these problems yet.
Can you please create a quick reproducible example via CodeSandbox?

I switched de and en in the example, changed my browser language to German, and opened localhost:3000 in an incognito window. It loaded the app in German.

@revskill10 Please don't discuss unrelated topics in issues. This is open source software that we develop in our free time - we are not here to engineer the perfect solution for you. PRs are always welcome.

@isaachinman I replaced defaultLanguage from en to de, but Chrome still rendered en for me.

@kachkaev Did you do this in an incognito window with your browser language set to German?

It's not magic - with localeSubpaths, preference is always given the route. With localeSubpaths enabled, the behaviour you're describing would indeed take place.
Otherwise, i18next-browser-languagedetector is used.
There might actually be a case for removing it once #28 lands, but I think it might be more complicated than that.

If you select the language of i18n to be 'en' in the previous session, the i18next-browser-languageDetector will cache language 'en' by assigning the value of 'next-i18next (lookupCookie key) of the cookies on the browser to be 'en'. So in the next session, the users use your website, in the initial request to get your website, the cookies that attached in req object will have the value of 'next-i18next' to be 'en' regardless of which language to be set as default language or the value of Accepted-Language field in the header -> your rendering server will send the 'en' version of your website, and obligate browser to set (again) the value of 'next-i18next' in the website cookies to be 'en' (the LanguageDetector of i18next-express-middleware will do that for you). So your website locale will forever be 'en', unless you clear the value of 'next-i18next' and assign it to be your rather language. My solution is clear the value of 'next-i18next' on the server-side to make your website`s 'locale setting' to be pristine.
 server.use((req, res, nextMD) => {     res.clearCookie('next-i18next');     nextMD();   });

I visit your website and search for the language toggle -> set language to English -> why would I not like to have your site in English the next time I visit it - but prefer the header field I already override last time?
Your use-case is unclear to me.

@p77u4n That's a fundamentally confused and hacky approach. I suggest you look carefully through the i18next options, especially the detector options.

I was able to resolve this issue by removing 'header' from detectors by adding the following to my config:
detection: {
    lookupCookie: 'next-i18next',
    order: ['cookie', 'querystring', 'localStorage', 'path', 'subdomain'],
    caches: ['cookie'],
  },

so the set up would be:
import NextI18Next from 'next-i18next'

const NextI18NextInstance = new NextI18Next({
  defaultLanguage: 'ar',
  otherLanguages: ['de'],
  detection: {
    lookupCookie: 'next-i18next',
    order: ['cookie', 'querystring', 'localStorage', 'path', 'subdomain'],
    caches: ['cookie'],
  },
})

export default NextI18NextInstance

/* Optionally, export class methods as named exports */
export const {
  appWithTranslation,
  withTranslation,
} = NextI18NextInstance

Simple and quick solution:

Rename the directory en (/public/locales/en) to something else, such as eng.
Edit i18n.js (an example where Serbian is the default language) :
`const NextI18Next = require("next-i18next").default;

module.exports = new NextI18Next({
defaultLanguage: "sr",
otherLanguages: ["eng"],
localePath: typeof window === "undefined" ? "public/locales" : "locales"
});`

Thanks, @ahmedengu this works for me.

Thank you very much @ahmedengu, you saved my day.

Hello everyone. but I had this problem and when I changed my default language to something like "fa" in the config, nothing happened and the "en" json file was loaded. I didn't have any custom server like server.js and after some search and playing with NextI18Next configs, set serverLanguageDetection option to false and everything worked properly.
new NextI18Next({   defaultLanguage: 'fa',   otherLanguages: ['en'],   defaultNS: 'agro',   localePath: path.resolve('./public/locales'),   debug: true,   browserLanguageDetection: true,   serverLanguageDetection: false, });


TypeValue and TypeSubtypeValue should be comparable

The classes TypeValue and TypeSubtypeValue should be Comparable. The serialisers for them say that they preserve object ordering - this doesn't mean anything if they are not comparable. The unit tests for the serialisers should test that they preserve the ordering.

Merged into develop.


[zuul] Update how the ci-framework hook is defined

Depends-On: https://github.com/openstack-k8s-operators/ci-framework/pull/1204

recheck

recheck

recheck

recheck

recheck
The dependency in openstack-operator is merged now

/lgtm


pe-bear: 0.6.5 -> <IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/hasherezade/pe-bear/releases.
meta.description for pe-bear is: Portable Executable reversing tool with a friendly GUI
meta.homepage for pe-bear is: https://hshrzd.wordpress.com/pe-bear/
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found <IP_ADDRESS> with grep in /nix/store/qhixf9kxi7a6i562rfk228086w2wkcqh-pe-bear-<IP_ADDRESS>
found <IP_ADDRESS> in filename of file in /nix/store/qhixf9kxi7a6i562rfk228086w2wkcqh-pe-bear-<IP_ADDRESS>

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
pe-bear

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qhixf9kxi7a6i562rfk228086w2wkcqh-pe-bear-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pe-bear https://github.com/r-ryantm/nixpkgs/archive/89b6f4114a173669da564e9d0a670cd450f1da9e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qhixf9kxi7a6i562rfk228086w2wkcqh-pe-bear-<IP_ADDRESS>
ls -la /nix/store/qhixf9kxi7a6i562rfk228086w2wkcqh-pe-bear-<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

pe-bear

Maintainer pings
cc @blitz for testing.

Result of nixpkgs-review pr 220582 run on aarch64-linux 1

1 package built:

pe-bear


CMOS-249: More Loki fixups

Ensure it has the directories it expects on startup, otherwise it won't execute the rules

Looks like with this, we're executing the queries - really need to figure out a good way of testing this...
2022-01-11T11:09:06.920130348Z [loki.sh]level=info ts=2022-01-11T11:09:06.919341601Z caller=metrics.go:92 org_id=fake latency=fast query="count_over_time({file=\"memcached.log\"} |= \"Breakpad caught crash\" | json | label_format cluster=couchbase_cluster[1h])" query_type=metric range_type=instant length=0s step=0s duration=2.752954ms status=200 limit=0 returned_lines=0 throughput=0B total_bytes=0B


Remove IdentityFrameworkClaimsAbpSession

Not needed to this class since ClaimsAbpSession handles all.

I Asp.Zero the class AbpNetZeroAbpSession need to be exclude e remove on initialization???
mat

AbpNetZeroAbpSession should be derived from ClaimsAbpSession, instead of IdentityFrameworkClaimsAbpSession like that: https://github.com/aspnetzero/aspnet-zero/blob/master/src/MyCompanyName.AbpZeroTemplate.Core/Runtime/Session/AspNetZeroAbpSession.cs


Migrate to commander

Resolves #18
Added:

Commander
Options, -o, --open, -p, --port, -v, --version, -h, --help

Re-ordered clear command as it was not a pleasant experience to clear the terminal even when you only want to see the version (I have seen the same behavior in many CLI tools), let me know your thought on this.

@alex-saunders We might want to add help for every command? Options seem fairly simple to me, What's your thought?

Re-ordered clear command as it was not a pleasant experience to clear the terminal even when you only want to see the version

Absolutely agree, good call on this.

@alex-saunders We might want to add help for every command? Options seem fairly simple to me, What's your thought?

Not totally sure what you mean by this?

@alex-saunders Nevermind about the last comment, I just meant help for every option. But, I think we are good.


Banner always shown at the top of the screen on IOS when overlap is set to true

First of all, thank you for your good work! I have been able to migrate my project from the plugin cordova-plugin-admob-pro to yours in less than 30 minutes. However, I think have found an issue on IOS.
If I try to show a banner with the following config:
admob.banner.config({
    id: 'ca-app-pub-xxx/xxx',
    bannerAtTop: false,
    autoShow: false,
    overlap: true
})

The banner is shown at the very top of screen, but it works well on android.
So, after investigating a little bit and reading some docs, I think I have found a quick workaround.
I changed the lines of code that you can find here:
https://github.com/ratson/cordova-plugin-admob-free/blob/master/src/ios/CDVAdMob.m#L791-L792
by:
if (bannerOverlap) {
    self.bannerView.frame = bf;
} else {
    self.bannerView.frame = bf;
    self.bannerView.bounds = bf;
}

and it seems to do the trick!
System Info
Ionic:

   ionic (Ionic CLI)  : 4.2.0
   Ionic Framework    : ionic-angular 3.9.2
   @ionic/app-scripts : 3.2.0

Cordova:

   cordova (Cordova CLI) : 8.1.1<EMAIL_ADDRESS>   Cordova Platforms     : android 6.4.0, ios 4.5.5
   Cordova Plugins       : cordova-plugin-ionic-keyboard 2.1.3,
                           cordova-plugin-ionic-webview 2.2.0,
                           cordova-admob-sdk 0.20.0,
                           cordova-plugin-admob-free 0.20.0 (and 14 other plugins)

System:

   Android SDK Tools : 26.1.1 (/Users/thibaultzanini/Library/Android/sdk)
   ios-deploy        : 1.9.2
   NodeJS            : v8.11.3 (/Users/thibaultzanini/.nvm/versions/node/v8.11.3/bin/node)
   npm               : 5.10.0
   OS                : macOS High Sierra
   Xcode             : Xcode 10.0 Build version 10A255

Non overlapped banner seems to be broken as well. #288

I also noticed that non overlapped banner seems to be broken as well.
#288
Can confirm.

Hey,
Changing the code at https://github.com/ratson/cordova-plugin-admob-free/blob/master/src/ios/CDVAdMob.m#L791-L792 did not help me...
I'm not using overlapping.
Any idea? someone?


Update to stable chokidar.

That's it. It is much more stable. @chrisdickinson

Merged in 82ab8ebb7f2cf4170d28ecb237bb8d9435d00abe. Thanks!


MAINT: bump napari-console to 0.0.5.

It does not exists yet, but will need to be published at some point.
In particular please see napari/napari-console#19 that tries to update
napari-console
Out of interest is bumping the minimum version of Python to 3.8,
and removal of deprecated napari API so that we can remove them from
napari.
Type of change

[ ] Bug-fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

References

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

Note that this is mostly a placeholder to get review on napari/napari-console as otherwise it seem to fall through the cracks.

please ping me for merge here when napari-console 0.0.5 is released

@sofroniewn it looks like you are the only maintainer for napari-console on PyPI, could you care to add a few other people from @napari/core-devs maybe ?
And one of you will need to make a release (pushing a tag on eponymous repo should be enough).

I've opened https://github.com/napari/napari-console/pull/20 as well to update the building process.

@Carreau : I think @sofroniewn might not respond until next week, so if we want this in 0.4.17, we might need to wait until then (which should probably be fine).


Define an input pattern if typeable

Hello, as it's not possible to play direcly with the input (afaik), how can it be possible to add a pattern on the input so when you type in it, slashes or dashes in the input are auto added.
As it is now, you have to manually put a valid format, and it's not intuitive for everyone.
Thank a lot in advance, sorry for my approximative English.

@M01n34u Try the following PR: https://github.com/charliekassel/vuejs-datepicker/pull/633
This will likely solve your issue.

Ok, I successfully tried that solutions. Thanks everyone.


Error when overriding nuxt/javascript config

Environment

Operating System: Darwin
Node Version:     v18.16.1
Nuxt Version:     3.11.1
CLI Version:      3.11.1
Nitro Version:    2.9.4
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      rootDir, devtools, typescript, sourcemap, alias, imports, runtimeConfig, modules, app, vite, css, doxErrors, i18n, build, server, analyze, loading, telemetry, vuex4
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Package
@nuxt/eslint
Reproduction
https://stackblitz.com/edit/github-xbgijp?file=eslint.config.mjs
Describe the bug
The .override('@eslint/js/recommended', {}) config does not work in nuxt dev tools eslint panel and gives the error:
Available names are: nuxt/javascript, nuxt/typescript/setup, nuxt/typescript/rules, nuxt/vue/setup, nuxt/vue/rules, nuxt/import/rules, nuxt/configs, nuxt/vue/single-root, nuxt/rules, nuxt/disables/routes, nuxt/import-globals

However, if I use nuxt/javascript, then the CLI gives the error:
Available names are: @eslint/js/recommended, nuxt/typescript/setup, nuxt/typescript/rules, nuxt/vue/setup, nuxt/vue/rules, nuxt/import/rules, nuxt/configs, nuxt/vue/single-root, nuxt/rules, nuxt/disables/routes, nuxt/import-globals

Additional context
Nuxt dev tools eslint panel doesn't seem to work in StackBlitz, but the StackBlitz link can be used to copy the eslint config to a local project for testing.
Logs
No response

I got the same error. How can this be resolved?


"Negrești" and "Poiana" are listed in the drop-down menu

Description:
"Negrești" and "Poiana" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Negrești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Negrești, NEAMȚ (Negrești)" and "Comuna Negrești, NEAMȚ".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Poiana" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Poiana, NEAMȚ (Negrești)".


Testing.

Yup.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #436   +/-   ##
=======================================
  Coverage   85.66%   85.66%
=======================================
  Files          39       39
  Lines        1863     1863
=======================================
  Hits         1596     1596
  Misses        267      267

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 d1cc2a0...1bfdcaf. Read the comment docs.


[DOC] Specify project node version in Contributions

Is this issue related to an existing part of the documentation? If so, please provide a link
I think Contributions would be a good place to put this into.
Describe the thing to improve
I was not sure which version of node to use for development but I see that package-lock.json is at version 1 so I opted for the latest node 14 version which finally did not seem to adjust package-lock.json on initial install.
My initial install with node 17 upgraded the whole package-lock.json which should not usually not be something a contributor does (I know I hate it when contributors create a PR with 50k lines of changes since they changed the lock version or structure by using a newer node/npm/yarn version). 😅
Describe the solution (optional)
Either a version file (.nvm, .tool-versions or similar) with the node version or a mention on the contributing page would be good to have.

Thank you very much for the warning. We updated it to our Contribution document!


mkDerivation.installPhase fails without a Makefile

Describe the bug
Without a Makefile the installPhase of pkgs.stdenv.mkDerivation simply fails. For projects that don't use make, they consistently have use dontInstall = true;
Steps To Reproduce
rm -rf /tmp/my-derivation
mkdir -p /tmp/my-derivation/bin
cd /tmp/my-derivation
echo '
{ pkgs ?  (import <nixpkgs> {}), ...}:
pkgs.stdenv.mkDerivation {
  name = "my-derivation";
  src = ./.;
}
' > default.nix
echo '#!/usr/bin/env bash
echo Hello there' > bin/hello.sh
chmod +x bin/hello.sh
nix-build

output
this derivation will be built:
  /nix/store/mr57j1cg42sh0gbmzzbphm5bjbca42cc-my-derivation.drv
building '/nix/store/mr57j1cg42sh0gbmzzbphm5bjbca42cc-my-derivation.drv'...
unpacking sources
unpacking source archive /nix/store/yd34hij6qplaqn61ayx247754p32dnlk-my-derivation
source root is my-derivation
patching sources
configuring
no configure script, doing nothing
building
no Makefile, doing nothing
installing
install flags: SHELL=/nix/store/dsd5gz46hdbdk2rfdimqddhq6m8m8fqs-bash-5.1-p16/bin/bash install
make: *** No rule to make target 'install'.  Stop.
error: builder for '/nix/store/mr57j1cg42sh0gbmzzbphm5bjbca42cc-my-derivation.drv' failed with exit code 2;
       last 10 log lines:
       > unpacking source archive /nix/store/yd34hij6qplaqn61ayx247754p32dnlk-my-derivation
       > source root is my-derivation
       > patching sources
       > configuring
       > no configure script, doing nothing
       > building
       > no Makefile, doing nothing
       > installing
       > install flags: SHELL=/nix/store/dsd5gz46hdbdk2rfdimqddhq6m8m8fqs-bash-5.1-p16/bin/bash install
       > make: *** No rule to make target 'install'.  Stop.
       For full logs, run 'nix log /nix/store/mr57j1cg42sh0gbmzzbphm5bjbca42cc-my-derivation.drv'.

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Other phases like the build phase don't fail without a Makefile however this phase always does. It would be great if it worked out of the box by e.g copying the sources to $out, which I would consider a sane default. That's because using dontInstall = true; in the sample code above just fails at the next phase because $out is simply empty:
this derivation will be built:
  /nix/store/mjiy6zkl2ikag2wkyyhniblamhfz3slw-my-derivation.drv
building '/nix/store/mjiy6zkl2ikag2wkyyhniblamhfz3slw-my-derivation.drv'...
unpacking sources
unpacking source archive /nix/store/9xd9a51d97pb8ya80gmyfzisysxli473-my-derivation
source root is my-derivation
patching sources
configuring
no configure script, doing nothing
building
no Makefile, doing nothing
post-installation fixup
find: '/nix/store/j45k0r86kjb48ydgy5s12r4j0zyscwqg-my-derivation': No such file or directory
strip is /nix/store/dq0xwmsk1g0i2ayg6pb7y87na2knzylh-gcc-wrapper-11.3.0/bin/strip
error: builder for '/nix/store/mjiy6zkl2ikag2wkyyhniblamhfz3slw-my-derivation.drv' failed to produce output path for output 'out' at '/nix/store/mjiy6zkl2ikag2wkyyhniblamhfz3slw-my-derivation.drv.chroot/nix/store/j45k0r86kjb48ydgy5s12r4j0zyscwqg-my-derivation'

Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.85, NixOS, 22.11 (Raccoon), 22.11.1137.dac57a4eccf`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.11.1`
 - channels(root): `"nixos-22.11, nixos-unstable"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

An output is needed and the primary phase that is supposed to be used for that is the installPhase. Hence, it should fail without an installPhase. I agree the communication is not very good here.
Make as default is how its always been around. Quite likely if there ever would be a change (and that is not going to happen lightly) then I imagine that Make support would be implemented as a setup took.
I want to close this as a won't fix but we can give it some time to let others see it.

I agree with FRidh. At some point a null derivation should fail, and failing to install is natural. I don't agree with having the default to be to copy the input directly to the output as in most scenarios that would be the result of an error in the derivation.
There are other builders which have simpler behavior. For the specific case you illustrate, have you looked at the trivial builders, in particular writeShellScriptBin?
Build systems other than make do have hooks to customize the installPhase so that dontInstall = true is actually very rare in nixpkgs. For example, buildPythonPackage will (more or less) run python setup.py install instead of make install. A quick grep shows it's in 0.2% of files in nixpkgs, mostly in test-specfic derivations and the build system definitions themselves.

Why not consistently fail the build, check, install, and installCheck phases if there's no Makefile and they haven't been overridden or skipped by the derivation author? The install phase is the only one of those phases that fails while:

build checks for a Makefile and sets foundMakefile
build does nothing when a Makefile isn't found
check and installCheck use foundMakefile to fallback to doing nothing if it's not set

IMO this is inconsistent, surprising and undocumented behavior.
@tpwrules, I'm not sure what a null derivation to you is, but if it's a mkDerivation {} then even with a default cp -r $src $out in the install, it would still fail at the unpack phase because there's nothing to copy.

Make as default is how its always been around. Quite likely if there ever would be a change (and that is not going to happen lightly) then I imagine that Make support would be implemented as a setup took.

@FRidh  I'm not suggesting to replace make. All I'm suggesting is a default fallback just like in the other phases that provide fallbacks. If the consensus is to keep the failing behavior, then I suggest that it should at least be documented that the install phase is mandatory and should either be:

overriden with installPhase = '' yada yada yada'';
skipped with dontInstall = true;

By a null derivation, I mean one that doesn't do anything. If it just has a source input and name and no phases run, then it can pretty much just be replaced by the source input and there's no point involving mkDerivation at all (modulo unpackPhase).
The job of the installPhase is to create the final output, so having it be the one to die noisily instead of an earlier phase makes the most sense. Having a fallback which just copies the input to the output would mean that this case succeeds but nothing useful happens. In the case of a derivation with e.g. a broken make install, the output would be filled up with build junk which is bad too.
The error message is indeed unhelpful. But the behavior and philosophy of the standard build environment is pretty explicitly documented in the relevant chapter of the Nixpkgs manual.

By a null derivation, I mean one that doesn't do anything.

As in no build phase? Or would you consider a bunch of bash, python, and perl scripts with dependencies (buildInputs) that have to be copied into $out/bin/ also "not doing anything"?

If it just has a source input and name and no phases run, then it can pretty much just be replaced by the source input and there's no point involving mkDerivation at all (modulo unpackPhase).

How would that work? I'm new to nix and still learning. derivation still needs to put something into $out in order to work

The job of the installPhase is to create the final output, so having it be the one to die noisily instead of an earlier phase makes the most sense. Having a fallback which just copies the input to the output would mean that this case succeeds but nothing useful happens.

I disagree here, because copying is useful (it's the entire goal of the step). make install's goal is to copy the compiled binaries and relevant assets to a configured prefix. In this case the prefix is often $out. In the simplest case, it's just a single cp.
Additionally, there are other phases that occur after e.g the fixup phase which includes patchShebang, patchelf, and others, so it is indeed not the final output.

But the behavior and philosophy of the standard build environment is pretty explicitly documented in the relevant chapter of the Nixpkgs manual.

I really do not find that helpful documentation. It's a huge chapter that starts with

The standard build environment in the Nix Packages collection provides an environment for building Unix packages that does a lot of common build tasks automatically. In fact, for Unix packages that use the standard ./configure; make; make install build interface, you don’t need to write a build script at all; the standard environment does everything automatically.

For the first two, common tasks that may deviate from the "standard" ./configure; make; make install fallbacks are provided, but for the last, common, and simplest step (copying build output to the destination), there's no fallback nor is it explicitly documented that there is no fallback.

How would that work? I'm new to nix and still learning. derivation still needs to put something into $out in order to work

Yes, but a derivation which does cp $src $out is, except for the unpack and fixup phases, the same as just replacing the pkgs.stdenv.mkDerivation {} with ./., as ./. expands to a store path with the contents of that path copied into it.

As in no build phase? Or would you consider a bunch of bash, python, and perl scripts with dependencies (buildInputs) that have to be copied into $out/bin/ also "not doing anything"?

Then you would have to specify a custom installPhase to copy the scripts to $out/bin/. Your previous suggested default of cp $src $out isn't correct here.
Which underscores the problem, that there's no general way to know what the "build output" actually is. And given that it's the purpose of a derivation, it's better to fail if the convenience here doesn't work so the user can do it properly instead of just copying some arbitrary files. In your example derivation, for instance, you'd end up with a spurious default.nix in the output if it worked how you wanted.

https://github.com/NixOS/nixpkgs/pull/209255

I think we're on opposing ends here @tpwrules on whether the default action should be a cp or not. IMO the middle ground is either @Artturin's PR to make it consistent with the other phases and print a message saying it'll do nothing, or to add documentation and very clear error message stating a Makefile is missing and the installPhase attribute has not been override.
Either way, it's my staunch opinion that the current situation should not persist at it does right now:

A somewhat cryptic error message
Missing documentation
no suggestion on how to remedy the situation


Implement and test GVP alternative

Minimal code to get features for a sample protein (see commit 72c2855):
# %%
from prody import fetchPDB

fetchPDB('10gs', compressed=False)

# %%
from src.utils.residue import Chain
c = Chain('10gs.pdb', grep_atoms={'CA', 'N', 'C'})
# %%
import logging
logging.getLogger().setLevel(logging.DEBUG)

c.getCoords(get_all=True).shape # (N, 3)

# %%
from src.data_prep.feature_extraction.gvp import GVPFeatures

gvp_f = GVPFeatures()

# %%
f = gvp_f.featurize_as_graph('10gs', c.getCoords(get_all=True), c.sequence)
# %%
```

Figure shows good performance with GVPL, GVPP not so much.

Updated plot with new aflow results from https://github.com/jyaacoub/MutDTA/commit/f6cd150faeb5de578a838fe275b4def7a63e07ff
After more extensive hyperparameter tuning since it seemed weird that it had such high variance.

Code to generate figure + remove old results:
# %%
import logging
from typing import OrderedDict

import seaborn as sns
from matplotlib import pyplot as plt
from statannotations.Annotator import Annotator

from src.analysis.figures import prepare_df, custom_fig, fig_combined

df = prepare_df()
sel_dataset = 'PDBbind'
exclude = []
sel_col = 'cindex'

# removing first instance of aflow, only keeping second more tuned model
idx = df[df.run.str.contains('DGM_PDBbin.*?D_nomsaF_aflowE_128B_0.00012')].index
df.drop(idx, inplace=True)
# %%
models = {
    'DG': ('nomsa', 'binary', 'original', 'binary'),
    'aflow': ('nomsa', 'aflow', 'original', 'binary'),
    'aflow_ring3': ('nomsa', 'aflow_ring3', 'original', 'binary'),
    # 'gvpP': ('gvp', 'binary', 'original', 'binary'),
    # 'gvpL': ('nomsa', 'binary', 'gvp', 'binary'),
    'gvpL_aflow': ('nomsa', 'aflow', 'gvp', 'binary'),
    'gvpL_aflow_rng3': ('nomsa', 'aflow_ring3', 'gvp', 'binary'),
}

# %%
fig, axes = fig_combined(df, datasets=['PDBbind'], fig_callable=custom_fig,
             models=models, metrics=['pearson', 'cindex', 'mse', 'mae'],
             fig_scale=(8,5))
plt.xticks(rotation=45)

# %%

Davis performance

I suspect that the poor performance of GVPL_aflow on Davis is due to the low ligand count in Davis, this makes it harder for it to generalize well to unseen ligands.
Due to the increased complexity of the GVP branch for the ligand it is more likely to overfit under such few data points.


Cannot read property accept-version when changing column from array to non-array

[ ] Repro

This is a sample payload that I tried with, which returned the error
name: "test_column"
comment: "this is a comment"
type: "int4[]"
defaultValue: "{1, 2, 3}"
defaultValueFormat: "expression"
isIdentity: false
isNullable: true

btw bump on this ^ i've a feeling its that pg-meta isn't returning the errors from postgres correctly? e.g if i have a column that has entries with null values in it, and I toggle is_nullable to false, this error gets thrown as well

Relevant issue: https://github.com/supabase/supabase/issues/592#issuecomment-769977569

I also reproduced this bug in the following steps:

Create a new table:

'

Save the new table.

Edit the object column and add the following Default value:

{'test':null}

Save the updated column and you will see the error.

i've a feeling its that pg-meta isn't returning the errors from postgres correctly?

This hits the mark, pg-meta wasn't returning the actual errors, which will be fixed in #149.
As for most of the errors when changing column types, the actual error seems to be that the types can't be converted automatically. E.g. changing a text column to text[] will give column "my_column" cannot be cast automatically to type text[]. The solution in this case is to drop down to SQL:
ALTER TABLE t ALTER my_column TYPE text[] USING ARRAY[my_column];

I think it's acceptable for the table editor to just error out when converting incompatible types, but maybe we should document how to get around this (e.g. by pointing them here).

gotcha on this, thanks so much @soedirgo! 🙏 Agreed that table editor should just return the errors from postgres rather than trying to do some magic to workaround the errors


Repaired TemplateURL issue

Repaired the TemplateURL issue pointing to the wrong URL.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/do-e2e-tests

need to update new commits


x64 new backend: port ABI implementation to shared infrastructure with AArch64.

Previously, in #2128, we factored out a common "vanilla 64-bit ABI"
implementation from the AArch64 ABI code, with the idea that this should
be largely compatible with x64. This PR alters the new x64 backend to
make use of the shared infrastructure, removing the duplication that
existed previously. The generated code is nearly (not exactly) the same;
the only difference relates to how the clobber-save region is padded in
the prologue.

Updated -- thanks! This has been verified to work with SpiderMonkey as well.


[Bug] issue from Logical functions

Before you submit this issue, have you checked the following

[X] Is this really a problem?
[X] I have searched the Github Issues for similar issues, but did not find anything.

Affected packages and versions
latest
Reproduction link
1、公式计算结果错误（）

分析：VLOOKUP 查找算法
2、修改引用选区后undo，公式未显示计算结果2024_7_8 10_58_16 commands.json
2024_7_8 10_58_16 video.webm

分析：数据更新问题
3、引用选区为空计算不出结果，Excel、365支持

分析：为空是大多数函数通用问题，很多没有处理，需要统一处理
Expected behavior
匹配Excel
Actual behavior
查找不对
System information
No response

After discussing with @wpxp123456 , we have come to the conclusion that the edge case does not need to be handled for now, and we are waiting for user feedback.


beta6 seems to ignore logarithmic setting

Hi there,
beta6 seems to ignore logarithmic setting like this:
scales: {
x: {
},
L: {
suggestedMin: 0,
suggestedMax: 60,
//max: 1100,
type: 'logarithmic',
display: true,
position: 'left',
gridLines: {
drawOnChartArea: false, // only want the grid lines for one axis to show up
},
display: false
}
}

Can you please make a simple jsfiddle with a example chart of the problem?

I have only 2 pictures from the same data with beta3 and beta6.

@fly74 I believe prior to beta.6 suggestedMin was not used on the logarithmic scale. Try removing that (setting to 0 is invalid anyway since log(0) is not defined). I thought @kurkle already made it work correctly though.

@fly74 I believe prior to beta.6 suggestedMin was not used on the logarithmic scale. Try removing that (setting to 0 is invalid anyway since log(0) is not defined). I thought @kurkle already made it work correctly though.

That was correct, thx.


What is the "Debug dropdown"?

I am trying to follow "Building CMake projects" https://docs.microsoft.com/en-us/cpp/ide/cmake-tools-for-visual-cpp?view=vs-2017#building-cmake-projects but I am lost at "Select the target in the Debug dropdown" because I do not know what is the "Debug dropodown". May you please add a screenshot to help me? Thank you.

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

ID: 781298c5-3bb4-0bd4-06ca-b09517a76ebc
Version Independent ID: acb60102-701d-ccb2-d138-2ceb35813292
Content: CMake Projects in Visual C++
Content Source: docs/ide/cmake-tools-for-visual-cpp.md
Product: visual-cpp
GitHub Login: @mikeblome
Microsoft Alias: mblome

@alessandro-gentilini Sorry about that! Yes I will add a picture. In the meantime, the "dropdown" is the button in the middle of the toolbar with a green arrow that means "start debugging." There is also a small black arrow pointing down. That's the "dropdown" part. Click it to see the different targets that are available.

FYI, when I opened a CMakeLists.txt file just now it only created a single configuration "x64-Debug (default)".
When I selected CMake -> Change CMake Settings -> projectname, it popped up a dialog that allowed me to select other configurations; I chose x64-Debug again and it deleted that previous configuration and created a new one called "x64-Debug" (which now compiled to a slightly different place than before).
Selecting the menu option again does absolutely nothing.  I eventually found that I could right-click the CMakeSettings.json file and select Add Configuration to bring back the dialog and add configurations one at a time (which was mildly annoying since I wanted debug+release+x86+x64, so four in total, and it reminded me to save changes to the settings file for each addition).

I was confused by the exact same behavior as you @uecasm. I was hunting for a way to do what you described with the "Add Configuration" option so that will probably save me a few hours of frustration, thanks!

fixed the wording. Change should appear later today. thanks!


Upgrade axios to 0.21.2

Axios 0.21.1 has a security issue which is causing npm audit to complain. Bumping it to 0.21.2 should fix the issue.

@nmorsman  seems like you might be the author of this codebase, can you please review this PR :)

Hey! 👋 Fixed in a93584f4817eca633cd594b7141c73e2357759c8 and published with v4.1.4.


Wiki: Improved systemd services (+VT-less)

Based on the service file from the cage service Wiki page, I created some improved services for running cage. One is pretty similar and now starts<EMAIL_ADDRESS>on service failure:
https://overhead.neocities.org/blog/cage-foot-initramfs/#replacing-getty
And the other starts cage without the dependency on Virtual Terminals (VTs):
https://overhead.neocities.org/blog/cage-foot-vt_less/#brand-new-shoes

It should be noted that this service currently requires seatd.service, though it should be possible to just use systemd-logind by itself once I figure out the PAM issue I've been having. I'll be report back here if and when that happens.

I thought I'd open this issue in case you were interested in including these services, feel free to close if not.

It turns out the services aren't as robust as I first thought, and are more tailored to my specific environment then I realised, so they probably won't be that useful to include in the Wiki. Closing issue


New tabs are created when exploring data

Hello!
I am facing an issue with where when I click on the data to explore already labelled tasks, I keep seeing new tabs created in the page by a user with the icon "(".
Also, I suddenly started receiving this error
"Error: [mobx-state-tree] Failed to resolve reference 'production' to type" when trying to check already annotated tasks.
I tried to look over the github issues but I did not find these reported. I might have missed it, apologies in advance.
Thank you so much for your work with label-studio!

@abfshaal Hello, could you send here some screenshots with an opened browser console errors?

Hello @makseq

I had solved the issue, It had to do with the table tasks_draft being created in the PostreSQL database.
I deleted that table inside the database and it removed all the randomly spawned drafts and the error with mobx.


chore(tagger): remove liveness probe for Replay Tagger

What does this PR do?
Removed the Liveness probe from the Replay Tagger.
Relates to https://github.com/DataDog/datadog-agent/pull/8193

Motivation
The Replay Tagger is only used for debug/bench purposes. While it is not used normally by the Agent, it should not have a Liveness probe that could have an impact on Agent deployments in case of misconfiguration.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

dogstatsd-capture is not working correctly as of now so we are skipping QA. An issue has been opened (AMLII-1652).

/merge


Search in narrowed view.

Search should be performed in current narrow.

Automated message from Dropbox CLA bot
@Sam1301, it looks like you've already signed the Dropbox CLA. Thanks!

@Sam1301 fix the merge conflicts!

@kunall17 resolved the merge conflicts :+1:

Works well! :) 👍
@timabbott LGTM!

Merged, thanks @Sam1301!


use JSON output

need to check how to calculate Network speed from
dl_flow
dl_throughput
lud_foreign_h2_rep_resp
lud_foreign_tcp_handshake_443
lud_self_dl_h2
lud_self_ul_h2

implemented with 1.0.6-beta - to be confirmed.


Apply algebra doesn't dispatch correctly to fantasy-land

Describing the bug in terms of the implementation:

src/core/flNames.js is missing the ap property.
src/pointfree/ap.js is calling hardcoded .ap, instead of calling the fantasy-land method name, if available. See map.js for inspiration.

To Reproduce
const fl = require('fantasy-land')
const R = require('ramda')
const C = require('crocks')
const inspect = require('util').inspect.custom

class Just {
  constructor(x) {
    this.x = x
  }
  static of(x) {
    return new Just(x)
  }
  [fl.map](f) {
    return Just.of(f(this.x))
  }
  [fl.chain](f) {
    return f(this.x)
  }
  [fl.ap](m) {
    return m[fl.map](this.x)
  }
  [inspect]() {
    return `Just ${this.x[inspect] ? this.x[inspect]() : this.x}`
  }
}

console.log(R.map(R.add(5), Just.of(5)))
console.log(R.chain(x => Just.of(R.add(5, x)), Just.of(10)))

const add5 = Just.of(R.add(5))

// Manual `ap` call works:
console.log(add5[fl.ap](Just.of(15)))

// Ramda's `ap` works:
console.log(R.ap(Just.of(20))(add5))

// Crocks' `ap` FAILS:
console.log(C.ap(Just.of(25))(add5))

Expected output
Just 10
Just 15
Just 20
Just 25
Just 30

Actual output
Just 10
Just 15
Just 20
Just 25

TypeError: ap: Both arguments must be Applys of the same type
    at ap (<redacted>/node_modules/crocks/pointfree/ap.js:14:11)
    at <redacted>/node_modules/crocks/core/curry.js:25:12
    at Object.<anonymous> (<redacted>/test-ap-crocks.js:43:30)

Possible solution
I implemented a quick hack to fix it:
Change src/pointfree/ap.js:20 to:
return (m[fl.ap] || m.ap).call(x, m)

Add the ap property to src/core/flNames.js:
ap: 'fantasy-land/ap'

Actual solution
Instead of maintaining a list of fantasy-land names in flNames.js, why not add the npm package fantasy-land as a dependency? It actually exports this list of names. I bet more stuff is missing, or will be in the near future ;)

Awesome. We have an issue for starting work on this here.
It is tricky, because we want to allow ap to behave with the function in the instance (opposite of what fl does).
We also need to make adjustments to each Apply type to account for that, as well as update traverse in some places.
We may be removing fantasy-land entirely, but will post up an issue for the community to debate the direction.
As far as dependencies got, we do not want to be tied to dependencies, especially around fantasy-land. That is why we do not use things like fantasy-land or fantasy-laws. If they pull something like they did with ap in the first place again, I do not want to be left behind if we opt not to go that way. So for instance, if a new property is added after a major changes, if we decide to stay up to our old version, but still want to include the new type, we can.
Will keep this open to track the work after applyTo is added to the types.

But. We may be able to just update the point free function, and worry about the fl dispatch on the crocks types for now, will need to think that trough on what the transition will be like. Also this will affect the lift functions, so you can verify by using liftA2 in crocks against your Just.

Ohhh. also, I think that implementation of fantasy-land/ap is backwards. The function is coming in as the data, that should be the value. To match the fantasy-land spec the implementation should be:
class Just {
  [fl.ap](m) {
    return this[fl.map](m.x)
  }
}

// These are now:
const add5 = Just.of(R.add(5))

// Manual `ap` call works:
console.log(Just.of(15)[fl.ap](add5))

// Ramda's `ap` works:
console.log(R.ap(add5)(Just.of(20)))

// Crocks' `ap` FAILS:
console.log(C.ap(add5)(Just.of(25)))

This comes from the Appy spec, so with those pointfree functions the data is the last, so that should be the value to be applied.

b must be an Apply of a function

also, I think that implementation of fantasy-land/ap is backwards

You're totally right, I was struggling a bit with that. I'm still learning about algebraic programming. Thanks for the tip!
Incidentally, it's also the reason I couldn't get Sanctuary's ap to play along in my example. Now it does:
const R = require('ramda')
const S = require('sanctuary')
const C = require('crocks')

class Just {
  constructor(x) {
    this.x = x
  }
  static of(x) {
    return new Just(x)
  }
  [fl.map](f) {
    return Just.of(f(this.x))
  }
  [fl.ap](m) {
    return this[fl.map](m.x)
  }
  [fl.chain](f) {
    return f(this.x)
  }
  [inspect]() {
    return `Just ${this.x[inspect] ? this.x[inspect]() : this.x}`
  }
}

// Manual `ap` call
console.log(Just.of(15)[fl.ap](add5))
//=> Just 20

// Ramda's `ap`
console.log(R.ap(add5)(Just.of(20)))
//=> Just 25

// Sanctuary's `ap`
console.log(S.ap(add5)(Just.of(30)))
//=> Just 25

// Crock's `ap`
console.log(C.ap(add5)(Just.of(25)))
//=> Error ap: Both arguments must be Applys of the same type

As far as dependencies got, we do not want to be tied to dependencies, especially around fantasy-land. That is why we do not use things like fantasy-land or fantasy-laws. If they pull something like they did with ap in the first place again, I do not want to be left behind if we opt not to go that way. So for instance, if a new property is added after a major changes, if we decide to stay up to our old version, but still want to include the new type, we can.

You could choose to pin the version when you add fantasy-land as a dependency. That way you can choose to support a specific version of fantasy-land, and if you don't agree with the direction in the future, just don't support that newer version and don't upgrade. I believe other libraries are doing something similar.

Awesome. We have an issue for starting work on this here.

Will keep this open to track the work after applyTo is added to the types.

Ok sure, will track this!

You could choose to pin the version when you add fantasy-land as a dependency. That way you can choose to support a specific version of fantasy-land, and if you don't agree with the direction in the future, just don't support that newer version and don't upgrade. I believe other libraries are doing something similar.

We would have to add "new" things ourselves and curate it anyway. So for instance, invert for Group happened after 1.x so if we locked down pre-1.x, then we would have to curate invert anyway.


[26.x][WFLY-16481] Fix NPE in EndpointService when PublishEndpoint

…axrs pom file license
https://issues.redhat.com/browse/WFLY-16481
Upstream: #15653

Hello, jimma. I'm waiting for one of the admins to verify this patch with /ok-to-test in a comment.


Discuss possible code checks to be used in meshpy

This issue shall serve as a spot to discuss possible code checks and pre-commit hooks to be used within MeshPy. Some possible choices can be seen here https://github.com/davidrudlstorfer/pyskel/blob/main/.pre-commit-config.yaml (thanks to @davidrudlstorfer).
Possbile tools:

[x] pylint currently we have 8.93/10 for meshpy/ and 8.55/10 for tests/
[x] Ruff
[ ] Code formatter for markdown
[x] Code formatter for c++
[ ] Code formatter for Cython. Does such a tool exist? Do we need this as the Cython code likely will not change on a regular basis.

To note it for later discussion; we could also utilize ruff (https://github.com/astral-sh/ruff) which replaces flake8, isort and black in one tool. This tool is currently spreading fast

I think with #153 we got a very long way towards completing this issue. Are there still some things missing? Two I can think of are the required docstrings and prohibiting relative imports (I added them to the description).

#153 includes a first suite of pre-commit hooks and also utilizes it within the code check pipeline
Further points to complete code checks are:

Enforce absolute imports, i.e., meshpy.rotation.blablub rather than ..rotation.blablub
Enforce the docstrings, currently we have 96% coverage => add remaining docstrings and set 100% coverage
Enforce the docstring style, i.e. args to be consistent across the code base
Type hinting - I think we briefly talked about this and you had some points against that?
Enforce that each source code file contains the license header

Run xml formatting and syntax check on vtu/vtk files (per https://github.com/imcs-compsim/meshpy/pull/153#issuecomment-2545871930)

Regarding the xml formatting and syntax check on vtu/vtk files:
Yesterday I wasted a lot of time to get this running and I was not able to get it to work at all. I was not able to add differing file endings to the xml hooks.
We probably need our own special hook for that. Maybe we can just take the contents of the vtu/vtk files and hand it over to the xml hooks.

That was just a suggestion, we don't have to do that if it is complicated. The relevant files are almost never created by hand so I am fine with just sticking with the default format there (now that I think of it, I think in 4C we also don't format those files - at least I never had any issues checking in the automatically created ones).


bug(@vtmn/react): VtmnDropdown doesn't support style property in jsx/tsx files

Describe the bug
When I set style property to VtmnDropdown component, it's not supported and I need to create a simple css file to momentarily
resolve the issue

Steps to reproduce

Install React
Install the Vtmn package for React

Expected behavior
When I create a style property for VtmnDropdown component, it should be supported
Version affected
@react: 18.2.0
@vtmn/react: 0.67.0

Thanks @jdeca-decat for this issue.
As the @vtmn/react is a community library, I hope someone will take this issue to help you.
If you want, feel free to contribute also! We are there to help you if needed regarding launching & contributing on the vitamin-web stack.


AttributeError: 'Response' object has no attribute 'req_session'

I installed this client with pip today. When I attempt to download a file using .from_web I get the attribute error shown. Am I missing something?
Using this client will be super helpful for my lab. Thanks!

I have the same problem. The problem seems to be the API link is broken and it cannot fetch anything because there is nothing to fetch. I'll be exploring this and will update here if I fix it.
@matteoferla Do you know if the API link has changed recently?

@sjrothfuss I fixed it. See Pull Request #2


DRUD-502: Add audit log-shipping to vault

DRUD-502
This uses the sidecar technique in fluentd-sidecar-gcp to ship logs to google cloud logging. They are shipped as a jsonPayload and then can be queried by field in the logging interface, and can also be exported or sent via "sink" to bigQuery.
Testing technique:

Deploy the vault deployments (vault-1 and vault-2), unseal the vault, make sure it works. (You could just interact with one vault server, it doesn't matter much for this one.)
Make sure the audit log is turned on (vault audit-enable file file-path=/vault/logs/audit.log)
Do some activities with the vault
Study the logs on google cloud logging.

Example advanced logging query (remember to change project if necessary):
resource.type="container"
resource.labels.cluster_name="vault-freshstart"
logName="projects/vault-freshstart/logs/file.audit.log"

Example bigQuery query with ingested logs:
SELECT jsonPayload.auth.display_name, jsonPayload.request.path FROM [vault-freshstart:auditlog.file_audit_log_20161216] LIMIT 1000

Quick note: file-path should be file_path, as such:
vault audit-enable file file_path=/vault/logs/audit.log

Edited to file_path - thanks.


Critiques and a feature suggestion

First, I would like to thank you for assembling and publishing this project.
There are a couple small things that could be improved:

Certain functions return what the library user is looking for directly, and other functions return a promise that the library user has to deal with. The library user has to read through the documentation more carefully to get it right.
A couple of functions loop through the contents in the Javascript, which can be slow for large objects. This should only be done in the case of old, broken browsers (assuming they will be fixed, someday).

For 1, I can think of several possibilities, in increasing order of favorability:

Break this into two projects (one for the functions that return promises and one for the functions that return the object directly) (not recommended)
Rename the functions to indicate which ones return a promise (a little better but still not recommended)
separate namespace or inner namespace for the functions that return a promise

For 2, I suggest the library checks the browser very carefully before actually looping through the contents in Javascript
A feature that could help some people is a pair of functions that provide the functionality of pouchdb/pouchdb#2900, to convert between a Blob and a binary string that can be stored in the existing Web SQL implementations (including my Cordova sqlite plugin). I may put this in a PR if I get a chance sometime.

Thanks for the suggestions! Responses:

Certain functions return what the library user is looking for directly, and other functions return a promise that the library user has to deal with.

Yeah, it's annoying, but I think the only solution would be to make every API return a promise for everything, which is kind of annoying. As of right now, you only need non-promises for createObjectURL, revokeObjectURL, and createBlob.

A couple of functions loop through the contents in the Javascript, which can be slow for large objects. This should only be done in the case of old, broken browsers (assuming they will be fixed, someday). Unless there's an API I missed?

On newer browsers I prefer the newer methods (e.g. readAsArrayBuffer() where it's available instead of readAsBinaryString()).

separate namespace or inner namespace for the functions that return a promise

I think sadly the only solution to this problem will come with ES7 when we have async functions. Then I can just mark the promise-returning functions as async and it will be crystal clear because your IDE will show an error if you try to use an async function as a function or vice-versa.
In general I would like to increase the modularity of this project by breaking everything up into separate files, so that you can e.g. require('blob-util/blobToBinaryString') and only use the functions that you need. I would happily accept a PR to change it that way! :)

Agreed with your idea to increase the modularity, I don't expect to have time to work on this one. You may want to open a new issue for this with a "help-wanted" label.


Rules:

Configurations are immutable, they cannot be added to or deleted
Configurations are applied to a device (sensor / element) via a DeviceConfiguration
There can be exactly one (1) DeviceConfiguration per device
Creating a new DeviceConfiguration for a particular device overwrites any prior DeviceConfiguration for that device
DeviceConfigurations can be deleted

Usage:
Given any device (sensor/element), you can fetch the DeviceConfiguration with device_configuration
[3] pry(main)> e = client.element("56618098-5145-445c-a6db-805eaf37ff51")
...
[4] pry(main)> device_config = e.device_configuration
=> #<Helium::DeviceConfiguration:0x007ffb71a74738
 @client=<Helium::Client @debug=false>,
 @created_at="2016-11-18T23:18:43.576921Z",
 @id="85a9bbf9-0ff7-4678-b071-03342b6c7f91",
 @loaded=nil,
 @params=
  {"attributes"=>{},
   "relationships"=>{"device"=>{"data"=>{"id"=>"56618098-5145-445c-a6db-805eaf37ff51", "type"=>"element"}}, "configuration"=>{"data"=>{"id"=>"461b1e38-6fc2-423b-974a-ae6f504c43a1", "type"=>"configuration"}}},
   "id"=>"85a9bbf9-0ff7-4678-b071-03342b6c7f91",
   "meta"=>{"loaded"=>nil, "created"=>"2016-11-18T23:18:43.576921Z"},
   "type"=>"device-configuration"},
 @type="device-configuration",
 @updated_at=nil>

That DeviceConfiguration can then be inspected for its device
[8] pry(main)> device_config.device
=> #<Helium::Element:0x007ffb7311c508
 @client=<Helium::Client @debug=false>,
 @created_at="2016-04-27T18:19:06.520815Z",
 @id="56618098-5145-445c-a6db-805eaf37ff51",
 @last_seen=nil,
 @mac="redacted",
 @name="SF Office",
 @params={"attributes"=>{"name"=>"SF Office"}, "id"=>"56618098-5145-445c-a6db-805eaf37ff51", "meta"=>{"mac"=>"redacted", "created"=>"2016-04-27T18:19:06.520815Z", "last-seen"=>nil, "updated"=>"2016-11-18T01:05:34.693805Z"}, "type"=>"element"},
 @type="element",
 @updated_at="2016-11-18T01:05:34.693805Z">

If the device happens to be an element, a Helium::Element will be returned, if it is a sensor a Helium::Sensor will be returned
Of course all of this would be pointless if we couldn't also see the configuration
[9] pry(main)> device_config.configuration
=> #<Helium::Configuration:0x007ffb7302ce68
 @client=<Helium::Client @debug=false>,
 @created_at="2016-11-09T21:43:03.471454Z",
 @id="461b1e38-6fc2-423b-974a-ae6f504c43a1",
 @params={"attributes"=>{"somenumber"=>"foo", "wifipasswd"=>"123456789", "jaredtest"=>true}, "relationships"=>{"device-configuration"=>{"data"=>[{"id"=>"85a9bbf9-0ff7-4678-b071-03342b6c7f91", "type"=>"device-configuration"}]}}, "id"=>"461b1e38-6fc2-423b-974a-ae6f504c43a1", "meta"=>{"created"=>"2016-11-09T21:43:03.471454Z"}, "type"=>"configuration"},
 @settings={"somenumber"=>"foo", "wifipasswd"=>"123456789", "jaredtest"=>true},
 @type="configuration",
 @updated_at=nil>

The settings can be fetched for any configuration with the settings call
[10] pry(main)> device_config.configuration.settings
=> {"somenumber"=>"foo", "wifipasswd"=>"123456789", "jaredtest"=>true}

To create a Configuration and DeviceConfiguration you simply apply the k/v pairs you want for the configuration
some_hash = {"pr_docs" => true,  "some number" => 8675309 }
new_configuration = client.create_configuration(some_hash)

From there, to create a DeviceConfiguration you must have both a Configuration and a Device
some_config = client.configuration("ffffffff-c7ff-4202-8426-a864d4bd9624")
some_sensor = client.sensor("ffffffff-9cda-4313-9cf7-cffee5d57050")
 new_device_configuration = client.create_device_configuration(some_sensor, some_config)

If you want to apply a new configuration to that sensor, once again you can just create a new DeviceConfiguration and it will overwrite the previous one.  You can also delete a DeviceConfiguration by simply calling new_device_configuration.destroy

Coverage decreased (-0.08%) to 99.923% when pulling bc0a69ef41626dbc35bd8705408f30382e44db59 on feature/device-configurations into 4aeb0933c219a5421bf6064a9b5586fd35b92c3a on master.

Coverage remained the same at 100.0% when pulling 4fdad71fadb3c0e912812469017f0b70c5cd801d on feature/device-configurations into 4aeb0933c219a5421bf6064a9b5586fd35b92c3a on master.

I'm +1 on this. some good refactoring opportunities for later


Implement Continous Replication

The underlying TDReplicator class seems to already support continuous replication. What needs to be done in order to enable continuous replication in CDTReplicator?

Sorry for the late reply.
Right now this is intentionally disallowed. CouchbaseLite also removed this feature a while back, iirc. It seemed a little too easy to use up cell data allowances and battery time with this.
What was your use-case, can it be solved using push notifications when databases change?

I am trying to synchronize changes in my app across the user's devices and several backend services which are listening for changes too. I think with some extra work, it can be achieved with push notifications and scheduled replication intervals just as well.

Continous replication would make this trivial and could inspire programmers to implement "live mode" in their apps. One could put two devices next to each other, make changes on the first and see them live, with only a few seconds delay, on the second one. In this case, continuous replication is more efficient than push notifications or polling.
Of course it would be the programmer's responsibility not to drain the batteries or cell data allowances and to warn the user appropriately.
And you are mistaken, CouchbaseLite still has continuous replication. I can find no evidence that this ever got removed nor any people actually complaining about battery or cell data allowances (or maybe I enter the wrong search terms into google).

Hmm, you're right -- not sure where I dragged up the continuous thing on CBL from. Sorry about that.
I'll take your thoughts into account on continuous - could be right that we should probably leave the decision up to the developer.
Will close this issue, but made a note :)


Updated zend-view to eventmanager v3

Uses dev-develop until we tag EM3.
Updates trigger and attach calls to follow v3.
Updates tests:

strategy tests primarily needed tooling for doing assertions on listeners and priorities after attaching aggregates (and updating aggregates to attach using the new signature).
Navigation and UrlIntegration tests were marked as incomplete as they depend on zend-mvc for testing.

Test coverage is expected, due to marking the navigation and URL integration tests as incomplete. However, this needs to be on the develop branch ASAP so we can continue with the zend-mvc updates. We can re-enable them once we have working code on the zend-mvc develop branch.


[rhobs-logs] Upgrade Loki to 2.7.2

Upgrade Loki from 2.6.1 to 2.7.2.
Depends on: observatorium/observatorium/pull/506
Ticket: LOG-3052

CC @periklis


styles in card_mod no longer working

styles no longer working in latest update
this is the card styles no longer works
show_name: true
show_icon: true
type: button
tap_action:
action: toggle
entity: light.lamp
icon: mdi:floor-lamp-torchiere
show_state: true
theme: LCARS Default
card_mod:
class: button-lozenge-right
style: |
ha-card {
{% if states['light.lamp'].state == 'on' %}
{% set rgb_color = state_attr('light.lamp', 'rgb_color') %}
background-color: rgba({{ rgb_color[0] }}, {{ rgb_color[1] }}, {{ rgb_color[2] }}, 1);
color: black;
{% else %}
background-color: #dd4444;
color: black;
{% endif %}
}
it worked perfectly in 2.3.1

Hey,
I can confirm this to be true. My lcars doesn't change the button background color according to state but now looks more standard with only the outline showing the desired color but always on. Only icon changes according to state as per default behavior.
This is kind of important to me as the use of card styles allows me to use lcars even on smaller distant screens to show state infos. :)

Same problem.

Simple fix, please use the !important directive wherever a style isn't being overridden. .
style: |
  ha-card {
    {% if is_state('light.torchier_one', 'on') %}
      background-color: aquamarine !important;
      color: black; /* or any other logic for text color */
    {% else %}
      background-color: default;
      color: black;
    {% endif %}
  }

Thanks.  Solution works perfectly!

Yep, that works, thanks! :)


NPM has incorrect information

It should say 'semrush-api' but it says 'semrush' which causes errors and cause you to download the wrong library if you only view it on npmjs.com and not github.

Thank you @apankDocero, I've updated the npm package.


[Debugger] Bad practice in gadp.proto

I've left a comment on the commit that added the gadp.proto file in the debugger branch here, but I thought it'd be also a good idea to open an issue and describe the problem.
The gadp.proto file you've created in the debugger branch is having enums that have bad keywords in them, such as UINT, VOID, or UNDEFINED. The code will be generated as-is in all languages, and particularly in C++ when compiling under Windows, a lot of these all-caps words will collide with Microsoft's headers.
For instance, winnt.h contains a #define VOID void which will make the resulting gadp.proto.h file not working fine when compiling under Windows with the Windows API included. This will greatly reduce the interoperability of ghidra with agents written in other languages.
The common way of creating enums here would be to prepend a small namespace, such as:
enum ExecutionState {
	ES_INACTIVE = 0;
	ES_ALIVE = 1;
	ES_STOPPED = 2;
	ES_RUNNING = 3;
	ES_TERMINATED = 4;
}

enum PrimitiveKind {
	PK_UNDEFINED = 0;
	PK_VOID = 1;
	PK_UINT = 2;
	PK_SINT = 3;
	PK_FLOAT = 4;
	PK_COMPLEX = 5;
}

On it. Thanks for the tip.

On it. Thanks for the tip.


Update ES to 5.6.8

@seut yep I somehow mixed up the patched branches and pushed the wrong one. Should be good now


CSV to load large fields?

A colleague reports that ArcGIS will successfully load tables with large (>256 char) fields from CSV files, unlike .xls files in which large fields are invisible to the ArcGIS foreign-table interface.
Is this correct?  If it is, the wiki page CMUandDMU should be rewritten to reflect this.

Save as csv works. Wiki has been updated.


Show the number of copies of a book

We need to show the number of copies of each book available in the library.
Requirements

Add a new column number_of_copies in the database table library_books
This count will appear on the book card of that specific book
The super-admin and book_manager can click on this number to update the count
When a new book is added, an input field will ask the user to enter the number of copies available in the library

@pankaj-ag I believe you meant show the number of copies of a book. Is that correct?

@pankaj-ag I've updated description. Please let me know if I missed something.

This issue is partially completed and the remaining work is being tracked in #629. Closing.


Fix InvalidCastException issue at action binding List Entity type

Fixed an InvalidCastException that caused the matching type of matchingEntity to be incorrect. more details
issue #89

 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.:x: SunKyungCho sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Thank you for opening an issue against the Bot Framework Cognitive Services repo. As part of the Bot Framework v4 release, we’ve moved all the Luis and QnA work to platform SDK repo. We will continue to support and offer maintenance updates via this repo.
From now on, https://github.com/Microsoft/botframework-sdk repo will be used as hub, with pointers to all the different SDK languages, tools and samples repos.
As part of this restructuring, we are closing all tickets in this repo.
For defects or feature requests, please create a new issue in the Bot Framework repo found here:
https://github.com/Microsoft/botframework-sdk/issues
For product behavior, how-to, or general understanding questions, please use Stackoverflow.
https://stackoverflow.com/search?q=bot+framework
Thank you.
The Bot Framework Team


Unable to communicate between hosts in windows overlay

Rancher versions:
rancher server 1.6.17
I am running windows server 2016 with docker 17.06.2-ee-12
I have two hosts registered in a windows environment, I followed the steps exactly form the documentation. the hosts connect as expected however the overlay only works on individual hosts, not between the hosts. below is a screenshot of what the environment hosts look like.

for example I cannot ping between the testing-1 container and testing-2 using the 192.168.x.x addresses or the dns names. communication between the hosts is open and windows firewall is off. both hosts have the agent and per-host-subnet service running. I have gone through the troubleshooting steps in the docs and everything looks correct.
here is what my ipconfig looks like:
host 1:

host2:

also here is the route table from inside of one of the containers. I see that it is routing requests form <IP_ADDRESS> to <IP_ADDRESS> which is the other host so this seems correct.

Is there something else I need to be configuring?

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


Simple wrappers to call the pds-batch-loader and pds-service-loader docker compose services

At the moment the pds-batch-loader and pds-service-loader docker compose services are executed with the environment variables defined in the docker compose .env file.
Create some simple wrappers (shell scripts) to execute these pds-batch-loader and pds-service-loader services with relevant arguments (E.g.: The harvest-job-config file is passed as an argument).

Created pull request: https://github.com/NASA-PDS/registry/pull/25


License

What's the license for this project?

Ah, I just saw that each individual file has an MIT-Header - maybe simply create a LICENSE-file, and set the appropriate license on NuGet, to make this more obvious in the future :)

@moritzuehling ah sorry, thanks for the info. I'll take care of this.


Support token based auth

We should support token based auth in addition to password based. See for example #99
https://developer.osf.io/#Introduction_authentication shows which header needs to change.

As far as I can understand the OSF.init() and OSF.login() methods do accept a token parameter for that purpose, but it is currently unused.
I access my OSF account using ORCID, I don't have a password. Is there any way to upload file to my OSF project?

As long as you can log in to OSF, you can generate a personal access token through this link: https://osf.io/settings/tokens/
That token can then be fed to the API instead of a password.

I do see that a token can be fed to the API, to OSF.__init__() and OSF.login(), but then token is not used as far as I can see. That would be the whole purpose of pull request #163. I'll give it a try though, but I doubt it works.

Tried this:
def main():
    osf = OSF()
    osf.login(USERNAME, token=TOKEN)
    osf.project('8ch5y')

if __name__ == '__main__':
    main()

The error message is:
Traceback (most recent call last):
  File "./osf2.py", line 15, in <module>
    main()
  File "./osf2.py", line 11, in main
    osf.project('8ch5y')
  File "/home/dimitri/.local/lib/python3.6/site-packages/osfclient/api.py", line 24, in project
    return Project(self._json(self._get(url), 200), self.session)
  File "/home/dimitri/.local/lib/python3.6/site-packages/osfclient/models/core.py", line 23, in _get
    return self.session.get(url, *args, **kwargs)
  File "/home/dimitri/.local/lib/python3.6/site-packages/osfclient/models/session.py", line 45, in get
    raise UnauthorizedException()
osfclient.exceptions.UnauthorizedException

Would the use of a token permit osfclient to work with accounts that have 2FA enabled also?

This should be fixed in the next release, which I am preparing now.
@devinberg, yes!  You create a token via regular login, which is protected by 2FA.  But using the token after that does not require 2FA.

This has been merged into master and released in osfclient==0.0.5. Thank you, all!


Cdn fix

first commit changes the unneeded directory "ununifi" and shorten the importing route.
second commit fix the problem of window.cosmosclient.codec for cdn

we can delete second commit after https://github.com/cosmos-client/cosmos-client-ts/pull/95/files released.
cdn.ts can be shortened as
if ((window as any).cosmosclient) {
  (window as any).cosmosclient.config.mergeCodecMaps(cosmosclient.config.codecMaps);
} else {
  (window as any).Long = Long;
  (window as any).cosmosclient = cosmosclient;
}```


fix a error

text_threshold = args.box_threshold should be  text_threshold = args.text_threshold

Thanks a lot for fixing this issue!


Attempting to use window.onDidChangeWindowState causes proposed api error

VSCode Version: Code - Insiders 1.18.0-insider (dcd1aa35dfa590b4a528e1ab55e957002f430f17, 2017-10-10T05:26:33.683Z)
OS Version: Windows_NT x64 10.0.16299

I'm trying to take advantage of the new window.onDidChangeWindowState, which as far as I can tell is no longer a proposed api, but every time I start debugging with it referenced in code I get the following error prompt

Proposed API is only available when running out of dev or with the following command line switch: --enable-proposed-api eamodio.gitlens.

According to the docs this should be available for use.
//cc @jrieken

Reproduces without extensions: No

It looks like this is the culprit https://github.com/Microsoft/vscode/blob/a627a95c4d78684e3285107c428b9cd2a151761d/src/vs/workbench/api/node/extHost.api.impl.ts#L349-L351

Oh no!!!

We used to have a big, bold warning on startup... But, yeah I agree we could check if some labeled as proposed isn't defined vscode.d.ts

I'll leave this assigned to October. If there is another recovery release, we'll make sure to put it in it. cc @egamma

@joaomoreno thanks! You just answered my next question :)

@eamodio There will be another recovery release, so this will go in!

verified via code review


Add lower bound for hspec-core

ResultStatus is exposed in hspec-core >= 2.5.0

Thanks for reporting. It should be fixed in hspec-golden <IP_ADDRESS>


Override LoadURL at Compiler

I'm implementing a feature that will allow schemas to be stored and updated; the details aren't very relevant, but the key point is that a schema URL may not have a globally-consistent referent (for instance, the current value vs one being updated). Thus, I'm finding the global LoadURL function to be limiting as a resolution strategy.
It seems like a simple solution would be to make the loader function local to the Compiler object (and initialized to the global). Does this change make sense? If so, I would be happy to send a PR.

makes sense. you can send PR.


Add docs

https://alexeykozhevin.github.io/segfast

@SergeyTsimfer asked to keep description of SEG-Y exactly at docstring. But I also think that it must be in a documentation in a separate chapter. I've fixed formatting
Done
Done
Done


Establish weekly meeting for Ceph-CSI issue/bug traige

With this, we would like to establish a process to triage ceph-csi issues ( https://github.com/ceph/ceph-csi/issues) weekly once . This helps on improving the code and also bring a forum for Ceph-CSI users to ask or highlight issues/bugs they encounter in their setup.
The initial version of this meeting can be in ceph-csi slack or via video conferencing.
https://cephcsi.slack.com/messages/CJV6G2DFT/
You can join the slack by https://join.slack.com/t/cephcsi/shared_invite/enQtNjc2NjEwMjUwODA2LWZjNzA1YjcwOGZjNjE1ODE5ZTZiOTE5OTEyY2NiM2QyZGE0MzVlZjcxNzA2MGM1MjBkNjI3MTI2NzBkZmJiODA
What we need ?
*) A volunteer for this effort
*) Meeting time
*) Sorting out the issues
*) Backlog clearing
...etc

@Madhu-1 @poornimag @ShyamsundarR ...etc

Proposed time:  weekly once on Tuesday from 7:00 PM IST to 8:00 PM IST
any comments or thoughts on this?

The proposal looks good to me. Thanks! lets kickstart it .

@nehaberry please add relavent person if am missing any  one

Proposed time: weekly once on Tuesday from 7:00 PM IST to 8:00 PM IST
any comments or thoughts on this?

This is fine, where are we meeting (i.e chat/call or other means and details)? Thanks.

@ShyamsundarR planning to meet on the slack channel. if we require audio/screen share etc will move to bluejeans (maybe in upcoming meetings)

The slack channel seems invite only and I do not have one, or a way to ask for one from the landing signup page, I see this message:
"Don't have an account on this workspace yet?Contact the workspace administrator for an invitation" but do not know what next.
What are the next steps?

@humblec can you help out with this.

@ShyamsundarR can you use this invite link https://join.slack.com/t/cephcsi/shared_invite/enQtNjc2NjEwMjUwODA2LWZjNzA1YjcwOGZjNjE1ODE5ZTZiOTE5OTEyY2NiM2QyZGE0MzVlZjcxNzA2MGM1MjBkNjI3MTI2NzBkZmJiODA ?

@humblec can you update the readme on how to join ceph-csi slack channel?

@ShyamsundarR can you use this invite link https://join.slack.com/t/cephcsi/shared_invite/enQtNjc2NjEwMjUwODA2LWZjNzA1YjcwOGZjNjE1ODE5ZTZiOTE5OTEyY2NiM2QyZGE0MzVlZjcxNzA2MGM1MjBkNjI3MTI2NzBkZmJiODA ?

Worked for me, now joined the channel.

Thanks @ShyamsundarR for confirming.

[update on 16-Jul-2019]
Open issues were at "83" and we were able to close "12" issues !!! Currently it stands @ 71.
4 issues were triaged or tracked for next and upcoming releases.

Do we still need this issue open?
@humblec  ?

Do we still need this issue open?
@humblec ?

hmm.. tricky to answer, we currently spent some time in a week to clear the backlog issues. However the slot is not consistent all the weeks. so give me some time, let me try to make it consistent and accordingly we can take the call.

@Madhu-1 @ShyamsundarR @nixpanic @Yuggupta27 @agarwal-mudit @pkalever @yati1998 I think we have to bring back this process. That said, we have a good count of issues opened here in this repo, most of them are actually solved. However the issue still remain open .
So 2 proposals:

Lets kickstart bug triage call or meeting once again ( May be weekly)
Look at the the stale bot configuration, looks like its not working as expected.

I would like to open it up for volunteers , if no, I can setup this call.

@kuja53 has offered help on looking into the stale bot issues and its configuration..etc. Thanks :+1:


Adding the tljh automation to terraform deployment

Earlier in the README we left it to the user to login to the vm and run some command to install tljh. To ensure this is more reproducible I've added this as automation.

@trallard ready for review

Merging now as this should be ready for team testing and any bugs or issues should be minimal


Update use cases for 'local' packages

Context: https://github.com/dbt-labs/dbt-core/issues/8541#issuecomment-1706982106
What are you changing in this pull request and why?
There are multiple legitimate use cases for 'local' packages, beyond the one that's currently documented — especially as we see more multi-project setups.

hey @jtcohen6 , thanks for opening this up and clarifying! I've left some suggestions for clarity and readability - if you're happy with them, i can go ahead and commit/merge

thanks so much for the quick response @jtcohen6 , I'll get these committed + merged for you ✨


Use appropriate treeview row styling for Gtk+ version, fixes #4855

The older Gtk+ treeview css make the treeviews background single
colored on newer Gtk+.  This patch discovers the Gtk+ version
through pkg-config as to introduce no new deps.
Ticket https://bugs.sugarlabs.org/ticket/4855
Replaces  #74

Tested on sugar-build, broot mode.
[osbuild sugar-build]$  pkg-config --modversion gtk+-3.0
3.10.9
[osbuild sugar-build]$ lsb_release -a
LSB Version:	:core-4.1-ia32:core-4.1-noarch
Distributor ID:	Fedora
Description:	Fedora release 20 (Heisenbug)
Release:	20
Codename:	Heisenbug
[osbuild sugar-build]$
Doesn't broke the current model.
Will test ASAP on Fedora rawhide with mode_none

Tested on:
[ignacio@ignacio-pc ~] $ pkg-config --modversion gtk+-3.0
3.18.1
[ignacio@ignacio-pc ~] $ lsb_release -a
LSB Version:	:core-4.1-ia32:core-4.1-noarch:cxx-4.1-ia32:cxx-4.1-noarch:desktop-4.1-ia32:desktop-4.1-noarch:languages-4.1-ia32:languages-4.1-noarch:printing-4.1-ia32:printing-4.1-noarch
Distributor ID:	Fedora
Description:	Fedora release 23 (Twenty Three)
Release:	23
Codename:	TwentyThree
[ignacio@ignacio-pc ~] $

Three test cases:
ListView, Treeview on Log activity, Journal activity.
patch not applied:

Patch applied:


Question: use case for async loading of a resource?

Out of curiosity, could you share a typical use case of the use of asynchronous resource loading?
(And maybe include such an example use case in the doc?)

The asynchronous case is when you know you have more than one resource to load that are not dependent on each other. In other words, loading any resource does not depend on any of the other resources being loaded first.
This could be multiple rows from a db, reading a camera, opening a file, whatever. The only thing that matters is that the load operations are not inter-dependent.
In that case, there is no reason to serialize the loads. You might as well spin up multiple short-lived processes to load all the resources at the same time and thus save some response time from your server.
Think of it this way, if you need to load two unrelated rows from a db, or different dbs... most of the time you are waiting for the load to complete is doing no work on the server. It is just waiting for a response from another machine. You will get better overall performance by getting those loads going simultaneously.

Thank you, I get it now. I thought that the assigns will be updated asynchronously haha. So I understand that it allows to load resources simultaneously/asynchronously, and once that all have been fetched, the assigns will be updated and program continues.


Implement two additional base functions: similar and copy!

Codecov Report

Merging #18 (a72ffd1) into main (41187b9) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #18   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           30        31    +1
=========================================
+ Hits            30        31    +1

Impacted Files
Coverage Δ

src/PSDMatrices.jl
100.00% <100.00%> (ø)

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 41187b9...a72ffd1. Read the comment docs.


Recently Closed tabs

I noticed that history on "recent closed tabs/windows" is not affected when using this addon. Would it be possible to clean that too?

Technically, they're a different type of history.
What you require was possible with a legacy extension, before Firefox Quantum.


Problem with building iOS samples

MacOS Catalina 10.15.5, XCode 11.5, .NET 5 Preview 7 (latest master):
dotnet build HelloiOS/HelloiOS.csproj
Microsoft (R) Build Engine version 16.7.0-preview-20270-03+bee129d1b for .NET
Copyright (C) Microsoft Corporation. All rights reserved.
Determining projects to restore...
Restored /Users/marcinkruszynski/Projects/net6-samples-master/HelloiOS/HelloiOS.csproj (in 2.73 min).
You are using a preview version of .NET. See: https://aka.ms/dotnet-core-preview
HelloiOS -> /Users/marcinkruszynski/Projects/net6-samples-master/HelloiOS/bin/Debug/net5.0/ios-x64/HelloiOS.dll
Detected signing identity:
Bundle Id: com.microsoft.net5.helloios
App Id: com.microsoft.net5.helloios

[warnings]
Optimizing assemblies for size, which may change the behavior of the app. Be sure to test after publishing. See: https://aka.ms/dotnet-illink
clang : error : linker command failed with exit code 1 (use -v to see invocation) [/Users/marcinkruszynski/Projects/net6-samples-master/HelloiOS/HelloiOS.csproj]
Build FAILED.
Any idea what is a problem?  Newer Xcode 11.5 or .NET 5 version?

I can reproduce this, I'll come up with a fix.

@MarcinKruszynski A fix should be in soon, but in the meantime you can either install a preview 6, or edit the top-level global.json like this: https://github.com/xamarin/net6-samples/pull/20/files.

@MarcinKruszynski A fix should be in soon, but in the meantime you can either install a preview 6, or edit the top-level global.json like this: https://github.com/xamarin/net6-samples/pull/20/files.

It works now. Thank you for the temporary solution.


Feedback and Feature suggestions

I posted in the forum before finding this repository so apologies for the double posting.
I’m currently trying out the new Alpha release and liking it so far - especially the GUI config. Makes things easier to quickly move entities around without having to edit the YAML
I did come across two changes I had to make to the template sensors within the weather.yaml file from DavidFW1960's repository (unsure if you are including these templates with the new version card). The alternate code for the bom_today_max and bom_today_min template sensors needed to have their comparison values changed from 'n/a' to 'unknown' as that was the value that the BoM integration was returning for missing forecasted temps - so my code block now reads -
     bom_today_max:
        value_template: >
          {%- if states('sensor.cardiff_temp_max_0') == 'unknown' -%}
            {{ state_attr('sensor.today_temp_bom', 'max_value') }}
          {% else %}
            {{ states('sensor.cardiff_temp_max_0') }}
          {% endif %}

I also came up with a couple of suggestions that I'm hoping could be considered:

It would be nice if the card could be made actionable like other Lovelace cards ? My idea was to have a ‘summary’ card showing some weather details but either going to a pop-up or navigating to another view with more detailed information when the card is tapped, double-tapped, or tapped and held.

Maybe not 'need to have' but 'nice to have' would be the ability to input templates into the entity fields. An immediate thought would be for the 'Forecast Possible' field where some weather integrations may provide separate min and max rain forecast entities and thus being able to join those together into a single string using a template

The alternate code for the bom_today_max and bom_today_min template sensors needed to have their comparison values changed from 'n/a' to 'unknown'

Did you log that as an issue for the card?

I don't believe this is an issue the card can solve. The sensor itself (ie. the input to the template) is set to unknown. This happens when the bom doesn't publish data for the field. This all happens before the template sensor gets passed to the card.

@ozmutley for the feature ideas, the first one may happen at some point, but not in the near future. The second one I am not even going to consider. You are far better creating a template sensor in ha and then just use it. I see no real benefit for the massive amount of work this would take (and likely to get broken often when the ha devs change things).

The alternate code for the bom_today_max and bom_today_min template sensors needed to have their comparison values changed from 'n/a' to 'unknown'

Did you log that as an issue for the card?

@DavidFW1960 - I thought I had created an issue under the card but going back and looking it appears that it did not get submitted to github. I have created an issue under the original card.

@ozmutley for the feature ideas, the first one may happen at some point, but not in the near future. The second one I am not even going to consider. You are far better creating a template sensor in ha and then just use it. I see no real benefit for the massive amount of work this would take (and likely to get broken often when the ha devs change things).

@Makin-Things - Thanks for the reply. After reading your comments about the 2nd item I'm happy for you throw out that idea.
The first item is something I think would be of benefit to the card sometime in the future so I will look forward to when it is able to be implemented.
Thanks for the time and effort both of you are putting into creating this awesome card - it is appreciated.


The link to the Arduino package is not working

The link to the Arduino package (http://atim-radiocommunications.github.io/armapi/pkg/arduino/armapi.zip) is invalid.
Could you please correct it?

This link is obsolete we solved this.


Option to not update a file except for release

In some cases (changelogs etc) users may not want to update a file with new versions when running a pre-release versup. In that case we'd only want to run the file update on release, patch, minor, major

Doing this per file doesn't make much sense. Instead a skip file update command line argument has been added to skip updating the version in all files


Fix wscript to support both Python 2 and Python 3

Fixes #23

I think waf still depends on python2 and that won't work where python3 is default...

It works on my machine if I put both the shebangs to python2 (python3 is the default).

I'm not sure if this will fix the issue entirely either but LGTM


Create processing pipeline for risk events on telemetry platform

Data product notebook

Indivual Trip Data Product
Aggregated Trip Data Product
....


The website field is not added to the vcard if it was of type other than MeCard

Root cause: Null was checked on phone field to add the website field to the vcard

This PR fixes/implements the following bugs/features:

[ ] #170

What existing problem does the pull request solve?
The website field was never added to the vcard if it was of type other than MeCard and if the phone field was null.

Test plan
Existing test cases should pass.
Closing issues

Fixes #
Changed the null checking to website field for adding the website data to the vcard.

Thanks for fixing this bug! :+1:


DLL_PROCESS_DETACH does not occur in native plugin

Not necessarily a bug report per se, but a behavioural issue I don't quite understand. I'm trying to write a simple plugin that performs actions upon game startup and shutdown (which do not require any REFramework API functionality).
What I've found is that DLL_PROCESS_DETACH never happens when the game shuts down. While I don't think (from a cursory glance) that REFramework calls FreeLibrary(), I was under the impression Windows would still trigger this event when unloading the calling process' address space.

Upon further investigation, using an independent proxy DLL (proxying version.dll), this behaviour seems to be a general issue (at least with RE4 Remake) and not related to REF.


Store raw data for incoming webhooks

https://app.asana.com/0/1200313386408105/1200309624168622
How to test?
Describe it!!!

@parhambarazesh I think you can define TTL on the schema level for mongoose: https://mongoosejs.com/docs/api.html#schematype_SchemaType-index


Could you please tell me how to fix the bug?

File "UAI1_full_resolution.py", line 278, in
out = model(batch)
File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
return forward_call(*input, **kwargs)
File "UAI1_full_resolution.py", line 36, in forward
x = F.relu(self.conv1(x, edge_index, edge_attr))
File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
return forward_call(*input, **kwargs)
File "/root/graph-pde-master/graph-neural-operator/nn_conv.py", line 271, in forward
return self.propagate(edge_index, x=x, pseudo=pseudo)
File "/root/miniconda3/lib/python3.8/site-packages/torch_geometric/nn/conv/message_passing.py", line 317, in propagate
out = self.message(**msg_kwargs)
File "/root/graph-pde-master/graph-neural-operator/nn_conv.py", line 274, in message
weight = self.nn(pseudo).view(-1, self.in_channels, self.out_channels)
File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
return forward_call(*input, **kwargs)
File "/root/graph-pde-master/graph-neural-operator/utilities.py", line 226, in forward
x = l(x)
File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
return forward_call(*input, **kwargs)
File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/activation.py", line 98, in forward
return F.relu(input, inplace=self.inplace)
File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/functional.py", line 1442, in relu
result = torch.relu(input)
RuntimeError: CUDA out of memory. Tried to allocate 1.44 GiB (GPU 0; 23.70 GiB total capacity; 20.41 GiB already allocated; 18.56 MiB free; 21.69 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF
We implement the code on Cloud Platform and the cost of GPU exceeds 24GiB, so could you tell us the capacity of your GPU?

Reduce the batch size you use per epoch. This should solve the issue

I also encountered the same problem, how did you solve it?thx

Reduce the batch size and try to clean up catch in the CUDA manually.


Seems to have a mistake in your paper https://arxiv.org/abs/2310.14558

In Page 5 Table 2, it seems that the right AVG '53.6' has switched its rightful position with the other value '67.6' at the last row.

hank you for pointing that out! We have revised the table and will upload the new version shortly.

Thanks for replying. I think your work has made a great contribution !


If a cluster is Spiderfied when cluster layer markers are removed from the map, the lines remain

When markers are removed from a cluster that is "spiderfied", the spider lines remain on the map. This is probably related to #53 and #54.
This can be tested and replicated by using the old test code in "remove-when-spiderfied.html". Just update the HTML and reference to latest build in the "dist" folder.
Please let me know if I missed anything.

Yes, I agree with you, the bug is still there.
On the same subject, there is another bug, but only for markers created using L.geoJSON.
To watch this bug, let's create 'doit4' :
L.DomUtil.get('doit4').onclick = function () { markers.removeLayer(markersList[0]); };
If you create the markers by using: m = new L.Marker([lat, lng]);
everything is fine when your click the button when spiderfy the cluster.
But if you create the markers using the following lines:
geoJsonFeature = { "type": "FeatureCollection", "features": [ { "type": "Feature", "geometry": { "type": "Point", "coordinates": [lng, lat] } } ] };
m = L.geoJson(geoJsonFeature, { pointToLayer: function (feature, latlng) { return L.Marker(latlng); } } );
then spider lines remain on the map.
Hope this will be useful for solving the issue.

olive380 thinks this is fixed by the rebuild hopefully.
Please reopen if not.

Bah, I haven't rebuilt this. TODO

Doing a new build today for #528

Thanks for fix! I know I am late to party but I didn't see anybody else confirm - this works for me when adding and removing L.geoJson layers while spiderfied, regardless of zoom level.


max burn credit per address

Codecov Report

Merging #307 (25d4eb6) into master (06b0407) will decrease coverage by 0.97%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master     #307      +/-   ##
==========================================
- Coverage   67.36%   66.39%   -0.98%
==========================================
  Files          55       55
  Lines       15863    16150     +287
==========================================
+ Hits        10686    10722      +36
- Misses       5177     5428     +251

Impacted Files
Coverage Δ

pallets/credit-accumulation/src/mock.rs
82.19% <ø> (ø)

pallets/credit/src/mock.rs
96.50% <ø> (ø)

pallets/credit/src/weights.rs
0.00% <0.00%> (ø)

pallets/micropayment/src/mock.rs
85.71% <ø> (ø)

pallets/staking/src/mock.rs
94.94% <ø> (ø)

pallets/tips/src/tests.rs
98.84% <ø> (ø)

runtime/src/lib.rs
10.91% <ø> (ø)

pallets/credit/src/benchmarking.rs
80.79% <33.33%> (-5.27%)
:arrow_down:

pallets/credit/src/lib.rs
52.24% <56.52%> (-13.12%)
:arrow_down:

pallets/credit/src/tests.rs
100.00% <100.00%> (ø)

... and 2 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Traffic control 2

For this second iteration, I made Ashton's recommended revision for Item 4: making refueling an action on the plane's resource.
I also made some additional routes in Items 9 - 14 that include a couple PUTS and one DELETE.
Thanks!

Looks good.  Closed.