Categorization (personal, business, services)

Hi @joaquimadraz ,
I am doing some live coding on Twitch and I would like to contribute to your project, so I tried to take a look and I've seen that there is something in the "nice to have" features that I could try to tackle: the categorization (personal, business, services) feature.
I would like to know how do you imagine that feature is supposed to be implemented. If you provide some enough instructions I think I can start work on it. In the meantime I'll try to setup the project on my local machine and undestand something about it.
Thank you,
joe.

Hey @joebew42 thanks for reaching out. I'd be pleased to have another contributor 👍
So my initial goal with the categorization was to have an idea of how the expenses are distributed.
For instance:

These stats could be put on the "All payments" page, and later this could also be used to personalize the messages on emails and monthly pagination.
What do you think?

Hey, perfect! In the meantime I'm trying to get the application up and running. I see that there are a few enhancements we can add in order to help people with the onboarding process (setup, seed, etc ...) for the development.
As soon as I am ready I will back to you to ask further details about this feature, ok? Do you have a gitter channel for this project? A place where we can chat about it could be useful. What do you think?

Hi @joaquimadraz ,
I just had the time to run the application on my local machine and play with it a little bit.
I am here to ask you some questions.

How it is supposed a user should categorize a payment? We have to consider to add a new field category for each payment entry? Like the simple mock up that you can find below?

If yes, where we can start with? Can we consider to add a free editable input text box? Or, we may have to consider to have a separate page, like settings -> categories where the user can organize all categories and then choose one of it through a dropdown menu' from the create payment modal window?

Can we associate more than one category to a payment?

How do you think the page all payments should be changed? Right now we have this kind of visualization:

The user will switch to the "categorization visualization" by clicking on a link above the list, or do you have in mind some different mechanism?

What the percentage value will represent there? The number of payments for each category, or the overall expenses for each category?

I think it could be useful if you share some mockups and some more details about this feature.
Thank you again,
joe!

Thank you for all your answers, so clear!

Hi @joaquimadraz,
just another question related to the Other category. What happens when the user don't specify a category? We may have to fall back to a default one (e.g. Other) or we may allow user to specify an empty category? In this case, how it is supposed to show the categorization for all the payments that haven't a category? :thinking:

I think it would be interesting to separate Other and Uncategorized payments.
Here are some things that comes to mind:

All existing payments (prior to the release of this feature) that are not categorized are placed in the Uncategorized category.
Other is something we don't have a category for.
New payments require a category.

Does it make sense?

It makes sense. So, we can end up with these requirements:

All the payments - prior to the release of this feature - will be migrated to a Uncategorized category (we translate this by adding the value uncategorized in the category field?).
Other will be the default value of category for all the new payments.
The field category is mandatory and cannot be blank.

Right?

Hi @joaquimadraz ,
I have in mind to end up with this API for the spendings summary, let me know what you think about:
HTTP GET /api/subscriptions/summary

{
  data: {
    currency: "EUR",
    currency_symbol: "€",
    spendings: [
      {category: "travel", amount: 239.99},
      {category: "videogames", amount: 999.99},
      {category: "other", amount: 9.99},
      {category: "uncategorized", amount: 1900.00},
    ]
  }
}

So, basically the fields currency and currency_symbol comes from the User, and the spendings will be a list of all expences grouped by categories. In this way we let the client (e.g. Reactjs) to decide what to do with this data. What do you think?

Hey @joebew42, sorry for the late reply.
Looks good. Just one thing, should we also return the total spending in this request to calculate the percentages?

Looks good. Just one thing, should we also return the total spending in this request to calculate the percentages?

Of course, we can adapt the API in order to return the total spending too!


[deploy] docs for Storj ?

Feedback Fish request for a deployment guide for https://www.storj.io/
We an create a stub!

Haven't seen community interest for this - closing for now, but feel free to reopen if you're interested in working on this?


investigate edx data transformation process

User Story
We want to understand how edx.org data is transformed from edx data package to aggregated schema using simeon CL https://github.com/MIT-IR/simeon.
This issue is created for investigation, the goal is to understand the transformation process and see if it's possible to do it on our end. As part of this, we should create a discussion post if anything comes up

https://docs.google.com/document/d/1EIW1g1Y0lTeesFRXZ5-I9oADXJg1iNyzHOihLKNzZOo/edit


configure options for enabling fips warning

Hi,
few OSes already provide support for FIPS enablement on the system. FIPS standard defines only several 'safe' crypto algorithms, but Vim uses pk-zip, blowfish and blowfish2 encryptions, which are not among the safe algorithms defined by FIPS.
But I am aware many Vim users are satisfied with current Vim's cryptography and it is mentioned in help pages these cryptographic methods are not designed for protection of sensitive data, I would like you to consider adding this patch to Vim project. In my humble opinion it is valid compromise for current usage of Vim and FIPS.
The patch is about adding configure options (which are disabled by default) --enable-fips-warning (turns on FIPS warning), --with-system-fips-file=PATH (the link to system-fips file, applicable only when --enable-fips-warning is used and default path is /etc/system-fips) and --with-fips-enabled-file=PATH (the link to fips_enabled file, applicable only when --enable-fips-warning is used and default path is /proc/sys/crypto/fips_enabled).
The first option - --enable-fips-warning - enables FIPS warning, which is shown when:

:X is used
when user opens encrypted file
It looks this way (f.e. when blowfish2 cm is used):

Need encryption key for "test"
Warning: This cryptography is not FIPS140-2 compliant.
Enter encryption key: *
The warning is shown only when FIPS is installed and active, which is known to user if:

system-fips file exists
fips_enabled file contains '1'

That's the reason why two other configure options are there - --with-system-fips-file=PATH and --with-fips-enabled-file=PATH - I'm not sure if other OSes (tried on Fedora+RHEL) have different places for these files, so I created options for setting different paths for these two files.
I tested the new configure options manually (general run, when files are missing, when paths are configured to different files)+ I ran 'make test' (I regenerated configure file, configure Vim with huge features and enabled fips warning, then ran 'make' and 'make test') and they worked correctly.
Would you mind adding this patch to Vim project?

This is not useful.  As I understand it there is a FIPS certification mechanism used by some people.  Thus one has to check that the system (not just a program) is certified.  Telling users something is not certified is quite pointless, since by default nothing is certified.  It would be useful to tell the user that what he is doing is FIPS certified, but that won't ever happen for Vim.

@brammool What is the point of saying that a program is FIPS certified in FIPS certified system? The patch is about integration of Vim (never will be FIPS certified - so let's warn them at least about it) into such FIPS certified systems.

@zdohnal 's arguments are not totally without merit, yet the proposed change looks a little pointless to me: Vim's encryption methods are not meant to protect users against a serious cryptographer with a fast computer and that's that — if you want really secure encryption (and if you believe that it is possible to get really secure encryption in today's world), don't use Vim for it, period.
@zdohnal : if you think you can write and debug an even better encryption subsystem in addition to the three Vim already has (and which are needed for compatibility with earlier versions of Vim), go ahead, Vim is free (as in speech) and open source code. Once such code is reasonably well tested and made part of Vim, it might be a little less pointless to warn about weak encryption methods.
Best regards,
Tony.

@tonymec Hi Tony,
I created the patch with your first paragraph in mind - Vim's cryptography is not meant to protect against serious attacker - that's why I did not try to create new cryptography for Vim. But even if I wrote the new algorithm, it still wouldn't be enough, because old algorithms would be still there and their removal (only way to make Vim FIPS compliant, AFAIK) would cause serious troubles for users during update.
With all mentioned above, I wrote the patch, which seemed like compromise for both sides. Vim could stay in FIPS certified system and Vim didn't have to design a new cryptography conforming FIPS. Maybe it is just me, but I cannot imagine system without Vim (at least Linux/Unix ones) :)
@brammool Would it be acceptable to change current message/add a message in crypt_check_method() function in src/crypt.c to (it will be shown for every encryption):
'Using encryption XY. See ':help 'cm''.'
and add into runtime/doc/options.txt a sentence (at the end of 'cm' help) similar to following:
'Encryptions mentioned above are not meant for protecting critical or sensitive data and they do not comply with existing security standards, e.g. FIPS 140-2.'
Would you mind considering such change, Bram?

@tonymec Hi Tony,
I created the patch with your first paragraph in mind - Vim's cryptography is not meant to protect against serious attacker - that's why I did not try to create new cryptography for Vim. But even if I wrote the new algorithm, it still wouldn't be enough, because old algorithms would be still there and their removal (only way to make Vim FIPS compliant, AFAIK) would cause serious troubles for users during update.
With all mentioned above, I wrote the patch, which seemed like compromise for both sides. Vim could stay in FIPS certified system and Vim didn't have to design a new cryptography conforming FIPS. Maybe it is just me, but I cannot imagine system without Vim (at least Linux/Unix ones) :)
@brammool Would it be acceptable to change current message/add a message in crypt_check_method() function in src/crypt.c to (it will be shown for every encryption):
'Using encryption XY. See ':help 'cm''.'
and add into runtime/doc/options.txt a sentence (at the end of 'cm' help) similar to following:
'Encryptions mentioned above are not meant for protecting critical or sensitive data and they do not comply with existing security standards, e.g. FIPS 140-2.'
Would you mind considering such change, Bram?

If we make a list of all the standards that Vim does not support, I'm
sure it will get quite long.  Adding just one gives a false sense that
we even tried.
Certification works to add something to certain software, it should be
obvious that if the certification isn't claimed that the software does
not comply.
I also don't see how it matters, since you can still edit plain text,
right?    Using ROT13 is
second best :-).
--
GOD: That is your purpose Arthur ... the Quest for the Holy Grail ...
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

I think FIPS may not be the right standard to reference. What @zdohnal is raising is that vim is giving a false sense of security to its users by claiming encryption capabilities. Would it help merge this patch if it printed instead:

Warning: This cryptography is not secure; use gnupg instead.

Why do I suggest this text? It's because vim provides an implementation of blowfish, but no unit tests or interoperability tests are performed, key derivation is undocumented; could be ok, though no-one can vet for it. Additionally, mixing application code with cryptography is considered bad practice (the first point is an indication on why that's bad), and furthermore blowfish is a relic of the past, could have been an interesting choice 20 years ago when the alternative is DES, though today there are options like AES which are considered the baseline.

I agree with @nmav , IMHO such warning is better than illusion of security given by current algorithms.
When user uses pk_zip algorithm in Vim, Vim already warns him about algorithm being 'weak', which gives false sense of security of the other algorithms implemented in Vim are secure. IMHO such warning is relevant for all three cryptomethods - so Vim  could show:
"Warning: Using a weak encryption method; use external cryptographic tools for stronger encryption."
or
"Warning: Using a weak encryption method; see :help 'cm'"
and then in help pages can be:
"Encryptions mentioned above are not meant for protecting critical or sensitive data. Please use external cryptographic tools for stronger encryption."


goBack header missing and got an error page

[x] I have read the Get Started - Installation section
[x] I have read and done the Get Started - Setup Android section
[x] I have read and done the Get Started - Setup iOS section
[x] I have already searched for the same problem

Environment

Technology
Version

Flutter version
2.2.2

Plugin version
5.3.2

Android version
10

iOS version
14.6

Xcode version
last

Device information:
Description
Expected behavior:
When called goBack() I would go back to the previous page with the same context as previously.
Current behavior:
I got an unauthorized page because the page is accessed without the right header (no header is provided).
Steps to reproduce

InAppWebView(
  initialOptions: InAppWebViewGroupOptions(
  crossPlatform: InAppWebViewOptions(javaScriptEnabled: true),
    android: AndroidInAppWebViewOptions(
      mixedContentMode: AndroidMixedContentMode.MIXED_CONTENT_ALWAYS_ALLOW,
      useHybridComposition: true,
      supportMultipleWindows: true,
    ),
    ios: IOSInAppWebViewOptions(allowsInlineMediaPlayback: true),
  ),
  onCreateWindow: (InAppWebViewController controller, CreateWindowAction createWindowAction) async {
    if (await canLaunch(createWindowAction.request.url.toString())) launch(createWindowAction.request.url.toString(), headers: createWindowAction.request.headers ?? const <String, String>{});
      return true;
  },
  initialUrlRequest: URLRequest(
    headers: MyCustomHeader,
    url: Uri.parse(MyCustomUrl),
  ),
),

Create a webview
Fill the initialRequest property with an url & a header
On the webview web page, go to an other website like google.com
Call the goBack method somewhere, you can see that you go back to your first page but the header is missing... As my first webpage require header for authentification, I got an error page...

Images
Stacktrace/Logcat

@always-together12 I'm not sure. I did some PR and maybe it is fixed today.I need to take time to check if I can reproduce it.
Do you reproduce it ?


Alternative method of habit notation

Hello,
I wanted to ask if you'd be open to an alternative method of looking for habits rather than nesting them under a habits block that doesn't work with formatting (headings).
What if instead of this opinionated nested block, we were able to tag each habit with something like #habit, so they could live anywhere in the document?

@someinternetguy since I'm tracking habits by habit text, to implement this format I'm planning to provide a habit template (regex). For your example (not final):
\d{2}:\d{2} {{habit}}

And 2 options:

Parent marker: Habits - to nest under as it is now.
Habit marker: #habit - you can put them anywhere in habit title, they will be stripped, tracking pushups and drink water habits. And if there is more than one instance on a given day, it will be counted.

If that is fine, just stay tuned, I will implement it when I find the time.

@c6p that regex looks good to my novice eyes. It would be cool if you could make it a user customizable regex so everyone can use the format they like... Also, I think having a customizable habit tag like you mentioned above would be good too. Thanks for your response and work on this 🤩.

Thanks again @c6p! I finally had some time to test it out this evening, and it works a charm... :)


Add support for loading custom label fonts in imglab

Closes #2732

Weird how Github Actions can sometimes cancel a job for no reason.

Nice, thanks :)

Oh I wasn't expecting for this to get merged before getting some feedback from who reported the issue.
I couldn't test it properly, because copy and paste don't work well with Wayland in the dlib toolkit.
The font is changed though, but I might need to handle the UTF-8 strings when loading the dataset...
I will do that tonight, probably.

Ah ok. Well still looks like a sensible thing to have in any event 🤷♂😁

I've started working on that, and I can get imglab to load the Chinese characters from the XML files, just by changing:
diff --git a/tools/imglab/src/metadata_editor.cpp b/tools/imglab/src/metadata_editor.cpp
index f3e0e49d..c7e59cf1 100644
--- a/tools/imglab/src/metadata_editor.cpp
+++ b/tools/imglab/src/metadata_editor.cpp
@@ -656,9 +656,13 @@ on_overlay_rect_selected(
     const image_display::overlay_rect& orect
 )
 {

-    overlay_label.set_text(orect.label);
+    overlay_label.set_text(convert_utf8_to_utf32(orect.label));
     display.set_default_overlay_rect_label(orect.label);
     display.set_default_overlay_rect_color(string_to_color(orect.label));
}

However, I can't get the overlay rectangle to display them properly...
Maybe its label field needs to be a dlib::ustring? But that would be a breaking change.

Yeah draw_string(), called in image_display::draw(), needs to get a ustring or it's just drawing ASCII.  image_display should probably just interpret the label as utf8 always.  I'm not sure where the conversion to ustring should live though.  Could be in draw_string() but IDK, that adds a memory allocation on every call along with the conversion and that will end up making the UI laggy sometimes.  Not this UI probably, since there isn't a lot of text, but others I would expect.
Although the code in convert_utf8_to_utf32() could be refactored into a function like this:
convert_utf8_to_utf32(some_utf8_string.begin(), some_utf8_string.end(), [](unichar ch) {
   visits the unicode characters in order.
});

That could be done without memory allocations and then draw_string() could use that and everything would just work with utf8 all the time.

Ah, after adding convert_utf8_to_utf32()() all over the place in image::display::draw(), everything works.
However, I can't see how we can make convert_utf8_to_utf32() allocation free, some_utf8_string.size() ≤ some_utf32_string.size(), right?
Maybe I am fundamentally wrong, I have a very shallow understanding about character encoding…

convert_utf8_to_utf32

Yeah that function as is can't be allocation free.  A function like this could be:
convert_utf8_to_utf32(some_utf8_string.begin(), some_utf8_string.end(), [](unichar ch) {
   visits the unicode characters in order.
});

Just needs to use something other than that istringstream to iterate over the input string and then instead of appending characters to that new string it would call the provided lambda.

At the risk of souding a bit dumb, it's not clear to me where the output uttf-32 string would be stored :sweat_smile:

I will give it a go later (still not sure I am understanding this correctly, maybe it's too late in here)


Fix: light theme

Closes https://github.com/surrealdb/surrealist/issues/340
Theme in terms of "dark" or "light" doesn't seem to work well with CodeMirror - for some reason themeType is not set as state, but based on what theme extension was added (if I understand codemirror source correctly).
That's why I refactored theme into it's own Compartment.

LGTM, thanks!


Allow metaCreator to be an object literal

Codecov Report

Merging #4 into master will not change coverage.
The diff coverage is 100%.

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


Chips get data doesn't function 1.0.0-beta

Hello, I have a problem, I use version 1.0.0-beta ans with chips I don't arrive to get the data, it's bugged ?
Thanks for your responses

Problem is resolved, I use this code for select data on chips:
var elem = document.querySelector('.chips');   var instance = M.Chips.getInstance(elem);   console.log( instance.chipsData[0]['tag']);


Add ability to directly give a playlist URL

Hi,
I've been using ytermusic a lot and it's been great. I still have a few quality of life improvements I'm thinking about discussing, but this one is definitely the biggest issue, since it actually prevents me from listening to certain music.
The Youtube Music search being what it is, sometimes the right album or song does not show up in the results. In the official website/mobile app, you have to - for example - navigate manually to the artist to get to the album and start playing it.
Making the search better seems like a lot to ask, so here's my idea: a mode where you paste something like https://music.youtube.com/playlist?list=<playlist_id> (or just the playlist ID), then ytermusic shows you the songs in that playlist like in the search view, and you can then decide to play it, just like from the search view.
How does that sound?

I think it's a great idea gonna work onto that when I have time


GUI for basic export functions (mirrors command line)

This should support our standard export functions, and it will probably be based on Electron.

We now have very different UI plans.


Strange behavior of the JavaExec.getCommandLine() method

Expected Behavior
I wrote a simple plugin that adds a task TestTask to the project:
public class TestPlugin implements Plugin<Project> {
    @Override
    public void apply(@Nonnull Project project) {
        TaskContainer tasks = project.getTasks();
        Task task = tasks.create("test-task", TestTask.class);
    }
}

I want to get command line arguments for bootRun task from TestTask:
public class TestTask extends DefaultTask {
    @TaskAction
    void run() {
        var log = getLogger();
        TaskContainer tasks = getProject().getTasks();
        JavaExec bootRun = (JavaExec) tasks.findByName("bootRun");
        bootRun.getCommandLine().stream().forEach(l -> log.warn(l));
    }
}

./graldew test-task

In Gradle version 6.5.1 this code prints path to Java executable and all command line arguments.
Current Behavior
In Gradle version 6.8.2 getCommandLine() method returns list with single null value.
Context

I have a project with a lot of sub-projects, each of which is a SpringBoot application. For integration testing, I wrote a plugin that launches all services. To do this, I receive the bootRun task command line arguments, modify them somewhat and create processes using the ProcessBuilder class. In 6.8.2 version my plugin doesn't work as I can't get the command line arguments for the bootRun task.

Steps to Reproduce
I prepare simple project to demonstrate the bug.
Your Environment

ArchLinux, OpenJDK Runtime Environment (build 14.0.2+12)

Build scan URL: https://scans.gradle.com/s/l3l7ukhflixm4

It seems that it fails because executable is not set. And executable is set only in exec: https://github.com/gradle/gradle/blob/06e40c03cdda4151f01e5f3529faea97c4abd08f/subprojects/language-java/src/main/java/org/gradle/api/tasks/JavaExec.java#L152
There's an extremely fragile workaround: crafting the command line manually.
Get the path to java via internal API: org.gradle.internal.jvm.Jvm.current().getJavaHome()
Add the jvm arguments:
String arguments = run.getAllJvmArgs().collect {
                        if (it != null && it.contains(" ")) "\"$it\"" else it
}.join(" ")

Classpath:
List<String> classPath = new ArrayList<String>()
classPath.add(org.gradle.util.CollectionUtils.join(File.pathSeparator, run.getClasspath()))
String classPathString = classPath.collect {
    if (it.contains(" ")) "\"$it\"" else it
}.join(" ")

The final result:
${org.gradle.internal.jvm.Jvm.current().getJavaHome()}/bin/java ${command} -cp $classPathString ${run.getMain()}"


Enable exactOptionalPropertyTypes

To quote from the TypeScript team lead:

If we were to start TypeScript over again, we believe the behavior of strictOptionalProperties would be on by default
https://github.com/microsoft/TypeScript/issues/44421

This configuration brings a pretty critical element to the type-soundness (critical because it drastically changes the behavior of operations that check for keys). SameValueZero checks remain unchanged, anyway, so there's basically no downside to having this rule enabled. The https://github.com/microsoft/TypeScript/pull/43947 from Anders provides some more context, as well.
Thankfully, this codebase was already pretty close to the mark, with only a few little minor things to update to increase strictness. Note a similar PR: https://github.com/bufbuild/protobuf-es/pull/431

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

Let's enable exactOptionalPropertyTypes when it becomes the default with TSC.


Image Location: In subfolder under current folder

I use obsidian setting:
Default locaton for new attachments: In subfolder under current folder
Subfolder name: attachments
And plugin setting:
Image Location: Default attachment location
When i add thumbnail, attachment saves in /attachments.
It should be saved in path/to/current/notefolder/attachments
Thank you for plugin and #1 realization. I like not being dependent on cloud services

I'll check this out when I get a chance

Trying to fix this unearthed a bunch of other problems with the way I was determining the file path, so thanks for bringing it up. Still working on it, though.

I fixed this in 1.2.6. Thanks for pointing it out.

Спасибо вам! ❤


Breakout ui-banners into separate CRDs  (Headers/footers, consent-banner)

Internal Reference: SURE-7619
We currently shove a bunch of data into the ui-banners CRD. Rancher Government would like to apply changes to the header and footer (text, colors) independently of the bannerConsent value.
Ideally, we break these out as separate resources that can be updated independently.
{"loginError":{"message":"","showMessage":"false"},"bannerHeader":{"background":"#4f924f","color":"#fff","textAlignment":"center","fontWeight":true,"fontStyle":null,"fontSize":"14px","textDecoration":null,"text":"HEADER TEXT GOES HERE"},"bannerFooter":{"background":"#4f924f","color":"#fff","textAlignment":"center","fontWeight":true,"fontStyle":null,"fontSize":"14px","textDecoration":null,"text":"FOOTER TEXT GOES HERE"},"bannerConsent":{"background":"#27292e","color":"#fff","textAlignment":"center","fontWeight":null,"fontStyle":null,"fontSize":"14px","textDecoration":null,"text":" LONGF ORM LOGIN Consent BANNER TEXT GOES HERE","button":"Accept"},"showHeader":"true","showFooter":"true","showConsent":"true"}

Suggest we add:
ui-banner-header and ui-header-footer
The UI will use these if they are defined, otherwise it will continue to use the single banner setting.
This allows someone to deploy seperate CRs for the banner - this will then be used by the UI and editable in the UI. Existing deployments and the default will still be to use the single, combined resource.

that would work for us @nwmac .

This will require a small backend change to allow the new individual settings to be retrievable by an unauthenticated user.

Created backend issue https://github.com/rancher/rancher/issues/44439

PR for backend changed: https://github.com/rancher/rancher/pull/45528

e2e tests are sufficient. moving to done


Allow the parsing of composer 2 installed.json

This PR allows to parse the installed.json generated by composer 2 as the format changed.
Due to this change it was not possible anymore to get the current versions of the installed tools.
https://getcomposer.org/upgrade/UPGRADE-2.0.md

vendor/composer/installed.json format changed:

packages are now wrapped into a "packages" top level key instead of the whole file being the package array

Thanks @philipheimboeck! I'm running into this issue as well.
Do you have any idea why CI would be failing?
  [RuntimeException]
  Could not scan for classes inside "C:\projects\phpqa\vendor/sebastian/phpcpd/src/" which does not appear to
  be a file nor a folder

Looks like some issue with running on windows tbh. I doubt this PR caused it though.
The error isn't present on other PRs, but they are all much older. Maybe it's an issue with composer 2.0?

I've been using this fork for a couple of weeks now and it works fine. Any chance we can get this merged soon?

any news on it?

It's going to be fixed in https://github.com/EdgedesignCZ/phpqa/pull/218/commits/673aab47c7fcc518fdae59437f56c6ebfa69187a


feat(konflux): update buildah to support subscriptions

## Secure Coding Practices Checklist GitHub Link
- https://github.com/RedHatInsights/secure-coding-checklist

## Secure Coding Checklist
- [ ] Input Validation
- [ ] Output Encoding
- [ ] Authentication and Password Management
- [ ] Session Management
- [ ] Access Control
- [ ] Cryptographic Practices
- [ ] Error Handling and Logging
- [ ] Data Protection
- [ ] Communication Security
- [ ] System Configuration
- [ ] Database Security
- [ ] File Management
- [ ] Memory Management
- [ ] General Coding Practices

@skateman

/reset

/retest

/retest

You don't need this as https://github.com/RedHatInsights/remediations-consumer/pull/330 makes it obsolete.

Superseded by #330


Principal labels are not filled for telemetry v2

Telemetry v2 misses source and destination principal labels. These two attributes are not yet available in wasm data accessor API. We need to add a new wasm API to read SAN from local and peer cert.

@kyessenov @mandarjog

The current workflow as far as I understand it:

istio_authn receives a config about the principal binding (SAN peer cert or JWT origin user)
once computed, it saves under dynamic metadata istio_authn, with struct {request.auth.principal: "..."}; it also adds source.user, source.principal, etc.
mixer filter reads this from dynamic metadata and sets the values from there for source.principal
mixer filter sets destination.principal directly not using authn_filter. There's some parsing logic to strip SPIFFE prefix.

@diemtvu to confirm.
Note that there is no TCP istio_authn filter.

Ok, source.principal is actually computed the same way AFAICT. So we should be OK re-computing the value in mixer v2 architecture for source and destination principal.
request.auth.principal should be delegated to authn_filter.

Example value: cluster.local/ns/default/sa/server
Note the stripped SPIFFE prefix:
 X509v3 Subject Alternative Name: critical
                URI:spiffe://cluster.local/ns/default/sa/server

Fixed by https://github.com/istio/proxy/pull/2503


Error in getAttestationAttesterCount() attestation.aggregationBits = null

Describe the bug
In some sim test multi-node multi-thread run the node error repeatedly with
2021-03-28 11:28:38 [NODE 2 NETWORK]  error: Gossip attestation validation threw a non-AttestationError message=Cannot convert undefined or null to object
TypeError: Cannot convert undefined or null to object
    at Function.from (<anonymous>)
    at getAttestationAttesterCount (/home/runner/work/lodestar/lodestar/packages/lodestar/src/chain/validation/attestation.ts:163:16)
    at Object.validateGossipAttestation (/home/runner/work/lodestar/lodestar/packages/lodestar/src/chain/validation/attestation.ts:17:19)
    at validateCommitteeAttestation (/home/runner/work/lodestar/lodestar/packages/lodestar/src/network/gossip/validatorFns/attestation.ts:23:11)
    at /home/runner/work/lodestar/lodestar/packages/lodestar/src/network/gossip/validator.ts:44:11
    at Eth2Gossipsub.validate (/home/runner/work/lodestar/lodestar/node_modules/libp2p-interfaces/src/pubsub/index.js:594:13)
    at Eth2Gossipsub.<anonymous> (/home/runner/work/lodestar/lodestar/node_modules/libp2p-gossipsub/src/index.js:328:39)
    at Generator.next (<anonymous>)
    at /home/runner/work/lodestar/lodestar/node_modules/libp2p-gossipsub/src/index.js:27:71
    at new Promise (<anonymous>)

The error is thrown in this function
https://github.com/ChainSafe/lodestar/blob/a20c540d0f585107a5952cdc4cc0a45810c922f7/packages/lodestar/src/chain/validation/attestation.ts#L162-L164
Expected behavior
Should never throw this
Steps to Reproduce
Run the sim tests, here are full debug logs for that run
multinode-multithread-test-logs.txt

it's good that we can reproduce in e2e bc I saw the same issue when I sync Prater
2021-03-28 01:56:46 [NETWORK]         error: Gossip attestation validation threw a non-AttestationError message=Cannot convert undefined or null to object
TypeError: Cannot convert undefined or null to object
    at Function.from (<anonymous>)
    at getAttestationAttesterCount (/root/lodestar/packages/lodestar/src/chain/validation/attestation.ts:163:16)

Possibly resolved in #2289 ?

it's still an issue with ssz 0.8.0


refactored search into decorate function and added to all headers

Description

Fixed the other header style pages not showing the search iframe.
Refactored into a decorate function to be shared between header layouts.
Some minor cleanup and ran buildCss command which applied style changes from previous commits.
Issues:

Button style changed after previous commits need to investigate (WIP)

Related Issue

https://jira.corp.adobe.com/browse/DEVSITE-121
Motivation and Context

To add search to all helix pages.
How Has This Been Tested?

Header layout 1 page:
https://search-on-all-headers--adobe-io-website--adobe.hlx.page/
Header layout 2 page:
https://search-on-all-headers--adobe-io-website--adobe.hlx.page/apis
Screenshots (if appropriate):
Types of changes

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

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

I fixed up the button style and it looks better now.


Requiring students to sign-off on code of conduct

One thing that was done at HackGenY was requiring students to sign off (via an iPad using a system called Smart Waiver) on the code of conduct before entering the event.
I felt that this was super-effective, and though our ticket registration flow does include prompts about the code of conduct currently, I feel something should be done to make the COC more prevalent.
(Perhaps simply putting together a mass email a few days before the event would be just as effective.)

cross-platform checkin app

Since clear is mobile-friendly now, we can just add it there.

Students now need to sign a waiver, and agree to uphold the code of conduct upon registration.


[PyTorch] Debug checkpointing with operation-based API

Description
This PR debugs checkpointing with the operation-based API (see https://github.com/NVIDIA/TransformerEngine/pull/707). The checkpointing logic is similar to the module-based API.
Type of change

[ ] Documentation change (change only to the documentation, either a fix or a new content)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Infra/Build change
[ ] Code refractor

Changes

Debug checkpointing with operation-based API

Checklist:

[x] I have read and followed the contributing guidelines
[x] The functionality is complete
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[x] 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

/te-ci pytorch

/te-ci pytorch

/te-ci pytorch

/te-ci pytorch

Merging with approval from @ptrendx and @ksivaman.


aria-modal attribute breaks jsx-a11y/aria-props rule

The aria-modal attribute is the part of the W3C recommended implementation for modals: https://www.w3.org/TR/wai-aria-practices/#dialog_modal
https://www.w3.org/TR/wai-aria-1.1/#aria-modal
They also use it in their example of the dialog modal:
https://www.w3.org/TR/wai-aria-practices/examples/dialog-modal/dialog.html
It seems to be listed as a registered prop in aria-query as of 0.7.0: https://github.com/A11yance/aria-query/blob/master/src/ariaPropsMap.js#L116
However, when included in a JSX file I am seeing the error error  aria-modal: This attribute is an invalid ARIA attribute  jsx-a11y/aria-props

Sorry, just noticed I am behind on version. Apologize for the noise! Closing now


update all metadata when updating a secret

I noticed that the labels (and ownerReferences) are only propagated when a secret is created, so you cannot update the values on an existing secret.  While all-out replacing the metadata is a little assertive, I think it's consistent with gitops best-practices and other kubernetes controllers.

LGTM, thnx for the merge Request :-)


(GH-1285) Add project init command

This adds a project init subcommand that creates a new Bolt project. When
specifying a filepath using bolt project init [filepath], the project
directory will be created at the filepath. Otherwise, the project
directory is created in the current working directory.

CLA signed by all contributors.

I think the changelog still needs an update (unless there's a reason not to?) otherwise lgtm

Updated. I ended up rebasing which overwrote the suggested change you made. All fixed now!


X.A.FloatKeys: Export Type ChangeDim

Description
Include a description for your changes, including the motivation
behind them.
Checklist

[x] I've read CONTRIBUTING.md

[x] I've considered how to best test these changes (property, unit,
manually, ...) and concluded: that the type is not currently exported

[x] I updated the CHANGES.md file

Well, so are P and G and they are exported, if it's exported it's going to appear on the hackage page so people know what it represents without looking through the source code.

Well, so are P and G and they are exported, if it's exported it's going to appear on the hackage page so people know what it represents without looking through the source code.

Oh the Haddocks do indeed look quite horrible with this not exported—thanks!


Build error on Windows VS2019

Hi @StRigaud ,
I saw your progress and was just trying to build it on my system. Visual Studio (2019, Windows 10) complains about a header file not found which is part of llvm apparently... Did you experience similar issues? I will try to find and build llvm ... Not sure if this leads to something.
Any hint is welcome!
Thanks!
Robert
1>------ Build started: Project: ZERO_CHECK, Configuration: Release x64 ------
2>------ Build started: Project: Clic, Configuration: Release x64 ------
2>CLE.cpp
2>cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 220 (OpenCL 2.2)
2>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\include\vcruntime.h(58,10): fatal error C1083: Cannot open include file: 'vadefs.h': No such file or directory
2>cleGPU.cpp
2>cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 220 (OpenCL 2.2)
2>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\include\vcruntime.h(58,10): fatal error C1083: Cannot open include file: 'vadefs.h': No such file or directory
2>cleKernel.cpp
2>cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 220 (OpenCL 2.2)
2>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\include\vcruntime.h(58,10): fatal error C1083: Cannot open include file: 'vadefs.h': No such file or directory
2>cleAddImageAndScalarKernel.cpp
2>cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 220 (OpenCL 2.2)
2>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\include\vcruntime.h(58,10): fatal error C1083: Cannot open include file: 'vadefs.h': No such file or directory
2>cleSmallerOrEqualConstantKernel.cpp
2>cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 220 (OpenCL 2.2)
2>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\include\vcruntime.h(58,10): fatal error C1083: Cannot open include file: 'vadefs.h': No such file or directory
2>cleMaximumZProjectionKernel.cpp
2>cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 220 (OpenCL 2.2)
2>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\include\vcruntime.h(58,10): fatal error C1083: Cannot open include file: 'vadefs.h': No such file or directory
2>cleAbsoluteKernel.cpp
2>cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 220 (OpenCL 2.2)
2>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\include\vcruntime.h(58,10): fatal error C1083: Cannot open include file: 'vadefs.h': No such file or directory
2>cleBuffer.cpp
2>cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 220 (OpenCL 2.2)
2>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\include\vcruntime.h(58,10): fatal error C1083: Cannot open include file: 'vadefs.h': No such file or directory
2>tiffreader.cpp
2>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\include\vcruntime.h(58,10): fatal error C1083: Cannot open include file: 'vadefs.h': No such file or directory
2>tiffwriter.cpp
2>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\include\vcruntime.h(58,10): fatal error C1083: Cannot open include file: 'vadefs.h': No such file or directory
2>utils.cpp
2>cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 220 (OpenCL 2.2)
2>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\include\vcruntime.h(58,10): fatal error C1083: Cannot open include file: 'vadefs.h': No such file or directory
2>Generating Code...
2>Done building project "Clic.vcxproj" -- FAILED.
3>------ Build started: Project: ALL_BUILD, Configuration: Release x64 ------
4>------ Skipped Build: Project: INSTALL, Configuration: Release x64 ------
4>Project not selected to build for this solution configuration
========== Build: 2 succeeded, 1 failed, 0 up-to-date, 1 skipped ==========

Hi Robert,
I just re-compiled it on a windows 10 with VSC++ 2019. No complains on my side except known warnings from possible loss of data during type conversions.
vadefs.h is called from the vcruntime.h which is a windows files. A quick search on my machine find vadefs.h here:
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.27.29110\include
You seems to be missing some files in your Visual Studio install, either incomplete or corrupted. I would redirect you to the VS2019 c++ installation guide. Hopefully a quick clean reinstall may fix the issue.
PS: LLVM is installed on my machine:
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\LLVM

You seems to be missing some files in your Visual Studio install, either incomplete or corrupted.

Indeed! I just build on another Windows machine and it worked immediately!
Thanks for the heads-up and see you soon!


Cannot read property 'find' of undefined

I'm not able to run a witness in production. I got stuck with the following error few seconds after starting the node:
/home/node/byteball-witness/node_modules/byteballcore/headers_commission.js:91
								var next_mc_unit_props = storage.assocStableUnitsByMci[parent.main_chain_index+1].find(function(props){return props.is_on_main_chain});

TypeError: Cannot read property 'find' of undefined
    at /home/node/byteball-witness/node_modules/byteballcore/headers_commission.js:91:91
    at Array.forEach (<anonymous>)
    at /home/node/byteball-witness/node_modules/byteballcore/headers_commission.js:89:22
    at Statement.<anonymous> (/home/node/byteball-witness/node_modules/byteballcore/sqlite_pool.js:115:6)

See related code in byteballcore :
https://github.com/byteball/byteballcore/blob/master/headers_commission.js#L91
Any idea how to solve this?

I don't think it's problem specific to byteball-witness. I had the same problem with Windows full wallet (2.4.1):

It has been syncing at 0% for a while and then crashed.

Fixed in https://github.com/byteball/byteballcore/commit/9f3bcff7cfbbe680b4985d8e489b5eee859a27af


feat: add support for configuring scheme in http probes

Signed-off-by: rakshith<EMAIL_ADDRESS>Fixes #985

@iliapolo Can you please take a look at this PR when you get a chance?

@rvshettigar Should I give this PR another round of review?

@iliapolo  Sorry, I missed your comment. Yes please, the PR is ready for your review. Thanks.

💚 All backports created successfully

Status
Branch
Result

✅
k8s-22/main

✅
k8s-23/main

Questions ?
Please refer to the Backport tool documentation


[Regression] C# project fails to build for no apparent reason

Godot version:
master / 252c841d7
OS/device including version:
Manjaro Linux KDE 18.1
Issue description:
Since I updated my engine build from 0d8f1ba6a to 252c841d7, I've been no longer able to build my project and there is no helpful message logged on the console except for this:
ERROR: call_build: A Godot Engine build callback failed.
   At: editor/editor_node.cpp:4840.

The only other messages I have are these, but I'm not sure if they are related because I had the same messages when I reported #29117 but I didn't have any build problem before the update:
ERROR: reload: Condition ' !obj_type ' is true. returned: ERR_BUG
   At: modules/mono/csharp_script.cpp:2807.
ERROR: get_class_info: GetTypeInfo fallback. Bug!
   At: ./core/type_info.h:91

With a recent update, I can no longer reproduce this error so I will close this issue for now.


questions about HQS algorithm

Hello,
Thank you for your excellent work!! But for now I have 2 questions.
1.I found that in your code, the "search" function calculate p * p.log() for every softmax grad of the image, this is "H" in the paper.However, in your paper, HQS is E[N - H].
2.Also, it is very possible that HQS for some timestep is <0 after N-H because N is not always > H(even if N and H are normalized using formulation 11 in the paper). But Figure 4 shows that HQS is always >0.
Can you please explain why?Thanks!

Hi,
Thanks for your questions.
We actually take HQS = norm(mean) + (1-norm(entropy)). So this HQS is always > 0. We are sorry for the confusion in the "search" function and we will fix it soon.

Thanks for your reply~Actually when I use "search" function in my task, it shows very sight changes of "entropy" value  between different time step.Like this:(all of them ≈ 49.9)
metrics-entropy_t100: 49.91398239135742
metrics-entropy_t150: 49.917816162109375
metrics-entropy_t200: 49.92081069946289
metrics-entropy_t250: 49.90937805175781
metrics-entropy_t300: 49.90165710449219
metrics-entropy_t350: 49.89959716796875
metrics-entropy_t400: 49.89561080932617
metrics-entropy_t450: 49.90335464477539
metrics-entropy_t500: 49.90515899658203
metrics-entropy_t550: 49.89979934692383
metrics-entropy_t600: 49.90167236328125
metrics-entropy_t650: 49.90288543701172
metrics-entropy_t700: 49.903568267822266
metrics-entropy_t750: 49.904762268066406
metrics-entropy_t800: 49.9051513671875
metrics-entropy_t850: 49.905784606933594
metrics-entropy_t900: 49.906009674072266
after using "norm" (formulation 11) I get metrics_list =
[0.7290342113230397, 0.8811686345746291, 1.0, 0.5463215258855586, 0.23993339388434756, 0.1581895246745383, 0.0, 0.30729639721465335, 0.37889797154102334, 0.16621253405994552, 0.24053890402664244, 0.2886769603390857, 0.3157735392067817, 0.36315470784135634, 0.3785952164698759, 0.40372388737511355, 0.41265516197396307]
It looks useful after "norm" function.  May I know that in your experiment if the difference between "entropy" value also slight?Maybe one explaination is that the grad is very small for every pixel.
Thanks a lot! If HQS is useful for me, I will appreciate it and cite your paper!

I'm glad we can discuss this together.
In my observation, for some images and text prompts, the entropy value could be very similar, just as your result. But it is not for all cases. For example, in the following results of "angry" manipulation, the entropy shows a great difference.
metrics-entropy_t100: 13.857027053833008
metrics-entropy_t150: 13.123653411865234
metrics-entropy_t200: 13.512639045715332
metrics-entropy_t250: 8.670392990112305
metrics-entropy_t300: 8.984338760375977
metrics-entropy_t350: 10.061752319335938
metrics-entropy_t400: 3.1760663986206055
metrics-entropy_t450: 1.5881437063217163
metrics-entropy_t500: 1.5926451683044434
metrics-entropy_t550: 1.4157923460006714
metrics-entropy_t600: 8.859975814819336
metrics-entropy_t650: 9.858148574829102
metrics-entropy_t700: 10.278231620788574
metrics-entropy_t750: 13.4658842086792
metrics-entropy_t800: 1.4716432094573975
metrics-entropy_t850: 5.805893898010254
metrics-entropy_t900: 13.193365097045898
Also, the entropy of different sampled images could be varied. Therefore, in practical scenarios, we typically sample 100 images and calculate the average HQS under the same text prompt. This approach helps in stabilizing the score by averaging out the variations.
To gain a deeper understanding of these results, it is beneficial to examine the gradient visualization in the file named 'grad_seq.jpg'. This could probably provide insights for your observation.

Thanks for your reply!I will try with other photoes.


Loading via Smithy and Json produces different result

I have repro, runnable via scastie.
Given the following Smithy:
$version: "2.0"

namespace a_test

@mixin
structure A {
    @required
    aMember: String
}

@mixin
structure B {
    @required
    aMember: String
}

structure MyStruct with [A, B] {
}

When you load this model through a ModelAssembler and extract the mixins of a_test#MyStruct$aMember, you'll get:
[a_test#A$aMember, a_test#B$aMember], but if you serialize to json and then load it again, you'll get: [a_test#B$aMember].
I'd like to fix it, but I'm not sure which one is at fault. I'd think the json one is at fault, and I believe the faulty logic is in software.amazon.smithy.model.loader.ApplyMixin.
Let me know which one is wrong, and I can work on a fix

I found the problem. So that rogue apply statement is the thing that revealed the bug, though it isn't itself the real issue. This issue will surface for any mixin where multiple mixins affect the same member and a trait is apparently introduced by the final shape.
The problem is right here. This block will effectively overwrite the existing builder. There's a block above that which specifically wants to account for multiple mixins, but the result is being ignored in this case.

The saga continues. It seems there was some broad assumption that members wouldn't be touched by multiple mixins.

Thanks a bunch @JordonPhillips, I certainly did not realize the serialized model was invalid.

It's not invalid, semantically it is equivalent, it's just a bit strange. There's probably a good reason for doing that which I'm forgetting at the moment


firecracker: Setup rootfs to be RO

Setup rootfs to be RO both from the VMM point of view and the
VM point of view.
Fixes: #1632
Signed-off-by: Manohar Castelino<EMAIL_ADDRESS>

/test

Let's unify with other architectures in a follow on PR.
LGTM

Added issue to track comments to closure
https://github.com/kata-containers/runtime/issues/1642
/cc @grahamwhaley @Pennyzct @nitkon @alicefr @devimc @egernst @jodh-intel

@devimc our daily build was successful this morning and it already included this commit. So, I think no issues for s390x

@alicefr but this commit is for firecracker and AFAIK fc is not running on s390x

Hi~
@devimc @mcastelino thanks for the notification~ ;)
I'm always thinking that I should find a time to switch to ro for qemu part when you @devimc changed it for x86_64 in #1390.
And since firecracker hasn't been ready for aarch64. maybe later in the future. ;)

Hi~ @devimc @mcastelino I have already raise the related PR #1660, ptal. ;)


⚠ CodePush has degraded performance

In b11276e, CodePush (https://codepush.appcenter.ms/v0.1/public/codepush/update_check?deployment_key=Fzqu71x4FXhOaKcAiwpqXkFQddjgYl2dIUW2K&app_version=4.4.1) experienced degraded performance:

HTTP code: 200
Response time: 24973 ms

Resolved: CodePush performance has improved in b45f805.


Bad constant value for epochSlots

These two lines are correct for mainnet and stagenet but is, in general, incorrect:
https://github.com/input-output-hk/cardano-node/blob/master/cardano-node/src/Cardano/Tracing/Tracers.hs#L352
https://github.com/input-output-hk/cardano-node/blob/master/cardano-cli/src/Cardano/CLI/Ops.hs#L176
These should be fixed sooner rather than later.
This issue was found by members of the Cardano Operators Guild.

There is still a hardcoded EpochSlots in the logging machinery which needs to be removed.

See #1085 for the hard-coded 21600 in the tracing.

The hard coded EpochSlots value in the Tracing module has been removed.


Fonts

Also need to install the appropriate fonts?

You can install MS Core Fonts

true, but it would be cool if the installer did everything needed to you know, install it! :)

I think that is more relevant to wine tweaking while this little script purpose is just an installation helper. It's still true and I agree with your idea about doing everything that needed to be done, maybe like unattended mode thing, or additional menu to select some setting(s).
I will try to write some code although can't promise new update. Thank you for your idea.

Hi @wolfen351 The font rendering will be improved with the latest update


Image scenario - notebook generation is broken

System Information (please complete the following information):

Model Builder Version: current main
Visual Studio Version

This should be in the next build we release right?

Yep

Is this the same as https://github.com/dotnet/machinelearning-modelbuilder/issues/1890?

Nope,, should be a different issue

#1849

Not repro this issue on latest main.

Notebook Editor [Preview]: <IP_ADDRESS>5404
ML.Net Model Builder 2022: <IP_ADDRESS>5901


Fault tolerance for eks deploy

Description
This PR introduces fault tolerance for the eks deploy subcommand by introducing a recovery file for storing deploy state.
The eks deploy is split into multiple stages and the state file is updated after each stage:

Gather ASG info: Retrieve the ASG object and gather required info
Set ASG max capacity: Make sure there is enough max size capacity to scale up
Scale up: Launching new nodes with new launch config
Wait for new nodes: Wait for new nodes to be ready and verify everything is OK in k8s
Cordon nodes: Cordon old instances in cluster ASG
Drain nodes: Drain Pods on old instances
Detach instances: Remove old nodes from ASG
Terminate instances: Terminating detached instances
Restore ASG max capacity: Restore the ASG into original max capacity

The state file is generated into the working directory ./.kubergrunt.state and persisted after each successful stage. If the eks deploy command fails for some reason, execution resumes from the last successful state. The existing recovery file can also be ignored with the --ignore-recovery-file flag. In this case the recovery file will be re-initialized.
The state is implemented with simple boolean flags instead of a state machine library. The stages in eks deploy are linear and there is no complex state handling, so a state machine library seemed overkill.
To better modularity and keeping action and verification stages separate, the scaleUp function is split into actual scale up and verification functions. This allows safer re-execution in case scale up was successful but verification fails for some reason.
Other notable things

Removing defer setAsgMaxSize and moving that to the last stage. If we're retrying using the recovery file, the original defer functionality could potentially lead to unexpected behaviour. I'm open for discussion on this, though.

Kubernetes drain and cordon operations are still executed for the whole set of existing nodes - I assume these are idempotent and can safely be executed multiple times.

As the AWS operations for detaching and terminating instances are batched, the command can still fail if previous detach, for example, was a partial success. Same applies to termination. Don't necessarily think this will be an issue

Documentation

README updated
cli option documented

TODOs

[x] Ensure the branch is named correctly with the issue number. e.g: feature/new-vpc-endpoints-955 or bug/missing-count-param-434.
[x] Update the docs.
[x] Keep the changes backwards compatible where possible.
[x] Run the pre-commit checks successfully.
[x] Run the relevant tests successfully.
[x] Ensure any 3rd party code adheres with our license policy: https://www.notion.so/gruntwork/Gruntwork-licenses-and-open-source-usage-policy-f7dece1f780341c7b69c1763f22b1378
[ ] Maintainers Only. If necessary, release a new version of this repo.
[ ] Maintainers Only. If there were backwards incompatible changes, include a migration guide in the release notes.
[ ] Maintainers Only. Add to the next version of the monthly newsletter (see https://www.notion.so/gruntwork/Monthly-Newsletter-9198cbe7f8914d4abce23dca7b435f43).

Related Issues
Fixes #109

Thanks for the review. I reworked the logic quite a bit.

Looks like there is a bug:
[] time="2022-01-10t21:49:15z" level=info msg="beginning roll out for eks cluster worker group eks-cluster-dnjdbl-additional-2022011021394957890000000d in us-east-1" name=kubergrunt
[] time="2022-01-10t21:49:15z" level=info msg="successfully authenticated with aws" name=kubergrunt
[] time="2022-01-10t21:49:15z" level=info msg="retrieving current asg info" name=kubergrunt
[] time="2022-01-10t21:49:15z" level=info msg="successfully retrieved current asg info." name=kubergrunt
[] time="2022-01-10t21:49:15z" level=info msg="\tcurrent desired capacity: 2" name=kubergrunt
[] time="2022-01-10t21:49:15z" level=info msg="\tcurrent max size: 4" name=kubergrunt
[] time="2022-01-10t21:49:15z" level=info msg="\tcurrent capacity: 2" name=kubergrunt
[] time="2022-01-10t21:49:15z" level=info msg="no max retries set. defaulted to 40 based on sleep between retries duration of 15s and scale up count 2." name=kubergrunt
[] time="2022-01-10t21:49:15z" level=info msg="starting with the following list of instances in asg:" name=kubergrunt
[] time="2022-01-10t21:49:15z" level=info msg="i-068c52a32617f04e0,i-0d31992bc468dc970" name=kubergrunt
[] time="2022-01-10t21:49:15z" level=info msg="launching new nodes with new launch config on asg eks-cluster-dnjdbl-additional-2022011021394957890000000d" name=kubergrunt
[] time="2022-01-10t21:49:15z" level=info msg="updating asg eks-cluster-dnjdbl-additional-2022011021394957890000000d desired capacity to 0." name=kubergrunt
[] time="2022-01-10t21:49:15z" level=error msg="failed to set asg capacity to 0" name=kubergrunt
[] time="2022-01-10t21:49:15z" level=error msg="if the capacity is set in aws, undo by lowering back to the original capacity. if the capacity is not yet set, triage the error message below and try again." name=kubergrunt
[] time="2022-01-10T21:49:15Z" level=error msg="*awserr.requestError ValidationError: New SetDesiredCapacity value 0 is below min value 2 for the AutoScalingGroup.\n\tstatus code: 400, request id: 15dece0b-6ee9-4257-a56e-42358af28475\n/home/circleci/project/eks/asg.go:153 (0x15710b1)\n/home/circleci/project/eks/asg.go:46 (0x15703b5)\n/home/circleci/project/eks/deploy_state.go:203 (0x1578ab6)\n/home/circleci/project/eks/deploy.go:72 (0x1576ee5)\n/home/circleci/project/cmd/eks.go:419 (0x158a5b1)\n/home/circleci/.go_workspace/pkg/mod/github.com/urfave/cli@v1.22.4/app.go:526 (0x5e36e5)\n/home/circleci/.go_workspace/pkg/mod/github.com/urfave/cli@v1.22.4/command.go:174 (0x5e4459)\n/home/circleci/.go_workspace/pkg/mod/github.com/urfave/cli@v1.22.4/app.go:407 (0x5e2454)\n/home/circleci/.go_workspace/pkg/mod/github.com/urfave/cli@v1.22.4/command.go:373 (0x5e659f)\n/home/circleci/.go_workspace/pkg/mod/github.com/urfave/cli@v1.22.4/command.go:102 (0x5e48f4)\n/home/circleci/.go_workspace/pkg/mod/github.com/urfave/cli@v1.22.4/app.go:279 (0x5e1668)\n/home/circleci/.go_workspace/pkg/mod/github.com/gruntwork-io/go-commons@v0.8.2/entrypoint/entrypoint.go:35 (0x615a78)\n/home/circleci/project/cmd/main.go:66 (0x158c8a8)\n/usr/local/go/src/runtime/proc.go:225 (0x438ed6)\n\tmain: fn()\n/usr/local/go/src/runtime/asm_amd64.s:1371 (0x46c021)\n\tgoexit: BYTE\t$0x90\t// NOP\n" error="ValidationError: New SetDesiredCapacity value 0 is below min value 2 for the AutoScalingGroup.\n\tstatus code: 400, request id: 15dece0b-6ee9-4257-a56e-42358af28475"

Yes, I think asg := state.ASGs[0] is a value assignment rather than a reference. Since some of the stages mutate the ASG we should pass the reference, instead:  asg := &state.ASGs[0]

Ah makes sense! Will cut a new test release and update the integration test branch.

Integration testing build is here btw: https://app.circleci.com/pipelines/github/gruntwork-io/terraform-aws-eks/1698/workflows/9e334364-7615-4c6d-8e8e-cfdc8c5d4485

Not 100% sure the test failures were related. I kicked off the tests again.
https://app.circleci.com/pipelines/github/gruntwork-io/terraform-aws-eks/1698/workflows/4c25d48e-7f65-4dcc-a778-58290c6ad0ff

I discovered a bug while testing this manually with an existing EKS cluster.
Since maxRetries is needed (and calculated) in gatherASGInfo, the calculated default value was lost for subsequent invocations due to the skip condition. If --max-retries option was omitted, the value was never re-calculated and was always set to 0, obviously leading to any stage relying on that to fail.
I fixed that by creating a method ensureMaxRetries that is invoked even when GatherASGInfoDone is true. This allows the user to override the value across retries.
The previous EKS module test was successful and now I've verified the functionality manually step by step, as well.

This is a cool feature. I look forward to reviewing it soon.

Just kicked off another regression build: https://app.circleci.com/pipelines/github/gruntwork-io/terraform-aws-eks/1709/workflows/a947a9a8-3124-4190-9c4b-8d4cbcc329c9
If that passes, I think we can merge this in!

Thanks for the review! I removed the extra assertion, so think we're ready to release this now!

Thanks for the reviews! Merging this in now!


WiX: only setup SDKROOT for native platform

While this would be nice, the SDKs are co-installed to the same location, so I'm just going to close this for now.


The weight of conv is not quantized, right?

From utee/quant.py, I can only find the process of adding quantized layer between different layer. But when it comes to quantized weight of conv, I can not find it.
So I wonder why you do not quant weight of conv, because it is importance in process of quantification.

when I run python quantize.py --type cifar10 --quant_method linear --param_bits 8 --fwd_bits 8 --bn_bits 8 --gpu 0.
It prints Traceback (most recent call last):
File "quantize.py", line 64, in
sf = bits - 1. - quant.compute_integral_part(v, overflow_rate=args.overflow_rate)
File "/home/hjs/pytorch-playground-master/utee/quant.py", line 14, in compute_integral_part
v = v.data.cpu().numpy()[0]
IndexError: too many indices for array
I am looking for your help 救救可怜的孩子吧，代码没跑通，进行不下去

weights are quantized to integers within a certain range defined by the bit-depth (args.param_bits) before being de-quantized to float. Layers are added to quantize activation.


Prettier, husky, et al are a broken mess

We've adopted some linters but we don't have a happy path to really use them. Right now if you're developing on our repo you use the --no-verify flag and what's the point?

Thanks @froi


Lock certain keys to their position in QWERTY

I'm pretty dead set on the punctuation keys being where they are. I personally want to keep them there. Can I lock those (or other) keys to stay in place throughout the annealing process?

i'm getting around this by simply omitting them from all the data. i'm making pretty significant changes that allow for arbitrary layouts, keymaps, and letter lists to do this, and to include the Planck EZ since that's the keyboard i use. PR coming soon

#18 Has a solution to this issue :)


Increment version for template releases

Increment version for template releases

I'm not done with my testing, there will be more releases and the PR to update azure-sdk-template will be made in master, not my branch, when I'm done with my tests.

Closing this out. Template's version was updated in Master and this branch was one just for testing.


Add feedback with current version

When clicking the "Feedback", a GitHub "new issue" page will be opened with version label already set, since the labels of an issue are not easier to be removed by the issuer than the title or body. However, the label of version must be created before, otherwise, there will be no label assigned automatically.

I edit the version field in package info of REST server and web portal to match the version of the system, does pom.xml of launcher also need? @yqwang-ms
There will be 2 more steps in the release process:

Modify the version field in the package.json of REST server and web portal.
Create the version label on GitHub issue.

Theoretically, a Travis validation task could be added on pai-v-prefixed branch to ensure them.

Coverage decreased (-15.4%) to 49.708% when pulling 8a87a845a0b5d5a24504d4568e1275461f1cf773 on qixcheng/webportal/add-version into 462a5bd37d60055002e7f86942bba422649e7b7d on master.


[NCL-8366] Integrate missing service URLs

We agreed to wait for backend fix first so that it can be fully tested before it's merged.


Update tray-indicators to v1.3

Adds a new icon that shows the current amount of ammo the cannon has.
Simplified some of the code.

Don't close PRs and open new ones. You can just push to the same branch.

Needs rebased

Marking as draft for now. Please make the requested changes, then mark the plugin as ready for review.


Analyse pipeline logs

It would be very useful to have some (bash ou python) scripts for analysing quickly the pipeline logs:

show the processing time for each user
extract logs of one particular user for a particular day for debugging

This commit https://github.com/PatGendre/e-mission-server/commit/13fe65bb78e76e65ea4a3b62af325e0b46c13fed shows how to do it in a notebook.
TODO : deploy on tracemob server ;
if Ok translate to a python script and run it periodically


Is the last layer in distributional critic optimized (jax implementation)?

Hi! I was wondering if the last layer in the distributional critic used in dmpo, for example, is optimized in the jax implementation, since it is instantiated in the call function and not in the init?
https://github.com/deepmind/acme/blob/98c4204b9be7f327035bf1dbef26aa820cc4c1ec/acme/jax/networks/distributional.py#L373-L414

It should, to check, you can take a look at the params initialized. It's a common pattern to create hk.Module inside call. You can find other examples in the Haiku examples.


Application crashes

I run
  npm install jshint -g
  tns plugin add nativescript-liveedit

Then node watch in another terminal, uninstalled the app and added the following code to my app.ts:
   [....]
  var liveedit = require("nativescript-liveedit" );
  liveedit.debugMode(true);
  application.start();

Result: 'the app has stopped' (on emulator)
Output of terminal with node watcher running on:
Pushed to Device:
Pushed to Device: ....
Pushed to Device: ...
Starting application...
Starting application...
Starting application...

Did you rebuild the app via a tns run or tns deploy?

yes via tns build
On Wed, Jan 13, 2016 at 5:59 PM, Nathanael Anderson <
<EMAIL_ADDRESS>wrote:

Did you rebuild the app via a tns run or tns deploy?
—
Reply to this email directly or view it on GitHub
https://github.com/NathanaelA/nativescript-liveedit/issues/13#issuecomment-171363922
.

--
Manuel Gajo
Full-stack web Developer and Business Designer
www.manuelgajo.me http://www.manuelgajo.me
+39<PHONE_NUMBER> / +32 484 369 265
IMPORTANT: My e-mail is personal and PRIVATE and CAN'T be shared with any
third party company or organisation without my explicit authorisation.

tns build won't deploy it to the emulator/device.   So you won't be running the plugin on the device.  You need to do a tns deploy or tns run so that the plugin and new runtimes get deployed to the device.
My personal work flow on a new project is:
tns plugin add nativescript-liveedit
tns run android --emulator --geny x
(Start watcher in another shell/cmd window)
Start editing my code and letting the watcher keep things in sync on the device/emulator.
The next morning (or if I kill the emulator); I just do another tns run android --emulator again so that it starts up.    So I use it to start when I start working on the project again.   But I let the nativescript-liveedit keep everything in sync.

One note; anytime you add any new plugins or change any files in the app_resources folder; you need to do a tns run/tns deploy once to get everything resynced.  Neither my liveedit nor the built in livesync will sync app resources or plugins.

the fact is that it gives me the issue even with deploy.
However I'll eventually try it again later on.
In fact, besides not re-compiling assets automatically, livesync has the
only big limitation to  force me (most times) to re-build everything if an
error occurs.
On Wed, Jan 13, 2016 at 7:56 PM, Nathanael Anderson <
<EMAIL_ADDRESS>wrote:

One note; anytime you add any new plugins or change any files in the
app_resources folder; you need to do a tns run/tns deploy once to get
everything resynced. Neither my liveedit nor the built in livesync will
sync app resources or plugins.
—
Reply to this email directly or view it on GitHub
https://github.com/NathanaelA/nativescript-liveedit/issues/13#issuecomment-171397349
.

--
Manuel Gajo
Full-stack web Developer and Business Designer
www.manuelgajo.me http://www.manuelgajo.me
+39<PHONE_NUMBER> / +32 484 369 265
IMPORTANT: My e-mail is personal and PRIVATE and CAN'T be shared with any
third party company or organisation without my explicit authorisation.


Allow return code checks on all K tools

In #160, we add a feature to KRun that allows the expected return code to be checked (rather than just failing if it's non-zero). We should make this change generically in the cli_utils module.

It appears that run_process checks return codes: https://github.com/runtimeverification/pyk/blob/b46fdfbbf87bbd731f7fa00afca902ab2f86c705/src/pyk/utils.py#L373
Probably each of the uses that shows up here we should consider threading through the check: bool = False argument to run_process.

I believe this is done now.


PDF Download / Export Feature Request Proposal

Version information

Laravel: v5.7.9
Voyager: v1.1.10
PHP: 7.27
Database: 5.7.21 - MySQL Community Server (GPL)

Description of problem

Right Now there is no option to download data in PDF or any other format. It will be really great if any button added or any hook will be created which provide feature that can help to export data in PDF or any other format like XLS, TXT etc. from BROWSE BREAD
Proposed solution
I suggest two option to add exporting functionality of BROWSE BREAD

Add Export Button in BROWSE BREAD threw it user can export table data in document format like PDF, XLS etc
Create separate hook which add functionality as mention above.

Alternatives considered
Right now there is no option available in voyager so I am using laravel package to download database  in pdf format
Additional context

This has been requested before.  Right now, we have no plans to add export functionality.


Typescript 4.7 package.json exports

Bug Report
After reading about exports in 4.7 realeasenotes I wanted to test it out, but I can't make it work.
I created an example app of something I think should work. I would very much appreciate some help to make it work. Or understand why it should't work.
I get errors like Cannot find module 'dep' or its corresponding type declarations. If I open a node session It ut can import dep just fine.
🔎 Search Terms
typescript package.json exports
typescript package.json exports types definition
package.json exports types
package.json exports map  with types
🕗 Version & Regression Information
I think it has never worked... not sure
⏯ Playground Link
💻 Code
I make a repro case https://github.com/stoivo/test-typescript-package-exports
🙁 Actual behavior
Checkout the readme in example app
> tsc -p tsconfig.json

src/lol.ts:1:19 - error TS2307: Cannot find module 'dep' or its corresponding type declarations.

1 import {add} from 'dep';
                    ~~~~~

src/lol.ts:2:17 - error TS2307: Cannot find module 'dep/sub' or its corresponding type declarations.

2 import sub from 'dep/sub';
                  ~~~~~~~~~

Found 2 errors in the same file, starting at: src/lol.ts:1

🙂 Expected behavior
It to work

Just my two cents here but have you tried to set moduleResolution to nodenext in your tsconfig.json?

Yes it worked! Thaks, node16 also work.

Thanks alot.
src/lol.ts:1:19 - error TS2792: Cannot find module 'dep'. Did you mean to set the 'moduleResolution' option to 'node', or to add aliases to the 'paths' option?

1 import {add} from 'dep';
                    ~~~~~

Maybe the error message should be improved since it seam to recommend node. probably where I got it from.
I can't find much information about moduleResolution, do you have any links. I found the official https://www.typescriptlang.org/tsconfig#moduleResolution but I find it a bit lacking. How would I knoe that I need to switch to if to suport exporting?


Consider getting rid of zookeeper as a coordinator

The purpose of the coordinator is to allow nodes to come online and offline dynamically. This is achieved by the following 3 functions:

inform about nodes coming online/offline and mediate their addresses to each other
generate assignment for each keyspace based on required replication factor and a state of previous assignment (to move as few partitions as possible)
elect leaders for online replicas of the same partition

this could be done by a combination of gossip/raft and single-partition kafka topic


i() interaction i_ref arguments fail / do not drop variables under formulaic 1.0.0

Current solution: do not allow formulaic>=0.6.6. In general, the code is fragile and dependent on not necessarily stable formulaic naming conventions.


cli uncaught error mac

⠁ Processing…node:internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise */);
^
[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "function Error() { [native code] }".] {
code: 'ERR_UNHANDLED_REJECTION'
}
Node.js v21.7.1

Duplicate of #44


Error in Nextjs

Hi,
Just trying out this and getting an error:

ReferenceError: Headers is not defined
/node_modules/formiojs/Formio.js:1502:18)

Does this library not support server side rendering?

This is currently not supported in the 3.x branch as our renderer is very tightly tied to the DOM and browser objects. In the 4.x branch it will support server side rendering and client side attaching of events. This is currently in alpha if you want to test it (we don't have documentation yet and it isn't entirely stable).

Just wondering does it now support server-side rendering?

Theoretically it does but we haven't tested it out really yet so we aren't sure if there are any gotchas. We haven't had anyone willing to sponsor this work or provide a pull request so it remains theoretical so far.
With the 4.x branch we completely separated the rendering to html from the building of the form. This means that it should be possible to render out all the html on the server and then attach the form instance to the html on the client side. Like I said though, we don't have any practical examples of this yet.

I am closing the issue as it was created too long ago and there are no new comments here. I hope it was resolved. If not, please reopen it. Thanks!


[#103486222] Fix test failures for service names with brackets

Fixes this bug: https://www.pivotaltracker.com/story/show/103486222 - the solution proposed here may be controversial and I'm open to other suggestions if you don't like it.
The step definition for Then I am on a page with that <service name> in search summary text currently includes a check that the service name is in the q parameter in the URL of the page. This query string check is failing for searches including service names with brackets.
The CGI encoder encodes brackets as %28 and %29 but our app doesn't, so matches fail.
Using a URI encoder is worse because as well as encoding the brackets it encodes spaces as %20 instead of +, which our apps do.
Doing ad-hoc replacement of %28 and %29 in CGI-escaped strings feels too hacky, and who knows what other characters might cause the same problem in future.
So I propose to not check the query parameter at all, and just stick with the check of the content on the page. The scenario description is just that the submitted query appears in the search summary on the page - it doesn't mention anything about the query parameter, so I think removing that check from this test is OK.  It still does what the scenario demands.
An alternative would be to change the way the buyer app and search API encode and decode query strings, but as they are all working nicely as they are I don't see the point in changing them just so we can run this test.
I also have a question: should Gemfile.lock really be included in this repository? Or should it be removed and git ignored, as it seems to me like a file that is specific to what the local bundler has done, rather than something that should be shared and updated?

:+1:


Profile Updates

Currently Tom appears for scores between 23-26 points
Please replace with Josh Moore

Is Josh the one with the kid on his shoulders?

just about to email you 3 new pictures for Josh Moore

but yes - that is the right picture


no pre_logits

I found that the model trained does not work well in transfer, I suspect it might because the model in this repo does not come with pre_logits

Hi @ZhiyuanChen,
Thanks for your question.
It's strange since we used the same model pre-trained on ImageNet for transfer learning and we are getting quite good results (see Table 8 in our paper). We will try to quickly add the code for the fine-tuning so it will be easier to reproduce our results in transfer learning ;).
I don't understand very well your question about pre-logits, could you give me more context ?
Best,
Hugo

Hi @ZhiyuanChen,
Thanks for your question.
It's strange since we used the same model pre-trained on ImageNet for transfer learning and we are getting quite good results (see Table 8 in our paper). We will try to quickly add the code for the fine-tuning so it will be easier to reproduce our results in transfer learning ;).
I don't understand very well your question about pre-logits, could you give me more context ?
Best,
Hugo

Hi @ZhiyuanChen,
Thanks for your question.
It's strange since we used the same model pre-trained on ImageNet for transfer learning and we are getting quite good results (see Table 8 in our paper). We will try to quickly add the code for the fine-tuning so it will be easier to reproduce our results in transfer learning ;).
I don't understand very well your question about pre-logits, could you give me more context ?
Best,
Hugo

I was pretraining on ImageNet and fine tuning on ImageNet ILSVRC-2012.
In ViT, the head of the model is composed of a two layer mlp, with tanh non-linearity. The first fc layer is called pre_logits in the original implementation of google. The MLP is being replaced by a single fc layer during fine tuning.

Hi @ZhiyuanChen,
Thanks for your question.
It's strange since we used the same model pre-trained on ImageNet for transfer learning and we are getting quite good results (see Table 8 in our paper). We will try to quickly add the code for the fine-tuning so it will be easier to reproduce our results in transfer learning ;).
I don't understand very well your question about pre-logits, could you give me more context ?
Best,
Hugo

I was pretraining on ImageNet and fine tuning on ImageNet ILSVRC-2012.
In ViT, the head of the model is composed of a two layer mlp, with tanh non-linearity. The first fc layer is called pre_logits in the original implementation of google. The MLP is being replaced by a single fc layer during fine tuning.

Thank you for the details I better understand your question.
For DeiT there is no pre-training with an MLP head. For training we use a simple linear classifier.
Best,
Hugo

Thank you for the details I better understand your question.
For DeiT there is no pre-training with an MLP head. For training we use a simple linear classifier.
Best,
Hugo


Add request header strategies to allow extensibility

The default strategy behaves the same way as the original behaviour, which is to return the headers from the route rules.
Making this into a Strategy means that projects may add their own strategies to control which headers are shown in various circumstances.
This commit also includes some tidying up of the example request templates for cases when no headers are required for the request.
Resolves https://github.com/mpociot/laravel-apidoc-generator/issues/622

I'm actually not certain of this Wrt design and future issues), but I'll merge it. Life's too short to always worry about perfection. Thanks!👍

I renamed it to headers so the parsed route key names are the same as stages, and reordered the stages. https://github.com/mpociot/laravel-apidoc-generator/commit/4bf2ede4945a2728ded2214b1ea44e730eb7f41e
Tagging RC1 now.


adding tenant domain field to playground sample

Since we provide the authorization endpoint of IS as a input parameter we can  provide the tenant domain as a query parameter as well. Why do we need a separate input here ?

Closing the PR until conflicts are resolved.


Build failed MacOS M1 cannot set permissions on "/usr/local/include": Operation not   permitted.

Problem description
When i was building Velox on MacOS M1, It's not ok. I need someone help, thanks.
System information
Velox System Info v0.0.2
Commit: bf8f183e2c597a25548fed9ebfa6bd2ebdb29e3a
CMake Version: 3.27.8
System: Darwin-21.6.0
Arch: arm64
C++ Compiler: /Library/Developer/CommandLineTools/usr/bin/c++
C++ Compiler Version: <IP_ADDRESS>00029
C Compiler: /Library/Developer/CommandLineTools/usr/bin/cc
C Compiler Version: <IP_ADDRESS>00029
CMake Prefix Path: /Library/Developer/CommandLineTools/SDKs/MacOSX12.3.sdk/usr;/opt/homebrew;/usr/local;/usr;/;/opt/homebrew/Cellar/cmake/3.27.8;/usr/local;/usr/X11R6;/usr/pkg;/opt;/sw;/opt/local
Result copied to clipboard!
CMake log
ninja: Entering directory `_build'
[0/1] Install the project...
-- Install configuration: "Release"
-- Up-to-date: /usr/local/lib/cmake/range-v3/range-v3-targets.cmake
-- Up-to-date: /usr/local/lib/cmake/range-v3/range-v3-config-version.cmake
-- Up-to-date: /usr/local/lib/cmake/range-v3/range-v3-config.cmake
-- Up-to-date: /usr/local/include
CMake Error at cmake_install.cmake:68 (file):
  file INSTALL cannot set permissions on "/usr/local/include": Operation not
  permitted.

I solved this error by  chown  xxx /usr/local/include，thanks


Cannot show file path on error test

Hi all,
Could anyone tell me how to show detail file path (and line code) when test case failed?

As you can see, error summary doesn't show file path for failed test case.

Can you please try another browser. The error message depends on the browser. I just want to make sure if it is a browser issue or an issue of the reporter.
Thanks

hi @4kochi

I saw log in chrome developer console, it still has no file path.
Note: my webpack is already configured to generate sourcemap for all code.
Thanks

hi @4kochi
Do you know how to work around for this issue?
Thanks

@lvthanh101 I had this same problem but I'm using webpack as a preprocessor. But a found a solution that'll work if you use webpack. If you include 'sourcemap' preprocessor after 'webpack' in the preprocessors object and then do devtool: 'inline-source-map' in your weback config of your karma.conf.js you can get what you're looking for.
here's my example karma.conf.js:
var webpackConfig = require('./webpack.config.js')

module.exports = function (config) {
  config.set({
    basePath: '',
    frameworks: ['mocha', 'chai', 'sinon'],
    files: [
      { pattern: 'test/**/*.spec.jsx', watched: false, serverd: true, included: true },
      { pattern: 'test/**/*.spec.js', watched: false, serverd: true, included: true },
    ],
    exclude: [],
    preprocessors: {
      'test/**/*.spec.jsx': ['webpack', 'sourcemap'],
      'test/**/*.spec.js': ['webpack', 'sourcemap'],
    },
    webpack: {
      devtool: 'inline-source-map',
      module: webpackConfig.module,
      plugins: webpackConfig.plugins,
      externals: webpackConfig.externals,
      resolve: webpackConfig.resolve,
      performance: false,
    },
    webpackServer: {
      stats: 'errors-only',
    },
    reporters: ['progress', 'mocha'],
    mochaReporter: {
      colors: {
        warning: 'black',
        error: 'red',
      },
      showDiff: true,
    },
    client: {
      captureConsole: false,
    },
    port: 9876,
    colors: true,
    logLevel: config.LOG_INFO,
    autoWatch: true,
    autoWatchBatchDelay: 1000,
    browsers: ['Chrome'],
    singleRun: false,
    concurrency: Infinity,
  })
}

Here's my example test file:
import chai from 'chai'
var expect = chai.expect
chai.should()

describe('Example Class', () => {
  describe('some stuff', () => {
    it('should do something', () => {
      true.should.not.be.ok
    })
  })
})

Example test output:

As you can see above there's now a sourcemap indicating the file of containing the failing test and the line of the failing assertion at the end of the failing test:

    at Context.<anonymous> (webpack:///test/ExampleTests.spec.js:12:25 <- test/ExampleTests.spec.js:13229:25)

I'll let you all know if I find a better way.

Hi @esayler
Thanks for your response. However, my karma config already has 'sourcemap' in preprocessor and devtool is 'inline-source-map'. So I cannot still solve this problem.


withoutHeaders supports verification

fix #49607
Validation logic is copied from the validation headers (except with minor adjustments), see:
https://github.com/istio/istio/blob/e09586dc04198cda05224b7d26b6be237a37e7a3/pkg/config/validation/virtualservice.go#L141

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@wulianglongrd: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
3951f47462e31538ad8ffbfecd0af80dace8f4a5
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wulianglongrd: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
3951f47462e31538ad8ffbfecd0af80dace8f4a5
link
true
/test unit-tests-arm64

unit-tests_istio
3951f47462e31538ad8ffbfecd0af80dace8f4a5
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wulianglongrd: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc_istio
f0bf75cfcdb4f71f200c7547e062dcc7708d0dfe
link
unknown
/test integ-telemetry-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Just cross checking, none of these new validations would make previously valid VirtualService "invalid" now?

/test integ-telemetry-mc

Just cross checking, none of these new validations would make previously valid VirtualService "invalid" now?

I think it will not.

The documentation of istio.io clearly states that withoutHeader has the same syntax with the header, but has opposite meaning, so I think it is reasonable to refer to the verification rules of header.
https://istio.io/latest/docs/reference/config/networking/virtual-service/#HTTPMatchRequest


social imgs are cut off in bad ways

the social img for linkedin is cut off, we should prolly just use the regular wordmark logo for that space

We should do this if we can, but it's not clear to me we can specify a different og (or other) image for LinkedIn previews. https://www.linkedin.com/help/linkedin/answer/46687/making-your-website-shareable-on-linkedin?lang=en

We'll probably want to update the image we use for Greenhouse listings also:

as an additional note, this is how our greenhouse links appear on twitter

Pushing this to the next milestone, as we're pulling in https://github.com/pulumi/pulumi-service/issues/6596 as higher priority.
A few findings for when this gets picked back up:

We can't set multiple og:image tags for different sites, but in theory we should be able to get one image with the right ratios to work everywhere and/or set something specific up for twitter if that's the one outlier because they have their own tags.
Testing this locally and with the site previews doesn't work :(.  Probably have to set up ngrok to test this, but haven't verified that works.
For linkedin, image must be a 1.91:1 ratio (1200x627 px) and min 200px width
To test + verify metadata without actually posting https://www.linkedin.com/post-inspector/

Please add  and
For the image can we do a small test to see if LinkedIn picks up the correct array?
The goal is to keep the same image but add the dimensions, so it knows it is square,

And add a second image for LinkedIn with its dimensions:

Moving to use a rectangular og:image to fix this.

Just to update, we were able to specify an additional tag, twitter:image, to allow the square image to be used on Twitter by default and the rectangular one on LinkedIn.


feat: Implement custom sharding for iOS

Fixes #1665
Detailed documentation
This is the first implementation of the custom sharding feature, below assumptions were made:

flank does not validate provided json -- we trust the user that he/she knows what is doing
sharding-json is the source of truth -- no smart sharding applied
dump shards structure was required to be updated

Test Plan

How do we know the code works?

V1

build flank ./gradlew flankFullRun
create config ymlgcloud:
  test: [PATH]/EarlGreyExample.zip
  xctestrun-file: [PATH]/EarlGreyExampleSwiftTests.xctestrun
flank:
  max-test-shards: 2
  disable-results-upload: true
  disable-usage-statistics: true

run flank firebase test ios run -c=[YOUR CONFIG] --dump-shards
copy ios_shards.json, rename it and play around with shards, example: add another shard, move tests etc
add sharding-json: [PATH TO YOUR CUSTOM SHARDING JSON] to your config yaml
run flank firebase test ios run -c=[YOUR CONFIG] --dump-shards
observe new sharding in ios_shards.json
run flank firebase test ios run -c=[YOUR CONFIG]
test run should proceed and end normally with sharding that you created

V2

build flank ./gradlew flankFullRun
create config ymlgcloud:
  test: [PATH]/FlankTestPlansExample.zip
  xctestrun-file: [PATH]/FlankTestPlansExample/AllTests.xctestrun
flank:
  max-test-shards: 2
  disable-results-upload: true
  disable-usage-statistics: true

run flank firebase test ios run -c=[YOUR CONFIG] --dump-shards
copy ios_shards.json, rename it and play around with shards, example: add another shard, move tests etc
add sharding-json: [PATH TO YOUR CUSTOM SHARDING JSON] to your config yaml
run flank firebase test ios run -c=[YOUR CONFIG] --dump-shards
observe new sharding in ios_shards.json
run flank firebase test ios run -c=[YOUR CONFIG]
test run should proceed and end normally with sharding that you created

Checklist

[x] Documented
[x] Unit tested

For reference: #1736


CI is grabbing ESP32 pre-releases

So the issue is that ci-arduino which is used for continuous integration for my ESP32 libraries is failing because it is grabbing the latest alpha2 pre-release of ESP32 board. This in return causes the library CI to fail as there are bugs/changes in that release which won't let me compile my library.
How can I force it to use a specific board version?

we do this on purpose so we can fix libraries ahead of the release - pre-releases become releases pretty fast! you can fork/edit the installer if you need a different BSP version

we do this on purpose so we can fix libraries ahead of the release - pre-releases become releases pretty fast! you can fork/edit the installer if you need a different BSP version

Gotcha. I tried looking through the source code but it's very convoluted for a person who hasn't worked on it before. Can you refer to line/lines which can be modified to set specific BSP version?

https://github.com/adafruit/ci-arduino/pull/168


fix: conversations messages date handling inconsistency

In the backend, at the Message model definition, we can find date = models.DateTimeField(auto_now_add=True) which, when a new row is inserted, automatically sets the value of the date field to the current date regardless of the given value.
But, in the frontend, in the src/views/TheConversationsView.vue in the sendMessage() function, through WebSocket we send a parameter 'date': new Date() which is received, at the end of the process, in backend in the save_message() function from file mymap/consumers.py where we can see the date parameter used and passed to the Message.objects.create() function, but where its affected value will never be used.
That makes the parameter useless in the frontend.
Two solutions:

Keep the parameter in the frontend, and switch the date field of the Message model from models.DateTimeField(auto_now_add=True) to models.DateTimeField(default=timezone.now). With this default value, it will only fill the field upon create()/insertion if the later is empty. Upside is that it can offer a more precise time of sending, if the user encounters some poor internet connection or so. Major downside is that it'll require a more secure way of transmitting the date as it opens a "breach" where the user can bypass the normal VueJS implementation of the WebSocket and can transmit any date he wants (in the future or in the past if not handled).

Remove the frontend implementation of the date parameter making the backend the only one handling it by keeping the current model structure (date will correspond to whenever the backend receives the message, just as it is working right now).

Any thought? I would go for the second one. Easy fix and prevent headaches!
A lot of explanations but for some reason I randomly thought about that issue and went to test the possible vulnerability, didn't want to leave one open if I could fix it quickly!
I'm open to do this fix on a new branch whenever I'll get an answer here.

Hello Florent,
Thanks for the notice ! I would also go for 2). Would be great if you could implement it within a specific branch !

Hello Florent, Thanks for the notice ! I would also go for 2). But what is the impact for users having different timezones, everything will be aligned based on backend timezone ? Would be great if you could implement it within a specific branch !

If I'm not wrong, datetimes in postgre store timezones too ("+00:00" in database), so all the messages will be sync on this "+00:00" timezone. Once displayed in the frontend, it should automatically transform and use the client timezone. I'll try that out.