RE/flex generated scanned in a Bison C grammar

The documentation and the examples suggest that it is possible to use a RE/flex generated scanner in a Bison generated C grammar. However, the header file generated by RE/flex cannot be included into a C source file (at some point down the includes chain <cstdio> is included and this does not work in C, there may be other issues as well). AFAICT, in the examples, when the header file generated by RE/flex is included in the Bison sources, they are compiled with a C++ compiler. Unfortunately, because of other constraints I cannot do that. Is the RE/flex generated header file supposed to work in a C source file? Is there an easy way to make it work?
I need the generated header file for the definition of yylex_init(), yylex_destroy(), yylex() and some other functions I define in the RE/flex source file, which are correctly present in the generated header file. But I would also like to be able to use yyget_text() and yyget_leng(), which do not seem to exist in the header, nor as exported C symbols.
If there is interest in this use case, I can provide a minimal example that demonstrates my issues.

The scanner requires C++ to enjoy the speed and usability improvements.
Using Bison's generated C code works fine, as long as you compile its source code also with C++, not C because that will never work when including C++ header files such as the one generated by reflex. If your compiler complains about the .c extension of the Bison parser source code, then just rename it to .cpp. C is a strict subset of C++.
As for yyget_text() and yyget_leng() they are defined when you set the following options in the lexer specification:
%option flex
%option reentrant

This will let reflex generate the scanner with reentrant functions. In fact, these are declared in include/reflex/flexlexer.h which is included with option flex and the definitions are available with option reentrant or bison-bridge.

While C++ being a superset of C may have been true at some point in the past, I don't think that this can be claimed any more: there are plenty of C constructs that are not valid C++. Another issue is symbols mangling in C++. The point I was trying to make is that I don't see why the generated header file needs to depend on any C++ header. At a first glance, the bulk of the work is to replace some macros with extern "C" functions. I'll see if I can make this work in my project and I will share the result here.

ISO C++: "C++ supports every programming technique supported by C95 (C90 plus an Amendment) and earlier."
ANSI C code (C95) and C code up to C99 actually should pose no problems masquerading as C++. I'm pretty sure Bison is C99.
However, there will be changes and additions to the C++ standard as of C++20 that can break C95 code (if certain constructs are used that will be banned).
This seems all a lot of work to me to force things into or from headers to make them compile with C, which I'm not sure is possible given that --flex essentially is -+ in Flex to generate C++ code. Like Flex, RE/flex imports aflexlexer.h header file that declares a C++ FlexLexer class.
Why not produce C++ code with Bison?

I am working on a project in which the parser is a small part. If I produce C++ code with Bison, I am only moving the boundary of the problem. I still need to embed some C++ into a C project. Judging from the documentation https://www.genivia.com/doc/reflex/html/#reflex-bison, at some point, being able to use RE/flex generated scanner in a C project was a goal. Indeed, doing it is easy but the RE/flex generated header cannot be used. What I have done is to use this header:
typedef struct _yyextra_t yyextra_t;
typedef void *yyscan_t;

int yylex(YYSTYPE*, YYLTYPE*, yyscan_t, PyObject* builder);
void yylex_init(yyscan_t*);
void yylex_init_extra(yyextra_t*, yyscan_t*);
void yylex_destroy(yyscan_t);

const char* __yyget_text(yyscan_t s);
size_t __yyget_leng(yyscan_t s);

#define yyget_text(s) __yyget_text(s)
#define yyget_leng(s) __yyget_leng(s)

where the last lines allow to use yyget_text() and yyget_leng() from outside the lexer definition. The indirection through the macros allows to keep using the macro version of yyget_text() and yyget_leng() inside the lexer definition. In the lexer definition I added this code:
%top{
#define YY_EXTERN_C extern "C"
}

...

YY_EXTERN_C const char* __yyget_text(yyscan_t s)
{
    return static_cast<FlexLexer*>(s)->YYText();
}

YY_EXTERN_C size_t __yyget_leng(yyscan_t s)
{
    return static_cast<FlexLexer*>(s)->YYLeng();
}

That's nice.

I think it is an hack that makes the thing work, but I wonder if something could be done to make the RE/flex generated header to work. From this experiment, it seems that some #ifdef __cplusplus / #endif trickery may solve most of the problems.
Also, can you comment about the use of macros for yyget_xxx() functions? Would using functions (that can be invoked from C code) have a noticeable impact on performance? I don't know if the linker is smart enough to inline them. This would solve the remaining problems.

Because the function definitions are not visible in the Bison parser source (i.e. the function body is lacking), they will not be inlined. This incurs some overhead versus macros or inlined functions. However, it depends on how and when these functions are used in the parser. Note that these two functions yyget_text and yyget_leng are typically not needed in the parser at all. Lexemes (yytext values) are usually returned by the scanner to the parser as the semantic values of tokens (i.e. attributes associated with terminals).

Absolutely. I need yyget_text() and yyget_leng() in my application because it has a debug facility that emits the tokens stream along with their semantic value and matched text (lexemes? I never encountered this word before). It is thus not important for these two functions exported to my application to be optimized, it is debugging after all.

That makes sense. Just saying that a lexeme of a grammar's terminal (token) that represents a syntactic category can be passed to the parser as a semantic value. It depends on how the project is structured if this is an easy implementation or not. But for sure it's easier said than done in C.

I am not sure I understand. As an example, this lexer recognizes dates in the form YYYY-MM-DD. These are returned as DATE tokens with a date object as a semantic value. Running the scanner on the string "2020-07-28" results in a DATE token with semantic value date(2020, 7, 28) object. The debugging facility prints something like:
DATE 1 date(2020, 7, 28) "2020-07-28"

where 1 is the line number. Are you saying that one think that could be done is to have a tuple (date(2020, 7, 28) "2020-07-28") as semantic value for the token? Because the lexeme is used only in debug, I think that this would be over engineering the solution.

Semantic values are not atomic, they can be anything, such as a pair or a struct with members. In your case there would be yylval.text = yytext(); yylval.date = date(yytext); for example. Typical lexers do more than just return one semantic value. For example, with Bison C++ "complete+location" parsers, scanners return the full location information for each token. That is the starting row/column and ending row/column. Four values plus other semantic values. This is used to enhance syntax error reporting. The parser could have used yyget_yylineno(), but that is not the direction in which these technologies are evolving, as with the cleaner Bison complete APIs. On the other hand, there are other ways to share the state of the lexer with the Bison complete parser directly, while ensuring that the state is nicely under control of C++ access privileges. This is efficient too, because accessing the state has zero calling overhead. It is certainly more efficient if the state is rarely used. In that case you don't have to return this state information as semantic values for each token. There are some examples of direct access to the lexer state in the RE/flex examples, such as the Mini C compiler minic.y.

I see. I completely agree and I would implement a better solution if this would not be simply a debug facility. Thank you!

I think it is an hack that makes the thing work, but I wonder if something could be done to make the RE/flex generated header to work. From this experiment, it seems that some #ifdef __cplusplus / #endif trickery may solve most of the problems.

Looking into this to improve the --header-file output for Bison C use, i.e. when option bison or bison-bridge is used and the header file is compiled in C.

The changes to improve reflex are almost done to generate yyget_text() and so, for compatibility with Bison-bridge C code with optional use of bison-locations. The C++ parts of the generated header file will be invisible in C, when lex.yy.h is included in a C file.
I am keeping the yyget_func macros in flexlexer.h for C++, which are visible in C++ code to improve efficiency, but will not be visible in C code, obviously.
It is coming together nicely. The C extern linkable functions are:
    char *yyget_text ( yyscan_t scanner );
    yy_size_t yyget_leng ( yyscan_t scanner );
    FILE *yyget_in ( yyscan_t scanner );
    int yyget_lineno ( yyscan_t scanner );
    YY_EXTRA_TYPE yyget_extra ( yyscan_t scanner );
    int  yyget_debug ( yyscan_t scanner );
    void yyset_debug ( int flag, yyscan_t scanner );
    void yyset_in  ( FILE * in_str , yyscan_t scanner );
    void yyset_lineno ( int line_number , yyscan_t scanner );
    void yyset_extra ( YY_EXTRA_TYPE user_defined , yyscan_t scanner );

The Bison C examples that come with RE/flex will be updated as well, serving both to demo the toolchain, but also serving as simple unit and regression test cases.

This is exactly what I was suggesting. Thank you. I am glad that the use case I proposed is not completely unreasonable.

See update v2.1.3. Several of the Flex+Bison examples, including the bison-bridge examples, are updated to compile with C, not C++. These use the reflex-generated header files. I hope this update works for you too.

Thanks. I gave v2.1.3 a try and it works for my use case. Thank you very much.


Add output to stats?

I ignore if this is possible, but could be useful to add a report to stats generated by webpack instead of outputting the result of the inspection.
I'm using webpack from another application and I expect the output to be a JSON (using --json option).
If not possible, consider outputting your result to a specified file instead like this other plugin is doing BundleAnalyzer

In 1.1.0, console.log and console.warn is no longer used and warnings are passed as compilation warnings and can be found in the stats.json, so this issue can be closed.


TypeError: Cannot read property 'setDecorations' of undefined

TypeError: Cannot read property 'setDecorations' of undefined
	at exitJumpyMode (/home/capaj/.vscode/extensions/wmaurer.vscode-jumpy-0.3.1/out/src/extension.js:37)
	at /home/capaj/.vscode/extensions/wmaurer.vscode-jumpy-0.3.1/out/src/extension.js:83
	at l.fire (/snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:45)
	at /snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:831
	at l.fire (/snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:45)
	at b.acceptDocumentsAndEditorsDelta (/snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:718)
	at b.$acceptDocumentsAndEditorsDelta (/snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:716)
	at m._doInvokeHandler (/snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:870)
	at m._invokeHandler (/snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:870)
	at m._receiveRequest (/snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:868)
	at m._receiveOneMessage (/snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:867)
	at /snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:865
	at l.fire (/snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:45)
	at v.fire (/snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:256)
	at /snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:1059
	at l.fire (/snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:45)
	at v.fire (/snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:256)
	at t.PersistentProtocol._receiveMessage (/snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:261)
	at /snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:258
	at l.fire (/snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:45)
	at p.acceptChunk (/snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:253)
	at /snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:253
	at Socket.t (/snap/code/48/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:263)
	at Socket.emit (/snap/code/48/usr/share/code/resources/app/out/vs/code/electron-browser/workbench/events.js:223)
	at addChunk (/snap/code/48/usr/share/code/resources/app/out/vs/code/electron-browser/workbench/_stream_readable.js:309)
	at readableAddChunk (/snap/code/48/usr/share/code/resources/app/out/vs/code/electron-browser/workbench/_stream_readable.js:290)
	at Socket.Readable.push (/snap/code/48/usr/share/code/resources/app/out/vs/code/electron-browser/workbench/_stream_readable.js:224)
	at Pipe.onStreamRead (/snap/code/48/usr/share/code/resources/app/out/vs/code/electron-browser/workbench/internal/stream_base_commons.js:181)

@capaj Fixed in Jump.


Non-static method Rawilk\Printing\Printing::newPrintTask() cannot be called statically

Laravel Printing Version
v3.0
Laravel Version
v8.83.3
Bug description
namespace -> use Rawilk\Printing\Printing;

Steps to reproduce
No response
Relevant log output
No response

use Rawilk\Printing\Facades\Printing;
fix


How to use dependabot-core to raise PR for a bitbucket repository

How to use dependabot-core to raise PR for a bitbucket repository

There's two types of BitBucket support:

Pulling dependency updates from repos from bitbucket... this is already supported, it's just another git repository endpoint. We do have a little bit of special handling for the bitbucket client, but not a lot.
Running dependabot itself on BitBucket to update code within a Bitbucket repo. For that you're looking for https://github.com/dependabot/dependabot-script


Questions about publishing on Pypi

Hi !
Thank you for open-sourcing those scripts !
We used them over the last year at work, and they were very useful.
We made some slight improvements to some of them, and just thought today that we could publish those on GitHub.
I've just created a public fork https://github.com/voyages-sncf-technologies/marathon-deployer
And we will soon upload additional commits to it,
and submit a PR if you wish to incorporate them.
We currently upload it as a package on our internal Python repository,
and we thought it could also be published on the public Pypi repo.
Hence I have some questions:

do you plan to publish it on Pypi ?
else, would you agree that we do so ?
if so, do you have a prefered license ? Maybe "Apache 2" ?

Kind regards @nicovillanueva

Bonjour Lucas !

Yes, please do send a PR with your changes. As you probably noticed, I published the project and basically forgot about it, but I'm now installing miniDCOS to give it a bit of love and maintenance.
Once your PR is merged and whatever changes I come up with are done, I'll put it up on PyPi, of course.
Now, given that you've been using it, do you have any features you'd like to see implemented? And, any suggestions for a catchier name than just "deployer"?
Merci beaucoup, @Lucas-C !

Here is our PR: https://github.com/nicovillanueva/marathon-deployer/pull/3
It includes some configuration for Travis CI (are you familiar with it ?) and a suggestion of steps to upload a package on Pypi: https://github.com/voyages-sncf-technologies/marathon-deployer/tree/version-3#pypi-publishing (wich could be done with Travis CI too if you wish)

Yeah, the changes look great. I'll merge them right now.
I know of Travis CI, but never really used it, so this definitely is a good chance to give it a go.
I'll leave this ticket open until this is up on PyPi. Thank you so, so much for your help.

@Lucas-C , the project is up in PyPi: https://pypi.org/project/marathon-deploy/3.0.2/
It's been a while since I published anything there, so the working version is 3.0.2. The previous ones are flukes.
Notice that there are a two potentially breaking changes: I changed the repository name to "marathon-deploy" to be consistent with the executable's naming; and I changed the executables from *-marathon to marathon-* (e.g., the executable is now marathon-deploy).
I'll keep working on the project so feel free to raise new issues with either bugs or feature requests. Also, PRs are more than welcome.

Awesome, ! Thank you very much !

For Travis CI, you should just need to login with your GitHub account and enable this repo on the page https://travis-ci.org/account/repositories


Fix the style of the web site

Resolve #76

what bg-color you choose to use ??

The putter is almost in good condition, some pages have a small space Any idea how to fix this?

try this => in footer css {position: fixed;}
if not try to change the main element height

LGTM
consider changing the path of search_article.html as said in issue #76

In addition to this comment.
@Anas-mhameed What do you think about deleting the templates/projboard folder? And just keep it templates/searchArticle

LGTM
consider changing the path of search_article.html as said in issue #76

In addition to this comment.
@Anas-mhameed What do you think about deleting the templates/projboard folder? And just keep it templates/searchArticle

it's ok, we can do that

@yaelnoyman1  in search_article.html there is an issue with the search bar height, fix that too.

@yaelnoyman1 in search_article.html there is an issue with the search bar height, fix that too.

Yes, now it makes sense to me why the footer is only good there

what bg-color you choose to use ??

look in base.css

in search_article.html there is an issue with the search bar height, fix that too.

I fixed it already

LGTM
consider changing the path of search_article.html as said in issue #76

done


huggingface

In huggingface, take sup-simcse-bert-base-uncased for example, its pytorch_model.bin is a compressed file, which is different from bert-base-uncased. How do I use its pytorch_model.bin to fine-tune my model?

error


Support Prometheus standard time formats in silence creation

Prometheus supports relative time options like y and w which would be quite helpful to use when creating silences.
https://github.com/prometheus/common/blob/0b1957f9d949dfa3084171a6ec5642b38055276a/model/time.go#L192-L205

It is for the UI, right?

Yeah, in the silence creation form in the UI

I am cool supporting w, but as a project alertmanager wants to discourage "eternal silences". It's still possible if users want to do it, but a month (4w) seems to me like the upper bound on how long something should be silenced.


Add ability to FETCH collections while focused on it

Focus mode in general has been ignored since v2.0. I want to start updating it so that it has more use cases. Currently, when a user enters FOCUS mode on a collection and then tries to use the FETCH COLLECTION <collection_name>  command they are told "Cannot fetch a collection while in focus mode....". This needs to be updated.
The user should be able to use the FETCH command without any other tokens while focused on a collection. This will have the same result if the user entered  FETCH COLLECTION <collection_name> while not in FOCUS mode.

This one is a super easy fix. literally need to just do this:
				str := data.OST_FETCH_COLLECTION(<focusObject>)
				fmt.println(str)

from the focus command line.

FOCUS mode is disabled


ag's file search (-g) doesn't respect '^' regex operator

E.g., I am seeing:
kevinushey@Kevin-MBP:~/agtest$ touch test.cpp
kevinushey@Kevin-MBP:~/agtest$ ag -g .
test.cpp
kevinushey@Kevin-MBP:~/agtest$ ag -g "p$"
test.cpp
kevinushey@Kevin-MBP:~/agtest$ ag -g "^t"

This is with homebrew ag, 0.24.1. The ^ operator seems to work for text searched within files, however.

I also just ran into this issue myself.

just got bit with this one too.
The real bummer here is it discourages migration from ack because the search behavior doesn't act the same way across tools:
❯ ack -g '^in'
index.js

❯ ag -g '^in'

❯ ag -g '^\./in'
index.js

❯ ack -g '^\./in'

Just my $0.02 but I think the ./ should be stripped to maintain compatibility. Pretty huge breaking change though.

Any chance of this being resolved? This is actually pretty annoying and it seems like it wouldn't be that difficult to fix?


Published Snyk report

@crenshaw-dev

Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

As discussed in meeting.

I think we could add a CI job to generate the relevant report(s) as JSON, convert that to HTML (there's a CLI for that), and upload the HTML as a release asset. Going to look into doing this for Argo CD and then will port it over.

@crenshaw-dev can I please bump

I've made a bit of progress in the argo-cd repo (https://github.com/argoproj/argo-cd/issues/8657). Relevant Snyk scans can now block builds on high-level failures. My next step is to add reports to release assets. I haven't scheduled time for that yet, but hoping soon.
Once the work is done, it should be trivial to replicate in Rollouts/Workflows/Events.

I noted yesterday, that snyk.io shows different issues to running snyk test.
I think we should probably just use snyk.io, not snyk test, as it is zero-config.

There are a few problems with the web UI:

It doesn't automatically scan new tags. Every time we cut Argo CD releases, I have to delete the old Quay projects and add new ones.
It doesn't block builds. We have to proactively go to the UI to check for high-severity vulnerabilities.
It doesn't allow declarative "ignore" configuration. When we know a high-severity issue isn't actually an issue in the project, we either have to remember to ignore it when we look at the Snyk UI, or we have to manually add an "ignore" rule in the UI.
"Ignore" rules in the UI are not reviewed, version-controlled, or public. I think it's good that the community can look at .snyk in the project repo to see when an ignore rule was added, what justification was given, and view any discussion on the change's PR.
The UI doesn't generate a report which is publicly associated with a release. In the case of the Quay checks, the checks are against certain tags - but the report isn't publicly-available, and there's no historical record of past versions. In the case of the GitHub checks, only the latest commit on the master branch is scanned. So there's no (for example) npm report available for current versions or historical versions; even if there were, they wouldn't be publicly available.

tl;dr - the web UI isn't exactly zero-config - versioned scans and ignore rules must be maintained. I think the benefits of the CLI are worth the relatively light config work.

@crenshaw-dev can I bump?

@alexec I'm gonna try to get this into next sprint.


vega-2375 - Move donor details to LPA details tab

vega-2375
Checklist

[ ] I have updated the end-to-end tests to work with my changes
[ ] I have added styling for Dark Mode
[ ] I have checked that my UI changes meet accessibility standards

Codecov Report
Attention: Patch coverage is 14.81481% with 23 lines in your changes are missing coverage. Please review.

Project coverage is 70.93%. Comparing base (8ad2ada) to head (53f5632).

Files
Patch %
Lines

internal/templatefn/fn.go
0.00%
23 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #485   +/-   ##
=======================================
  Coverage   70.92%   70.93%
=======================================
  Files         106      106
  Lines        3587     3588    +1
=======================================
+ Hits         2544     2545    +1
  Misses        740      740
  Partials      303      303

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


KML widget very slow with multiple open files

When having or adding multiple files, the handling of KML overlay widget becomes unbearably slow.
Code investigating shows that 5 files cause them to be loaded 5 times, i.e. 25 operations, instead of 5, progressing quadratically for more files.

We currently (would like to) use a dozen KML files with hundreds of placemarks and this is killing MSUI.
That all KML files are loaded again for every check/uncheck operation would be a further optimization beyond the scope of this fix.


[Help] Can't get custom styling to work

I feel like I am missing something.
Mix: 6.0.11
Laravel: ^7.0
Sass-loader: 9.0.3
So I got this template from a company, and they were using the vue-cli-builder. I tried to move it over to laravel-mix, but I am running into an issue where none of the custom css is transferring over, and I'm not exactly sure how to include it.
My mix is
mix.js('Resources/platform/src/main.js', path.resolve(__dirname, '../../public/assets/webinars/vueplatform/js') )
   .webpackConfig({
        resolve: {
            alias: {
				'@': path.resolve(__dirname, 'Resources/platform/src/'),
            }
        },
        output: {
			filename: '[name].js',
			path: path.resolve(__dirname, '../../public'),
            chunkFilename: mix.inProduction() ? 'assets/webinars/vueplatform/js/[name].[chunkhash].js' : 'assets/webinars/vueplatform/js/[name].js',
        },
        plugins: [
            new MomentLocalesPlugin({
                localesToKeep: ['el'],
			}),
		],
    })
   .vuetify('vuetify-loader', path.resolve(__dirname, 'Resources/platform/src/styles/variables.scss')).vue();

my variables.scss is
@import "~vuetify/src/styles/styles.sass";
@import<EMAIL_ADDRESS>// the custom styles

// Globals
$body-font-family: 'Ubuntu', serif;
$border-radius-root: 6px;
$rem-base: 14px;
$font-size-root: 14px;
$line-height-root: 1.4;
$primary-text-color: #001f28;
$primary-link-color: #005A77;
$primary-link-hover: #33B268;

and then the main.scss contains a bunch of stuff like
@import 'mixins/breakpoints';
@import 'mixins/functions';
@import 'mixins/helpers';
@import 'mixins/mixins';
@import "~vuetify/src/styles/settings/variables";

@import "components/admin-panel";

.v-application {
  overflow: hidden;
}

.header, .content{
  min-height: 100%;
  position: relative;
}

.twocolumns{
  height: 100vh;
  position: relative;
}

Just trying to figure out the best way to include these custom styling, as I am obviously doing something wrong.

You need to add the sass method to compile your sass:
.sass('resources/sass/main.scss', 'public/css')

You need to add the sass method to compile your sass:
.sass('resources/sass/main.scss', 'public/css')

Yeah I tried that to but it doesn't seem to be applying them. Do you know of another project I can look at per chance?

To be more clear, looks like my custom styling is getting applied. But I can't seem to over-ride vuetify custom variables and css.
For example
in my variables.scss
$body-font-family: 'Ubuntu', serif;
$border-radius-root: 6px;
$rem-base: 14px;
$font-size-root: 14px;
$line-height-root: 1.4;
$primary-text-color: #001f28;
$primary-link-color: #005A77;
$primary-link-hover: #33B268;

None of that seems to be applying. Despite it being first in my import app.scss
@import 'variables';
@import '~vuetify/src/styles/main.sass';
@import '~vuetify/src/styles/styles.sass';
@import 'mixins/breakpoints';
@import 'mixins/functions';
@import 'mixins/helpers';
@import 'mixins/mixins';
@import 'custom';

However, my css is app.scss is applying
.v-application {
  overflow: hidden;
}

.header, .content{
  min-height: 100%;
  position: relative;
}

mix.js('Resources/platform/src/main.js', path.resolve(__dirname, '../../public/assets/webinars/vueplatform/js') )
	.vuetify('vuetify-loader', path.resolve(__dirname, 'Resources/platform/src/styles/variables.scss'))
	.vue()
	.webpackConfig({
		resolve: {
			alias: {
				'@webinar': path.resolve(__dirname, 'Resources'),
				'@assets': path.resolve(__dirname, 'Resources/platform/src/assets'),
				'@': path.resolve(__dirname, 'Resources/platform/src/'),
			}
		},
	.sass('Resources/platform/src/styles/main.scss', path.resolve(__dirname, '../../public/assets/webinars/vueplatform/css') )

Im pretty sure its not the package and is something wrong with what I am doing. I appreciate any guidance though.

After some more tweaking, my styles are being applied to my app.scss, but they are not being applied to vuetifies styles

I am having this same problem. Maybe it would help if you put all of this code into a http://codepen.io/ or something so that they can tell us what to change!

I am having this same problem. Maybe it would help if you put all of this code into a http://codepen.io/ or something so that they can tell us what to change!

I downloaded the example mix git he linked as a working project. Did an npm install, npm run dev, composer install. Couldn't even get that to work, so I think its something with the package / laravel mix update?
I kind of gave up and moved on to this solution.
https://github.com/vuetifyjs/vuetify-loader/issues/49#issuecomment-780752959
Which loads my variables perfectly. Now I am just having issues with Vuetify overriding my custom css. From the comments, it looks like laravel-mix loads the config before doing vuetify-loader or something. Related to this maybe?
https://github.com/JeffreyWay/laravel-mix/issues/2439
All I know is I did mix.listen and set it up, and it seems to load my variables now.

Hey @alexbbt,
If you are still having problems, I was able to fix it doing this
https://github.com/vuetifyjs/vuetify-loader/issues/49#issuecomment-784454928
Fix, workaround, whatever. it works lol

Oh nice, thanks! I'll try those steps


Adding support for Gmail extensions

Gmail added a few non-standard extensions to the IMAP protocol, for handling labels and a few other things.
What's this project's stance on supporting non-standard extensions?

I'm not against adding these in, probably behind a trait of some kind so that users have to explicitly say they want access to those methods. Or maybe better yet, through a
impl Session {
    fn gmail(&mut self) -> Option<GmailClientExtensions<'_>> {}
}

which returns None if the appropriate capability is present on the server.

Okay, cool. I'll give it a shot. ^_^

Well, that was easy -- it turns out that support for Gmail labels (which was the only thing I care about) was added to imap-proto a couple of months ago.
Unfortunately, they haven't made a release yet that includes those changes.
In the meantime, I forked rust-imap, switched the imap-proto dependency to pull from the git, and did what needed to be done: https://github.com/CrispinStichart/rust-imap/commit/6e5ec17be5184e1ddd0f3f41b7c1cd5bf5c570d4
You'll notice I deleted NameAttributes entirely, because imap-proto implemented that with this commit: https://github.com/djc/tokio-imap/commit/4f60707e4e81982dae1d1a6820628357d2e81154

@djc Any chance we could have a new imap-proto release with the label changes?

I just published imap-proto 0.16 to crates.io.

Thank, djc!
I made a pull request for this: https://github.com/jonhoo/rust-imap/pull/225


Refactor test_errors.py

test_errors should probably be reorganized and broken into smaller functions (while reusing the error validation logic).
Originally posted by @omry in https://github.com/omry/omegaconf/pull/503#discussion_r570537028

Please wait with this until we merge #445,


"EDITATI" section - An extra option/search bar to search the counties

for the moment, in the "Editati" section (for each job) you can only search the locality. It would be nice if the search can be alos done by county (ex: to be possible to search for the Dolj county and select it even if it isnt any locality selected) .

Added in pull request #94


Next release

Hi
What is the ETA of 0.4.0? I'm eagerly waiting for reactive charts :-)
Jan

What feature are you currently missing?

Only what seems to be in master, with version number and all. Just wondering if I should clone or just wait a day or two for it.
"meteor add" gives me 0.3.0, in master there's 0.4.0 with the "realtime charts" commit.

Oh, yeah. You are right. Lets call @MaazAli

Pushed the latest onto atmosphere!

Thanks!


delete a deployment

It would be great to have put be able to delete a deployment.

I agree. Seems like a reasonable addition. I'll go ahead and add this to the list of features to implement in the near term. Always happy to accept PRs as well :)

I'll look into it.

Hey there! Closing this issue as this feature was just released as part of 2.8.0.


How to use mixins from .scss files in .vue files?

Hi,
I got an error - "no mixin named sm" when trying to use my scss mixins in Single Vue Components - sm is my mixin variable name.
My _mixins.scss is in my assets/styles folder. How can i use my mixins in .vue files?

Hi,
I think you'll need to import the mixins file in your components. You can read some alternatives here.
long story short: import the file in your component or add it to your webpack configuration.
Hope it helps!


Problem : data not wrote in elasticsearch

Hey,
I'm trying to load a json file in elasticdump.
I execute this command line
elasticdump --bulk=true --input="/home/exploi/kibana/zips.json" --output=http://localhost:9200/zips --type=data
The data is sent but not write on elasticsearch
Tue, 19 Apr 2016 15:44:26 GMT | got 603 objects from source file (offset: 697)
Tue, 19 Apr 2016 15:44:43 GMT | sent 603 objects to destination elasticsearch, wrote 0
Have you any idea

bulk mode was just removed in recent versions, as it was known to be buggy.  We are also working on fixing some bugs with elasticsearch v2.   https://github.com/taskrabbit/elasticsearch-dump/pull/202

Thanks a lot, this wasted 4 hours of my life. 👍

maybe you shoud upgrade your elasticdump and upgrade your nodejs version


Fix "Unknown task: git_fsck" error on admin dashboard (#11468)

Backport of #11468

Make lg-tm work


Use progress bar from Gradio

Hi, great package.
Gradio supports a custom progress bar TQDM-style. Is there any chance to support this?
Example:
import gradio as gr
from cached_path import cached_path
def update(url, progress=gr.Progress()):
	file = str(cached_path(url, progress=progress.tqdm))
	return file
with gr.Blocks() as demo:
    inp = gr.Textbox(label="Enter URL", info="Enter URL")
    out = gr.File(interactive=False)
    btn = gr.Button("Run")
    btn.click(fn=update, inputs=inp, outputs=out)

demo.launch()

Hey @fakerybakery this is definitely doable. We could provide an API for this, but in the meantime you would just need to create a thin wrapper around gr.Progress to pass it to cached_path. I think something like this would suffice:
from typing import Optional

class GrProgressWrapper:
    def __init__(self, gr_progress):
        self.completed = 0
        self.total = 0
        self.inner = gr_progress

    def add_task(self, description: str, total: int) -> int:
        del description
        self.total = total
        return 0  # returns a task_id, doesn't matter unless you're doing multiple downloads with the same bar

    def advance(self, task_id: int, n: int):
        del task_id  # not needed unless you're doing multiple downloads with the same bar
        self.completed += n
        self.inner((self.completed, self.total))

    def update(self, task_id: int, total: Optional[int] = None, completed: Optional[int] = None):
        del task_id  # not needed unless you're doing multiple downloads with the same bar
        if total is not None:
            self.total = total
        if completed is not None:
            self.completed = completed
        self.inner((self.completed, self.total))

I haven't tested this so let me know if you have issues.

Thanks so much! I tried doing something like this previously but wasn't able to figure it out :) Should I close this issue now?

If that worked for you feel free to close :)


Poorly written examples difficult to follow

This page needs more clearer and concise examples of usage

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

ID: 038ae35e-c5e9-e1a4-a6dd-afe379201245
Version Independent ID: d73f3d5a-00d4-2e22-c120-8e8d6d101a54
Content: ?? and ??= operators - C# reference
Content Source: docs/csharp/language-reference/operators/null-coalescing-operator.md
Product: dotnet-csharp
Technology: csharp-language-reference
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thanks for reaching out to us @Benny1007
Can you provide more details about what questions you have, and how new examples would help? We'd like to address this, but I'm not sure what questions you have.
Thank you.


Job Scheduler is Inconsistent in lenovo(5.0.2)

Job service did not get call always periodically after every 30 second. It is very inconsistent some time it is getting called some time not. Below is the code. This work well in other device.
Job myJob = dispatcher.newJobBuilder()
// the JobService that will be called
.setService(LocationJob.class)
// uniquely identifies the job
.setTag("location")
// one-off job
.setRecurring(true)
// don't persist past a device reboot
.setLifetime(Lifetime.FOREVER)
// start between 0 and 60 seconds from now
.setTrigger(Trigger.executionWindow(1, 30))
// don't overwrite an existing job with the same tag
.setReplaceCurrent(true)
// retry with exponential backoff
.setRetryStrategy(RetryStrategy.DEFAULT_EXPONENTIAL)
// constraints that need to be satisfied for the job to run
//.setExtras(jobBundle)
.build();
    dispatcher.mustSchedule(myJob);

In fact, it is inconsistent in general. I have 2 phones (same model, same Android version, same app). Jobs are running fine in one while in another it can take hours to run.
We can't rely 100% on it and Google continue to recommend it. That's inconceivable!

.setTrigger(Trigger.executionWindow(1, 30))
means: start this task between 1 and 30 seconds after the last run of this task. You might be after:
.setTrigger(Trigger.executionWindow(30, 30))

Recurring jobs soon will have 15 minutes period enforced by the Android platform in order to save battery.
If you need to execute you job more frequently you need to schedule not recurring job at the end to your job.
Perfect timing is not guarantied.


README.md: Add info about Change-type and Changelog-entry

Change-type: patch
Changelog-entry: Document Change-type and Changelog-entry git commit footers
Signed-off-by: Andrei Gherzan<EMAIL_ADDRESS>

Documentation change - no need to wait for builds.


Infinite loading on form with Select and FileUpload

Package
filament/forms
Package Version
v2.16.37
Laravel Version
v9.38.0
Livewire Version
v2.10.7
PHP Version
PHP 8.1.12
Problem description
When creating a form with Select and FileUpload components, it will infinitely request to server
This issue appears only if using Select and FileUpload components together.

Expected behavior
No infinite loading
Steps to reproduce

Create a form with Select and FileUpload components.

                Forms\Components\Select::make('categories')
                    ->label('Categories')->translateLabel()
                    ->multiple()
                    ->relationship('categories', 'name')
                    ->preload(),

                Forms\Components\FileUpload::make('attachments')
                    ->multiple()
                    ->maxFiles(3)
                    ->storeFileNamesIn('attachment_file_names'),

Add attachments and attachment_file_names to the model fillable and casts array:

    protected $casts = [
        'attachments' => 'array',
        'attachment_file_names' => 'array',
    ];

Open the resource Create page, upload a file and save the resource

Reproduction repository
https://github.com/icaliman/filament-bug-infinite-loading
Relevant log output
No response

Issue disappeared without storing the original file names:
protected $casts = [
    'attachments' => 'array',
    // 'attachment_file_names' => 'array',  // <------
];

Forms\Components\FileUpload::make('attachments')
    ->multiple()
    ->maxFiles(3),
// ->storeFileNamesIn('attachment_file_names'),  // <------

Bug in Livewire. Related to array keys that contain . triggering watchers erroneously. Bumped this to v3 to see if it will be fixed with Livewire v3 when it arrives.

I have the same undesired polling problem with preloaded Select and FileUpload. Does it have a workaround? I had to put the FileUpload to a different page but unfortunately it is not user friendly.

Fixed by Livewire 3.


Proofs about retiming sbox

Prove that if the s-box is retimed, the AES circuit still produces the right result (just at a different index).
Depends on #810, #811

Closing this; the circuit retiming work has been paused indefinitely due to the cava2 rewrite, and the in-progress work pushed to the retiming-interactive branch.


provide standalone grpc test applications

What does this PR do?
This PR provides standalone test applications for gRPC.
This allows to quickly test gRPC support and effects with/without agent outside of any integration / unit test.
Those simple applications execute a set of known RPC calls to an embedded server within the same JVM, and use exactly the same endpoints as unit tests.
Checklist

[x] My code follows the style guidelines of this project
[x] I have rebased my changes on top of the latest master branch
I have made corresponding changes to the documentation
I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
I have updated CHANGELOG.asciidoc
I have updated supported-technologies.asciidoc
Added an API method or config option? Document in which version this will be introduced
Added an instrumentation plugin? How did you make sure that old, non-supported versions are not instrumented by accident?

Author's Checklist

[x] manual testing without agent
[x] manual testing with elastic agent

:broken_heart: Build Failed

Expand to view the summary

Build stats

Build Cause: [Pull request #1165 opened]

Start Time: 2020-04-29T16:16:50.877+0000

Duration: 8 min 10 sec (489560)

Commit: eb3c70a8e4fddb8866dfaa532122356688bbd094

Steps errors
Expand to view the steps failures

Name: Shell Script

Description:

Result: FAILURE

Duration: 2 min 24 sec<

Start Time: 2020-04-29T16:22:26.001+0000

Log output
Expand to view the last 100 lines of log output

[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:apm-jedis-2-tests ................... SUCCESS [  0.796 s]
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:apm-jedis-3-tests ................... SUCCESS [  0.557 s]
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:apm-lettuce-3-tests ................. SUCCESS [  1.000 s]
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:apm-grpc-test-1.6.1 ................. FAILURE [  3.372 s]
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:apm-grpc-test-latest ................ SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:apm-opentracing ..................... SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:integration-tests ................... SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:simple-webapp ....................... SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:jsf-app ............................. SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:jsf-app-dependent ................... SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:jsf-app-standalone .................. SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:cdi-app ............................. SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:cdi-app-dependent ................... SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:cdi-app-standalone .................. SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:soap-test ........................... SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:apm-agent-attach .................... SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:application-server-integration-tests  SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:spring-boot-1-5 ..................... SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:spring-boot-2 ....................... SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:spring-boot-2-base .................. SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:spring-boot-2-jetty ................. SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:spring-boot-2-tomcat ................ SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] co.elastic.apm:spring-boot-2-undertow .............. SKIPPED
[2020-04-29T16:24:50.345Z] [INFO] ------------------------------------------------------------------------
[2020-04-29T16:24:50.345Z] [INFO] BUILD FAILURE
[2020-04-29T16:24:50.345Z] [INFO] ------------------------------------------------------------------------
[2020-04-29T16:24:50.345Z] [INFO] Total time: 02:21 min
[2020-04-29T16:24:50.345Z] [INFO] Finished at: 2020-04-29T16:24:49Z
[2020-04-29T16:24:50.345Z] [INFO] Final Memory: 114M/387M
[2020-04-29T16:24:50.345Z] [INFO] ------------------------------------------------------------------------
[2020-04-29T16:24:50.345Z] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single (default) on project apm-grpc-test-1.6.1: Execution default of goal org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single: java.lang.ExceptionInInitializerError: null
[2020-04-29T16:24:50.346Z] [ERROR] -----------------------------------------------------
[2020-04-29T16:24:50.346Z] [ERROR] realm =    plugin>org.apache.maven.plugins:maven-assembly-plugin:2.5.5
[2020-04-29T16:24:50.346Z] [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[2020-04-29T16:24:50.346Z] [ERROR] urls[0] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/apache/maven/plugins/maven-assembly-plugin/2.5.5/maven-assembly-plugin-2.5.5.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[1] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[2] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/slf4j/jcl-over-slf4j/1.5.6/jcl-over-slf4j-1.5.6.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[3] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/apache/maven/reporting/maven-reporting-api/2.2.1/maven-reporting-api-2.2.1.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[4] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/apache/maven/doxia/doxia-sink-api/1.1/doxia-sink-api-1.1.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[5] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/apache/maven/doxia/doxia-logging-api/1.1/doxia-logging-api-1.1.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[6] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/junit/junit/3.8.1/junit-3.8.1.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[7] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/commons-cli/commons-cli/1.2/commons-cli-1.2.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[8] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-4/plexus-interactivity-api-1.0-alpha-4.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[9] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[10] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[11] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[12] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/apache/maven/shared/maven-common-artifact-filters/1.4/maven-common-artifact-filters-1.4.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[13] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/codehaus/plexus/plexus-interpolation/1.22/plexus-interpolation-1.22.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[14] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/codehaus/plexus/plexus-archiver/2.10.2/plexus-archiver-2.10.2.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[15] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/apache/maven/shared/file-management/1.1/file-management-1.1.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[16] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[17] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/commons-io/commons-io/2.2/commons-io-2.2.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[18] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/apache/maven/shared/maven-filtering/1.3/maven-filtering-1.3.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[19] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/apache/maven/shared/maven-shared-utils/0.6/maven-shared-utils-0.6.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[20] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/com/google/code/findbugs/jsr305/2.0.1/jsr305-2.0.1.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[21] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/sonatype/plexus/plexus-build-api/0.0.4/plexus-build-api-0.0.4.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[22] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/codehaus/plexus/plexus-io/2.6/plexus-io-2.6.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[23] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.jar
[2020-04-29T16:24:50.346Z] [ERROR] urls[24] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/codehaus/plexus/plexus-utils/3.0.21/plexus-utils-3.0.21.jar
[2020-04-29T16:24:50.347Z] [ERROR] urls[25] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/org/apache/maven/shared/maven-repository-builder/1.0/maven-repository-builder-1.0.jar
[2020-04-29T16:24:50.347Z] [ERROR] urls[26] = file:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165/src/github.com/elastic/apm-agent-java/.m2/commons-codec/commons-codec/1.6/commons-codec-1.6.jar
[2020-04-29T16:24:50.347Z] [ERROR] Number of foreign imports: 1
[2020-04-29T16:24:50.347Z] [ERROR] import: Entry[import  from realm ClassRealm[project>co.elastic.apm:apm-grpc:1.15.1-SNAPSHOT, parent: ClassRealm[maven.api, parent: null]]]
[2020-04-29T16:24:50.347Z] [ERROR]
[2020-04-29T16:24:50.347Z] [ERROR] -----------------------------------------------------
[2020-04-29T16:24:50.347Z] [ERROR] -> [Help 1]
[2020-04-29T16:24:50.347Z] [ERROR]
[2020-04-29T16:24:50.347Z] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[2020-04-29T16:24:50.347Z] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[2020-04-29T16:24:50.347Z] [ERROR]
[2020-04-29T16:24:50.347Z] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[2020-04-29T16:24:50.347Z] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
[2020-04-29T16:24:50.347Z] [ERROR]
[2020-04-29T16:24:50.347Z] [ERROR] After correcting the problems, you can resume the build with the command
[2020-04-29T16:24:50.347Z] [ERROR]   mvn <goals> -rf :apm-grpc-test-1.6.1
[2020-04-29T16:24:52.886Z] Stage "Tests" skipped due to earlier failure(s)
[2020-04-29T16:24:53.118Z] Stage "Unit Tests" skipped due to earlier failure(s)
[2020-04-29T16:24:53.131Z] Stage "Smoke Tests 01" skipped due to earlier failure(s)
[2020-04-29T16:24:53.144Z] Stage "Smoke Tests 02" skipped due to earlier failure(s)
[2020-04-29T16:24:53.155Z] Stage "Benchmarks" skipped due to earlier failure(s)
[2020-04-29T16:24:53.167Z] Stage "Javadoc" skipped due to earlier failure(s)
[2020-04-29T16:24:53.378Z] Failed in branch Unit Tests
[2020-04-29T16:24:53.386Z] Failed in branch Smoke Tests 01
[2020-04-29T16:24:53.395Z] Failed in branch Smoke Tests 02
[2020-04-29T16:24:53.403Z] Failed in branch Benchmarks
[2020-04-29T16:24:53.412Z] Failed in branch Javadoc
[2020-04-29T16:24:54.712Z] Stage "Integration Tests" skipped due to earlier failure(s)
[2020-04-29T16:24:54.833Z] Stage "AfterRelease" skipped due to earlier failure(s)
[2020-04-29T16:24:54.887Z] Stage "AfterRelease" skipped due to earlier failure(s)
[2020-04-29T16:24:55.001Z] Stage "AfterRelease" skipped due to earlier failure(s)
[2020-04-29T16:24:57.711Z] Running on Jenkins in /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1165
[2020-04-29T16:24:58.575Z] [INFO] getVaultSecret: Getting secrets
[2020-04-29T16:24:58.641Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2020-04-29T16:25:00.709Z] + chmod 755 generate-build-data.sh
[2020-04-29T16:25:00.709Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1165/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1165/runs/1 FAILURE 489560
[2020-04-29T16:25:01.260Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1165/runs/1/steps/?limit=10000 -o steps-info.json
[2020-04-29T16:25:01.811Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1165/runs/1/tests/?status=FAILED -o tests-errors.json
[2020-04-29T16:25:01.811Z] jq: error (at tests-errors.json:4): Cannot index string with string "_links"
[2020-04-29T16:25:01.811Z] jq: error (at tests-errors.json:4): Cannot index string with string "_class"
[2020-04-29T16:25:01.811Z] jq: error (at tests-errors.json:4): Cannot index string with string "state"

Codecov Report

Merging #1165 into master will increase coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1165      +/-   ##
============================================
+ Coverage     59.40%   59.44%   +0.03%
- Complexity       85     2869    +2784
============================================
  Files           330      330
  Lines         15010    15010
  Branches       2086     2086
============================================
+ Hits           8917     8923       +6
+ Misses         5482     5480       -2
+ Partials        611      607       -4

Impacted Files
Coverage Δ
Complexity Δ

...m/agent/profiler/collections/Long2LongHashMap.java
21.00% <0.00%> (+0.62%)
18.00% <0.00%> (+18.00%)

...o/elastic/apm/agent/profiler/SamplingProfiler.java
78.77% <0.00%> (+1.11%)
48.00% <0.00%> (+48.00%)

Continue to review full report at Codecov.

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


[W5.7][F11-3]Vignesh Shankar

Features

delete now accepts a variable number of indices to delete users

My bad 😓


add arduino as decent language to prism.js

This will add highlighting for arduino files (*.ino) as extension of c++.

Merged! Thank you for contributing!


Update README to account for function name change

validate.lassosum.pipeline is now called validate and pseudovalidate.lassosum.pipeline is now called pseudovalidate

Thanks Sam, I've updated the README


Drop "workgroup" marker.

The "workgroup" marker has a really long lifetime in IREEs compilation
stack. It is produced by the dispatch region formation and is consumed
all the way during executable translation. THere is also some
weirdness about when the tiling patterns trigger. This was relevant
when not all ops were tiled and distributed. Since this isnt the case
any more, the "workgroup" marker can be dropped.
Fixes #5045

Depends on https://reviews.llvm.org/D113057 but is ready for review


Tidy up the docker files and documentation slightly

Main change is removing ENV statements and instead relying on the default
locations for relevant files. We have default values for the locations
of config and logging files, it makes sense for docker to use these also.

This also allows us to have the logging and config in separate directories
while using Docker.

Adds the -p argument to the docker README code sections as this is
almost certainly going to be needed by anyone deploying this.

Also makes the README fit 80 character terminals.

Hi @KitL. Faucet's default for logs and configs are /var/log/ryu/faucet and /etc/ryu/faucet, respectively. I note you dropped the ryu part, with /etc/opt/faucet/ and /var/log/faucet/ in the Dockerfiles. This is not a major problem, but it might be nice to have consistency. Should we change the defaults in faucet.py?

No, we should change the docker files.
Sorry that was a subtle merge collision I missed.
On 27 May 2016 at 23:18, Simeon Miteff<EMAIL_ADDRESS>wrote:

Hi @KitL https://github.com/KitL. Faucet's default for logs and configs
are /var/log/ryu/faucet and /etc/ryu/faucet, respectively. I note you
dropped the ryu part, with /etc/opt/faucet/ and /var/log/faucet/ in the
Dockerfiles. This is not a major problem, but it might be nice to have
consistency. Should we change the defaults in faucet.py?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/REANNZ/faucet/pull/90#issuecomment-222122137, or mute
the thread
https://github.com/notifications/unsubscribe/AB48FeRWWL3otb0_rTzPeEGZ8n_LEpYtks5qFtLrgaJpZM4InLfd
.


Add a ReferenceCopyLocalOutputGroup

Fixes #3069.
There are a number of places where we need to get the set of items produced by a project's references and needed for packaging purposes or just running the code on the target platform. These may well be different from the reference passed to the compiler (e.g., a NuGet package may have a single ref assembly for compiling but multiple lib assemblies for different runtimes) and may not be code at all (e.g. PDBs or resource assemblies). As noted in #3069 a number of individual project types have implemented their own targets to collect this information, with varying levels of correctness.
This change adds a new ReferenceCopyLocalPathsOutputGroup to Microsoft.Common.CurrentVersion.targets to make this functionality centrally available to anyone who needs it. It also does some refactoring to make it a little easier to extend the other output groups.

LGTM.

@rainersigwald @cdmihai Do you know if bits with this change have made it into the VS repo?

It should be in lab/d15.8stg, I think. If not, https://devdiv.visualstudio.com/DevDiv/MSBuild/_git/VS/pullrequest/123194 should get it into rel/d15.8 if I'm reading commit history right.


Failed to set up owlet connection - V2 Sock with version 2024.3.1

When I tried to use the integration (v 2024.3.1), it says it failed to set up:

Here is the log:
ERROR (MainThread) [homeassistant.config_entries] Error setting up entry<EMAIL_ADDRESS>for owlet
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 390, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/owlet/__init__.py", line 75, in async_setup_entry
    socks = {
            ^
  File "/config/custom_components/owlet/__init__.py", line 76, in
    device["device"]["dsn"]: Sock(owlet_api, device["device"])
                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/pyowletapi/sock.py", line 84, in __init__
    self._manuf_model = data["manuf_model"]
                        ~~~~^^^^^^^^^^^^^^^
KeyError: 'manuf_model'

First I thought that was because I have a V2 Sock, but I saw that you added support in #8 (v  2023.11.2).

I updated to the new release and got a different error.
When initializing, either the old integration, or by creating a new one from scratch, it logs this:
2024-07-09 01:23:58.384 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform owlet.binary_sensor: Platform not found (cannot import name 'DeviceInfo' from 'homeassistant.helpers.device_registry' (/usr/src/homeassistant/homeassistant/helpers/device_registry.py)).
2024-07-09 01:23:58.388 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform owlet.sensor: Platform not found (cannot import name 'DeviceInfo' from 'homeassistant.helpers.device_registry' (/usr/src/homeassistant/homeassistant/helpers/device_registry.py)).

Whenever I tried to reload the integration, it logs this:
2024-07-09 01:26:48.639 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry<EMAIL_ADDRESS>for binary_sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 546, in async_unload
    result = await component.async_unload_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/binary_sensor/__init__.py", line 175, in async_unload_entry
    return await component.async_unload_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 202, in async_unload_entry
    raise ValueError("Config entry was never loaded!")
ValueError: Config entry was never loaded!
2024-07-09 01:26:48.642 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry<EMAIL_ADDRESS>for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 546, in async_unload
    result = await component.async_unload_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 137, in async_unload_entry
    return await component.async_unload_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 202, in async_unload_entry
    raise ValueError("Config entry was never loaded!")
ValueError: Config entry was never loaded!

I updated to the new release and got a different error.
When initializing, either the old integration, or by creating a new one from scratch, it logs this:
2024-07-09 01:23:58.384 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform owlet.binary_sensor: Platform not found (cannot import name 'DeviceInfo' from 'homeassistant.helpers.device_registry' (/usr/src/homeassistant/homeassistant/helpers/device_registry.py)).
2024-07-09 01:23:58.388 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform owlet.sensor: Platform not found (cannot import name 'DeviceInfo' from 'homeassistant.helpers.device_registry' (/usr/src/homeassistant/homeassistant/helpers/device_registry.py)).

Whenever I tried to reload the integration, it logs this:
2024-07-09 01:26:48.639 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry<EMAIL_ADDRESS>for binary_sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 546, in async_unload
    result = await component.async_unload_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/binary_sensor/__init__.py", line 175, in async_unload_entry
    return await component.async_unload_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 202, in async_unload_entry
    raise ValueError("Config entry was never loaded!")
ValueError: Config entry was never loaded!
2024-07-09 01:26:48.642 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry<EMAIL_ADDRESS>for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 546, in async_unload
    result = await component.async_unload_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 137, in async_unload_entry
    return await component.async_unload_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 202, in async_unload_entry
    raise ValueError("Config entry was never loaded!")
ValueError: Config entry was never loaded!

This happens when you are running an old version of home assistant. There was a change around 8 months ago that moved the DeviceInfo class. If you update your home assistant install to either the latest 2024.7.1 or even 2024.1 onwards should resolve this.

This happens when you are running an old version of home assistant. There was a change around 8 months ago that moved the DeviceInfo class. If you update your home assistant install to either the latest 2024.7.1 or even 2024.1 onwards should resolve this.


Update to WorldGuard 7 and Bukkit 1.13

I'm hoping you can make use of some of this, though you may want to wait until the WorldGuard API stabilizes.
People were asking about 1.13 support and I need it for my own server so I'll be using this for now.

Oh well, those API changes are going to break compatibility with older versions.

They definitely are, but I don’t think there’s a way around that unless you convert to a multi-module project or use reflection.
I bumped the major version of the plugin, I think you’d have to just offer up both and be clear about which version works with what WorldGuard.
This is pretty much how it’s going to be for most plugins on 1.13, backwards compatibility is really difficult,

I also don't recommend going to ask the WorldGuard team why they couldn't make a consistent API between two major versions of their plugin. I'd post the response I got here but it contains some inappropriate language 😬

I don't mind them changing it and improving it as they like, It's always bumper when it becomes harder to maintain for multiple versions.

Managed to fully update to WG 7 and still support old WG 6 with some reflection and doing some hacky stuff, haha

Nice! I was able to do that for my own plugin but honestly didn't know if you'd want such a hacky solution here :)
Thank you!

It kinda debends how clean it looks, I managed to make it not too confusing in my opinion. Tho the reflection is kinda ugly but at least there is very little


Bring back mount

Fixes https://github.com/carllerche/nix-rust/issues/85

(Rebased)

Hmmm... it doesn't seem to pass CI. Unsure why.

Nightly I think is some nightly weirdness. 1.1.0 is because the test is using Result::expect(), which was added in 1.4.0. I'll update it to use unwrap() or unwrap_or_else() given the desire to test on 1.3.0.

@carllerche I've bashed Travis into submission*. Please check the test to see if what's going on makes sense. Thanks!

well, Travis forced me to disable one of the tests in CI, but we'll make do.

Instead of re-implementing the test runner, is it possible to use Once (call once) construct to do initialization?

Sadly not. The unshare call must happen before any threads are spawned. The built-in runner does not have any way to get code to run before that.

Other alternatives involve doing weird things with fork / exec and exit statuses to communicate success or failure to the runner.

@carllerche ping for comments on the test runner

I'll merge this soon, leaving the "test runner" as is. I filed https://github.com/carllerche/nix-rust/issues/248 to track its improvement.


Lights

Ambient light
Directional
Point/Sphere light ( attExp, inner and outer radius )
Spotlight ( attExp, inner and outer radius )

Hooray!!


Min height or combination of line-height and padding to build button and similar components

Draft
While working with our new sizing we looked into how our buttons was built. Today we use min height to set the height of our buttons.

Min-height
pros:

Simple solution with good control over the height of our button and other similar components.

Cons:

No padding if the button have to much text and breaks down into two or more lines on small screens.

You could argue that this is something that should never happen, and we shouldent make a component that support this.

Design systems that use min-height: (as I understand the code 😅)
designsystem.dk
Punkt (Height)
Jøkul (Height)
Combination of line-height and padding
pros

(maybe) Better controll of the relation between text and spacing. Can be sure that all spacing is within 4x (4-gangen)

Cons:

We need to use pixels in Figma to overwrite the line-height

This will give us a much more complicated typography system

If we are going to get the height we want on our buttons we need to use spacing that is not in our scale (10px for instance) How are we going to solve this?

Too make this work I think we would need to have sizes corresponds with 4x. This will probably make it so that we have a bigger difference between the sizes... Maybe.

Design systems that use this method: (as I understand the code 😅)
Aksel
designsystem.arbetsformedlingen.se
Gov.uk
### Tasks
- [ ] https://github.com/digdir/designsystemet/issues/1726
- [x] Consider to use only line-height to make the height of the components correct (remove min-height?)

Im a little lost on what we discussed last time, but couldent this work? 1.5 rem lineheight on all button components and ramp up padding and text size. If the size of line-height is not based on the text size within the button. @Thuneer

We use a combination of min-height, line-height and padding to build our button component.


Save Sepolia ETH

Currently, we are using sETH to:

[ ] top-up bots on Fairground (cron),
[ ] top-up bots on Devnet (cron),
[ ] self-delegate on Devnet (network restart),
[ ] self-delegate on Devnet (cron: validator join&leave),
[ ] generate Ethereum events on Sandbox (cron)

Each action uses a small amount (0.01-0.1) of sETH each time, which is not bad.
But from time to time, gas prices on Sepolia jump rapidly, and single action can cost a couple of sETH at once.
We need to save sETH, cos we don't have a source to get more.
I initially thought to modify the code to abort action/pipeline when the gas price is above a certain threshold.

no longer needed


Including Windows.h breaks the level enum.

Since Windows.h has a #define ERROR 0 in the wingdi.h file, the enum has to be changed in order to resolve the conflict.

Fixed in the newest version!


Installation instructions - improvements

I tried following the installation instructions but it did not work: the go install... commands threw errors. I unfortunately do not have the stack trace on hand, sorry. I managed to get it to work by doing go get instead of go install (which I realize might be evident for someone familiar with go).
I would suggest to add this last step to the instructions:
cp -rpi ~/go/terraform-provider-proxmox* ~/.terraform.d/plugins/linux_amd64/

I wrote a little bootstrap which do

@sticky-note docs/terraforminit.md mentions this

docs/terraforminit.md no longer exists
the go get ... commands fail (command and output listed below)
this might be obsolete by https://github.com/Telmate/terraform-provider-proxmox/issues/227#issuecomment-722763472

$ go get github.com/Telmate/terraform-provider-proxmox/cmd/terraform-provider-proxmox
package github.com/vmihailenco/msgpack/codes: cannot find package "github.com/vmihailenco/msgpack/codes" in any of:
        /usr/lib/go-1.10/src/github.com/vmihailenco/msgpack/codes (from $GOROOT)
        /home/user/go/src/github.com/vmihailenco/msgpack/codes (from $GOPATH)
package github.com/hashicorp/hcl/v2: cannot find package "github.com/hashicorp/hcl/v2" in any of:
        /usr/lib/go-1.10/src/github.com/hashicorp/hcl/v2 (from $GOROOT)
        /home/user/go/src/github.com/hashicorp/hcl/v2 (from $GOPATH)
package github.com/hashicorp/hcl/v2/hclsyntax: cannot find package "github.com/hashicorp/hcl/v2/hclsyntax" in any of:
        /usr/lib/go-1.10/src/github.com/hashicorp/hcl/v2/hclsyntax (from $GOROOT)
        /home/user/go/src/github.com/hashicorp/hcl/v2/hclsyntax (from $GOPATH)

$ go get github.com/Telmate/terraform-provider-proxmox/cmd/terraform-provisioner-proxmox
package github.com/Telmate/terraform-provider-proxmox/cmd/terraform-provisioner-proxmox: cannot find package "github.com/Telmate/terraform-provider-proxmox/cmd/terraform-provisioner-proxmox" in any of:
        /usr/lib/go-1.10/src/github.com/Telmate/terraform-provider-proxmox/cmd/terraform-provisioner-proxmox (from $GOROOT)
        /home/user/go/src/github.com/Telmate/terraform-provider-proxmox/cmd/terraform-provisioner-proxmox (from $GOPATH)

go get commands run on an Ubuntu 18.04 box with golang installed via apt.


fix(deps): update dependency @types/node to v18

This PR contains the following updates:

Package
Type
Update
Change
Pending

@types/node (source)
dependencies
major
^16.18.25 -> ^18.0.0
18.17.9 (+3)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Thanks for the PR!
Any successful deployments (not always required) will be available below.
Frontend available
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: frontend/package-lock.json

This can't be updated before node itself.  Closing.

 You will not get PRs for any future 18.x releases. But if you manually upgrade to 18.x then Renovate will re-enable minor and patch updates automatically.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

Correction.  Our builder is using Node 20.  This dependency update brings us closer to lining up versions.


Request to modify the OIDC plug in documentation

Okta configuration by default send openid scope under the claim label scp. By default in the plug the label is set to 'scope' and therefore developers have to spend time trying to figure out why the default scopes are not being passed. This documentation correct aims to reduce the friction for developers.
Summary
I followed the documentation but I was still facing a problem with required scopes not being passed.
Reason
As a developer I had to struggle a bit to understand where the problem was and why I was getting scope errors despite following the documentation
Testing
Re-did the steps of setting up a Okta developer account from scratch and tested the plugin with the correct labels for claim.

review:copyedit: Request for writer review.
review:tech: Request for technical review from an SME.

@rajeevkong Thanks for opening this PR! I wanted to make some additional changes to this file but couldn't push to your branch due to branch permissions. I've opened up a new PR (#4590 ) with those changes, which I'll tag you on, and close out this PR in the meantime.


Add config option for the kourend library region check

This will allow the user to return the previous behavior of the plugin to keep the sidepanel always active.
Fixes  #3929

Fixed in #3934


Difference between runnable and supplier

Would the difference between runnable and supplier be that runnable is just some function that gets executed when called, with no output, whereas supplier outputs the executed function's output?

I guess so, since runnable accepts nothing and returns nothing(void) since its only abstract method run accepts nothing and returns void.

Supplier => () -> returns T (must return a thing)
Runnable => () -> void (like System.ou.println) doesn't return anything

Runnable does not return anything. Supplier has a return value

Thanks everyone for the responses! I have a better idea of what runnable and supplier does now!


IdToken Lookup Uses Faster Cache API to Avoid Extra Decryption

Moves idtoken lookup over to newer lookup api to avoid hitting cache multiple times (1x per tenant) when an account exists in multiple tenants
Builds on:

New cache API to avoid repeat decryption
Test fixes

Oddly, I cannot merge this PR despite 3 approvals....

@iamgusain Do you know why this PR cannot be merged? From looking at our code owner enforcement rules, this appears to be acceptable....

Dismissing prior reviews because I may have gone too crazy in these latest changes 😆

Have backed out the more questionable changes from this PR and clarified log tags... rerequesting reviews

As you are touching the "cache" area, It needs signoff from code owners for cache..  you and Shane at the moment.
And it doesnt allow you to signoff your own PR.

In reply to: 844639652

As you are touching the "cache" area, It needs signoff from code owners for cache.. you and Shane at the moment.
And it doesnt allow you to signoff your own PR.
In reply to: 844639652

@iamgusain I am going to add you as a codeowner then, because in this state I can't merge


Resolve Legacy Python and SQS Endpoint Issues

Issue #, if available:
Description of changes:
Firstly, I wanted to thank you for making this example. It works super well and has been a pleasure to work with. I had to make some changes to it to bring it up to the current requirements for lambda and SQS, but otherwise it functions as expected.

Updated the README to provide information about your local Python version needing to match that of the AWS Lambda Python runtime to be used. The issue is detailed here and here. The PyMuPDFlike library is platform and version specific, so compiling with another version locally than the destination python runtime will result in dependency errors.
The legacy SQS endpoint is no longer accessible within the lambda's VPC without private DNS, and attempting to use it results in the lambda failing to write the message to SQS for the next step in the process. This has been updated to use the currently accepted and required SQS endpoint, which results in successful message delivery.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Going to tag you @mvonlanthen on this as you were the original author

Going to tag you @mvonlanthen on this as you were the original author

Hey @austinpilz! Saw this PR and the associated README change. Even with swapping everything to python3.8 and creating the venv from 3.8, still receiving
Runtime.ImportModuleError: Unable to import module 'main': cannot import name '_extra' from partially initialized module 'pymupdf' (most likely due to a circular import) (/opt/python/lib/python3.8/site-packages/pymupdf/__init__.py)
Wondering if you were encountering this too!


Should List V2 handle the case where there is no selectable row, but List is multiselectable?

https://github.com/scaleway/scaleway-ui/blob/77bf1b6b43441daa4b6843ee11cfe9989e9b7fa9/packages/ui/src/components/ListV2/ListHeaderRow.tsx#L84
For now, whenever all rows are selectable=false (so will be disabled), the checkbox in the header to select / unselect all is not disabled (or hidden). Maybe it would be better if it was?

@fabienhebert What do you think of this issue? Do we have a way for the list to get if all rows are disabled and so disabled the all select checkbox?

It should probably be hidden indeed, I guess it can be handled


Documentation needed on valid values for various az commands

Describe the bug
Command Name
az billing period show
Errors:
argument --name/-n: expected one argument

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

az billing period show --name

Expected Behavior
Environment Summary
Windows-10-10.0.14393-SP0
Python 3.10.4
Installer: MSI

azure-cli 2.37.0

Extensions:
account 0.2.3
azure-devops 0.18.0
azure-iot 0.12.1

Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.1.0b1

Additional Context
In this command, there is no documentation that shows where I can get the values for the "name" parameter.  I tried using the "az billing period list" and it gave me empty list.  I have logged in to Azure and set the subscription as well because I am able to get all the key vaults in the same powershell window.
Similar issue exists (on missing documentation) for many other commands and arguments as well.

route to CXP team

@srikcgaa2 Thanks for reaching out to us and reporting this issue. We are looking into this issue and we will provide an update.

@srikcgaa2 az billing period show and az billing period list commands are only supported for Azure Web-Direct subscriptions. Other subscription types which were not purchased directly through the Azure web portal are not supported through this preview API. More Info here.
I was able to run the command and get the available period list name:
az billing period list

{
"billingPeriodEndDate": "2022-07-31",
"billingPeriodStartDate": "2022-07-01",
"id": "/subscriptions/b83c1ed3-c5b6-44fb-b5ba-2b83a074c23f/providers/Microsoft.Billing/billingPeriods/202209-1",
"invoiceIds": null,
"name": "202209-1",
"type": "Microsoft.Billing/BillingPeriods"
}

I used the above name to fetch my named billing period as shown below:
az billing period show -n 202209-01
I will create a PR to improvise our documentation. Hope this helps.

@srikcgaa2 I wanted to do quick follow-up to check if you had a chance to look at my above comment. Please let us know if you need any further assistance on this. Awaiting your reply.


Change 'checked' property of checkbox element

Not sure if I'm missing something here, but it seems to me that when changing the state (clicking) of a switch the checked property of the underlying input element's checked property remains unchanged.
Having the checked property reflect the state of the switch seems like an essential feature to me since I would assume that most developers would prefer not to have to change the way they treat their checkbox input elements when applying this plugin.
I'd be more than happy to make a PR for this if we can reach a consensus.

:+1: !!

Yes I found this also and currently I use this simple code to propagate the changes to the dom element.
I give all checkboxes a class named 'switch' then use this simple js code:
	$(".switch").bootstrapSwitch().on('switchChange.bootstrapSwitch', function(event, state) {
		$(this).trigger("change");
	})

this is a MUST feature that should be implemented and I'd recommend removing the namespace added to the methods.
I'd also passing adding the events handlers in the same way as jquery slider works as options. It should be compatible with the jquery slider.

the issue does not occur. you retrieve correct value using .prop("checked") as you should.

does it clarify your doubts?

What I mean myself the change property of the DOM element does not fire. I do not want to change my code to listen to the plugin, why would everyone to change the firing of the checkbox to code like this:
$(id or class).bootstrapSwitch().on('switchChange.bootstrapSwitch', ....

why not fire the default checkbox 'change' event.

I have the same issue. This is my initialization code:
var $checkbox = $('[type="checkbox"]');
$checkbox.bootstrapSwitch({
    onColor: 'success',
    onSwitchChange: function(value) {
        console.log($(value.currentTarget).prop('checked'));
     }
 });
 $checkbox.on('change', function() {
     console.log($(this).is(':checked'));
     console.log($(this).prop('checked'));
 });

In the onSwitchChange() function state of checkbox is correct. But original change event of checkbox is not triggering.

This missing important feature forced me to switch to another nice plugin also:
http://www.bootstraptoggle.com/

Hmm.. Well bootstrap toggle does NOT seem to work on an iPhone though (e.g. iOS Safari).

Too bad either, I have not tested on iPhone, you may tell the author about it. I liked it because it occupy small area almost half of all others with the same functionality.

@juriejan Do you have time to built in this feature? :smile: It is indeed invaluable.
This switch control looks pretty nice, and I myself want to use this switch control in Knockout using the checked binding that is available for HTML checkboxes. If this plugin does not reflect changes back to the original checkbox element this is not possible.

:+1: Not sure why the state of the switch wouldn't be aligned with the underlying checkbox element. Also, triggering the change event on the element is a must. I would think these features would be the foundation of such a plugin. Weird.

the switchChange custom event is independent by the checkbox change, which is not triggered since it is used as event receiver. this paradigm is based on code of version <= 3, therefore must be updated.
the checkbox change event has not to be called internally and instead free to be listened for external use.
the update is quite broad and affects many parts of the plugin.

@LostCrew, sorry, but your explanation a little confused me. Your plugin is wrapped default checkbox, but not used default change event, so developer's code should implement change event listening.

@joni-jones apologise for the confusing explanation.
what i meant is exactly what you said. the checkbox change event has not to be used internally like now.

In the process of getting back into this issue, I've realised that the behaviour that initiated the creation of this seems to be related more to the standard Checkbox HTML element than anything else.
With the latest version (3.3.2) I can get the appropriate value of the checkbox using all of the following commands:
$('input[name=active]').is(':checked')
$('input[name=active]').prop('checked')
$('input[name=active]')[0].checked

I even get the appropriate value when using the $.serializeArray method (even though unchecked returns no value, which is expected) (see jquery.serializeJSON plugin for better collection of form data).
It seems to be however that what initially cause my to raise this issue is that neither the Firefox or Chrome HTML inspectors remove or add the checked property when a checkbox is toggled. This led me to believe that the input element in the DOM was not being altered.
In terms of the change event it seems to me that the event is only triggered when the element is actually clicked. When changing the value using code I think the only way for it to be triggered would be manually. I'll submit a very simple pull request to this effect.

@juriejan thanks for the PR.
A week ago I added the feature that allows users to prevent the change of a switch once it is clicked.
Can you check that this code works?
Can you test this feature?

Returning false on a function set using the onSwitchChange option prevents the switch from changing as intended.
The standard change event is still not triggered when the switch is changed. Not sure how the feature relates to this issue.

Closing this issue as I'm no longer using this library and the attached PR has been awaiting feedback  for too long.


Change references from notifywait_win32 to inotifywait_win32

The library you are depending on seems to have changed its name and has prepended the "i". This minor adjustment makes the library work for Windows without any further changes.

Thank you! I have released v0.0.3.

You are welcome. :) Thanks for creating this in the first place.

I was actually using the exsync library which I see also comes from your profile. It depends on version 0.0.2 of this library. Is it necessary to bump its dependency on exfswatch to 0.0.3 and then bump the library's own version to 0.0.4 to make everything work out of the box, or is the current situation ok?

Version 0.0.X is difficult to maintain, so I release exfswatch v0.1.0 and exsync v0.1.0.
Maybe now everything works. :smile:


android.text.format.Time has been deprecated since API 22

Hi,
Class has been deprecated since API level 22 according to the document due to multiple problems.
I noticed the class is still used in MyRemoteViewData.java. As suggested by the document, replace this class with GregorianCalendar is safer implementation to avoid potential issues.
Hope the information could help.

@frankFic Thank you for noticing. By the way, source code of AndStatus is analysed periodically by the Sonar service:
https://sonarcloud.io/dashboard?id=andstatus
So I usually know about deprecated APIs.

GregorianCalendar is outdated already.
I will migrate this to java.time after switching to minimum API 26. Current API 24 doesn't have even constructor from UNIX milliseconds...


Breaks with the file:/// protocol

Nothing happens when the user clicks on the toolbar icon to toggle the inspector while viewing a page with the file:/// protocol.

The Inspector pane will open if the app is connected with a server, which can easily be done with SimpleHTTPServer if you don't want to write up any server side code.


Feat: Conditionally import NodeJS packages, thus making them work in webpack 5

This does not affect the current workflow in any way. With this change the package is fully compatible with Webkack 5 and thus Angular

Done. Remember to make changes to the Dev branch if possible


Show output folder for exported files

Added display of the output folder (because it's not at all obvious where it's going to end up, and if you close the window that auto-opens at end of process - it's gone! Also: Windows10 has a habit of not-repopening Explorer windows that were already open, making it hard to find the file with current design).
Also changes the success message to give the actual filename/location (previous version only gives a relative filepath, which can't be copy/pasted, can't be opened directly, etc)

I came here to add something like this, looks like adamgit beat me to it. I second this pull request.

It's been over a month, I'm guessing this project isn't maintained any more.
Sigh. Time to fork it.

We could try @hybridherbst Hey look over here!

Hey! Somehow I totally didn't see this. Will take a look, pinging was the right choice :)

Included in 0.6.0, sorry for the delay!


Clean metadata examples

Metadata examples needs cleaning up.

[x] Remove redundant comments
[ ] Remove restart_from (currently not used)
[x] Add file.size
[x] Add multi-level fmu.realization.parameters
[ ] Add table example
[ ] Remove data.properties? (Not used)
[ ] Remove data.grid_model (Not used)
[x] Remove realization.jobs (Not used)

Keep restart_from and grid_model - part of schema.