Plyara version changes

Newer versions of plyara have different output and semantics - will need to adjust YaraGuardian accordingly.

Since plyara version 2, metadata field in parsed rules changed from a dict to a list of dicts. You can see 'complaints' about this in this issue: https://github.com/plyara/plyara/issues/52
It would be easier if you force or recommend to use some specific version. Last plyara version that returns a dict is 1.4.1.
This would be helpful too with the Django version, as some views name were refactored:
https://github.com/PUNCH-Cyber/YaraGuardian/blob/c09d8f054aa12357a61ea9caf41b5cf5b62fc727/YaraGuardian/urls.py#L45 and https://github.com/PUNCH-Cyber/YaraGuardian/blob/c09d8f054aa12357a61ea9caf41b5cf5b62fc727/YaraGuardian/urls.py#L49
django version 2.0 is the last version that uses the same view names as you.


Update Packet API to lastest version

Update Packet API to latest version
Porting needs a new SSH client option. Other vendored files were deleted by "make vendor".

Retry on provisioning timeouts

Improve bonding check and lower threshold
After https://github.com/coreos/bugs/issues/2065
a test for "excessive bonding link status messages"
was introduced which also is good to keep for
https://github.com/coreos/bugs/issues/2374.
However, having this message printed 10 times
does not directly relate to an error.
The test should check if something like
'bond0: Gained carrier' or
'link status definitely up for interface enp0s20f0'
is coming at the end and then continue.
Add a second match for these messages that skips
the test. Also lower the threshold to see if the
logic works well.

I need to make the loop cover the rest of the function so that if StartMachine gives an error we can try with an other machine.

Done


Request for a new dialog

Hi Aidan Follestad, can you make NumberPicker with material dialog style?
Thanks in advance.

You'll need to create one on your own using a custom view.


Tiff returns Input buffer contains unsupported image format

Possible bug
Loading the attached image returns the error Input buffer contains unsupported image format
Is this a possible bug in a feature of sharp, unrelated to installation?

[x] Running npm install sharp completes without error.
[x] Running node -e "require('sharp')" completes without error.

Are you using the latest version of sharp?

[x] I am using the latest version of sharp as reported by npm view sharp dist-tags.latest.

What is the output of running npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp?
System:
    OS: Linux 5.10 Amazon Linux 2
    CPU: (2) arm64 unknown
    Memory: 166.59 MB / 2.92 GB
    Container: Yes
    Shell: 4.2.46 - /bin/bash
  Binaries:
    Node: 14.18.3 - /var/lang/bin/node
    npm: 6.14.15 - /var/lang/bin/npm
  npmPackages:
    sharp: ^0.30.1 => 0.30.1

we use pre-built binaries, fwiw we can process thousands of images without any issue, we encounter that error in very rare occasion. It is reproducible on every case with the attached file.
What are the steps to reproduce?
load the attached image from the filesystem in memory as a Buffer and use with the code:
const image = sharp(imageBuffer, {
      density: 300,
      limitInputPixels: 636805378,
      failOnError: false,
    });

    image.withMetadata({ icc: `....AdobeRGB1998.icc` });

      image.rotate().jpeg({
        quality: 100,
      });
    }

    image.toBuffer((err, buffer, info) => {
      if (err) {
        console.log(err);
      } else {
        console.log({ buffer, info });
      }
    });

Please provide sample image(s) that help explain this problem
ICC profile https://rawpixel-marketing.s3.us-west-2.amazonaws.com/AdobeRGB1998.icc
Tiff https://rawpixel-marketing.s3.us-west-2.amazonaws.com/invalid-input-sharp.tif
sorry for the large image file size, this is the smallest one we have that trigger that error

Are you sure this is a TIFF image? It looks very much like a Photoshop PSD file to me.
$ file invalid-input-sharp.tif
invalid-input-sharp.tif: Adobe Photoshop Image, 5800 x 5200, RGB, 3x 16-bit channels

$ hexdump -C invalid-input-sharp.tif | head -1
00000000  38 42 50 53 00 01 00 00  00 00 00 00 00 03 00 00  |8BPS............|

of course!
and the message Input buffer contains unsupported image format now makes total sense.. I'll remember to check the file type first next time I see that, and we'll definitely add a file type detection to that workflow
thanks a lot 🙏🏻


Release version 2.0.0 at rubygems.org

Currently rubygems.org doesn't know about rest-client 2.0.0, which brings problems because gem maintainers usually don't want to change .gemspec file in a way when it references Github repo instead of version number.
Please release it to rubygems.org
Thanks.

@ab, do you control rubygems.org account of rest-client? Can you release the gem please?

@DanielVartanov and others, have you tested 2.0.0.rc4? gem install --pre rest-client
If there are no showstopper bugs, it sounds like we're ready for the final release this week.

I've updated the apipie-bindings gem to support 2.0.0 and rc4's been working fine in my testing.

https://rubygems.org/gems/rest-client/versions/2.0.0


Fix Windows warnings

The goal is to fix most of the warnings in order to have a build break to any new warnings. Most of the warnings were on Windows around some code security concerns.

I was not aware of the gitHub diff tool limitation. Next time, I will be careful.
Concerning pystring.cpp, here are the warnings I wanted to fix:

pystring.cpp
D:\OpenSource\ocio_rw_1\src\core\pystring\pystring.cpp(458): warning C4800: 'int': forcing value to bool 'true' or 'false' (performance warning)
D:\OpenSource\ocio_rw_1\src\core\pystring\pystring.cpp(468): warning C4800: 'int': forcing value to bool 'true' or 'false' (performance warning)
D:\OpenSource\ocio_rw_1\src\core\pystring\pystring.cpp(483): warning C4800: 'int': forcing value to bool 'true' or 'false' (performance warning)
D:\OpenSource\ocio_rw_1\src\core\pystring\pystring.cpp(500): warning C4800: 'int': forcing value to bool 'true' or 'false' (performance warning)
D:\OpenSource\ocio_rw_1\src\core\pystring\pystring.cpp(516): warning C4800: 'int': forcing value to bool 'true' or 'false' (performance warning)
D:\OpenSource\ocio_rw_1\src\core\pystring\pystring.cpp(532): warning C4800: 'int': forcing value to bool 'true' or 'false' (performance warning)
D:\OpenSource\ocio_rw_1\src\core\pystring\pystring.cpp(548): warning C4800: 'int': forcing value to bool 'true' or 'false' (performance warning)
D:\OpenSource\ocio_rw_1\src\core\pystring\pystring.cpp(565): warning C4800: 'int': forcing value to bool 'true' or 'false' (performance warning)
D:\OpenSource\ocio_rw_1\src\core\pystring\pystring.cpp(608): warning C4800: 'int': forcing value to bool 'true' or 'false' (performance warning)

@lgritz  The ::getenv method is using an internal static buffer so the proposed method was not adding extra limitations. But with the _dupenv_s usage on Windows platform, that internal buffer could be removed. Unfortuantely, it could not be done for *nix platforms.

I'm not familiar with the needs of the Platform specific memory fix, though I am familiar with the errors they raised, they look fine by my eyes. @lgritz how strongly do you feel about the formatting PR?

I feel strongly about segregating formatting changes to their own PRs... in the future. There's no reason to screw up an existing PR.

I'm fine with this as it stands. LGTM. I will merge.


add parse_mode to Telegram agent

With this path it will be possible to embed some html/markdown into messages

Cool!

Updated

Thanks!


Improve error handling, fix #416

Phew, got the tests passing.
Up for review, ping @cdrage @kadel

Good job man! Did a review and the code LGTM :+1:
Just need to rebase against master (I updated the vendoring in a different PR)

@cdrage fixed! :)

@cdrage fixed.

LGTM! :+1:


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test-source

Docs Build status updates of commit 96b2840:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-10-11-02-54-22 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-10-11-02-54-22

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


problems if one or more jars in classpath have "Main-Class" defined in MANIFEST.MF

Scala-Cli Version
# scala-cli version
Scala CLI version: 1.5.0
Scala version (default): 3.5.0

When attempting to test the new @arguments file feature, as suggested here, it fails if any entries in the classpath have a Main-Class property defined in the MANIFEST.MF.
To Reproduce
Create an args.txt to define a classpath having one or more executable jar files (any jar file with Main-Class defined in the MANIFEST.MF).
-cp postgresql-42.7.4.jar

scala-cli run -e 'println("Hey, I am using an @args file!")' @args.txt
Here's what happens with the above example @args file:
# scala-cli run -e 'println("Hey, I am using an @args file!")' @args.txt
Compiling project (Scala 3.5.0, JVM (21))
Compiled project (Scala 3.5.0, JVM (21))
Running org.postgresql.util.PGJDBCMain. Also detected script main classes: snippet_sc
You can run any one of them by passing option --main-class, i.e. --main-class snippet_sc
All available main classes can always be listed by passing option --list-main-classes

PostgreSQL JDBC Driver 42.7.4
Found in: jar:file:/C:/Users/philwalk/AppData/Local/https/repo1.maven.org/maven2/org/postgresql/postgresql/42.7.4/postgresql-42.7.4.jar!/org/postgresql/Driver.class

The PgJDBC driver is not an executable Java program.

You must install it according to the JDBC driver installation instructions for your application / container / appserver, then use it by specifying a JDBC URL of the form
    jdbc:postgresql://
or using an application specific method.

See the PgJDBC documentation: http://jdbc.postgresql.org/documentation/head/index.html

This command has had no effect.

Here are a few common libraries that are executable, no doubt there are many more:
rscala_2.13-3.2.19.jar
postgresql-42.7.4.jar
mdoc_3-2.3.6.jar
ldtp-4.0.jar
jna-5.14.0.jar
itext-2.1.5.jar
icu4j-59.1.jar
commons-compress-1.26.2.jar
byte-buddy-1.15.0.jar
xnio-nio-3.8.8.Final.jar
xnio-api-3.8.8.Final.jar
scala3-compiler_3-3.1.3.jar

Expected behaviour
A classpath defined in an @arguments file should be prepended to the classpath, but should not otherwise affect the behavior of scala-cli.

This is likely caused by https://github.com/VirtusLab/scala-cli/pull/3079
We are now looking for main classes in dependency JARs as well, which should perhaps be opt in behind a flag, unless no explicit inputs are passed.


Nuxt3 'persist' does not exist in type 'DefineStoreOptions'

Describe the bug
using pinia plugin persistedstate returns this error for me whenever I use persist inside the store and it breaks the whole TS support in pinia
Error:
Object literal may only specify known properties, and 'persist' does not exist in type 'DefineStoreOptions<"ui", { navTheme: ThemeType; }, {}, { setNavTheme(theme: ThemeType): void; }>'.ts(2353)
this is my store
import { defineStore } from 'pinia';
import { ThemeType } from '~/types/enum';

export const useUiStore = defineStore({
    id: 'ui',
    state: () => ({
        navTheme: ThemeType.LIGHT,
    }),
    persist: {
        paths: ['navTheme'],
    },
    actions: {
        setNavTheme(theme: ThemeType) {
            this.navTheme = theme;
        },
    },
});

my nuxt.config.ts
 modules: [
        ...
        '@pinia/nuxt',
        '@pinia-plugin-persistedstate/nuxt',
        ...
]

Reproduction
pinia-plugin-persistedstate
System Info
"@pinia/nuxt": "^0.5.1",
"nuxt": "3.12.2",
"@pinia-plugin-persistedstate/nuxt": "^1.2.0",
"typescript": "^5.3.3",

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible of the bug.

Have you found any solution for this ? 🙏

Have you found any solution for this ? 🙏

Yes, I have added to tsconfig.json
"include": [
        ".nuxt/**/*.ts"
    ],
    ```

Make sure to re-run the Nuxt typegen if you installed via nuxi

Make sure to re-run the Nuxt typegen if you installed via nuxi
Correct, this fixed the issue for me, here is the command:  nuxt generate


Fix cross-connect metrics mapping

A bug was reproduced after testing metrics with the 4g-network example:
cross-connect id did not always map event metrics properly. This change
provides a fix. It also updates the documentatation with more details
how to use metrics observability features
Signed-off-by: Ivana Yovcheva<EMAIL_ADDRESS>
Description

Motivation and Context

How Has This Been Tested?

[x] Covered by existing integration testing
[ ] Added integration testing to cover
[x] Tested locally
[ ] Have not tested

Types of changes

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

Checklist:

[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.

Failed tests are not related to the changes.

Could you rebase?

@edwarnicke Yep, just pushed after rebase.

@haiodo Do we have any idea why these VPN tests might be failing?  They should be unrelated to this PR.


Add optional catcher to Adapter

Proquest accepts an optional "catcher" function that is called when requests fail (i.e. return a 4xx or 5xx response). This PR updates Immunid's Adapter class to accept a catcher in the constructor and configure the Proquest request object with it.
This will be used to add global handling to 401 responses to handle session expiration in v3 interfaces.
Note: It seems that the last time Immunid was worked on, the engineer(s) had a number of testing dependencies installed globally. I've updated package.json with the missing dev dependencies that are needed to run the test suite.

@sorentwo: What's the release process for Immunid? I have access to the dscout NPM organization, but I'm guessing this package is published under an account of yours?


fix inconsistencies in instructions

small changes, see commit

@linsun made the changes discussed above and squashed commits.


[docs] update style guide to use correct shell indicator

Signed-off-by: echohack<EMAIL_ADDRESS>Directing a user to invoke a command via documentation is done by using a prompt indicator--$ is a standard convention. Using a prompt indicator avoids confusing situations where commands are followed by output, other commands, or commands run on a remote shell.
Using the prompt indicator offers an advantage as it allows you to specify the output of commands in the same code block. The proximity of the command and output prevents unnecessarily breaking the output apart from the command, while retaining clarity of the command that was executed.
Using a prompt indicator introduces a usability problem, where users cannot easily copy and paste the command from the documentation. This is an accepted drawback. One workaround is that static site generators may provide a copy button for code blocks, which will copy the code without the prompt indicator or any output following the command.
If this pull request is accepted, I will followup with another PR to fix all existing code examples to use the correct prompt indicator.

Are we sure this is an acceptable drawback? We used to have all codeblocks done this way and purposely changed it (knowing it would reduce readability slightly) in favor of better copy/paste usability. If we want to reverse that decision, we can, but this was explicitly changed to it's existing form after users expressing interest in improve copy/paste functionality.
This is not something I feel very strongly about either way, but it was a conscious decision, not just what we decided to do on a first pass.
There may be a different implementation of the copy/paste functionality that would marry the two, but we might have to develop it ourselves. Specifically, having the copy button, instead of copying whatever is in the codeblock, to specifically cope a defined command that is built into the docs. This is more annoying & time consuming for anyone writing documentation, but it probably the best user experience.

I'll go ahead and close this issue. I think learning more around the direction of the docs, tooling, and framework, will inform this topic in the near future.


FPE in zrotg with g++-13 -O3

I have a simple test program that worked on Ubuntu 22.04 and now fails after upgrading to 24.04. I filed an Ubuntu bug report and then realized that I can reproduce the issue without using Ubuntu's OpenBLAS package but rather building from source. For reference, here's the bug report:
https://bugs.launchpad.net/ubuntu/+source/openblas/+bug/2083157
This is the test program (g++ -o test_blas test_blas.cpp -lopenblas):
#include
#include
#include <fenv.h>
typedef std::complex dcomp;
extern "C" {
void zrotg_(dcomp*, dcomp*, double*, dcomp*);
}
int main(void) {
feenableexcept(FE_INVALID |
FE_DIVBYZERO |
FE_OVERFLOW |
FE_UNDERFLOW);
dcomp ain(0.28048120941867205058,0.028460086243503417841), bin(0.018279187257355982571,0);
double c(0.0);
dcomp s(0.0);

dcomp a=ain, b=bin;
zrotg_(&a, &b, &c, &s);
std::cout << a << " " << b << " " << c << " " << s << std::endl;

return 0;

}
Expected output (get this with -O0):
(0.28107,0.101469) (0.0182792,0) 0.997905 (0.0643715,0.0065317)
Output with -O1, -O2, -O3:
Floating point exception (core dumped)
Output with -O3 but FPE turned off:
(0.28107,inf) (0.0182792,0) 0.997905 (0.0643715,0.0065317)
Additional notes:

Also fails with the Intel compiler and OpenBLAS
Works with the Intel compiler and MKL BLAS

Here are some results for different OpenBLAS versions:

0.3.20 (version in Ubuntu 22.04, where my program used to work): works
0.3.23: works
0.3.24: fails
0.3.26 (version in Ubuntu 24.04): fails

It seems this may be related to the implementation of "safe scaling" that went in for 0.3.24, possibly from #4130.

What architecture/cpu do you see this with ?

My system is a dual Xeon e5-2630v4.

So a fairly common Haswell-generation x86_64... I cannot reproduce this with the current 0.3.28 and gcc 13.2 or 14.2 here

I can try with 0.3.28 but I won't have time to get to it until this evening. Did you try with 0.3.26?

This (a typo leading to uninitialized data being used as denominator) was fixed in the context of #4499 (released as 0.3.27)

Thanks - I confirmed that it works on my system with 0.3.27. I will mention it on the Ubuntu bug report.


Add .editorconfig

This avoids annoying wrong indentation when people use tabs in their editors (like they are supposed to :speak_no_evil:).

But only if they use an editor that supports .editorconfig, no ?

Most do or have plugins. Editorconfig is an attempt at a bare-minimum formatting standard that's very easy to support in any editor.

Why is this not merged? o_O
Let's merge this!
(Or write in README that we're in need for contributors (that would also get merge permissions))

Why is this not merged? o_O
Let's merge this!
(Or write in README that we're in need for contributors (that would also get merge permissions))

Mainly because there is rustfmt...

Mainly because there is rustfmt...

Or write in README that we're in need for contributors (that would also get merge permissions)

Definitely the issue here isn't that we need someone to click the Merge button for us. It's just not clear what value this adds over rustfmt which (is checked in CI).
I guess I'm not actually opposed to it, though.

Or write in README that we're in need for contributors (that would also get merge permissions)

Definitely the issue here isn't that we need someone to click the Merge button for us. It's just not clear what value this adds over rustfmt which (is checked in CI).
I guess I'm not actually opposed to it, though.

@gwenn @thomcc editorconfig and rustfmt answer different questions though.
rustfmt says how to format well structured Rust code.
Editorconfig tells your editor what should happen when you press Tab or Shift-Tab while editing:
fn test() {
    im_forgetting_semilicon_but_that_is_not_relevant()
    <--- cursor here

Also, editorconfig is supported by most text editors, even if they don't have rust plugins.

@gwenn @thomcc editorconfig and rustfmt answer different questions though.
rustfmt says how to format well structured Rust code.
Editorconfig tells your editor what should happen when you press Tab or Shift-Tab while editing:
fn test() {
    im_forgetting_semilicon_but_that_is_not_relevant()
    <--- cursor here

Also, editorconfig is supported by most text editors, even if they don't have rust plugins.

But you don't care of correct indentation because rustc don't and you must use rustfmt anyway !

But you don't care of correct indentation because rustc don't and you must use rustfmt anyway !

@gwenn humm, interesting... Rust repo currently seems to have editorconfig, but only for clippy: https://github.com/rust-lang/rust/blob/0d97f7a96877a96015d70ece41ad08bb7af12377/src/tools/clippy/.editorconfig
I've asked a question on it here: https://github.com/rust-lang/rust/pull/45002#issuecomment-765226033
Apparently Rust had an .editorconfig, but lost it in a PR that says "Validate miri against the HIR const evaluator #45002". Let's see if anybody will reply on that old thread..

@gwenn humm, interesting... Rust repo currently seems to have editorconfig, but only for clippy: https://github.com/rust-lang/rust/blob/0d97f7a96877a96015d70ece41ad08bb7af12377/src/tools/clippy/.editorconfig
I've asked a question on it here: https://github.com/rust-lang/rust/pull/45002#issuecomment-765226033
Apparently Rust had an .editorconfig, but lost it in a PR that says "Validate miri against the HIR const evaluator #45002". Let's see if anybody will reply on that old thread..


Recently not working with FastSwitchPlayerViewInRadar

Hi, your mod is amazing which gives a lot of advantages for a terminal guy. However recently, it does not work with FastSwitchPlayerViewInRadar (mod that uses arrow keys for switching to players) which is also a great addition for terminals. As a terminal guy, your mod is very useful, and with FastSwitchPlayerViewInRadar, your mod will be so much better. It will be a great help tho, if it's fixed.
Note: I do not really know how these codings of mods work. I approach this github, because there might be an easy fix?
Thanks a lot! and great work!

this is being tracked in #8 so i'm going to close this one.
Thanks for the bug report!


Distrib training for tabular data!

DistributedDL.create_item(): Only return idx here, let TabDataLoader.create_batch() do its job using iloc.
train_tabular.py: Test driver  for training url.ADULT_SAMPLES from cmdline, in single or multi-GPU mode.  Derived from train_imagenette.py.
torch_core.distrib_barrier(): Check against uninitialized distrib environment b4 entering synchronization barrier.

I'm a bit lost here, as to the nbdev_diff_nbs error?
I edited the notebook, ran nbdev_build_lib, ran test, then check in both the notebook and the .py files as usual.  The changes are simple one-liners.  Also added a new file under nbs/examples/.
What did I miss ?

Make sure you have latest version of nbdev (install from git)

Make sure you have latest version of nbdev (install from git)

Thank you.  Retrying now.

after updating/installing latest nbdev, still getting nbdev_diff_nbs @ CI, even though none in local repo. Will retry from scratch.


data issue

where the Data is  stored locally in the hive how to see the data

You can find the file that contains the entire database on your machine, depending on which platform you choose to run the project on.
For Windows, that will be "%USERPROFILE%/Documents" (or "$HOME/Documents/" on Linux). If you're running the app on Android, the database file will be hidden from the user as it uses the function getApplicationDocumentsDirectory from path_provider.

As this is not an issue, I'll be closing the thread. If you have any further questions, please email me at<EMAIL_ADDRESS>or create a Discussions thread. Have a nice day!


[11.x] Add sometimeDaily() to scheduler

Often times you have scheduled commands that you want to run every day, but you don't particularly care when during the day they run. For apps that have many scheduled tasks, this can unintentionally cause a huge spike in command execution every midnight—the default for daily().
This PR introduces a sometimeDaily() method that incrementally schedules tasks 5 minutes apart from each other throughout the day:
$schedule->command('model:prune')->sometimeDaily();       // scheduled at 00:05
$schedule->command('telescope:prune')->sometimeDaily();   // scheduled at 00:10
$schedule->command('cloudflare:reload')->sometimeDaily(); // scheduled at 00:15

If, somehow, you manage to fill out every 5-minute increment, it will reset back to midnight and start again.

I don't know if what I'm thinking makes sense, but for me, it would be more appropriate to call this sometimeMinutes, the term daily gives the impression that it will occur daily, just once, like the original proposal for daily

the term daily gives the impression that it will occur daily, just once

It will happen once daily. Each call is essentially a macro for ->dailyAt() that changes the hour and minute passed every call.

Personally i would still use closures with dailyAt method like this
Schedule::call(function () {
    Schedule::command('refresh-integration-token');
    Schedule::command('telescope:prune --hours=168');
    Schedule::command('cache:clear');
})->dailyAt('00:00');

Schedule::call(function () {
    DB::table('activity_log')->where('created_at', '<', now()->subYear())->delete();
    Storage::disk('local')->delete(Storage::disk('local')->allFiles());
})->dailyAt('02:00');

Schedule::call(function () {
    Schedule::command('send:birthday-messages');
    Schedule::command('send:order-alerts');
})->dailyAt('07:00');

I like it, my only suggestion would be maybe an optional parameter to customize how far apart they are scheduled in case you have longer running tasks or tasks you want to space out more for some other reason.

This is how I wished the normal daily worked. Definitely fits a need I have
The only project I wouldn't use it on is one that has a peak usage time. Makes me wish there was a dailyBetween() along the same lines

Makes me wish there was a dailyBetween() along the same lines

Ooh, I do like that! It'd be nice to schedule all these "cleanup" style tasks during slow hours only.
I might take a crack at tweaking this tomorrow!

I like the idea, I would have imagined something that would balance out the commands during the day evenly depending on the number of commands that want to be balanced. May I suggest  something like this?
Schedule::command('artisan:inspire')->duringTheDay();
Schedule::command('artisan:info')->duringTheDay();

Schedule::command('migrate')->duringTheHour();
Schedule::command('db:seed')->duringTheHour();
Schedule::command('db:prune')->duringTheHour();

Which would:

Schedule artisan:inspire every day at 00:00
schedule artisan:info every day at 12:00
Schedule migrate every hours at minute 00
Schedule db:seed every hour at minute 20
Schedule db:prune every hour at minute 40

WDYTAI?

I wonder if this would be a bit better like:
Schedule::call(fn)->daily()->nextVacancy();
Schedule::call(fn)->weekly()->nextVacancy();
Schedule::call(fn)->quarterly()->nextVacancy(after: 5); // 5 minutes after next quarterly scheduled task

@taylorotwell I shied away from something like that because it would involve tracking more data across the scheduler. If you're OK with a bigger refactor, I'm up for taking a stab at it. The way I see it, for something like that to work we'd either need to make the existing schedule available to future tasks, or track a bunch of data about the last/next scheduled task of each type.

I dunno - I'm close to thinking this is a neat idea but I can't decide if it's really going to be that trustworthy in practice. The 5 minute time feels a bit arbitrary and isn't configurable and doesn't help you at all if most of your commands take longer than that.


podman-save: log when more than one image is specified

Podman save can only save one image.  While we are planning to support
multiple images to catch up with Docker, we still need time to get the
work done.
Instead of ignoring other arguments, log when there are more than one.
Signed-off-by: Valentin Rothberg<EMAIL_ADDRESS>

Closing for now.


fix pagination bug

This should fix https://github.com/akgulebubekir/Maui.DataGrid/issues/159

This bug is fixed in my use case.
Thanks


[i18nIgnore] docs: fix a few links with inconsistent locale

Description
This PR updates starlight-links-validator to the version 0.11.0 which now validates links in <LinkCard> and <LinkButton> components.
Following this update, the PR also fixes a few links in such components that were using inconsistent locales.

Lunaria Status Overview
🌑 This pull request will not trigger status changes.

Learn more
Lunaria automatically ignores changes on specific PRs by adding a ignored keyword in its title. Found: i18nIgnore.
You can change this by either removing the keyword above from the PR's title, or modifying the ignoreKeywords property in your Lunaria configuration file.

Tracked Files

[!NOTE]
The notes below indicate what would happen if the pull request is merged when triggering status changes. Since a ignored keyword was found in the PR's title, the status changes indicated below won't be applied.

Locale
File
Note

ja
resources/plugins.mdx
Localization changed, will be marked as complete.

pt-pt
resources/plugins.mdx
Localization changed, will be marked as complete.

zh-cn
guides/components.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

I'll have to take a look to see how you did it.

This was a fairly small change as in MDX, this is pretty much the same as an <a> tag. The next step will be supporting custom user components but taking the time to figure out the best way to let users define their own components/props.


Don't let the entry scripts fail if there is no cert (dir)

Having a fail will fail the entire instance.
When the certs (dir) is missing, it gets recreated at puppetserver startup anyway.

LGTM. did you run some local tests with it? we dont have ci tests yet, that validate that the container is still start-able 😅

I have tested this with and without the ssl/ dir.
Both run well.
I am now still struggling with DNS ALT NAMES not getting applied to the NEW server certificates so i'm still looking/changin/testing.
I think adding that change to this branch/PR may make sense, if it turns out to work as hoped.

so i should wait until you add that. ok.


Background Color is still white

Is there something I need to do to make the background use the theme color? Currently using obsidian, but this is a problem in all the themes.

Did you switch the main theme to Obsidian in NPP setting? (Settings ▶ Style Configurator ▶ Select theme)

@Edditoria Markdown is not in the list of languages in the Style Configurator though. So all I can do is to choose Global Styles as the language and Global Override as the Style, and then I have to manually configure the color. Is that what you're suggesting?

@DerekZiemba @ichbinsteffen
The .xml files in this GitHub package are not complete style files but only user defined language files. That's way they work only properly if you use them with the same named style file.
The Bespin theme DerekZiemba is using comes with Notepad ++ and is automatically copied to your computer along with many other style files when the application gets installed. The style files are in the folderC: \ Users \ UserName \ AppData \ Roaming \ Notepad ++ \ themes \. You should therefore click the menu Settings -> Style Configurator and select the theme Bespin or another one according to the chosen language file (Select theme).

But if you only see the Default (stylers.xml) in the menu, then your Notepad ++ was probably launched in a user account that does not have admin rights.
In my experience, the problem is that by the installation the above folder themes is not automatically created in every user account on the computer. You should therefore log on to the computer as an admin, look for the themes folder in the admin account and copy the folder and its contents to the other user account (i.e. those without admin rights). You had best not to do this as an admin, otherwise you cannot easily change the newly created folder in the user account without admin rights later.
I don't know if this is a "clean" way to fix your problem, but at least it worked fine for me.

@ichbinsteffen Which Notepad++ theme are you using?
In normal situation, you don't need to change background and foreground colors in NPP. I don't recommend to force global colors and font-size. It's because some characters in some UDLs (Not only Markdown UDL) may not display properly.

@jf20191031

But if you only see the Default (stylers.xml) in the menu, then your Notepad ++ was probably launched in a user account that does not have admin rights.

That happens to be the case and therefore i only have the Default style. I tried to install Obsidian on my machine at work, where I do not have admin rights and Notepad++ is only available to install over SCCM and might even be modified by our admin. idk.
What I could do, by your description, is to take the style files from my machine at home and copy them over to the themes folder at work. I might try that at some point, I dont think our admin cares about my style preferences a tiny bit 😊

Nice to hear a possible solution. I would consider this issue solved. Thanks!


Update README.md

GitHub issue resolved: #
Briefly describe the changes proposed in this PR:

PR Author Checklist (see the contributor guidelines for more details):

[ ] my pull request is self-contained
[ ] I've added tests for the changes I made
[ ] I've applied code formatting (you can use mvn process-resources to format from the command line)
[ ] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change
[ ] every commit has been signed off

Note: we merge all feature pull requests using squash and merge. See RDF4J git merge strategy for more details.

So this is a direct web edit, which obviously works. I am unsure why a push on your branch would then not work. The only thing I can think of is that I have your upstream connected via https rather than ssh. I'll try and change that, see if it makes a difference.

There we go. Bit of a mission but that seems to have solved the problem.


How did you determine the number of intervals while using adaptive_trapezoid()?

@AhmedCode99 The adaptive_trapezoid function dynamically adjusts the number of intervals based on the convergence of the integral estimate towards a specified accuracy level. The number of intervals is initially low and doubling each time until the required accuracy is attained.


Just wanted to say thanks!

This library is absolutely wonderful.  Great work!

Thanks for the encouragement!  It's much appreciated.


Authentication without Cognito Users, federated only

Is this feature request related to a new or existing Amplify category?
No response
Is this related to another service?
No response
Describe the feature you'd like to request
It should be possible to configure authentication so that one or more social providers can be used without setting up options for native cognito users.
It does not always make sense for an application to want to manage its own user accounts
Describe the solution you'd like
A new option when adding auth
Do you want to use the default authentication and security configuration? (Use arrow keys)

Default configuration
Default configuration with Social Provider (Federation)
Social Provider without cognito default
Manual configuration
I want to learn more.

Describe alternatives you've considered
Option 1 Using Manual configuration option but this insists on setting up cognito users
Option 2
Configuring cognito users but only displaying custom dedicated social signin buttons and not using the authenticator UI at all.
Unfortunately that is not full proof as in some cases the UI falls back to rendering the authenticator view including cognito username and password
Additional context
No response
Is this something that you'd be interested in working on?

[ ] 👋 I may be able to implement this feature request

Would this feature include a breaking change?

[ ] ⚠ This feature might incur a breaking change

Hey @MigeBill, to better understand the feature, could you provide us your use case here?

@ykethan, sure.....
Amplify website is stage 1 in customer journey
Stage 2 is managed on an external providers site unrelated to AWS.
Stage 2 system allows social sign in or its own username and password
When a user completes stage 1 in our amplify solution with a social account, we can then automatically grant that social account access to stage 2.
When they choose to set up a cognito username and password at stage 1 we cannot do this.
Therefore we want to be able to configure the Auth component for federated sign on without the username and password option so that all users will get seamless access to stage 2 upon completion
Does that make sense?
Cheers

@ykethan - I'd like to add an additional use case: I'm building an application where the only option for sign-in is Google auth. That's it. No username/password, Apple, Github, or other OAuth2 solution. If you aren't a part of my employer's Google org, you can't get in. I don't need or want to create IAM roles, cognito users, etc.
Presently, I'm using an authenticator lambda function on all of my endpoints that need authentication (so ... all of them except the ones that actually reach out to Google to get the tokens in the first place). It's a very simple function that takes the google token, validates it, and then lets the REST API endpoint proceed to contact the main lambda function with which it's associated. Works great! Right up until I change anything about my API using the CLI, and then do amplify push, at which point all of my authenticators on every single route get blown away, and I have to go set them again. It even deletes the actual authenticator, so I have to set that back up and point it to the lambda function.
It's a pretty small API that's not going to change much once it's established, so it's not a huge deal, just a minor annoyance. Nonetheless, it'd be really excellent if we could create and configure lambda authenticators that stick around between API pushes.
Thanks!

hey @cwbuecheler, thank you for adding your use case. wanted to add some information on this, Amplify provides an override functionality for REST API which should enable you to add an authorizer to your API. unfortunately, I do not have an example for the Lambda authorizer but our documentation does provide an example for Cognito authorizer, refer to https://docs.amplify.aws/cli/restapi/override/#add-a-cognito-user-pool-authorizer-to-your-rest-api

Oh, fantastic, thanks - I'll absolutely see if I can adapt that to my needs. I wasn't aware overrides could be used in that manney.


Record locks taken for external deploys

Information about a lock attempt now includes a list of lock attempts done
while holding the lock, forming a tree (forest) structure.
Records the duration and locking attempts done as part of an external
deploy, forming a tree of locks with timing info.  The currently active
external deploys are shown in an "ongoing-recording" field of
/nodes/v2/locks.
The 3 longest external deploys are kept in "recordings" in /nodes/v2/locks.
Extracts the global process-wide parts of ThreadLockStats into separate
class for clarity.

Also showing nested locks may drastically increase the size of the response, e.g. internal redeployment takes one maintainer lock and would include deployment locks for many apps.  I'll check if this is a problem or not.

Looks good


Multiple AC Inputs - How to Modify to Show all

Thank you for putting this together.  I have a Victron VM-3P75CT energy meter with 2 AC inputs on my boat.  Please note that I have the device currently configured as a 3 phase device while I am actually monitoring 2 single phase input lines.  Victron is planning a future firmware update to handle multiple single phase lines, but it not yet released.  This emulator allows me to properly show an AC input on VRM and on the html5 app on my MFD, which is something that I have been struggling to figure out.  I have a couple of issues that I am hoping you can help me understand.
On VRM the grid input power is properly reflected.  I can see both of my inputs and the total power is correctly the summation of the two inputs.
On VRM the for AC loads I can only see the consumption from one of my lines (L2) while L1 shows 0.  I know from looking at my energy meter that L1 consumption is not 0 and is the same as the grid value.  Can you help point me how I can correct this?
On my MFD app the shore power appears to be showing the current for L1 and not L2.  But when I looked closer I realized that it is always showing 13.9 amps.  And for AC loads is the same - always showing 13.9 amps.  I'm not seeing any obvious reasons for that in the code or via dbus-spy.  If you had any ideas for why that would be or troubleshooting tips I would appreciate it.  Ultimately I want the MFD app shore power and AC loads to be the summation of the L1 and L2 inputs.
I made a small donation as I really appreciate you creating this - I woud be happy to contribute further if I can get it working properly :-)

You solved it?

Thanks for the quick reply.  I included a very simple wiring diagram.  I know that the energy meter is installed and functioning correctly as I can see the L1 and L2 values in remote console (included screenshot of that).
I discovered that the MFD app is not froze - I needed to reboot the Cerbo and when I did that it is now properly displaying L1.  I still do not see any readings for L2.
I included a couple of Dbus-spy screenshots that show the energy meter and the multibus emulator.  I can see L1 and L2 in in the energy meter Dbus.  But I only see L1 as having values in the multibus emulator.
I looked at the multibus emulator code and I see a couple of lines that talk about "NumberofACInputs".  I tried changing these to "2" and also changing "ACInput2" from "0" to "1", but this did not work.  Am I on the right track?  Or are there other changes that I should be trying?

Simple Energy Meter Schematic.pdf

A MultiPlus has only one input. If you have AC-In 2 then you have a Quattro device. In a real constellation you would need one MultiPlus/Quattro per phase linked together via VE.Config. unfortunately I don't know yet how this looks like in dbus-spy. I have to look if I find something.

Ok that makes perfect sense and I should have remembered that the Multiplus has a single input.  One other thought - what if I set the emulator up as 3 phase?  If I changed line 839 "Number of Phases" from "1" to "3" then I wonder if the emulator would pull in L2 (L3 would be 0).  I had to leave my boat for the night or I could have quickly tried that.

Have you internet access at your boat? If yes, you can use tailscale to access via SSH. venus-os_TailscaleGX

I don't have tailscale yet but am going to download it and get it set up.  That's a really good option.
I went to my boat tonight and the change to 3 phase didn't work.
I did discover that when I changed the inverter phase from "L1" to "L2" that the my MFD app then displayed the readings for my second power input (L2).  So that did make a difference that surprised me.
I tried a couple of other things but didn't have any luck.  If you have any other tip I can always give them a try . It should be easier for me once I install and figure out how to use tailscale.

You basically need to have a MultiPlus per phase, therefore in this case a MultiPlus emulator for L1 and one for L2. The most clear it would probably be, if you name one dbus-multiplus-emulator -L1 and the other dbus-multiplus-emulator -L2. Then you have to correct all paths, to make it work.

Thanks for the tailscale tip.  That is very helpful!  It took me a few minutes to get it working but once I did it worked great.
Adding the 2nd multiplus instance tested my Linux skills but I finally got it.  And it works!  For the most part.  The power readings between input and output looks to be slightly off so I will need to investigate that further.  And I'm not at my boat so I can only go by what I am seeing on VRM and the gui but I do believe it is working better.

All solved now? :-)

I thought I had made good progress earlier today but then I ran into similar problems to what I was having for the past couple of days.
One thing I did find is that I must not have successfully added the second multiplied emulator.  I discovered those by noting that the VRM device list only contains the original multiplied emulator and not the new one that I created.  I did have some trouble installing the new one today so I think tomorrow I will start over and uninstall that and reinstall it.  I took the commands that you had provided and added an "L2" to the directory name:
For example I changed the copy file command to:
cp -R /tmp/venus-os_dbus-multiplus-emulator-master/dbus-multiplus-emulatorL2/ /data/etc/
When I did this I had some trouble but did get the files copied.  I then followed the same logic for install.  Is that the correct way to do it?

Today I got the data from a three phase system with a MultiPlus on each phase. I worked the whole day to fix all and make the emulator one, two and three phase compatible. Install the last version and see, if it works. Only once instance is needed.

Thanks for all of the work you put in on this!  I updated the version to the latest this morning and have been doing some troubleshooting.  The grid values are correct.  I am still having trouble with the AC loads.  Here is what I have found:
I updated the user values as shown in the photo.  Changed grid frequency, uncommented voltage for American grid, added DC and AC Dbus services and uncommented phases to be L1 and L2. In the photo timestamped 11:33 you can see that the AC input is correct.  The AC loads not - they jump around slightly but are always near 0.
When I change the phase combination to L1 then I get correct AC load values for L2 but not L1 ( always near 0).  The AC grid input values are correct for both L1 and L2.  This is in the photo timestamped 11:49.
When I change the phase combination to L2 then I get correct AC load values for L1 but not L2 ( always near 0).  The AC grid input values are correct for both L1 and L2. This is in the photo timestamped 11:56.
When I comment out all of the phase combination then the AC grid input values go away (of course).  In this case I get correct AC load values for both L1 and L2.  This is in the photo timestamped 12:12.
So I do feel like we are getting closer.  I haven't had a chance to look at the code further yet but there seems to be some type of interaction when selecting multiple phases that are interfering with the AC load values.

Can you make a wiring diagram of your whole setup with where which device/sensor is located with the different voltages? 120 VAC / 12 VDC
What is converting the power from DC to AC?
Are you using a SmartShunt to fetch the power that comes from the battery and MPPT?

Apologies for the crude schematic.  I started with the crude schematic that I sent a couple of days ago and expanded from that.  I do have 2 smartshunts - one for my 2 starboard batteries and one for my 2 port batteries. I do have a small 800 VA inverter but it o my feeds some branch circuits on the L2 input.
So with my particular setup the DC side wouldn't play very much into the overall setup.  What I'm looking at more than anything is getting the grid values properly represented (which they now are).  But in the process of getting those properly represented I have lost the AC loads.  Hope that makes sense?

I see that with the new version the multi is in bulk whereas yesterday it was in pass thru.  If it was in pass thru then the battery connection wouldn't matter right?  I tried to turn it to "OFF" mode but that doesn't work.  Is that something that would help?

Ok so I had a discovery.  I went to the boat to pick something up and took a look at my MFD.  And the app readouts are showing that this working as expected.  So it's working fine on the MFD app.  And I also see that it is working on remote console.  See enclosed for photos of both of those.  Yet on VRM and gui (beta) it is not.  So strange.

The state of the emulated multiplus can be ignored, since you have none the state could be whatever. Also other report some issues regarding the load, but currently I have very limited time to look into it.

This should be solved with the next version. In the current version there are some thinking issues.


⚠ Thumbnails API Endpoint has degraded performance

In 9822f14, Thumbnails API Endpoint (https://thumbnails.roblox.com/v1/assets?assetIds=82738847&format=Png&isCircular=false&size=30x30) experienced degraded performance:

HTTP code: 200
Response time: 1175 ms

Resolved: Thumbnails API Endpoint performance has improved in fe9254c after 15 days, 20 hours, 2 minutes.


Support offset in write

Replaces: #11
Support the offset parameter on calls to write().
Thanks @DrNecromant for the initial implementation.

Cool. thx. =)


DBZ-8128 Don't stop engine twice

https://issues.redhat.com/browse/DBZ-8128

@vjuranek Applied, thanks


Guig is not a valid selector for chart.

I'am trying use c3 chart in angular4 app, for several charts on page, i need specify unique id for each.
But when i set guid like a string to bindto, i see error in browser console:
'0058bc4d-754b-43d7-8e91-860d47012f4d' - is not a valid selector.
if i concat guid with char like 'z0058bc4d-754b-43d7-8e91-860d47012f4d', all work perfect.
This is bug or feature?
C3 version:
"c3": "0.4.14",

https://github.com/d3/d3/issues/1858

Thanks, i'm not strong in css :) issue closed


Support audio transcription on drag and drop

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


Add and move symbols

I'd like the the option for visitors to add symbols and move them and store the symbols and order in local storage. Is somebody working on that already?

This crossed my mind a few days ago, but to my knowledge nobody is working on it. I don't plan to add it myself, but I would happily review a PR if it's something you're interested in doing!
The way I'm envisioning this working (after only an hour or so of thinking about it, so feel free to suggest other ideas), is an unobtrusive + button next to the search box that pops up a form/modal for adding your own symbols. Custom symbols would then appear first in the list, and be visually distinct from the "default" ones. They would save into local storage and be available on the device you've saved them on. No plans for any auth or cross-device syncing.


terminology fix from PR-4044

Implementing a terminology tweak from this PR: https://github.com/harness/developer-hub/pull/4044

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66141d9aea10a100a50b1678--harness-developer.netlify.app


[stable/jenkins] RBAC deployment with Kubernetes plugin does not use the created service account

**Is this a BUG REPORT
Version of Helm and Kubernetes:
helm 2.5.0;  k8s: 1.7
Which chart:
[stable/jenkins]
What happened:
RBAC deployment with Kubernetes plugin does not use the helm chart created service account (SA).
What you expected to happen:
be able to use the service account the helm chart created.
I did not find the way to specify to  Kubernetes plugin which SA to use. Apparently by default it uses the "default" SA in the specific namespace.
While this helm chart creates and gives perms to a different SA
More than this, I could not find a way to point the kubernetes-plugin to a specific k8s service-account.
It seems that it's always looking to the default service account for that namespace:
Error connecting to [edited]: Failure executing: GET at: [edited]/api/v1/namespaces/jenkins/pods. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. User "system:serviceaccount:jenkins:default" cannot list pods in the namespace "jenkins"..

while the helm chart creates a service account like: jenkins-jenkins
@carlosedp @lachie83 I see you checked #1092 maybe you can suggest any hints?

As the service-account is created during helm install, it was expected that it will also configure the installation to use it. Maybe in future versions.

There was such issue with an older version of k8s plugin. I am not aware of
this in the last period.
Alternatively, you create a namespace for jenkins (if you don't do it
already),  you can give the required perms to the default service account.
This works and there is no need to specify it anywhere.
On Thu, Mar 1, 2018 at 8:59 AM, fejta-bot<EMAIL_ADDRESS>wrote:

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta
https://github.com/fejta.
/lifecycle rotten
/remove-lifecycle stale
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/charts/issues/1643#issuecomment-369495257,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG43M2hnzrmCEpcdwlhqr_q4NZ54LWC2ks5tZ5xogaJpZM4OwhUz
.


Colour cells of pivot table If value greater than 0

Ian trying to develop a pivot table to show who has completed certain training
I want to color the cells green that have a value
What’s the best and simplistic way to do this
Thank you

This example https://pivottable.js.org/examples/montreal_2014.html has a custom color scale, which is what I would use in this case.

Thanks for the feedback, one other thing I am developing a pivot table based on the Pivot Demo From Local CSV sample
is there a way to have the heatmap as the default when the pivot table loads
thank you


HSM edits

Changing user's guide to reflect what's in this CR: https://gerrit.hyperledger.org/r/c/fabric/+/32298/

@mastersingh24 Yes this was part test and part actual commit. Talked to Bret and I need to abandon this commit and start over. Wasn't aware I couldn't add a commit message after the fact.


[question] dropBufferSupport & JSON.parse

JSON.parse is highly optimized in V8 and works on a buffer. Lets assume we have hiredis parser, were there any measurements on hiredis -> buffer -> js code -> JSON.parse vs hiredis -> utf-8 -> js code -> JSON.parse performance?
Lets look at the following snippet:
const data = new Buffer('{"very":"good","json":true}', 'utf-8');

const sampleOne = JSON.parse(data);
const sampleTwo = JSON.parse(data.toString());

Doing sampleOne is always faster because we avoid parsing buffer into utf-8 and pass it directly to JSON.parse. Wouldn't it be the same for hiredis?

Anyone ever tested this thoroughly?

@trevnorris could you give some input here? I remember your optimization talk during one of the the first nodeconfeu

Have any benchmarks been done with this? There is no API that allows passing a char* (though I wish there was). The call to JSON.parse() would automatically call .toString() on the Buffer. Example of what's happening:
 var b = { toString: () => '{"foo":"bar"}' };
JSON.parse(b);
// output: { foo: 'bar' }

So I'm honestly unsure how one could be faster than the other.

I must be confusing this with 1-byte strings and trick to decode it to binary representation before json.parse and then creating a buffer before we put to to db. Likely doesnt apply here because of inapplicable assumptions
Thanks!

On 31 May 2016, at 20:00, Trevor Norris<EMAIL_ADDRESS>wrote:
Have any benchmarks been done with this? There is no API that allows passing a char* (though I wish there was). The call to JSON.parse() would automatically call .toString() on the Buffer. Example of what's happening:
var b = { toString: () => '{"foo":"bar"}' };
JSON.parse(b);
// output: { foo: 'bar' }
So I'm honestly unsure how one could be faster than the other.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@AVVS

I must be confusing this with 1-byte strings and trick to decode it to binary representation before json.parse and then creating a buffer before we put to to db.

Never thought about using it that way. If you could tell your source for the data to encode in one-byte (i.e. latin1 or iso-8859-1, not win-1252) then converting to JS string from Buffer would be faster.


Working with django and react application with webpack-dev-server (Hot-reloading). I am getting this error in console. But my page is loading fine

Do you want to request a feature or report a bug?

What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.
https://stackoverflow.com/questions/59441494/working-with-django-and-react-application-with-webpack-dev-server-hot-reloading
Issue in the above link .

Please fill issue template, be patient wait answer


Pointers in shared memory work only in some environments

Note: the issue was created automatically with bugzilla2github tool
Bugzilla Bug ID: 76
Date: 2016-02-08 11:08:37 +0100
From: Sorin Vultureanu<EMAIL_ADDRESS>To:   Sorin Vultureanu<EMAIL_ADDRESS>Last updated: 2016-03-04 10:45:55 +0100
Bugzilla Comment ID: 150
Date: 2016-02-08 11:08:37 +0100
From: Sorin Vultureanu<EMAIL_ADDRESS>free_* pointers and pointers in ofp_rtl_node structure should be avoided.
A SHM will have different pointer values on each context.
Now it seems this works because threads have access to the same addresses.
Bugzilla Comment ID: 156
Date: 2016-03-04 10:45:55 +0100
From: Sorin Vultureanu<EMAIL_ADDRESS>The shm pointers should be equall on all threads/processes.
On linux environment this happens, but this might be true for all environments.
In this case the redesign work to replace pointers with some indexes in shm would be masive.

This is fixed by cc24ec6c208396ee43396ee456cda4cc9a162685 which uses the new ODP_SHM_SINGLE_VA flag to request SHM blocks to have the same address mapping in all threads. The fix requires new enough ODP (>= <IP_ADDRESS>) that has the flag and makes OFP depend on the availability of such a mapping.


Prevent division by zero

Problem: rnd.getrandbits can result in 0, so that b could equal to 0.
This fix makes it that b is a pseudorandom number close, but not equal,
to zero.

Thanks!


added script for running phylophlan

@ekopylova I added PhyloPhlAn support.

Coverage increased (+0.1%) to 94.461% when pulling 339aef32e878ac3cdb6e9bba67a32c6410ed7bb6 on qiyunzhu:bash into 4cb571fba31ab139d628a140f59b64bebeeb0d9c on biocore:master.

Coverage increased (+0.1%) to 94.461% when pulling 72f41da36e84e42019025eb3e44e97df63b11a23 on qiyunzhu:bash into 4cb571fba31ab139d628a140f59b64bebeeb0d9c on biocore:master.

Also modified the T-REX script.

Coverage remained the same at 94.311% when pulling 50c0379ccf94b3c49e8db6d2f9fa42af43e94924 on qiyunzhu:bash into 4cb571fba31ab139d628a140f59b64bebeeb0d9c on biocore:master.

@sjanssen2 @mortonjt @tkosciol Thanks for your kind offer! Here is the latest PR. It is a Bash script that calls a third-party program (PhyloPhlAn).

@tkosciol Thank you! These are valuable comments!

Also we discussed about two alternative ways of using $verbose. Solution A (4 lines):
if [ "$verbose" == "true" ]
then
    echo "Command:"$'\n'"  $cmd"
fi

Solution 2 (1 line):
$verbose && echo "Command:"$'\n'"  $cmd"
The latter will require that I modify the get_args function in utils.sh to force $verbose to be true or false.
Which one do you like? @ekopylova

Coverage remained the same at 94.311% when pulling b4cc34008f2e9e82122b98d7b2d25c466bd0f678 on qiyunzhu:bash into 4cb571fba31ab139d628a140f59b64bebeeb0d9c on biocore:master.

Coverage remained the same at 94.311% when pulling cf0591c25304bc041e9297ff1c4e497d53de1b39 on qiyunzhu:bash into 4cb571fba31ab139d628a140f59b64bebeeb0d9c on biocore:master.

Would anyone like to give some final comments and/or merge? @mortonjt @tkosciol @ekopylova

@qiyunzhu  thanks!

@ekopylova Thank you for merging!


Problems with STM32L432KCU

I am still having some issues with the STM32L432KCU. Also see: #42
Not having the embassy main end with loop {}, will case the following issue:
(HOST) INFO  flashing program (15.99 KiB)
(HOST) INFO  success!
(HOST) ERROR Max number of RTT attach retries exceeded.
Error: RTT control block not found in target memory.
- Make sure RTT is initialized on the target.
- Depending on the target, sleep modes can interfere with RTT.

Adding the loop will (obviously) however not run the rest of the program.

Ok, the RTT issue I could fix by applying the following workaround: https://github.com/probe-rs/probe-rs/issues/350#issuecomment-740550519
I had to tweak the call a bit:
let pp = pac::Peripherals::take().unwrap();
pp.RCC.ahb1enr.modify(|_, w| w.dma1en().set_bit());

Ok, the last issue was me … not starting the ticker :shrug:


Uncaught TypeError: Cannot read property 'element' of undefined

Using Hydrogen with Python within a Markdown file
Have Markdown preview open. Getting this error repeatedly. Every time I close the error a new one pops up. Have 6 instances of the error on my screen at one time.
The same issue comes up when the Hydrogen output area is toggled and the Markdown preview is closed.
It seems to be related to the Output area sizing. If I start with the Hydrogen output area closed>then run a line, the output will open. If I let it sit I will not see the error. If I try to resize the pane the error shows up almost immediately (that may be a coincidence).

Atom: 1.22.1 x64
Electron: 1.6.15
OS: Microsoft Windows 7 Professional
Thrown From: Atom Core
Stack Trace
Uncaught TypeError: Cannot read property 'element' of undefined
At C:\Users\pney\AppData\Local\atom\app-1.22.1\resources\app\src\text-editor-component.js:2225

TypeError: Cannot read property 'element' of undefined
    at TextEditorComponent.measureLongestLineWidth (~/AppData/Local/atom/app-1.22.1/resources/app/src/text-editor-component.js:2225:63)
    at TextEditorComponent.measureContentDuringUpdateSync (~/AppData/Local/atom/app-1.22.1/resources/app/src/text-editor-component.js:399:16)
    at scheduler.readDocument (~/AppData/Local/atom/app-1.22.1/resources/app/src/text-editor-component.js:278:20)
    at ViewRegistry.module.exports.ViewRegistry.performDocumentUpdate (~/AppData/Local/atom/app-1.22.1/resources/app/src/view-registry.js:191:15)
    at ~/AppData/Local/atom/app-1.22.1/resources/app/src/view-registry.js:3:65

Commands
  2x -6:04.1.0 core:move-down (input.hidden-input)
     -6:03.2.0 intentions:highlight (input.hidden-input)
     -6:02.8.0 editor:delete-line (input.hidden-input)
     -6:00.6.0 editor:newline (input.hidden-input)
     -6:00.3.0 core:move-up (input.hidden-input)
  5x -5:55.8.0 core:backspace (input.hidden-input)
  7x -5:53.2.0 core:move-down (input.hidden-input)
  6x -5:46.1.0 core:move-up (input.hidden-input)
  5x -5:44.1.0 hydrogen:run-and-move-down (input.hidden-input)
     -4:13.1.0 intentions:highlight (input.hidden-input)
     -4:12.6.0 command-palette:toggle (input.hidden-input)
  3x -4:10.7.0 core:backspace (input.hidden-input)
  4x -4:06.6.0 core:move-down (input.hidden-input)
     -4:05.6.0 core:move-up (input.hidden-input)
     -4:05.3.0 core:confirm (input.hidden-input)
     -4:05.3.0 hydrogen:toggle-output-area (input.hidden-input)

Non-Core Packages
autocomplete-python 1.10.5
busy-signal 1.4.3
file-icons 2.1.14
highlight-selected 0.13.1
Hydrogen 2.1.1
intentions 1.1.5
language-vue 0.23.1
linter 2.2.0
linter-flake8 2.2.1
linter-ui-default 1.6.10
minimap 4.29.7
minimap-highlight-selected 4.6.1
python-autopep8 0.1.3
script 3.17.3

Same error here, after doing a 'shift-tab' (= un-indenting a line of code)
[Enter steps to reproduce:]

...
...

Atom: 1.25.0-beta2 x64
Electron: 1.7.11
OS: "Fedora release
Thrown From: Atom Core
Stack Trace
Uncaught TypeError: Cannot read property 'element' of undefined
At /usr/share/atom-beta/resources/app/src/text-editor-component.js:2236

TypeError: Cannot read property 'element' of undefined
    at TextEditorComponent.measureLongestLineWidth (/usr/share/atom-beta/resources/app/src/text-editor-component.js:2236:63)
    at TextEditorComponent.measureContentDuringUpdateSync (/usr/share/atom-beta/resources/app/src/text-editor-component.js:400:16)
    at scheduler.readDocument (/usr/share/atom-beta/resources/app/src/text-editor-component.js:279:20)
    at ViewRegistry.performDocumentUpdate (/usr/share/atom-beta/resources/app/src/view-registry.js:245:13)

Commands
     -1:20.1.0 core:delete (input.hidden-input)
     -1:18.8.0 core:backspace (input.hidden-input)
     -1:16.2.0 core:save (input.hidden-input)
  3x -1:13 core:move-right (input.hidden-input)
     -1:10.7.0 core:move-up (input.hidden-input)
     -1:10 core:move-right (input.hidden-input)
     -1:07.3.0 core:move-left (input.hidden-input)
     -1:05.6.0 snippets:next-tab-stop (input.hidden-input)
     -1:05.6.0 snippets:expand (input.hidden-input)
     -1:05.6.0 editor:indent (input.hidden-input)
     -0:58.1.0 core:save (atom-pane.pane)
     -0:54.9.0 core:move-up (input.hidden-input)
     -0:54.3.0 core:move-down (input.hidden-input)
     -0:54 core:move-left (input.hidden-input)
     -0:52.2.0 snippets:previous-tab-stop (input.hidden-input)
     -0:52.2.0 editor:outdent-selected-rows (input.hidden-input)

Non-Core Packages
atom-ide-ui 0.9.2
atom-typescript 12.2.0
git-plus 7.10.0
language-elm 1.5.0
language-haskell 1.17.3
quick-highlight 0.12.0
tree-sitter-syntax-visualizer 0.0.2

Sorry @rsese I didn't get a notification for that comment. I'm not able to reproduce in safe mode either. Might have been a problem with pigments? I've had Atom crash/errors thrown before when pasting in color codes for pigments to parse; However never an error thrown from the Atom core.

@clojj I was unable to reproduce with your steps on Fedora 26 with 1.25.0-beta2 - you can reproduce consistently with those steps?
@DanielTamkin no problem - I installed pigments but still wasn't able to repro with your steps on Window 10 and 1.24.0.  Can you still repro on 1.24.0?

@rsese yes, I can reproduce it consistently

@clojj can you disable all your community packages except for language-haskell and see if you can reproduce?  If you can't, can you enable tree-sitter-syntax-visualizer and try again?    It looks like it hasn't been recently updated while some changes have been made on our end.

Not exactly sure how to reproduce, but it only happens when I am resolving Git merge conflicts
Atom: 1.25.0 x64
Electron: 1.7.11
OS: Microsoft Windows 10 Pro (1710)
Thrown From: Atom Core
Stack Trace
Uncaught TypeError: Cannot read property 'element' of undefined
At C:\Users\<user>\AppData\Local\atom\app-1.25.0\resources\app\src\text-editor-component.js:2236

TypeError: Cannot read property 'element' of undefined
    at TextEditorComponent.measureLongestLineWidth (~/AppData/Local/atom/app-1.25.0/resources/app/src/text-editor-component.js:2236:63)
    at TextEditorComponent.measureContentDuringUpdateSync (~/AppData/Local/atom/app-1.25.0/resources/app/src/text-editor-component.js:400:16)
    at scheduler.readDocument (~/AppData/Local/atom/app-1.25.0/resources/app/src/text-editor-component.js:279:20)
    at ViewRegistry.performDocumentUpdate (~/AppData/Local/atom/app-1.25.0/resources/app/src/view-registry.js:245:13)

Commands

Non-Core Packages
atom-beautify 0.32.2
atom-html-preview 0.2.5
atom-material-syntax 1.0.8
atom-material-syntax-dark 1.0.0
atom-material-ui 2.1.3
atom-rst-preview-docutils 1.0.0
busy-signal 1.4.3
code-peek 1.4.21
dockerletion 0.2.0
editorconfig 2.2.2
intentions 1.1.5
language-apache 1.8.0
language-batchfile 0.7.3
language-diff 0.7.0
language-docker 1.1.8
language-ignore 1.7.4
language-lua 0.9.11
language-restructuredtext 1.1.0
linter 2.2.0
linter-eslint 8.4.1
linter-ui-default 1.7.1
preview 0.17.0
svg-preview 0.12.1
teletype 0.10.0
wakatime 7.0.4

Same here.
Occurred after moving line with Cmd+Ctrl up and down through a multi-line function argument
Doesn't always occur, though. And it's very specific. Had the one argument which was an object, with one of the values a string with a number. After repeating, didn't error again. In Javascript.
Atom: 1.26.0-beta0 x64
Electron: 1.7.11
OS: Mac OS X 10.13.3
Thrown From: Atom Core
Stack Trace
Uncaught TypeError: Cannot read property 'element' of undefined
At /Applications/Atom Beta.app/Contents/Resources/app/src/text-editor-component.js:2243

TypeError: Cannot read property 'element' of undefined
    at TextEditorComponent.measureLongestLineWidth (/Applications/Atom Beta.app/Contents/Resources/app/src/text-editor-component.js:2243:63)
    at TextEditorComponent.measureContentDuringUpdateSync (/Applications/Atom Beta.app/Contents/Resources/app/src/text-editor-component.js:408:16)
    at scheduler.readDocument (/Applications/Atom Beta.app/Contents/Resources/app/src/text-editor-component.js:279:41)
    at ViewRegistry.performDocumentUpdate (/Applications/Atom Beta.app/Contents/Resources/app/src/view-registry.js:245:13)

Commands
  9x -0:40.4.0 core:move-down (input.hidden-input)
  9x -0:39 editor:move-line-up (input.hidden-input)
 10x -0:37.5.0 editor:move-line-down (input.hidden-input)
     -0:33.9.0 core:move-up (input.hidden-input)
     -0:33.6.0 core:backspace (input.hidden-input)
     -0:32.9.0 core:save (input.hidden-input)
     -0:30.4.0 atom-minify:close-panel (a.btn-issue.btn.btn-error)
     -0:30.4.0 core:cancel (a.btn-issue.btn.btn-error)
     -0:09.1.0 core:move-down (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-city-lights-ui)
     -0:08.6.0 atom-minify:close-panel (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-city-lights-ui)
     -0:08.6.0 core:cancel (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-city-lights-ui)
     -0:08.4.0 core:move-up (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-city-lights-ui)
     -0:06.7.0 core:move-down (input.hidden-input)
     -0:06.4.0 core:move-up (input.hidden-input)
  9x -0:06.2.0 editor:move-line-up (input.hidden-input)
  9x -0:03.8.0 editor:move-line-down (input.hidden-input)

Non-Core Packages
atom-beautify 0.32.2
atom-handlebars 1.3.0
atom-icons 0.2.2
atom-ide-ui 0.9.4
atom-minify 0.8.0
atom-monokai 0.10.9
atom-ternjs 0.18.3
atom-typescript 12.3.8
atom-uikit 1.2.2
atom-visual-studio-code-ui 1.3.4
auto-indent 0.5.0
auto-indent-file 0.2.0
autocomplete-modules 1.12.0
autocomplete-paths 2.12.2
autocomplete-python 1.10.5
autoprefixer 3.7.1
ava 0.11.0
better-handlebars 0.1.1
busy 0.7.0
busy-signal 1.4.3
carbon-now-sh 2.0.3
city-lights-ui 1.3.3
color-picker 2.2.5
dash 1.7.1
docblockr 0.13.7
docker 0.8.0
dockerletion 0.2.0
docs-snippets 0.8.0
emmet 2.4.3
es6-javascript 1.0.0
guess-indent 0.1.0
Handlebars 1.8.0
hyperclick 0.0.0
ide-java 0.8.2
ide-json 0.2.1
indent-detective 0.2.0
indent-guide-improved 1.4.13
intentions 1.1.5
intentions-colorpicker 1.0.1
jade 1.2.0
javascript-snippets 1.2.1
js-hyperclick 1.13.0
language-docker 1.1.8
language-javascript-jsx 0.3.7
language-lua 0.9.11
language-nginx 0.8.0
language-pug 0.0.22
language-source-cfg 0.3.1
language-vue 0.23.1
linter 2.2.0
linter-docker 0.3.0
linter-eslint 8.4.1
linter-ui-default 1.7.1
material-ui 1.0.10
nms-color-bracket 0.1.0
php-twig 4.0.0
pigments 0.40.2
prettier-atom 0.53.0
pristine-ui 1.1.11
Quick-JavaScript 2.2.0
quick-scroll 2.1.3
rainbow-tabs 2.5.1
react-es6-snippets 0.3.0
react-snippets 1.1.0
seti-ui 1.10.0
solarized-seti-ui 0.8.6
spacegray-atom-dark-syntax 1.3.2
split-diff 1.5.2
sync-settings 0.8.3
teletype 0.8.0
travis-ci-status 1.3.1
tree-view-git-branch 0.1.2
vue2-autocomplete 0.1.0-alpha.4
wakatime 7.0.4

Open a new untitled buffer and paste the following contents

const Something = require('something').A

Something.load('something').then(result => {
  console.log(result.something)
})

Change the language mode to JavaScript
Place the cursor at the end of the last line
Run editor:toggle-line-comments

Atom: 1.26.0-beta1 x64
Electron: 1.7.11
OS: Microsoft Windows 10 Pro
Thrown From: Atom Core
Stack Trace
Uncaught TypeError: Cannot read property 'element' of undefined
At C:\Users\bene\AppData\Local\atom\app-1.26.0-beta1\resources\app\src\text-editor-component.js:2243

TypeError: Cannot read property 'element' of undefined
    at TextEditorComponent.measureLongestLineWidth (~/AppData/Local/atom/app-1.26.0-beta1/resources/app/src/text-editor-component.js:2243:63)
    at TextEditorComponent.measureContentDuringUpdateSync (~/AppData/Local/atom/app-1.26.0-beta1/resources/app/src/text-editor-component.js:408:16)
    at scheduler.readDocument (~/AppData/Local/atom/app-1.26.0-beta1/resources/app/src/text-editor-component.js:279:41)
    at ViewRegistry.performDocumentUpdate (~/AppData/Local/atom/app-1.26.0-beta1/resources/app/src/view-registry.js:245:13)

Commands
     -3:46.8.0 core:move-right (input.hidden-input)
     -3:44.4.0 core:save (input.hidden-input)
     -1:44.8.0 core:backspace (input.hidden-input)
  2x -1:44.3.0 core:delete (input.hidden-input)
  2x -1:43.1.0 core:save (input.hidden-input)
     -0:20.3.0 editor:toggle-line-comments (input.hidden-input)
     -0:01.6.0 application:new-file (input.hidden-input)
     -0:01.3.0 core:paste (input.hidden-input)
     -0:00.6.0 core:undo (input.hidden-input)

Non-Core Packages
highlight-selected 0.13.1
language-latex 1.1.1
latex 0.49.0
teletype 0.12.0

Thanks as always @Ben3eeE :v:  I can reproduce with those steps on macOS and Atom 1.27.0-dev-aa469d5e1.

This issue only occurs when tree-sitter is enabled with the current steps to reproduce. When toggling line comments the longest line changes and gets a new id which causes the update to want to remeasure the longest line. But the old line with the old id is cached and never updated.


Fix | Avoid high mem alloc in TDSWriter#writeReader

This fixes #1475

Thanks for the contribution @vyaslav, we've merged in your PR.

Thanks for the contribution @vyaslav, we've merged in your PR.


Added missing summary description

The summary is missing the important bit of info that is present on the old site at https://msdn.microsoft.com/en-us/library/system.web.httpresponse.setcookie(v=vs.110).aspx
Title
On the title describe
what you've fixed (or created) with this Pull Request (PR).
Summary
Insert a short (one or two sentence) summary here.
Fixes #Issue_Number

Note: The "Fixes #nnn" syntax in the PR description causes
GitHub to automatically close the issue when this PR is merged.
Remove that line if you don't have issues associated with this
PR. Click on the Guidelines for Contributing link above for details.

Details
Explain your changes, and why you made them. If that
information is already available in the issue referenced
above, just referencing the issue is preferred to copying
the text.
This may not be necessary depending on the scope of the PR
changes. For example, "fix typo in introduction.md" is
sufficient to describe that PR.
Suggested Reviewers
If you know who should review this, use '@' to request a review.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Thanks, @slobo80, for adding the missing internal-only boilerplate. Unfortunately, this is part of a more general problem that in migrating from our existing authoring system to GitHub, all information on internal-only types and members was not migrated.
We'll still merge your PR if you can make one change. The first and second sentences will in the same paragraph, and so the internal-only text will not clearly stand out. Could you add a <br/> at the end of the first sentence?

Thanks for making the changes, @slobo80!

My pleasure @rpetrusha ! :)


[SPARK-46678][TEST] Set datanucleus.autoStartMechanismMode=ignored to clean the wall of noisy logs

What changes were proposed in this pull request?

We set datanucleus.autoStartMechanismMode=ignored to clean the wall of noisy logs in this PR.
Why are the changes needed?

An individual test in HiveVersionSuite can print a massive wall of logs as below. Each test file has to be run multiple times in different versions to make things worse.
[info] - 3.1: Decimal support of Avro Hive serde (1 second, 452 milliseconds)
16:20:31.482 ERROR org.apache.spark.sql.execution.command.DDLUtils: Failed to find data source: avro when check data column names.
org.apache.spark.sql.AnalysisException: Failed to find data source: avro. Avro is built-in but external data source module since Spark 2.4. Please deploy the application as per the deployment section of Apache Avro Data Source Guide.
	at org.apache.spark.sql.errors.QueryCompilationErrors$.failedToFindAvroDataSourceError(QueryCompilationErrors.scala:1630)
	at org.apache.spark.sql.execution.datasources.DataSource$.lookupDataSource(DataSource.scala:660)
	at org.apache.spark.sql.execution.command.DDLUtils$.checkDataColNames(ddl.scala:1028)
	at org.apache.spark.sql.execution.command.DDLUtils$.$anonfun$checkTableColumns$1(ddl.scala:1016)
	at org.apache.spark.sql.execution.command.DDLUtils$.$anonfun$checkTableColumns$1$adapted(ddl.scala:1004)
	at scala.Option.foreach(Option.scala:437)
	at org.apache.spark.sql.execution.command.DDLUtils$.checkTableColumns(ddl.scala:1004)
00:20:31.485 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:31.486 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:31.487 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:31.489 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:31.490 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:31.496 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:31.497 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored

00:20:31.500 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:31.582 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:31.583 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored

00:20:31.587 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored

00:20:31.590 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored

00:20:31.591 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored

00:20:31.594 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored

00:20:31.598 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored

00:20:31.599 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored

00:20:31.602 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored

00:20:31.603 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
[info] - 3.1: read avro file containing decimal (135 milliseconds)
16:20:31.626 ERROR org.apache.spark.sql.execution.command.DDLUtils: Failed to find data source: avro when check data column names.
org.apache.spark.sql.AnalysisException: Failed to find data source: avro. Avro is built-in but external data source module since Spark 2.4. Please deploy the application as per the deployment section of Apache Avro Data Source Guide.
	at org.apache.spark.sql.errors.QueryCompilationErrors$.failedToFindAvroDataSourceError(QueryCompilationErrors.scala:1630)
	at org.apache.spark.sql.execution.datasources.DataSource$.lookupDataSource(DataSource.scala:660)
	at org.apache.spark.sql.execution.command.DDLUtils$.checkDataColNames(ddl.scala:1028)
	at org.apache.spark.sql.execution.command.DDLUtils$.$anonfun$checkTableColumns$1(ddl.scala:1016)
	at org.apache.spark.sql.execution.command.DDLUtils$.$anonfun$checkTableColumns$1$adapted(ddl.scala:1004)
	at scala.Option.foreach(Option.scala:437)
	at org.apache.spark.sql.execution.command.DDLUtils$.checkTableColumns(ddl.scala:1004)
00:20:31.630 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:31.631 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:31.632 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:31.634 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:31.639 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
16:20:31.647 ERROR org.apache.spark.sql.execution.command.DDLUtils: Failed to find data source: avro when check data column names.
org.apache.spark.sql.AnalysisException: Failed to find data source: avro. Avro is built-in but external data source module since Spark 2.4. Please deploy the application as per the deployment section of Apache Avro Data Source Guide.
	at org.apache.spark.sql.errors.QueryCompilationErrors$.failedToFindAvroDataSourceError(QueryCompilationErrors.scala:1630)
	at org.apache.spark.sql.execution.datasources.DataSource$.lookupDataSource(DataSource.scala:660)
	at org.apache.spark.sql.execution.command.DDLUtils$.checkDataColNames(ddl.scala:1028)
	at org.apache.spark.sql.execution.command.DDLUtils$.$anonfun$checkTableColumns$1(ddl.scala:1016)
	at org.apache.spark.sql.execution.command.DDLUtils$.$anonfun$checkTableColumns$1$adapted(ddl.scala:1004)
	at scala.Option.foreach(Option.scala:437)
	at org.apache.spark.sql.execution.command.DDLUtils$.checkTableColumns(ddl.scala:1004)
00:20:31.650 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:31.651 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored

00:20:31.653 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored

00:20:31.654 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored

00:20:31.655 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored

00:20:31.656 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored

00:20:31.657 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored

00:20:31.660 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored

00:20:31.661 WARN org.apache.hadoop.hive.metastore.HiveMetaStore: Location: file:/Users/hzyaoqin/spark/target/tmp/spark-25540345-5c0e-40aa-9049-ce088ccd77fb/tab1 specified for non-external table:tab1
00:20:31.693 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:31.695 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:31.698 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:31.701 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:31.703 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:31.705 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.223 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.229 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.232 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.273 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.275 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.282 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.289 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.291 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.294 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.356 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.358 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.361 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.428 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.430 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.433 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.437 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.439 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.441 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.893 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.897 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.950 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.952 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.956 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.963 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.965 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.968 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.970 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.974 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.981 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.982 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:32.985 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.089 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.091 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.094 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.098 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.100 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.102 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.106 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.108 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.111 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.112 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.127 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.128 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.131 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.135 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.137 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.140 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.145 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.146 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.149 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
00:20:33.150 WARN org.apache.hadoop.hive.metastore.ObjectStore: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored

Does this PR introduce any user-facing change?

no
How was this patch tested?

run HiveVersionSuites locally
SPARK_TEST_HIVE_CLIENT_VERSIONS=3.1 ./build/sbt  -Phive -Phive-thriftserver "testOnly *HiveClientSuite*"

Was this patch authored or co-authored using generative AI tooling?

no

@dongjoon-hyun. Thank you very much and the Jira ticket has ben attached.

Thank you! Merged to master.


Small changes for gcc 4.4 compat

With the patch, benchmark_pool_allocator now builds ok.
Est.
2012/1/5 Francois Beaune
<EMAIL_ADDRESS>
Excellent.  I think we need to fix foundation::PoolAllocator<> to make it conformant, i.e. we need to implement operator=.
Could you try this patch?
diff --git a/src/appleseed/foundation/utility/poolallocator.h b/src/appleseed/foundation/utility/poolallocator.h
index dca6eda..3d002d4 100644
--- a/src/appleseed/foundation/utility/poolallocator.h
+++ b/src/appleseed/foundation/utility/poolallocator.h
@@ -168,6 +168,12 @@ class PoolAllocator
    {
    }

+    PoolAllocator& operator=(const PoolAllocator& rhs)
+    {
+        m_fallback_alloc = rhs.m_fallback_alloc;
+        return *this;
+    }
+
    pointer address(reference x) const
    {
        return &x;
@@ -216,8 +222,6 @@ class PoolAllocator

    Pool&               m_pool;
    FallBackAllocator   m_fallback_alloc;
-
-    void operator=(const PoolAllocator& rhs);
 };

 // A partial specialization for the void value type is required for rebinding

Reply to this email directly or view it on GitHub:
https://github.com/jupiter-jazz/appleseed/pull/117#issuecomment-3370979

Awesome, thanks!  I will commit that.
A friend of mine is actually building appleseed on Mac OS X with gcc 4.2 and we're fixing many more errors, I'll let you know when we managed to produce a working build so you don't waste your time on issues we have already identified/fixed.

Let me know if I can help with anything.
Est.
2012/1/5 Francois Beaune
<EMAIL_ADDRESS>
Awesome, thanks!  I will commit that.
A friend of mine is actually building appleseed on Mac OS X with gcc 4.2 and we're fixing many more errors, I'll let you know when we managed to produce a working build so you don't waste your time on issues we have already identified/fixed.

Reply to this email directly or view it on GitHub:
https://github.com/jupiter-jazz/appleseed/pull/117#issuecomment-3371767

Hey Est, my friend managed to build appleseed on 64-bit Mac OS X using Qt 4.8 and llvm-gcc 4.2.  We had to fix a few things on the way, maybe you could pull the changes and give it a try on your machine?


Use both 'signature_img' and 'signature' in makepdf

This PR addresses issue #80

I don't understand the purpose of this change.
If you do not want text in the signature, but only an image, enter only the image as a parameter.
In this change, if there is text, add it to the pdf document, but if there is a picture, also add it to the text, but omit the reference to the text and overwrite it with the picture.
Maybe you mean changing priorities? If we have a picture and text, is the picture more important? Then the whole change would look like this:
annotationimage = udct.get ("signature_img", None)
if annotationimage is None:
annotationtext = udct.get ("signature", None)
else
annotationtext = None
but this is still not what the subject of the report indicates

I don't understand the purpose of this change.
If you do not want text in the signature, but only an image, enter only the image as a parameter.
In this change, if there is text, add it to the pdf document, but if there is a picture, also add it to the text, but omit the reference to the text and overwrite it with the picture.
Maybe you mean changing priorities? If we have a picture and text, is the picture more important? Then the whole change would look like this:
annotationimage = udct.get ("signature_img", None)
if annotationimage is None:
annotationtext = udct.get ("signature", None)
else
annotationtext = None
but this is still not what the subject of the report indicates