Trouble with double underscore and MySQL

Good day, well, this is kind of weird, I have been having trouble while working with variables with a double (or more) underscore "__" in my variable names.
For example, if I have a property like this:

It will not map the value of my tables/views while doing a QueryAsync, even with the header of ExplicitColumns, but, strangely enough, if I declare it like this:

The variable will get the values correctly.
This generates a problem for me, since I generate interfaces for my Angular and react projects where the property names are declared with the same name and (compatible) data type.
Another option would be to refactor my database to use pascal or camel case to name my columns, but that's just too much of a work around solution
BTW, I'm working with .Net 6

Well, it's been a week and there has been no update on this, and, I see issues with 1 month or older, sadly, I had to switch my ORM, my old project doesn't use this style of table and column naming, so, it wasn't a problem there. If in the future this gets corrected then I'll switch back (since I have a class generator and it's kinda easy to do...
Even with this, I do recommend sticking to this project, lightweight and easy to use with great performance


implement to_writer method and clean up RustCycle csv serde

adds a to_writer method

RustCycle just needs to override to_writer instead of to_file
Cleanup/reorg of SerdeAPI-alike functions in RustCycle (write_csv etc)
New RustCycle::to_csv function to be consistent with to_yaml etc, same functionality as RustCycle::to_str("csv") (which now calls RustCycle::to_csv)

All SerdeAPI errors are now exposed as IOError/OSError in Python rather than RuntimeError

I noticed the Python-exposed RustCycle::from_csv loads a cycle from a given filepath, rather than a string like from_yaml, from_json, etc. I think this is something that I would definitely want to change in FASTSim 3. @calbaker what are your thoughts about making all these string deserialization methods have _str at the end (starting in FASTSim 3, to avoid API changes)?
i.e. from_yaml would become from_yaml_str to make it clear that it takes a YAML-formatted string, rather than a filepath

@kylecarow , is this ready to merge?

@calbaker Left a comment for you to ponder, but this PR is ready to merge, yea


Use ApplicationExperience#experienceable

Context
Now that all ApplicationExperience records have experienceable columns populated we can use this column to link the ApplicationExperience to the ApplicationForm.
We still need to save the application_form_id on the application_experience because of the db constraint and we also need to set the experienceable value when when we call
application_experience.application_form=
Other commits will follow to remove the application_form_id
Changes proposed in this pull request
ApplicaitonExperience relation to ApplicationForm
Guidance to review
Pull locally or go on the review app and add/edit work experiences.
Things to check

[ ] If the code removes any existing feature flags, a data migration has also been added to delete the entry from the database
[x] This code does not rely on migrations in the same Pull Request
[ ] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[ ] If this code adds a column to the DB, decide whether it needs to be in analytics yml file or analytics blocklist
[ ] API release notes have been updated if necessary
[ ] If it adds a significant user-facing change, is it documented in the CHANGELOG?
[ ] Required environment variables have been updated added to the Azure KeyVault
[ ] Inform data insights team due to database changes
[x] Make sure all information from the Trello card is in here
[x] Rebased main
[x] Cleaned commit history
[x] Tested by running locally
[x] Add PR link to Trello card

 Edit work experiences - Change db structure to accommodate work experience edits


Offline auth state

Can this module also somehow be used in maintaining auth states for extended periods offline?

This module currently only supports database methods. Feel free to request auth features along with any implementation details/use cases you find important. Thank you!

When you do an auth request is should persist regardless of being disconnected. Problem is you cant guarantee it..


X Rebrand strings

Replacing most mentions of Tweet, Twitter, Retweets, Quote Tweets etc to the new language.
We're not updating the python code files or "under the hood" tables for now.

lgtm

Good point! Feel free to close. Appreciate the reply.
On Thu, Jul 27, 2023, 17:26 Lucas Neumann @.***> wrote:

@.**** commented on this pull request.
In README.md
https://github.com/twitter/communitynotes/pull/128#discussion_r1276837380
:

Here you can also find our research paper.
About Community Notes
-Community Notes aims to create a better informed world, by empowering people on Twitter to add helpful notes to Tweets that might be misleading.
+Community Notes aims to create a better informed world, by empowering people on X to add helpful notes to posts that might be misleading.
That is 4 days old! Things here move too fast now 😅
—
Reply to this email directly, view it on GitHub
https://github.com/twitter/communitynotes/pull/128#discussion_r1276837380,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZCZI2UK6RNJFRUFHH7SB3XSLMI7ANCNFSM6AAAAAA22LMED4
.
You are receiving this because you commented.Message ID:
@.***>


Normalization for Tabula Muris documentation dataset is off-by-one

Hi CZI folks,
First -- thanks for the great resources!
I was playing with the Tabula Muris anndata object linked in the cellxgene documentation and noticed the normalization was a little funny.
The lowest count value in the dataset appears to be 0.69...
adata.X.min() # 0.6931472, a.k.a. ln(2)

I think the error may have originated in this notebook:
https://github.com/chanzuckerberg/cellxgene-compbio-methods/blob/master/dataset-processing/tabula-muris-processing.ipynb
During normalization, it looks like 1 was added to all counts before using sc.pp.log1p, which also adds one before applying the log transformation.
Thanks again!
Jacob

Thanks for finding this, Jacob! I've removed the spurious duplication of += 1 during normalization.


Automated cherry pick of #7357: baremetal colloct isolated devices info

Cherry pick of #7357 on release/3.4.
#7357: baremetal colloct isolated devices info

/lgtm
/approve


Documentation update

Here's an attempt at creating some minimal documentation for the modules and functions of the library.
Please check it over and make suggestions.

Codecov Report

Merging #3 into main will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #3   +/-   ##
=======================================
  Coverage   96.00%   96.00%
=======================================
  Files           3        3
  Lines          25       25
=======================================
  Hits           24       24
  Misses          1        1

Impacted Files
Coverage Δ

lib/keyboard_layout.ex
95.65% <ø> (ø)

lib/keyboard_layout/key.ex
100.00% <ø> (ø)

lib/keyboard_layout/led.ex
100.00% <ø> (ø)

Continue to review full report at Codecov.

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


Implement % and auto sizing for point style

Refer the docs for details.

Introduced SizeValue as a StyleParam::Value
Explicit handling of size stop evaluation
Fix to take care of mixed dimension size stops

Explanation:
Since we no longer have a single "Unit" (pixels) for size style parameter, we can not simply encode size parameter values from style sheet in a vec2. We will need to have the unit specified for the size in the stylesheet.
We will also require cssSize and aspect ratio of the texture/sprite being used for the feature drawn using a point style. This means we can not pre-calculate stops as vec2 values before build the quad for the point being drawn, as cssSize and aspect ratio of the texture/sprites can only be determined by the style builders.
TODO:

[x] A bit more code cleanup
[x] Fix/add unit tests
[x] Remove JS function string value support for StyleParam::size as its not supported in TangramJS

Up for review now. I feel the StyleParam interface is being abused for a while now and has outgrown its initial design. Will start thinking on it for separate work, but not touching any of that for the purposes of sticking to the task of being parity with JS features.

Testing this feature has illuminated a more general problem with the way we're evaluating style parameters from JS functions in StyleContext: https://github.com/tangrams/tangram-es/blob/master/core/src/scene/styleContext.cpp#L355-L367
The logic here checks the type of the JS return value first, then based on that type, tries to assign it with the given style key. The problem here is in the duk_is_string block, where the default case calls the generic StyleParam::parseString function. Since any parameter can be parsed from a suitable string representation, this means that a JS function can return strings for any parameter and produce a successful output. For example, a point size can currently be specified as function() { return '32px'; } and you'll get a 32px point. It even works with the way that we stringify arrays: function() { return '32, 16'; } produces a 32px by 16px point. Clearly this isn't how the docs describe this parameter, and it's not how we meant it to work!
The obvious solution to try is to just remove the parseString from the default case. Unfortunately I am not sure whether any other parameters depend on this behavior, so we'll want to carefully check for any changes in styling when we remove it.

Addressed your comments/suggestions @matteblair.

Reviewing again now. @tallytalwar did you decide against giving SizeValue a default constructor?

@tallytalwar I took a while to understand the changes here and I think I've been able to simplify it a little. Take a look at the changes I just pushed and let me know if we should edit or revert.

Ok All good. If you can approve it then I will merge it.

Probably makes sense to squash some of these commits in here, I'll let you merge @tallytalwar


Error lexer in resouceUrlWhitelist

In my .config I have a white list like this:
$sceDelegateProvider.resourceUrlWhitelist([
        'self',
        'https://s3-eu-west-1.amazonaws.com/something/**'
    ]);

But this fire a lexerr error:
Error: [$parse:lexerr] Lexer Error: Unexpected next character  at columns 2-2...

Only if I remove "**" (two asteriks) works (but the url is blocked for $sce). My url is somthing like this:
https://s3-eu-west-1.amazonaws.com/something/img$002.jpg

My white list is very close to the angular docs example. I not sure if this is a error. Any idea?

Can you post where the error points to? Without the context it's hard to say what's wrong

Yes, sorry. This image is the complete message error.

The image is unfortunately hardly readable.
However, it looks like the image / its base64 representation is being parsed by angular. It's possible that /** is catching too much ...
However, since you are using Angular Foundation I would advice you to open an issue there, because I don't know what happens in their directives (interchange).

It's very odd (no image is served in base64) I have some other images with Foundation-interchange and all works fine except this one.
I'll try to ask Foundation forum.
Thanks anyway. (I attach the imagen again. Just in case...)

It is hard to investigate further without a reproduction. If you are still seeing this, please open a new issue providing a way to reproduct the error. Thx!


Differences in output between MacOS & Linux

The results of running jp-watch on Linux and MacOS are currently different. The differences are summarised below with the type of change and the resulting output per OS. Ideally the Linux version should produce output that is the same as the MacOS version which is more correct. Linux usually returns parent directories of changes instead of the actual changed files or directories:
FILE EDIT: echo '123' > <existing file>
Linux

<existing file>

MacOS

<existing file>

FILE CREATION: echo '' > <file>
Linux

Parent Directory: <parent dir>
File: <file> (should be just <file>)
Note: b contains FAN_CREATE (ignore the lone create event)
b2 contains FAN_MODIFY (return this only)

MacOS

<file>

DIRECTORY CREATION: mkdir <dir>
Linux

Parent Directory: <parent dir> (should be <dir>)
Note: b contains FAN_CREATE + FAN_ONDIR

MacOS

<dir>

FILE/DIRECTORY MOVE: mv <file> <dir> | mv <dir> <dir>
Linux

Parent Directory: <parent dir> (should be <file>)
Fix/Hack:

Three events will appear in b:

b contains FAN_MOVE (src parent path)
b contains FAN_MOVE (dst parent path)
b contains FAN_MOVE_SELF (the end of this path contains the name of the file moved)

Take the file name from FAN_MOVE_SELF and append it to both FAN_MOVE directory paths. Output only the FAN_MOVE directory paths with the appended filename.

MacOS

Destination: dst <dir/file>
Source: src <dir/file>

From the example code in https://www.man7.org/linux/man-pages/man7/fanotify.7.html we can see that by using the FAN_EVENT_INFO_TYPE_DFID_NAME option it may be possible to retrieve filenames in addition to parent directories.


Add "SuspendedAt" field to User struct.

There is "suspended_at" key in "/users/:username" response  when I use GitHub Enterprise. so I added "SuspendedAt" field to User struct same as CreatedAt & UpdatedAt.

cherry-picked as 6387a9448dec3a903271745e7baddd14e0ba90c9. thanks


Update landscaper version to v0.98.0

What this PR does / why we need it:
Update landscaper version to v0.98.0
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

- Update landscaper version to v0.98.0.

I have closed this PR because there was another one already switching LaaS on Landscaper 0.98.0


Use topaz CLI instead of developer commands

Replaced by https://github.com/aserto-dev/aserto/pull/60


Coverage Question!

Hello again!
I have a question regarding the coverage.
When I run the JQF, it is always started with almost the below values! and also it will be constant for the whole duration of the test!
Total coverage:       14,260 branches (21.76% of map)
Valid coverage:       14,260 branches (21.76% of map)
Remaining as a constant value could be made sense as it cannot go through more path in the app but I suppose it should not be started with these values!
Could you please explain why?

You can run mvn jqf:repro with the flag with -DlogCoverage=<file> to print the coverage achieved by some of the saved inputs.
My guess---if this coverage is always present for all inputs---is either from code that is run from your test method before the input is processed, or is run from static initializers of classes. The latter is common in app frameworks that initialize caches or something.

Oh ok, could it be because we have some functions with an annotation such as before,beforeclass in our test? it means that they are run before reaching to JQF point?
But if this is the case why we cannot have more coverage than this?!  while the "cycles completed" will be increasing. Am I missing something?

I have run one input file from the corpus with mvn jqf:repro using the flag -DlogCoverage=, and the only path I can see are just related to the libraries as I could understand!

Oh ok, could it be because we have some functions with an annotation such as before,beforeclass in our test? it means that they are run before reaching to JQF point?

Yes, that's possible.

But if this is the case why we cannot have more coverage than this?! while the "cycles completed" will be increasing. Am I missing something?

I'm not sure. It looks like the coverage instrumentation is working for your program, so you need to debug whether there are any input-dependent control-flow branches or not in your test. I'm guessing you have had success with other tests or with the examples provided in the tutorials. Without seeing your particular test, I cannot say why there is no input-dependent coverage increase. My guess is either your test method is not executing new code based on changes to the input, or the changes to the input required for achieving new coverage are very difficult to achieve by random input generation (e.g. if (x.equals("FooBar")) is hard to cover with input x because JQF cannot magically construct the string "FooBar".

Thank you, I will try to find why it is like this.
Can I ask you to not close this issue, so I can ask my further questions in the same place? because these days I am just focusing on JQF to apply it on our app. also I am trying to understand everything about JQF.

Regarding the previous discussion, I want to confirm that the coverage instrumentation is working and there is no problem I suppose.
Now I have some questions regarding the outputs(mostly the information of input numbers). I want to check to be sure that I understood them.
I am using the numbers that I have gotten from a test in 50 minutes duration.

"valid inputs": 14,074 => this should be all the inputs that JQF used to test the application

corpus("queue size"): 98 => these are the most suitable inputs based on our application that cover a new path so they are used for applying mutation algorithm to create new inputs(mutated inputs)

but based on the "fuzz.log" file there are only 12 inputs that make to have a new branches coverage! So I suppose that corpus is not just considering new path coverage, yes? or do I missing something else?

"current parent input": 96--->0(after 40m) (I think for this one I need some explanation because I cannot see why it went back to zero!)

using flag "printArgs": I got just 19 inputs => unfortunately, I cannot see this number which is not matched with any results that I got.

At the end of the test: I had this message "Fuzzing resulted in the test failing on 1005 input(s)."==> this number is related to invalid inputs but I cannot see why we have it as long as we are using a generator for having valid syntactical inputs. Could you please tell me which kind of invalid things could happen?

in the "plot_data" file:
"paths_total" is exactly our queue size?

"unique_crashes" is our failures?
"unique_hangs": Can be generated by Zest or it is just for AFL? And I would like to know how I can have them in a different folder if I can get them by Zest?

Another point that does not make sense to me is that I used the "-DlogCoverage" flag for two different inputs from the corpus(the first one and input 80 because of the coverage information that I have in the log file as below)

# Cycle 1 completed.
Here is a list of favored inputs:
Input 0 is responsible for 14161 branches
Input 1 is responsible for 64 branches
Input 8 is responsible for 16 branches
Input 13 is responsible for 1 branches
Input 17 is responsible for 1 branches
Input 25 is responsible for 1 branches
Input 43 is responsible for 7 branches
Input 51 is responsible for 1 branches
Input 75 is responsible for 3 branches
Input 77 is responsible for 10 branches
Input 79 is responsible for 1 branches
Input 80 is responsible for 3 branches
Total 14269 branches covered

I expected to have different outputs as reaching input 80 give us more coverage(number of branches), but the two outputs are completely the same. Could you please tell me why?
Thank you in advance.

Regarding the previous discussion, I want to confirm that the coverage instrumentation is working and there is no problem I suppose.
Now I have some questions regarding the outputs(mostly the information of input numbers). I want to check to be sure that I understood them.
I am using the numbers that I have gotten from a test in 50 minutes duration.

"valid inputs": 53,612 => this should be all the inputs that JQF used to test the application

corpus("queue size"): 90 => these are the most suitable inputs based on our application that cover a new path so they are used for applying mutation algorithm to create new inputs(mutated inputs)

but based on the "fuzz.log" file there are only 12 inputs that make to have a new branches coverage! So I suppose that corpus is not just considering new path coverage, yes? or do I missing something else?

"current parent input": I think for this one I need some explanation because it is always changing!

"Cycles completed": what is this?

At the end of the test: I had this message "Fuzzing resulted in the test failing on 3577 input(s)."==> this number is related to invalid inputs but I cannot see why we have it as long as we are using a generator for having valid syntactical inputs. Could you please tell me which kind of invalid things could happen?

in the "plot_data" file:

"paths_total" is exactly the same number as our queue size! but why? I mean why the name is like this?!
"unique_crashes" is our failures?
"unique_hangs": Can be generated by Zest or it is just for AFL? And I would like to know how I can have them in a different folder if I can get them by Zest?
Thank you in advance.

I have another question regarding debugging.
In the last part of this link "Fuzzing a Compiler"  you mentioned that we could easily debug our test like JUnit test but actually applying @Fuzz will remove Run/Debug options, so how is that possible? (I am using vscode)

You could try tagging GitHub user @fuzz to see if he can debug it for you, but I hear he’s quite expensive.

On May 5, 2021, at 7:52 AM, pinkhat-m @.***> wrote:

I have another question regarding debugging.
In the last part of this link "Fuzzing a Compiler" you mentioned that we could easily debug our test like JUnit test but actually applying @fuzz will remove Run/Debug options, so how is that possible? (I am using vscode)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@pinkhat-m

"valid inputs": 53,612 => this should be all the inputs that JQF used to test the application

Correct. These are all inputs that resulted in the test method being executed and returning normally without exception.

corpus("queue size"): 90 => these are the most suitable inputs based on our application that cover a new path so they are used for applying mutation algorithm to create new inputs(mutated inputs)

Correct.

but based on the "fuzz.log" file there are only 12 inputs that make to have a new branches coverage! So I suppose that corpus is not just considering new path coverage, yes? or do I missing something else?

Correct. Zest borrows a heuristic from AFL where if the same code branch is executed a different binary-order-of-magnitude number of times, it is considered new coverage. This is used to distinguish inputs that execute a loop say 1 times, 2 times, 3-4 times, or 17-32 times, 513-1024 times, etc. all as different "coverage".  You can disable this by setting -Djqf.ei.DISABLE_SAVE_NEW_COUNTS=true.

"current parent input": I think for this one I need some explanation because it is always changing!

It's the ID of the input from the queue that is currently being mutated. It will always keep changing.

"Cycles completed": what is this? is it related to the queue? it means that in every cycle, all the inputs in a queue are tested?

Yes. In each cycle, all inputs in the queue have been mutated some number of times. At the end of the cycle, Zest goes back to mutating the first saved input. In most cycles, the size of the queue increases before you cycle back to the beginning. If you go through many cycles without saving new inputs, it is an indication that fuzzing has saturated and you can CTRL+C if you wish to do so.

At the end of the test: I had this message "Fuzzing resulted in the test failing on 3577 input(s)."==> this number is related to invalid inputs but I cannot see why we have it as long as we are using a generator for having valid syntactical inputs. I think invalid means failing in our assert test driver yes? could it be related to other things also?

The message means your test method threw an exception for those many inputs. Test failure means that there is possibly a bug in your application (or your test). These inputs are saved under the failures directory and can be repro'd to see what went wrong.
Just to clarify, these are not invalid inputs. Invalid inputs are not test failures. Invalid inputs are those that resulted in an assume() statement not being satisfies. It is possible for a generator to generate syntactically valid inputs by construction, but the input may not satisfy the semantics specified by assume() predicates.

in the "plot_data" file:

"paths_total" is exactly the same number as our queue size! but why? I mean why the name is like this?!
"unique_crashes" is our failures?
"unique_hangs": Can be generated by Zest or it is just for AFL? And I would like to know how I can have them in a different folder if I can get them by Zest?

Yes to all. The plot_data file uses the same column names as AFL and it's main purpose is to be compatible with afl-plot. It therefore uses AFL's terminology such as paths, crashes, and hangs... these are not terms used by JQF/Zest elsewhere.
I believe Zest currently stores crashes/hangs in the same folder: failures. From a Java testing point of you, both timeouts and unexpected exceptions are test failures meaning some action is needed. If all tests succeed, then there is nothing to worry about.

Btw, fuzz.log logs each saved input and provides a reason for why that input was saved. Inputs that are saved due to new coverage have a suffix +cov those that were saved due to the loop counts have +count; inputs that are valid have +valid; finally, +crash and +hang distinguish the failures respectively.  An input can have more than one reason for why it was saved.

All your questions are great, and it makes me realize that there is a bunch of stuff that's not super well documented, because most previous users of JQF were already familiar with AFL. I should probably document JQF terminology and options for non-AFL users.

Thank you so much for your answers.
Yes, actually I know a little about AFL, not exactly the details. When I realized that for our input(JSON structure) I should work with JQF+Zest, so I just started to explore Zest more deeply.
Could you please tell me about the debugging question?

 See screenshot below:

I don't know why vscode doesn't recognize it. An @Fuzz test is a valid regular JUnit 4 test. It is also executed by default without coverage when you run mvn test. Maybe this is a configuration issue or a bug in vscode?

If you remove the @Fuzz annotation and parameters, are you able to run/debug this from vscode? If yes, then it shouldn't change when you add parameters or the @Fuzz annotation.

Just when I put @Test I could see run/debug, but we cannot have two annotations for a method.
And for a normal JUnit test method, I could do debugging.

What happens if you annotate with @Property from junit-quickcheck?

It only works for normal junit test, not for fuzzing.

Hello,
I could see "Parametric-based" definition from the example on Zest paper, but could you please tell me what is the definition of "Property-based"? maybe by giving an example.

I don't think the Zest paper uses the term "parametric-based" anywhere. It does use the adjective "parametric" for generators . Traditional generators for property-based tests simply perform random sampling of syntactically valid inputs, whereas parametric generators (as defined in the Zest paper) instead decode a sequence of parameter bytes into a syntactically valid input.
The term "property-based" is generally used as an adjective for the test. Property-based testing simply means that it is a test that checks a property that holds over a range of inputs, as opposed to a traditional unit test that hard-codes inputs/outputs. You can read the Quickcheck paper to get an idea of the original tests that used this style.

Sure, thank you.

Hello,
I have a JSON generator, and for producing random string instead of using
identifier = random.nextChar('a','z') + "_" +identifiers.size();

which is a simple string, I tried to use the below one to have more different kinds of characters
identifier = new  String(gen().type(String.class).generate(random , status));

But I suppose apparently, Zest does not accept it, could you please tell me why? what could be the problem?
Respectfully,
Mahdis.

What do you mean by "Zest does not accept it"? Do you get an exception or other error message?

Oh sorry, the problem is not about Zest, I guess!

Hello,
Do you know the relationship between "total paths" and "current path" in the plot? because they do not match together if both are talking about a real "path"!

This is not a plot created by JQF. This looks like the output of the AFL-plot utility. AFL uses a confusing terminology of "paths" to refer to seed inputs that are saved in its fuzzing queue. So, the "current path" most likely refers to the ID of the seed input that is being mutated, and "total paths" as the size of the fuzzing queue. Therefore, the "total paths" increase monotonically whereas the "current path" cycles through the range [0, total_paths]. See https://github.com/google/AFL/tree/master/docs for more AFL docs.

Oh, I thought that this plot provides coverage information.
You are right, I did not realize this part before, "number of test cases ("paths")".
Thank you for your response.

Is there any documentation why AFL is using bitmap?

I pointed you to AFL docs above (e.g.  see technical_details.txt)---I'm not sure what about the bitmap you are looking for. Do you have a specific question about using JQF with AFL?  Note that I am not the author of AFL. You can ask AFL questions at https://github.com/google/AFL or the afl-users mailing list.

Sure, you are right. Sorry about that.
Respectfully,
On Wed, 16 Jun 2021, 20:54 Rohan Padhye, @.***> wrote:

I pointed you to AFL docs above (e.g. see technical_details.txt
https://github.com/google/AFL/blob/master/docs/technical_details.txt)---I'm
not sure what about the bitmap you are looking for. Do you have a specific
question about using JQF with AFL? Note that I am not the author of AFL.
You can ask AFL questions at https://github.com/google/AFL or the
afl-users https://groups.google.com/g/afl-users mailing list.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rohanpadhye/JQF/issues/137#issuecomment-862629538,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALJSQXH3IVYYNMZROQCNCADTTDXPZANCNFSM44C37IMQ
.


[docs] Use proper state handling in basic Menu example

Using an element as state is bad practice since drawn elements should be based on the state and not the other way around. It's also not intuitive to have the element be kept as state and the open prop as derived state.
Changed the basic example to use a simple boolean state for the open and closed state and use the ref prop on the Button element to pass the element to the Menu component. Also wrapped the callbacks with useCallback to avoid creating new callback references on subsequent renders.

The existing solution ensures that the menu popup doesn't show up before the anchor ref is set up (for example when open: true on mount). This could cause the menu to appear in an incorrect position.


Homepage Redesign

We have some action items for a homepage redesign:

Replace flash graphic with javascript based image slideshow (likely a jQuery plugin)
Add a twitter feed
Add something for user interaction

Get Satisfaction
Contact Us!
Got an Idea?

Added Wufoo contact form.

Did the flash graphic get replaced @blueroot?


Build Failures for android-testing

I just did the git clone for the android-testing project about a half-hour ago and imported the project using Android Studio as the instructions suggest. I got a warning message complaining about VCS but no root, so I selected "Add Root". That allowed the import to complete and display files, but with some build errors, to wit:

BasicSample-app: MainActivity won't build because R not found. Of course, I have seen this often enough before in both Eclipse and Android Studio, the solution in either case seems to be about the same. So I am more concerned about:

espresso-BasicSample-app builds and runs, but the test does not build , complaining that it cannot find AndroidJUnit4.class. Even more surprising, in the import android.support.test.runner.AndroidJUnit4, it complains it cannot even find runner, though I do have the directory /opt/adt-bundle-mac-x86_64-20140702/sdk/extras/android/m2repository/com/android/support/test/runner (yes, I installed the bundle under Mac OSX, this was the default at the time) and I followed the instructions (long ago, actually) for downloading  the Android Support Repository and Android Support Library. That said, I do have to point out that the instructions for the latter do not actually say to add the mentioned changes to the dependencies in the Gradle files, so I did not follow that part, leaving it up to the imported project to set those (hopefully correctly).

BTW: if adding those dependencies is the way to fix this, then WHICH "Gradle file" are they referring to at https://developer.android.com/tools/testing-support-library/index.html#setup when they say, " add these dependencies in your build.gradle file??
Finally, just in case it is relevant, the contents of the above runner directory contain jars for javadocs and source for runner-0.2 and runner-0.3, nothing for AndroidJUnit4.

Thanks for reporting this. Importing and building all the samples is an issue in the latest AS builds. This feature was originally there so that we can run all samples on CI but the plan always was that each sample would be checked out individually. We will update shortly and remove the top lvl build.gradle file and update the READMEs. So please import each sample as a separate project by using the build.gradle in the root of your sample of choice.

Once I figured you meant to select 'build.gradle' (from, in my example, BasicSample-app) in the file chooser dialog that pops up subsequent to choosing Import Project, I saw that sure enough, BasicSample-app now builds and runs. So that resolves the original issue.
Now the remaining problem is much simpler: for a given project there, where do I find the code that tests it? I expected (based on other examples) something like a package using the same name plus 'Test' in the same module, but I do not even see one in the same project. It looks like the user has to guess which other project is the test.

The new build system uses a new structure, tests are now located in src/androidTest/ or src/test/ for unit tests. Hope that helps. Please also check which View filter you have selected in your Android Studio, choose either Project, which will show the full project tree or use the Android View, which has a customized filter especially for Android projects.

I met the same problem after imported the whole project to Android Studio. :(

Looks like this does not work anymore in AS 1.3.2 it was never our intention to make all samples importable through a top-lvl build.gradle file. With the next push we will remove the top lvl build.gradle file to avoid confusion


Rendering markdown links

Hey, I think this library should render original markdown links or, if this is specialised in slack, include all kinds of Slack links, including telephone numbers.
The original markdown notation for links is as its follows:
[Anchor](URL)

I'm not sure what you mean, can you to elaborate? An example might help.

Markdown is a markup language which has a proper syntax for expressing links.
If this library is called lightMarkdown, one should expect that this:
[anchor](url)

would be rendered as
anchor

Can we make this happen?

That seems pretty specific, but I don't see a reason we shouldn't implement it with an allow flag and have it off by default.

Specific? That is what we call Markdown on the internet.

You are welcome to submit a PR.


Add USB and example

The examples require release mode to run correctly.
Blocked on:

~~https://github.com/stm32-rs/synopsys-usb-otg/pull/4~~
~~https://github.com/stm32-rs/stm32-rs/pull/401~~
~~https://github.com/stm32-rs/stm32h7xx-hal/pull/103~~

There are actually two USB peripherals:

Name
Type
Base Address
Pin Name

OTG1_HS
HS
0x4004_0000
OTG_HS

OTG2_HS
HS
0x4008_0000
OTG_FS

This PR only adds support for OTG1_HS. synopsys-usb-otg could support OTG2_HS too, except it currently hard-codes the base address (0x4004_0000). It would be interesting to see if this could be fixed with no runtime cost by adding a const fn to the UsbPeripheral trait. If anyone is interested in picking this up I would be happy to help.
Supports both OTG1_HS and OTG2_HS with https://github.com/stm32-rs/synopsys-usb-otg/pull/5
Otherwise I will look at merging this once the blocking PRs are resolved.
It would also be interesting to understand why release mode is required for the example. Likely the inlining in release mode is needed to reduce the latency when responding to events, but more experimentation is needed.

I released synopsys-usb-otg v0.2.2 with the relevant changes.

bors r+


What happened to codeunit 80?

Somehow then I no longer can reference directly to codeunit 80.
Intellisense does not show it:

But I can use it if I reference directly to it:

The same goes for a number of other codeunits, including 90.
I'm using the CTP17 DK build on Azure. Same happens on local Docker install.

Codeunit 80 has a hyphen in the middle of the name ie. it is Sales-Post, you can also see that if you use Go-To-Definition on "Codeunit 80".
Give it a try without the space but simply writes "salespost" then you should see it.

Thanks. Still strange that the hyphen makes it not show up in the "search" - then it shouldn't show Sales Batch Post Mgt either.


allow either lgtm or approved for merge

This change is

cc @lavalamp. We're trying to allow approved or lgtm to merge. Would that work?

This basically LGTM. I do think getting the 'latest lgtm/approval time' should be in its own function. I also think we need to update the tests to check how these two things interact.

so close!
# k8s.io/contrib/mungegithub/mungers
mungers/submit-queue.go:811: invalid operation: lgtmTime < approvedTime (operator < not defined on pointer)
godep: go exit status 2

squash and feel free to self LGTM


Update CONTRIBUTING.rst to point to website

See original issue on GitLab
In GitLab by [Gitlab user @adds68] on Sep 14, 2018, 18:11
Background
Currently !796 just points to the source BuildStream Policies file, but once the website is finished we should point to that, to stop fragmentation.
Task description

[ ] Point users to the BuildStream website instead of gitlab source files

Acceptance Criteria

In GitLab by [Gitlab user @adds68] on Sep 14, 2018, 18:11
mentioned in merge request !796

In GitLab by [Gitlab user @tristanvb] on Sep 17, 2018, 08:54
Note, this information is about contributing, along with commit policies, labeling of issues, etc; so this will not point to the website, but rather the CONTRIBUTING.rst will get more structured and will consume the additional policies we need to add there.
There was some discussion about putting policies about committers and such separately on the website, but it was ultimately decided that this should all go in one place.

In GitLab by [Gitlab user @adds68] on Mar 27, 2019, 16:15
closed


Cleaner log for timeouts

I think one should expect devices to be offline from time to time.
This could be very true for devices like smart light bulbs etc., where you may have a physical switch that is not always on.
Currently devices that are offline causes a quite verbose log like this:
2024-02-01 09:34:21 matter-server chip.DIS[1] ERROR Timeout waiting for mDNS resolution.
2024-02-01 09:34:35 matter-server chip.DIS[1] ERROR OperationalSessionSetup[1:0000000000000004]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout
2024-02-01 09:34:35 matter-server matter_server.server.client_handler[1] ERROR [548172696912] SDK Error during handling message: CommandMessage(message_id='90', command='device_command', args={'node_id': 4, 'endpoint_id': 1, 'cluster_id': 768, 'command_name': 'MoveToHueAndSaturation', 'payload': {'hue': 0, 'saturation': 238, 'transitionTime': 0, 'optionsMask': 0, 'optionsOverride': 0}})
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/matter_server/server/client_handler.py", line 188, in _run_handler
result = await result
^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py", line 503, in send_device_command
return await self.chip_controller.SendCommand(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/chip/ChipDeviceCtrl.py", line 834, in SendCommand
device = self.GetConnectedDeviceSync(nodeid, timeoutMs=interactionTimeoutMs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/chip/ChipDeviceCtrl.py", line 779, in GetConnectedDeviceSync
returnErr.raise_on_error()
File "/usr/local/lib/python3.11/site-packages/chip/native/init.py", line 67, in raise_on_error
raise self.to_exception()
chip.exceptions.ChipStackError: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout
I think it would be better with a bit cleaner log for this scenario as this will make it easier to spot real unexpected issues.

I don't agree that we should go hide things from the log. This is where a log is for, log important things that happened. In this case a timeout issue. What we could have done in this case is not try the command at all if the node is known to be offline, that is an actual improvement. But hiding things from logs? No, bad idea.

I was not suggesting to remove the log entry, but make it cleaner. Is a stack trace really needed?

For now (while we're still developing) YES the full stacktrace is needed.
Once we mature, we will bring it down


DRAFT: release pipelines configurations

Description of changes

Issue #, if available

Description of how you validated changes
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Please incorporate publish.sh script split, see for reference https://github.com/aws-amplify/amplify-cli/pull/12775 .

Closing in favor of: https://github.com/aws-amplify/amplify-cli/pull/12918


Can't open custom entry point from the list of available ones

Discord username
No response
What type of issue is this?
Permanent – Occurring repeatably
Is this issue blocking you from using Enso?

[ ] Yes, I can't use Enso because of this issue.

Is this a regression?

[ ] Yes, previous version of Enso did not have this issue.

What issue are you facing?
When running IDE with a non-existing startup.entry (like _ or foo), I see the list of available entry points.
After clicking on some of the entries, I see an error message like in https://github.com/enso-org/enso/issues/5786

However, this time IDE crashes.
Logs:
❯ dist/ide/mac-arm64/Enso.app/Contents/MacOS/Enso -startup.entry=_
The single argument '-startup.entry=_' does not denote a readable file: Error: ENOENT: no such file or directory, access '-startup.entry=_'
╭ Setting Chrome options
│ Setting '--disable-gpu-sandbox' because 'performance.disableGpuSandbox' was enabled.
│ Setting '--disable-gpu-vsync' because 'performance.disableGpuVsync' was enabled.
│ Setting '--no-sandbox' because 'performance.disableSandbox' was enabled.
│ Setting '--disable-smooth-scrolling' because 'performance.disableSmoothScrolling' was enabled.
│ Setting '--enable-native-gpu-memory-buffers' because 'performance.enableNativeGpuMemoryBuffers' was enabled.
│ Setting '--force_high_performance_gpu' because 'performance.forceHighPerformanceGpu' was enabled.
│ Setting '--ignore-gpu-blocklist' because 'performance.ignoreGpuBlocklist' was enabled.
│ See '-help-extended' to learn why these options were enabled.
╰ Done in 0.8 ms.
╭ Starting the application
│ ╭ Starting the backend process with the following options: .
│ │ Backend has been spawned (pid = 41637).
│ ╰ Done in 3.5 ms.
│ ╭ Starting the content server.
│ │ Server started on port 8080.
│ │ Serving files from '/Users/ilyabogdanov/projects/enso/Users/ilyabogdanov/projects/enso/dist/ide/mac-arm64/Enso.app/Contents/Resources/app.asar/assets'.
│ ╰ Done in 7.6 ms.
│ ╭ Creating the window.
│ ╰ Done in 29.4 ms.
│ Loading the window address 'http://localhost:8080?startup.entry=_&startup.platform=darwin&engine.preferredVersion=2023.1.1-nightly.2023.4.26'.
╰ Done in 51.9 ms.
[info] [2023-04-26T14:39:34.156Z] [org.enso.projectmanager.boot.ProjectManager$] Starting Project Manager...
[info] [2023-04-26T14:39:34.176Z] [org.enso.projectmanager.boot.ProjectManager$] Started server at <IP_ADDRESS>:30535, press enter to kill server
Uncaught exception: ReferenceError: origin is not defined
Exception origin: uncaughtException
[warn] [2023-04-26T14:39:39.519Z] [org.enso.projectmanager.boot.ProjectManager$] Failed to read line.
[info] [2023-04-26T14:39:39.519Z] [org.enso.projectmanager.boot.ProjectManager$] Stopping server...
[info] [2023-04-26T14:39:39.52Z] [akka.actor.CoordinatedShutdown] Running CoordinatedShutdown with reason [ActorSystemTerminateReason]

Opening an entry point directly with -startup.entry=interface works fine for any entry point.
Expected behaviour
I should be able to open an entry point.
How we can reproduce it?
No response
Screenshots or screencasts
No response
Enso Version
dcfbf841b30765f9c511bc0e4a48cc64f6f73154
Browser or standalone distribution
Standalone distribution
Browser Version or standalone distribution
dcfbf841b30765f9c511bc0e4a48cc64f6f73154
Operating System
MacOS
Operating System Version
MacOS Ventura 13.3.1 (22E261)
Hardware you are using
No response

Can reproduce this on a Linux machine. But this only seems to occur in the Electron app. When doing the same in a browser, it seems to work without issue.

the error line info indicates the bug happens here (parsedUrl.origin !== origin):
https://github.com/enso-org/enso/blob/ae94a9f40d3e98b9068da716b8b6416bba517a19/app/ide-desktop/lib/client/src/security.ts#L78-L88
not 100% sure what specifically causes the bug, since origin is defined in electron, and parsedUrl would throw if it was an invalid url, so that shouldn't be it either

so it seems like window, alert, origin etc are all missing for some reason...

oh, maybe security.ts is running on the main process, not in a window

not sure if there's a way to figure out the origin without being in a window. i can think of a couple of solutions but none of them aren't A Bad Idea:tm:

it's theoretically possible to pass the port from the server to this file (app/ide-desktop/lib/client/src/bin/server.ts)
alternatively, send a message containing the origin via IPC from the window - but make sure the console side (?) only accepts the first such message

note for whoever wants to tackle this, the URLs will need to be updated (heading number incremented) so might as well do that at the same time:
(only these three URLs though)
 * https://www.electronjs.org/docs/tutorial/security#12-verify-webview-options-before-creation. */
 * https://www.electronjs.org/docs/tutorial/security#13-disable-or-limit-navigation. */
 * https://www.electronjs.org/docs/tutorial/security#14-disable-or-limit-creation-of-new-windows. */

@vitvakatu you may want to QA this PR https://github.com/enso-org/enso/pull/6507 which should fix the problem and we can merge it


ACL

An Access Control List system is required to allow MQTT clients to only PUBLISH and SUBSCRIBE to topics if the packets pass the ACL.
If there are no ACL's for a client then an implicit deny is enforced for both PUBLISH and SUBSCRIBES packets. The ACL will have the following format
PUBLISH sensor/1234/# ALLOW
PUBLISH sensor/1236/# ALLOW
SUBSCRIBE sensor/# ALLOW
PUBLISH sensor/1234/# DENY
The DENY's overrule all permissions irrespective of the position in the ACL.
PUBLISH sensor/1234/2 will be denied because there is an explicit DENY (PUBLISH sensor/1234/# DENY), even though there is an explicit ALLOW (PUBLISH sensor/1234/# ALLOW)
A client can subscribe to SUBSCRIBE # and will only get packets for topics which pass the ACL.

Any changes in the ACL's for a particular MQTT client need to be enforced by the broker as soon as the changes are applied.


WIP: Fuse frontend

It's not done yet. Linux v4.4/Ubuntu 16.04 broke the mount loopback inside container for fuse(see #204).
Also since truncate hasn't been implemented, write directly to Fuse file won't work.

Also there is a racy between delete replica and stop processing need to be fixed.

Replica deletion racy fixed.


An error occurred when the Safire browser opened the dashboard of Grafana

Expected Behavior
Actual Behavior
Steps to Reproduce the Problem

Additional Info

deepflow version: 6.1.1
Output of kubectl exec -it -n deepflow sts/deepflow-server -c deepflow-server -- deepflow-server -v:
Output of kubectl exec -it -n deepflow ds/deepflow-agent -- deepflow-agent -v:

--

deepflow agent list:
Output of deepflow-ctl agent list:

--

- Kubernetes CNI:

--

- operation-system/kernel version:

**Output of `awk -F '=' '/PRETTY_NAME/ { print $2 }' /etc/os-release`:**

**Output of `uname -r`:**

--

<!-- Any other additional information -->

We're happy to report that your issue has been fixed.
If you have any additional questions, please let us know.

Verify that the problem has been fixed


readme: add community communication channel

Signed-off-by: Changwei Ge<EMAIL_ADDRESS>

Should be great if using the ding talk QR of english version.

Should be great if using the ding talk QR of english version.

Good point. Fixed


Add CLI "tutor mode" to Web UI/Desktop

This issue has a bounty!
Successfully closing this issue by making a PR of production-ready code can earn you not only the undying love of the IPFS community — it can net you a financial reward. See the current list of bounty issues and their values here.
How to claim this bounty
Want to work on this bounty project? Please leave a comment on this issue, and we'll be back in touch ASAP to discuss specifics. Note that because this project requires changes to the existing UI, we'll want to work closely on making sure the solution integrates well with current patterns.
The need in brief
Meet the needs expressed in the original proposal below by adding some form of "CLI tutor mode" to IPFS Web UI (which, in turn, will be included in IPFS Desktop, since they share this portion of the codebase). The solution should ...

Enable the user to generate copy/paste-able CLI snippets for the actions available in Web UI, with an aim to making it easier for newer IPFS users to self-learn the CLI
Be readily available for such users, but not so unavoidable that users who don't want to take advantage of the feature can't ignore it

Original proposal from @lanzafame
I was just creating a VM on GCP and they have a button at the end that takes a UI hand-craft VM creation and turns it into either a curl request or a gcloud cli command and thought it would be cool to have something similar for the webui so if people wanted to know how to pin something like they are in the webui on the cli, they could get the command and the arguments that they had already input. Sort of a self-teaching moment for the curious

@lanzafame This is such a cool idea 😊 ... and also sort of a big chunk to bite off. Do you think it's something that would be appropriate to put out for a bounty? Otherwise I fear it might languish just given current resourcing. Any other thoughts from your end?

@jessicaschilling I think that is a great idea.

hey @lanzafame, can i please start working on this over the weekend?

@jay-dee7 sure thing

@jay-dee7 I’ll assign you, but as noted above, please check in first with sketches/descriptions of where and how this will appear in the interface before getting too deep in the work. There’s a pretty substantial impact on the UI, so we want to be sure this is implemented in a way that supports but doesn’t distract the reader. (This is also one of the conditions for bounty payout.) Thank you!

Screenshots and any descriptions to explain them would be great. We don’t have existing designs, unfortunately, but please borrow from any existing metaphors/patterns already in the app that are analogous. Thanks!

@jessicaschilling i was wondering about how to approach this. Do we really need to pop up a modal to display the content? or simply by clicking, you copy the command to the clipboard?
Like check this example, if we want to overwrite the settings, we can either do this,

@jessicaschilling i was wondering about how to approach this. Do we really need to pop up a modal to display the content? or simply by clicking, you copy the command to the clipboard?
Like check this example, if we want to overwrite the settings, we can either click on a button, to open a modal, we display whats going to happen and then give the user an option to copy the equivalent command

or we instead of opening a modal, we just copy the command to his clipboard?
ps: dont mind the wrong texting in the screenshot, i'll fix it later on and post more of them

@jay-dee7 That’s a good question. One thing to consider is how you might like to learn a new CLI tool, as well as how existing ways of learning new CLI tools present the info.
Everyone’s needs and wishes are different, but I might suggest that we want to present the info in a modal (or some other form of fallout, but a modal seems most obvious) for a few reasons:

Most IPFS commands are a lot shorter than that big block of json, so we aren’t as likely to present the user with a big, maybe overwhelming modal like the original illustration
The user might just want to see the equivalent command but not actually use it in the terminal (for example, there may be someday when the user is using webUI on a phone and doesn’t have a terminal available)
The user might still paste into a terminal, but their terminal makes it hard to read (and understand) long commands

Suggestion: if you want to research this deeper, look around at other similar situations and tools out in the wild and see how they handle similar scenarios. It doesn’t have to be code snippets, just any other examples of “discover another way of doing a thing” you can find. People do best learning new ways to do things when they’re presented with familiar patterns.
Great work so far and thank you for checking in!

@jessicaschilling i understand, a modal makes a lot more sense than just plain copy-command approach, there's a lot we can do to help under understand the CLI approach much better. i tried digging in the code a bit and understand it. I'll keep you guys posted with the development :)

hey @jessicaschilling , i'm so so sorry for delaying this one. Been caught up with tons of work at office lately. I spent few hours this weekend trying to understand how redux-bundler-react works in the webapp and also i've tried to move a bit forward.
I've made small changes to the UI (trying to not drift away from the existing development patterns), nothing much bold tho. Please take a look at this and let me know if it's okay to follow this path

Since settings page in particular has so much space, it seems possible to add a BUTTON but there are other places where we dont have enough space like Add Connection in peers page

So maybe i should add a smaller outline button? or a tooltip? since having different kinds of buttons on different pages might confuse the user. A tooltip seems like a good fit here. please let me know you opinion on this.

Thank you for the updates! I'm going to make two comments -- this first one deals with where the on/off switch for this should live, and the other will deal with the interaction itself 😊
As far as where we should put the option to turn tutor mode on/off, let's include it in the preferences screen as such. Feel free to reword if you find the text confusing. It would also be good to include an image of the icon itself after the text "'copy code' icons" in the messaging itself -- pardon me for not doing so in the screenshot!

The second comment may take a bit to get down on paper, so please bear with me.

(comment 2/2) - this one deals with how the option to copy CLI commands should be implemented visually within the UI.
First, we need to consider all the places where this option might exist. I quickly round up the following, but please have a look to see if there are others not on this list:

Files screen > "Add" button > "New folder" (results in a modal popping up)
Files screen > "Add" button > "Add from IPFS" (results in a modal)
Peers screen > "Add connection" button (results in a modal)
Settings screen > "IPFS Config" section (as an aside, the CLI resulting from this should be to open the config file in an editor)
Home screen (the one you get to when you click the up/down icon in the top right of every window) > set custom API field > "Submit" button
Files screen > "three dots" action menu > "Delete" (results in a confirmation modal)
Files screen > "three dots" action menu > "Rename" (results in a modal)
Files screen > "three dots" action menu > "Download" (results in native OS save-file window)
Files screen > "three dots" action menu > "Pin" or "Unpin"

Next, we need to solve for how this will appear in a consistent manner across all those items above. One approach to this would be to include a "copy code" icon next to the button/menu option that would ordinarily start the process of performing the action in the GUI -- i.e. rather than putting the "copy code" icon in the modal that opens when you click on "Add from IPFS", we'd put the icon next to the "Add from IPFS" option. Examples of how that could potentially look (icon itself can be found here):

Note that if we took this route of visual implementation, we'd have to make sure that when the icon appears in a menu, the user can clearly discern between clicking on the menu item and clicking on the icon.
**Finally, we'd need to solve for what happens after the user clicks on the icon. The modal you reference here is a great start, though I might remove the megaphone icon (it's not needed in this context) and tweak the explanatory text a bit: maybe "Replace any placeholder text and copy this command into your terminal to use the IPFS command-line interface." The button could just say "Copy" -- "clipboard" is pretty implicit here.
Please don't consider any of the above set in stone -- happy to iterate on this if you see room for improvement!

hey @jessicaschilling, i think it's a great idea to include the option to enable cli tutor mode inside the preferences page.
Including an icon next to the buttons also looks great (icon itself is beautiful). I'll try to find all the places that can can have an equivalent CLI command.
As for the modal, i was really trying to reuse the components which were already present in the code, before making any submission, i'll make sure to remove anything that doesn't add up.
Thanks a ton for spending so much time and making everything clear :)

hey @jessicaschilling i was able to make some progress this weekend. Here's what i've done

changed the text as you requested
added the new copy icon
added the cli tutor component in the files pages
made the existing dropdown options distinguishable from the copy icon

I think i'm very close the end of the task but i did run into some issues while trying to retrieve the individual file names and passing them along to generate their cli equivalent commands (which is why we see [object object] in the modal) but i'll figure it out soon enough.  Let me know when you're ready for a more thorough PR review ... I have a few tiny visual tweaks in mind based on your screenshots (just to bring them a little more in line with the mockups) but we should just go through everything all at once when you're ready. This looks great so far!


pull request for e2e test at 12/23/2016 00:15:17

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


docs(project): adding project specific files

The PR adds/edits the following project specific files to guide contributors and repository maintainers

github issue template
github feature request template
github pull request template
CONTRIBUTING.md
MAINTAINERS
README.md
RELEASE.md
code-standard.md

Signed-off-by: Akhil Mohan<EMAIL_ADDRESS>

Codecov Report

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

@@            Coverage Diff             @@
##           master     #405      +/-   ##
==========================================
+ Coverage   46.66%   46.81%   +0.14%
==========================================
  Files          59       59
  Lines        2668     2668
==========================================
+ Hits         1245     1249       +4
+ Misses       1324     1321       -3
+ Partials       99       98       -1

Impacted Files
Coverage Δ

cmd/ndm_daemonset/probe/udevprobe.go
68.08% <0.00%> (+2.83%)
:arrow_up:

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 8b69235...651ee2a. Read the comment docs.


Fix issue with parsing hex integers in F# build

It looks like big_int_of_string from FSharp.Compatibility.OCaml v0.1.10 can't handle hex numbers. It was fixed in v0.1.14 (https://github.com/fsprojects/FSharp.Compatibility/pull/19), but it comes with a dependency on newer FSharp.Core. We can either bump version of FSharp.Compatibility.OCaml and FSharp.Core in F* (CI seems to be passing), or copy the fixed code for big_int_of_string into F*.
What do you think?

bumping to new FSharp.Core sounds good to me. thanks!


AdminController: adding unit tests

fixes #609

pinging @mheggeseth @MisterJames for a quick review before we move forward. Thanks!

Left a few comments. And create this issue: https://github.com/HTBox/htbox.github.io/issues/4
Once the comments are addressed, and the merge conflicts resolved, this is ready to merge.

@BillWagner, how do I go about handling these merge conflicts? The regular steps for rebasing from master?

@mgmccarthy Yes, that's right. Rebase from master (which will show the merge conflicts) and resolve them.

pinging @BillWagner. All merge conflicts fixed. This is ready to go.


New scoring weights should prefer beginning of line words more

[ ] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[ ] bash
[x] zsh
[ ] fish

Problem / Steps to reproduce
As stated in the release notes for 0.32.0, the scoring weights were updated. However, this changed the behavior in previous versions that preferred words at the beginning:
fzf --query=bar --height=4 << EOF
foo bar.sh
foo/bar.sh
EOF

gives:
foo/bar.sh
foo bar.sh

whereas in previous versions it would be the other way around. I definitely prefer it to match foo/bar.sh first. The current behavior makes it a pain to search for files whose names are also part of other files' name, like in the example posted above where I want to search for bar.sh.
Thanks!

fzf is a general-purpose text filter, so the scoring algorithm isn't specifically designed for file paths. In this particular context, foo bar.sh may be the better match, but in other contexts, for example with a list of commands (e.g. CTRL-R), it may make sense to prefer git add something over rm foo/add on add.
fzf --query=add --height=4 << EOF
rm doc/addendum/patch1
git add somedir/patch1
EOF

What I presumed was that file paths with whitespace are not very common. Do you have many files with spaces in their paths?

Yeah I do have many files with spaces. Makes sense though. So how about this: A special "path" mode for fzf that enables specific path behavior. For example, it would also be useful if files were sorted before folders (since you usually always search for files)

For example, it would also be useful if files were sorted before folders (since you usually always search for files)

fzf, being a text filter, does not know which entry is a file or a directory. The user should just feed a list of files excluding directories to fzf.
# Only files
fd --type f --strip-cwd-prefix | fzf

Yeah I do have many files with spaces.

Can you post a few screenshots where the scoring algorithm of fzf isn't working as desired?

The user should just feed a list of files excluding directories to fzf.

Ah thanks that works.

In each case I'm looking for the source files. While I could filter out the image files, I can't filter the text files because I might want to open them too.

I see. The bonus points for the boundary characters are currently hard-coded.
https://github.com/junegunn/fzf/blob/779d8e16273a9ca776bef4136b3ff1886e10d19a/src/algo/algo.go#L115-L127
But maybe we could consider adding an option to tweak the scores.
A workaround for now would be to prefix your query with / (e.g. /weap). You can even start fzf with / as the default query. (fzf --query=/)

Same problem on MacOS, fzf 0.32.0.
An easy solution would be to give the same additional bonus for both cases (lines 124 & 127 in the snippet above), no?

I do not consider this a bug. But I would love the option to disable bonus points for boundary characters.
Among other things I use fzf for bash history. There I sometimes find myself in situation where I am looking for command where I remember only part of it. For simple example let's say I have forgot exact name of tcpdump. I just know its something with dump in it. Searching for dump gives me a lot of other entries like less dump_file, pr_restore smthg smthg smthg product_dev_dump_date.tar or rm dump.tgz etc. These are relevant but I need to revert to less .bash_history for simpler search to find it. I tried fzf --exact but bonus points for boundary seem to be used there as well.
If I can dream a bit then ability to toggle this boundary bonus points on/off during search session would be amazing. Then I can switch between "prefer older exact matches" and "prefer newer substring matches" live... but feel free to ground me back to earth.

@james64 Have you tried (dynamically) disabling sort as suggested above when that happens? Still not satisfied with the result?

@junegunn I have not found this feature so far and ou man yes it helps. Together with using or not using ' in front of query this gives me all the flexibility I want. Thanks a lot!


disassembler crash in OPCODE_ASSIGN_TYPED_NATIVE

Latest master:
When trying to disassemble issues linked here:  https://github.com/godotengine/godot/issues/43997 and  here: https://github.com/godotengine/godot/issues/44411
I can not disassemble functions in those issues due to a crash in OPCODE parsing OPCODE_ASSIGN_TYPED_NATIVE:

The crash is unrelated to the issues listed above, but fixed with the correct dissasembly in #44419

Fixed by #44419.


login page styling

I changed the LoginContainer.js file to customize the styling and text for the Boys and Girls Club.
I also added the boys and girls club logo to the component.

As it stand it is all good from what I can see and looks good

I can see it as well, looks great


Add ability to change tab scroll area background color

Add the ability to change the tab scroll area background color

Looks good, thanks!


Fix formation before half starts

This, untested but low risk, puts robot into formation before the half time starts
Pre pull request checklist:
Code Quality

[ ] Is the code is understandable and easy to read
[ ] Changes to the code comply with set clang-format rules
[ ] No use of manual memory control (e.g new/malloc/colloc etc)
[ ] Are (only) smart pointers used?

Testing

[ ] All tests are passing.
[ ] I added new / changed existing tests to reflect code changes (state why not otherwise!)
[ ] I tested my changes manually (Describe how, to what extent etc.)

Commit Messages

[ ] Commit message is saying what has been changed, why it was changed? Remember other developers might not know
what the problem you are fixing was. Note also negative decision (e.g., why did you not do particular thing)
TLDR: Commit message are comprehensive
[ ] Commit messages follows the rules of https://chris.beams.io/posts/git-commit/

Better alternative has been made


[question] I want to convert struct to JSON, struct have a optional value is nil

like this
struct GoListUpdateSequenceModel: Encodable {
    let id: Int?
    let label: String
    let type: String
    let items: [GoListUpdateSequenceItemModel]
    func toJSON() -> JSON? {
        return jsonify([
            "id" ~~> self.id ,
            "label" ~~> self.label,
            "type" ~~> self.type,
            "items" ~~> self.items,
            ])
    }
}

if id is nil, after convert toJSON(), i get JSON like this: "[{"type":"label","label":"Divieder","items":[{"type":"place","id":12964}]}]"
I want to get "[{"id":null,"type":"label","label":"Divieder","items":[{"type":"place","id":12964}]}]"
can you help me?
sorry for my english.

you'll probably want to create your own encoding function (see Custom Transformations: https://github.com/hkellaway/Gloss#custom-transformations)


Unable to delete server from list

I got 404 error when remove server from list, is there any other way can remove server from list?
My genghis is Version 2.3.8 and starting by execute command genghisapp

I had the same problem. The caching was indeed the problem.
After deleting the cookie the servers where removed...


page data store now runes state

The stores expected  in sveltekit-flash-message as parameters are writable stores and page store is now a runes store. this will need updating.

The stores expected in sveltekit-flash-message as parameters are writable stores and page store is now a runes store. this will need updating.

is there a way to get past this?

@hgoona It actually still works, you just gotta import the old page store and ignore the deprecation warnings:
// Using both the new page from app state for other things and old one for flash messages.

import { page } from '$app/state';
import { page as pageStore } from '$app/stores';

const flash = getFlash(pageStore);
....

{#if $flash}
   <div>{$flash.message}</div>
{/if}

Caveat: if you are setting flash messages on the server before a redirect you will get taken to an error page for a split second before the redirect kicks in.  I assume this is due to the Svelte 4 to 5 migration.
It's a jarring but I'm ok with it for now...

If there's a way to detect which one of the stores are used at runtime, I could add a compatibility fix.


Rename AutocompleteSuggestionProvider

While the name is "correct", it's a mouthful.
Rename it to AutocompleteProvider and make the world a better place.

This can be tested in the master branch.


How about using OpenSuse Tumbleweed for WSL2?

How about using OpenSuse Tumbleweed for WSL2?
I am currently using OpenSuse Tumbleweed for WSL2 , It already support podman, working perfect.
alpine looks too small , and now it's now working for my test.
I am try rancher desktop + windows 11 + WSL2.
but got failed to run them.

I guess the rancher team has fewer resources to maintain a full linux distro.
Why not join big OpenSuse family together.
I love OpenSuse more than alphine , and it's really a full feature and tested linux distro i think.

This distribution is only meant for use with Rancher Desktop, and not a general distribution; as such, we're aiming for it to be minimal.  As such, this being "too small" (but still enough for Rancher Desktop) seems desirable.
We've looked at podman before, but due to compatibility concerns we've decided to not go down that route.
Generally speaking, we like OpenSUSE (my office machine is running Leap), but we've had issues getting it to be minimal. The appropriate BCI still contains things we have no need of like Kerberos support and pam.  It would be good for interactive use and to emulate a proper Linux installation, but that's not what we need here.
Thanks for your comments, but at the moment we're probably not going to switch unless there's a PR that demonstrates an OpenSUSE base image with similar size, or other significant advantages.


Simplify entrypoint

Don't use args anymore but rely on env. variables.
Test reviewdog/action-shellcheck as well

These env variables are automatically created by GitHub?

@Zimmi48 yes :)

and the shellcheck linter seems to work:
https://github.com/erikmd/docker-coq-action/runs/574138160?check_suite_focus=true
so I'm going to revert the CI test commit and merge this PR if you don't object


 IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/example.justlists.ts
Checklist

[ ] I understand that this is not the place to request a token listing.
[ ] I have tested that my JustList is compatible by pasting the URL into the add a list UI at just-swap.org.
[ ] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL:
JustList Name:
Link to the official homepage of the JustList manager:

Sorry, your issue will be closed as you did not submit your information in the correct format.


INFO

You fix the code, thank you, you are the best and I appreciate your work, I had two questions if you could answer I would appreciate it a lot, you made the code to download videos from snaptik, can the code be changed to download from tikmate - for example or from somewhere else, and the second question, can the videos be downloaded, with a higher resolution, snptik has offered the download in HD but I don't know why it has been removed as an option.
I wish you the best, and I appreciate you for the work you do!

yea it adjustable just change selectors and might even less steps than snaptik , you can also make it more quicker if changed math function but it might be detect by cloudflare or tiktok azure, i guess HD option not available anymore since Tiktok protect their API from automated bots , i just do trying to make simple as much as possible


Don't add breadcrumb when it is already in collection

Hi,
perhaps I misunderstood something, but if I navigate back in my breadcrumbs the clicked breadcrumb will be added again which looks awkward:
Home/Finanzpläne/Konsolidierungsblätter/Konsolidierungsdetails/Konsolidierungsblätter/Konsolidierungsblatt/Konsolidierungsblätter
Can I do something against that behaviour?
I think your Add Method should check if the URL is already in the breadcrumb array and only add if its not the case.
Best!
Alex

Hello Alex,
I think what you trying to do is not supported by this component. The breadcrumb navigation itself does not evaluate navigation events and resets them if you navigate back.
The breadcrumb trail needs to be rewritten on every page.
In your given example this would mean that Konsolidierungsblätter needs to set up a trail like this.
    BreadcrumbService
        .Set<HomeBreadcrumb>()
        .Set<FinanzplaeneBreadcrumb>()
        .Set<KonsolidierungsblaetterBreadcrumb>();

While Konsolidierungsblatt needs to setup the whole trail like this.
    BreadcrumbService
        .Set<HomeBreadcrumb>()
        .Set<FinanzplaeneBreadcrumb>()
        .Set<KonsolidierungsblaetterBreadcrumb>()
        .Set<KonsolidierungsblattBreadcrumb>();

Keep in mind that HomeBreadcrumb needs to be derived from RootBreadcrumb.


test: add wallaby config

https://wallabyjs.com/
I saw Wallaby in your typescript boilerplate repo @ProbablePrime and it looked cool. I'm trying it out now and will probably keep it. If this config looks good to you, go ahead and merge this at your leisure.

Coverage remained the same at 100.0% when pulling 2976a06246d6ddc4a2f6ffef7951456906d2f6ba on wallaby into 22d057096ce6c807f5e9551fffd50965e630855d on master.

WALLABY \o/


Added Pipeline transformer capabilities with MXNet

This allows the use of spark ml, which is the preferred route for the future of spark.
Note, I have not been able to test this, because after following the directions on the mxnet page, I am still unable to run scalapkg. It is based off of something similar that I did for dl4j. So if someone could test it, that would be awesome. If I get it building, I will let someone know.
https://spark.apache.org/docs/latest/ml-classification-regression.html
Example same as before (mxnet lives under transformers for pipeline):
val conf = new SparkConf().setAppName("MXNet")
val sc = new SparkContext(conf)

val mxnet = new MXNet()
  .setBatchSize(128)
  .setLabelName("softmax_label")
  .setContext(Context.cpu()) // or GPU if you like
  .setDimension(Shape(784))
  .setNetwork(network) // e.g. MLP model
  .setNumEpoch(10)
  .setNumServer(2)
  .setFeaturesCol("features") //adding for dataframe/datasets
  .setLabelCol("label") //adding for dataframe/datasets
  .setNumWorker(4)
  // These jars are required by the KVStores at runtime.
  // They will be uploaded and distributed to each node automatically
  .setExecutorJars(cmdLine.jars)

val training = spark.read.format("libsvm").load("data/mllib/sample_libsvm_data.txt")

val model  = mxnet.fit(training)
model.predict(someVector)

More importantly, it opens up the ability to use spark's classification evaluators, and to join pipeline stages.

@javelinjs @Ldpe2G

I'll get my other computer out to see if I can get this running, so it can be tested, if there are any found issues. Long term, I would like to process the data from dataset level, rather than using this as a wrapper for the existing spark mxnet.

will look into it today.

Finally got it building. There are a couple of issues. Will fix it soon.

built

Realized that argmax was not being used for classification. I made the switch.

Can one of the admins verify this patch?

@javelinjs Sorry, I was playing around with this again, and made one last change, due to java interop issues with the "copy" method. All should be good now.

Good to me. But the Travis build stucks, could you help to do a force merge? @piiswrong


The --target option doesn't seem to exist

I think there was a mistake where the target option was added to the plugin. Specifically in https://github.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/231 the referenced documentation is https://docs.docker.com/build/building/multi-stage/#stop-at-a-specific-build-stage
That option is specific to docker build though, not docker-compose build. If I understand the original request correctly, the way to do this in the plugin would be to add the option to the override yml instead.
Currently the plugin tries to add --target ... to the docker-compose build command and fails because it's not implemented https://docs.docker.com/engine/reference/commandline/compose_build/
(Unless this is some version specific behaviour that was added/removed in the meantime)

I am really interested in your expectations on how it should work and what kind of configurations you want off it.

My original use case was to have a service app pointing at a Dockerfile with multiple stages. Then the test steps would use an override to use target: ci which includes the test tools, while other steps would use the default which builds just the deployable image.
Turns out I had more differences to implement, so ended up just duplicating the service as ...-prod and ...-test in the docker-compose itself and assigning different targets there.
I think the option could still be useful in a simpler setup.

Also, I am not 100% sure how specifying a target would work when you are building multiple services. Do you have any thoughts on that?

Nope, I suspect it would have to be a hack for a single service only.

I just ran into this issue and assumed that specifying the target option would override the compost file to add a target directive to my service, thus allowing me to target a stage in a multi stage build. Sadly this just slaps an incorrect --target onto the docker compose cmd which results in
$ docker-compose -f docker-compose.yml -p buildkite018c900423954192bc6a0b21321ae8ae -f docker-compose.buildkite-10-override.yml build --pull --target base app
unknown flag: --target
🚨 Error: The command exited with status 16

FWIW - My use case is similar to @viraptor in that i want to target a multi stage build.
https://github.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/231#issuecomment-550067960 provides a similar use case I have where i'd like to prebuild multi stage cache images to avoid extra work in subsequent builds.


release 4 possible project issues in the browser

Project: 0fd8f918-62d6-4b8b-ac35-4c53dd601f71
https://data.humancellatlas.org/explore/projects/0fd8f918-62d6-4b8b-ac35-4c53dd601f71?catalog=dcp4
Ami is listed as a contributor rather than data curator, we should investigate if this is something we need to update. The other 4 projects show this correctly.
Also currently all matrices are missing - I have flagged this on the DCP2 channel as I don't expect this to be anything to do with us.
https://embl-ebi-ait.slack.com/archives/C9XD6L0AD/p1617734832085700

This has been done so closing


If ISTIO enabled , data loading init job does not exit

If istio is enabled in the vdc charts, the init* jobs will have an additional istio proxy.
However this proxy will be running & not exit when for example the postgres data loading has completed.
There is some discussion of the relationship between sidecars such as istio & jobs at https://github.com/istio/istio/issues/6324
For now mitigation is to disable istio (which isn't yet default in any case)
However istio is needed even in jobs as it will monitor & permit/deny traffic between the pods.

Note the tail end of the discussion
'Please keep in mind, this KEP is very important for Istio !
It's a show stopper for all projects using service frameworks with coordinated bootstrap/shutdown (akka cluster, lagom etc.) together with istio service mesh'

still valid


Chapter 2 | How To ? | Getting Pandas Object from Sklearn Pipeline Output

Hi @ageron :
Thanks a ton for putting together an excellent book, I am learning a lot and its been very satisfying.
I am interested in analyzing the Pipeline output, however, as you know the output of a pipeline is a numpy array which loses the information pertaining to the columns.
Another related goal is to analyze the model output in greater detail.
I see that you have provided a code where we manually construct the dataframe from the numPy array.
housing_extra_attribs = pd.DataFrame(     housing_extra_attribs,     columns=list(housing.columns)+["rooms_per_household", "population_per_household"]) housing_extra_attribs.head()
I wanted to get your thoughts on the above.
To reiterate, the goals are:

To get the pipeline output as a data frame in a more 'automated' fashion
To be able to interpret the linear regression results in a comprehensive manner (e.g. r-squared, the significance of parameters, relative weight of parameters )

Thanks for your help
Rama
PS::
I have a question re. Pipelines. Is building pipelines needed when the model is built from an exploratory/learning POV? (i.e. the model is not to be deployed in a production environment)

Hi @ageron
I figured out a nifty piece of code that creates a data frame with the sorted columns
`coefficients = pd.concat([pd.DataFrame(all_attribs),pd.DataFrame(np.transpose(lin_reg.coef_))], axis = 1)
coefficients.columns = ["attribute","coefficients"]
coefficients = coefficients.sort_values(['coefficients'], ascending = [False])`
I'll await your response to know if you have further comments, else I'll close out the issue.
Thanks again.

Hi @raamav ,
Thanks for your kind words, I'm glad you find the book useful!
Unfortunately, Scikit-Learn was created before Pandas existed, which explains why it offers little support for it. So when you pass a DataFrame to a Scikit-Learn model, you often get a NumPy array out, thus without column information, as you noted. There may be some tools to help preserve the column names, but I have not used them. When I want to recover the column names, I do it manually, as shown in the code example you pointed to.
Regarding your second question, in a LinearRegression model, the weights are listed in the same order as the input columns. For example:
>>> from sklearn.linear_model import LinearRegression
>>> import pandas as pd
>>> import numpy as np
>>> X_train = pd.DataFrame({"age": [44., 23., 35.], "weight": [80., 77., 68.]})
>>> y_train = np.array([20., 19., 15.])
>>> lin_reg = LinearRegression()
>>> lin_reg.fit(X_train, y_train)
LinearRegression(copy_X=True, fit_intercept=True, n_jobs=None,
         normalize=False)
>>> lin_reg.score(X_train, y_train)
1.0
>>> coefs = pd.DataFrame(lin_reg.coef_.reshape(1, -1), columns=X_train.columns)
>>> coefs
        age    weight
0 -0.013333  0.426667

Note that the score() method computes the R2 score (see doc).
Regarding your last question (in the PS), you never have to use pipelines. They're just convenient ways of, well, pipelining multiple preprocessing steps. I think it's good practice, but you're welcome to use any other preprocessing system you prefer, Scikit-Learn is very modular, you can just use any piece you like without using the rest.
Hope this helps!

Thanks a ton @ageron


Add returning trick to relations in insertGraph / upsertGraph

It would be great to have a way to return relation data in this methods, similar to how returning * trick works. Currently it's applied only to root query, relation queries return just an id.
This is useful when you want to return all model data without using another select queries.

As I mentioned in gitter, I don't think this should be added to objection. returning only works on positgres (and oracle maybe?) and implementing this yourself is just a couple of lines.
function deepReturningAll(builder) {
  builder.mergeContext({
    onBuild(builder => {
      if (builder.isInsert()) {
        builder.returning('*');
      }
    })
  })
}

...

LeatherType.query(trx).insertGraph(input).modify(deepReturningAll)

Could it be added to recipes then?

@kibertoad Feel free to add it there

@koskimas returning trick is mentioned in many places in the docs and is very useful, I'm using it everywhere and love it.
If adding it to graphs is that easy, why not add it as a method so users don't need to copy-paste it from project to project?

I see this becoming another snakeCase = true conversation with you @vladshcherbin. Not going that road this time.


missing image for Spanish localizacion of Business Central sandbox 14.5.35970.0

Hi,
I can't find the tags for downloading the 14.5 version for Spanish localization, in:
https://mcr.microsoft.com/v2/businesscentral/sandbox/tags/list
I tried inspecting with Get-NavContainerImageLabels the update28-es and the latest, to see if we could work with that, but both are pointing to version 14.4:
PS C:\WINDOWS\system32> Get-NavContainerImageLabels mcr.microsoft.com/businesscentral/sandbox:update28-es

country    : ES
created    :<PHONE_NUMBER>17
cu         : update28
eula       : https://go.microsoft.com/fwlink/?linkid=861843
legal      : http://go.microsoft.com/fwlink/?LinkId=837447
maintainer : Dynamics SMB
nav        :
osversion  : 10.0.14393.3204
platform   : 14.0.36066.0
tag        : <IP_ADDRESS>
version    : **14.4.35602.36102**

We need this in order to patch a customer extension that failed upgrade in saas to version 14.5.35970
On-prem images are correctly tagged.
Any help is appreciated.
Thanks

Just requested a rebuild of the latest builds, will monitor progress.
14.5 should also be marked update29 (some was wrongfully tagges as update28)
14.4 is update28 as seen above

mcr.microsoft.com/businesscentral/sandbox:update29-es-ltsc2019 should be there now


libuihook compilation fails on Windows

Hello there,
When running cmake . in the libuihook folder, I get this error :
PS D:\_DEV\electrontest\node_modules\iohook\libuiohook> cmake .
-- Building for: Visual Studio 15 2017
-- The C compiler identification is MSVC 19.10.25019.0
-- The CXX compiler identification is MSVC 19.10.25019.0
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error: File D:/_DEV/electrontest/node_modules/iohook/libuiohook/include/config.h.in does not exist.
CMake Error at CMakeLists.txt:97 (configure_file):
  configure_file Problem configuring file

Is there any config.h file that could have been omitted in the repo ?
Note : In cloned this repo in my node_modules folder.
Thanks

Ok nevermind, this was really a compilation issue. On windows, one should use e.g. MSYS2 to use autoconf and cmake and generate that config.h file. Closing this for now.

@Djiit could you share the resulting .dll file?

@AjManoj Yes, i just switched to another working lib.

May I ask which one ?
Le 12 févr. 2018 14:09, "tobeorla"<EMAIL_ADDRESS>a écrit :

@AjManoj https://github.com/ajmanoj Yes, i just switched to another
working lib.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/WilixLead/iohook/issues/30#issuecomment-364917759,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHZtN5bIzpMJAKMPQ1MIZRe9n-_31Rpks5tUDfvgaJpZM4PbX1H
.

@Djiit can you explain how do you solved this more detailed? Thanks