ARM Travis tests running on Emulator == SLOW

Just opening this ticket to keep a reminder, I'll look into getting a cloud instance to enable native tests on Arm hardware. I don't have access to ARMv6 or ARMv7 hardware but I can provide ARMv8 tests, which can emulate ARMv7 via AArch32 natively on the machines that support AArch32.
With the last meaningful ARMv6 machine being RaspberryPi 1 and with that all but long gone, I think we should be fine just testing v7 and v8.
What are the requirements for the client? Do we need to install a slave in the machine, like Jenkins, or is that done via SSH keys access?

No idea actually, the current CI tests use whatever API is provided by github. I should be able to run ARMv7 (Asus Tinkerboard) and ARMv8 (Sony Xperia) tests locally when actually required so the CI addition from #1864 is mostly for convenience. One problem with integration could be that I do not have administrative control of the project and it is unclear if/when xianyi is available again.

I see, that's not optimal.
I could use my cloud instance to keep a local loop and somehow exposing the results (webpage? webservice?) until we get travis to fire at it. Let me see what I can do on my side, and I'll ping you when I have something running, we can decide later.
Worst case scenario, we can try a CI on our personal repos, which we do have control. But would be good to have someone active in the community (like you) with admin access. :)

Apparently there is a company (and service) named shippable that provides free CI on ARMV8a hardware http://blog.shippable.com/shippable-arm-packet-deliver-native-ci-cd-for-arm-architecture

Interesting, would that work with Travis without need for admin access on the github project?

As far as I can tell it is a Travis-like service that would need the same admin access to set up, I just came across it in another context and wanted to put that information somewhere.

Got an instance running, @martin-frbg send me your public ssh keys so I can give you access to it. My email is<EMAIL_ADDRESS>

Given we don't have admin rights in the project, I'm thinking in using GitHub's API to track commits and pull requests, build a branch or a PR and then make the result available somehow.
Btw, it takes about 1/2 hour to build all four variants, what's the timeout on Travis? It's under 10 min for one variant, which we can make that the "CI loop" for pull requests, but do a full build + run benchmarks and BLAS-Testers on all TARGETs overnight.

It seems that it is 60min, also there is some monitor for 5min without output.
Probably some simple thing like buildbot can poll latest commit and trigger rebuild(s)

Right, if/when we get Travis triggering build on that machine, 60 minutes should be plenty for build-tests.
I'll think about the overnight tests in separate, as they'll need lots of cores to build, but only one to test, so need to balance the resources in the right way.

You can set up PID file as a mutex and skip builds while one batch is churning. It just takes some days to tune for purpose.

Anything will be better than yesterday, you know.

:)

So, I got a server building and running BLAS-Tester:
https://openblas.ddns.net/
This should get us going, at least for the basic support. We can work the Travis triggers once we have admin rights on the project.


fix: Recursively search parent directories for lefthook

Previously, only lefthook stuff under the current $PWD/node_modules was checked. Now, the current directory up until the Git root is checked (see try_exec function.
I did chang the formatting since it was really difficult to parse the shell script. If you want to change it back, let me know.
Closes #510
Closes #249 (stale / fixed)
:zap: Summary
Optimizations:

Don't waste time running a subshell with git rev-parse --show-toplevel when it is not needed
Does not attempt to run lefthook to determine if lefthook can be run (use command -v instead)'

slight performance improvement

Use exec to run commands

Makes process signals more reliable / less buggy

Note that this slightly changes the resolution algorithm. Before, it would look for ./node_modules/lefthook/bin/index.js, then<EMAIL_ADDRESS>etc. Now, it looks for ./node_modules/lefthook/bin/index.js, then ../node_modules/lefthook/bin/index.js, etc., all the way up to the git root. Once it reaches git root, then it goes back to the original $PWD and looks for<EMAIL_ADDRESS>and climbs up the directory tree for that path.
:ballot_box_with_check: Checklist

[x] Check locally
[ ] Add tests
[ ] Add documentation

Thank you for submitting a PR! I will take a look and come back in a few days.

Are you sure this will fix https://github.com/evilmartians/lefthook/issues/510? In the issue they have node_modules in a subdir, not the parent dir 🤔

Oh oops, you're right, it doesn't fix that issue. I was having issues where the existing lefthook binary couldn't be found because I was in a subdirectory of the root git directory - and I did not read that issue carefully enough and thought it was the same problem.

@hyperupcall , I've just reviewed the PR one more time. I can't think of a case when we need to check parent directories to find the lefthook executable in node_modules. What do you think about removing this part? Other optimizations look good to me.

@mrexox Sounds good - I have removed the recursive parent directory search. I have kept the other optimizations

Because the original changes of this PR did not fully fix the mentioned issue, and the current diff no longer reflecting the original issue, and the length of time that has passed since creating this issue, I'm closing this PR. If needed, someone else can pick up the torch :fire: - a fresh PR would probably be easier to review too


Delete deleted shards in retention service.

Overview
Previously the retension.Service would only delete expired shards but ignore already deleted shards in the local filesystem. If a shard directory was not deleted for some reason then this would cause the shard to never get checked and removed later.

thanks @benbjohnson...
@rbetts @gshif  will this be part of a 1.5.2 release?
We'd like to get this fix over to PayPal as soon as possible


Add presentations to sphinx

Follow up for #59. Add the possibility to embed presentations in sphinx documentation.
E.g.:
https://github.com/sphinx-contrib/slide

We should also update doc/introduction.rst with the latest changes from Readme.md.


Clipboard redirection

clipboard redirection for  images(bmp/jpeg) is not working.
If I copy the image in remote machine it is giving undefined format i.e cof9 & cofc.
In freerdp old version format is showing like "Dropdescription" and "UIDisplayed".

Working on current master (post 2.0.0-rc1)


build: prerender 404 and detail page

Adds routes file to prerender new pages
For now, projects details prerendered are hardcoded

Current dependencies on/for this PR:

main

PR #26   👈

This comment was auto-generated by Graphite.


Added support of method prefixes

Using prefixed methods is very comfortably for group methods by Models.
For example: instead of methods: get_user_info, get_partner_info, get_user_money, get_partner_money, send_message_to_user, send_message_to_partner
you can use: user.get_info, partner.get_info, user.get_money, partner.get_money, partner.send_message, user.send_message
with using two classes User and Partner
With methods dispatcher.add_class, dispatcher.add_object you can automaticaly load all models in folder (with importlib.import_module for example)
class Math:
def sum(self, a, b):
    return a+b

def diff(self, a, b):
    return a-b

dispatcher.add_class(Math)
dispatcher"math.sum"

16

Coverage remained the same at 100.0% when pulling a17fa266bc7abb3ed3f146247fd2c7948a902da3 on Santinell:master into f4b453def34a4b0da1ea7ad4217d5bc64fd10eb0 on pavlov99:master.

Thanks!
Version 1.9.2 with your pull request has been released: https://pypi.python.org/pypi/json-rpc/1.9.2


i686-pc-windows-gnu support

We have a rust binary with openssl that we need to cross compile for windows - both x86_64 and i686.
I was able to create a custom docker image for x86_64-pc-windows-gnu that works well.
I also tried to create a custom image for i686-pc-windows-gnu. There was no base image to customize, so I copied the Dockerfile.x86_64-pc-windows-gnu file to a new one, and changed some stuff around to make it use g++-mingw-w64-i686.
That got me further along - openssl-sys seems to compile correctly.
However, now I get these errors:
/rustc/c367798cfd3817ca6ae908ce675d1d99242af148\/src\libstd/backtrace.rs:229: undefined reference to _Unwind_Resume
This seems to stem from mingw64 for i686 using sjlj for exception handling instead of dwarf-2 which the rust compiler expects (according to this).
Has anyone here had success with this?
In the past, we had success with the japaric/i686-pc-windows-gnu docker image, so maybe @japaric can shed some light on this?
This image no longer works for me. I tried reverting to older versions of cross and older versions of rust, but it still fails.
The weird thing is that this image still works on an old ci machine machine we have, but not on my machine, and I could not figure out why.
Thanks
Amir

so maybe @japaric can shed some light on this?

I'm sorry it's been too long since I looked into that target's Dockerfile.

This seems to stem from mingw64 for i686 using sjlj for exception handling instead of dwarf-2 which the rust compiler expects (according to this).

Different exception handling is the only thing I remember about these mingw targets.

I created a fix: https://github.com/rust-embedded/cross/pull/471

Awesome news @malbarbo Thanks!

@malbarbo Just tried it and it worked like a charm. Thanks!


#75 Split  value by spaces for javafx:run

When javafx:jlink command creates the luncher all  values are joined using an space like separator, because of this the luncher pass VM args in the right way. In the other hand for the command javafx:run the values of  are used as they are defined, but if this values contain spaces there are not handle well and the VM does not receive them correctly.
It is desirable that the behavior of both commands, regarding the treatment of the VM args, be the same.
This PR fix #75.

both commands, regarding the treatment of the VM args, be the same

I looked at both when I was first contemplating this problem. Now that I think of it, by the jlink copying into a string, if the source has quotes, then that get's handled automatically when the command is processed. That would also handle my case where there are multiple args.

I looked at both when I was first contemplating this problem. Now that I think of it, by the jlink copying into a string, if the source has quotes, then that get's handled automatically when the command is processed. That would also handle my case where there are multiple args.

Yes, in the case of jlink there is no problem because as you say everything is concatenated into a string and we don't need to process the arguments, but with run does.

Cloned the betanzos repository. 0.0.5-SNAPSHOT works well with the IDE profiling feature.


[Feature]: MetaNode requests Master dp information list reuse

Describe the solution you'd like

A single MetaNode node merges the client/partitions (not limited to) requests of the meta partition of the same volume to reduce the load.

Additional context
MetaNode obtains meta partition partition information by requesting the master's client/partitions interface. In a scenario with a large cluster, repeated acquisition of the MetaNode dimension will lead to overloading of the master's pressure.

Hello, is this issue still ongoing? If still going on, can I complete the development of this feature? If so, which git branch should I continue working on? @leonrayang @pengtianyue025

hello,can i try this?

Hello @leonrayang, please let me try it.


[TEST] Remove version titles

In a static build (ENV=anything-but-local), .Scratch seems to not be set in regular pages (i.e. non-section pages, layout: default), but it works fine using the watch mode with hugo server. Could be a Hugo bug, or maybe a problem with the output format partials that the Relearn theme came with.

Both hugo and hugo server seem to be randomly affected, where .Page.Store.Get fails to get a value. Possibly because the processing order is not serially - https://gohugo.io/methods/page/store/#determinate-values. Only appears to be a problem if we try to access the scratch from within e.g. breadcrumbs.html, a partial used after version.html. If breadcrumbs.html determines the version again instead of trying to use the precomputed page store, everything is fine, and it doesn't appear to make a measurable difference.


G0B1 patches for new SVD

I tried adding new patches for the g0b1 board with the updated SVD now.

Added USART CR1
Removed EXTI for now since the SVD still doesnt mention it
Applied some timer patches
Renamed PLLCFGR register so it fits with the rest of the G0 family

Pointers appreciated, I am new to embedded

Hey, maybe somebody could help me out with an issue I haven't figured out yet: the generated code of the RegisterBlock struct of the tim2 timer looks like this now:
#[doc = "0x20 - capture/compare enable register"]
pub ccer: CCER,
_reserved_9_cnt: [u8; 0x04],
#[doc = "0x28 - prescaler"]
pub psc: PSC,
#[doc = "0x2c - auto-reload register"]
pub arr: ARR,

Instead, I need the CNT register 0x24 to look like the other struct fields as my HAL expects this. The CNT field gets created like this in devices/common_patches/tim/tim2_common_32bit.yaml:
CNT:
  # Actualy a 32bit register
  _modify:
    CNT_H:
      name: CNTH
      description: Counter value
    CNT_L:
      name: CNTL
  _merge:
    - "CNT*"

Why does this result in a different struct?

Hey, maybe somebody could help me out with an issue I've been having. I included the following code from common_patches/tim/tim2_common_32bit.yaml:
CNT:
  # Actualy a 32bit register
  _modify:
    CNT_H:
      name: CNTH
      description: Counter value
    CNT_L:
      name: CNTL
  _merge:
    - "CNT*"

The CNT field of the tim2 RegisterBlock struct that gets generated by this code looks like this:

#[doc = "0x20 - capture/compare enable register"]
pub ccer: CCER,
_reserved_9_cnt: [u8; 0x04],
#[doc = "0x28 - prescaler"]
pub psc: PSC,

The CNT should look like the other fields as far as I understand, and if I change the resultig code it works with my HAL. How do I fix this? Thanks!

if register is not in RegisterBlock, this means it has alternate register with same address or its address is incorrect

Ah I see, thanks for the hint, I disabled the alternative mode for the TIM2 counter for now. Works now, thanks!
Do you maybe have some other comments/hints regarding this PR?

Many of the changes in this PR have either already been applied or are handled by the latest update to the G0 vendor SVDs in #947.
On a quick review, the only changes I see here which are still relevant are:

Add the missing DMAMUX:CCR* registers (7-11). This is still a good idea, and is relevant to the entire G0 family, but the approach taken in this PR isn't great. Ideally we would use something like the _copy verb, but I'm not sure that works on registers (it's only documented for peripherals).
Renaming RCC:PLLCFGR on G0B1/G0C1 to match the rest of the family.

Closing as partially outdated. Open new PR if still interested in improvement.


Add arrow shifting

This facilitates diagrams with parallel morphisms and their inverse analogue.

Resolves #10.

I've resolved the merge conflict and comment.


Options to disable smart album selection?

I would like to allow my users to select videos in the Videos folder only. Is it possible to have an option / config to disable smart album selection and defaults to Videos folder only?

Hi, @shivanraptor
Yes you can.
configure.fetchCollectionTypes = [(PHAssetCollectionType.album, PHAssetCollectionSubtype.smartAlbumVideos)]

Great. I can now select only videos using the codes below:
    let vc = TLPhotosPickerViewController()
    vc.delegate = self
    var config = TLPhotosPickerConfigure()
    config.fetchCollectionTypes = [(PHAssetCollectionType.smartAlbum, PHAssetCollectionSubtype.smartAlbumVideos)]
    config.singleSelectedMode = true
    vc.configure = config
    self.present(vc, animated: true, completion: nil)

However, how can I obtain the video local URL in the delegate function func dismissPhotoPicker(withTLPHAssets: [TLPHAsset])? Seems TLPHAsset class does not provide an URL property. Thanks.

Solved the problem. Using the answer here, and access the URL via phAsset property.


--with-tcti-* results in TCTI module being disabled

This is a mistake in the logic used for the configure.ac. What we want is:

If --without-tcti-* is provided, disable said TCTI
If --with-tcti-* is provided, build with the requested TCTI enabled, display error if it's not detected.
If neither with/without is provided, check to see if the TCTI is available. If so enable it, if not disable it with no errors.
Ensure that at least one TCTI is enabled.

I messed up the first and second of these. Instead the TCTI is disabled whenever --with/--without is provided. This was caused by my misunderstanding of how the AC_WITH_ARG macro works.

resolved in #121


Quartz v4 - Github Pages failing to build

Describe the bug
With the GitHub workflow deploy.yml described at https://quartz.jzhao.xyz/hosting#github-pages fails during the Build Quartz step with the following error:
Run npx quartz build
  npx quartz build
  shell: /usr/bin/bash -e {0}

 Quartz v[4](https://github.com/husjon/husjon.github.io/actions/runs/5918459299/job/16047808931#step:8:4).0.[8](https://github.com/husjon/husjon.github.io/actions/runs/5918459299/job/16047808931#step:8:9)

Error: R] Could not read from file: /home/runner/work/husjon.github.io/husjon.github.io/content/build.ts

Couldn't parse Quartz configuration: ./quartz/build.ts
Reason: Error: Build failed with 1 error:
error: Could not read from file: /home/runner/work/husjon.github.io/husjon.github.io/content/build.ts
Error: Process completed with exit code 1.

It seem to be looking for build.ts in content/ instead of quartz/
Not able to reproduce locally running the same command (npx quartz build).
Build log can be found here: https://github.com/husjon/husjon.github.io/actions/runs/5918459299/job/16047808931
I added 3 extra steps prior to Build Quartz for debugging (showing current directory and listing files)
To Reproduce
Steps to reproduce the behavior:

git clone https://github.com/jackyzha0/quartz.git
cd quartz
git checkout v4
npm i
npx quartz create
Add GitHub workflow deploy.yml according to https://quartz.jzhao.xyz/hosting#github-pages
Commit changes (either with npx quartz sync or git push)

Expected behavior
Build step should go through with no issues.
Screenshots

Desktop (please complete the following information):

Device: PC
OS: Archlinux
Browser: Google Chrome

Additional context
Running npx quartz build locally on my machine works as expected.

Hey, seems like you have a symlink at https://github.com/husjon/husjon.github.io/blob/v4/Quartz that GitHub might have trouble with. Can you try removing that symlink and trying again?

Yeah, seem like the symlink did indeed caused it to fail, still not entirely sure why that is since it's a relative symlink which the GitHub pipeline should understand. :thinking:
I used it so that it showed up in Obsidian with a more recognizable name instead of content :)

I think git is case insensitive so it treats Quartz and quartz as the same folder :// Closing this as resolved for now! Feel free to reopen if problems keep popping up


Change in LED setup after group feedback

minimal change to the SSP setup upon Volker's suggestion

Incorporated in #235 by cherry-pick.

I also had to add a last minute change in the data. I missed some csp technologies (having 16 technologies with irregular names does not help automatize the parametrization ..)
I would still like to merge this in main and not just cherry-pick in ssp-dev because I don't want to have divergent branches like in message_data, at least for the water implementation.


Kata container support for benchmarking

kata container support for benchmark

I signed it

Hi @Random-Liu
It seems there is one testcase failed in travis, but I cannot find what's the root cause.
Could you have a look?

This PR is not Kata-specific, on the contrary, it introduces some more cases, which are cared about more in the multi-runtime scenarios.
For the README file, it described how to test with Kata Containers, which is not directly related with the cases, and should be claimed as an example.


Sync progress partial config

Could this PR get a description?
From a network perspective it doesn't seem to have much to do with "sync progress partial config".


Feature Request: Open new file buffer via API

VSCode Version: 1.5.2
OS Version: OSX 10.10.5, Win 7 x64

Is it possible to open a new file buffer via the API? Essentially, when you use your mouse (or keyboard shortcuts) and goto File menu > New File, it creates a new Untitled file buffer in the workspace. When you Save the file, it opens a Save File dialog where you choose where to save it along with the filename. Is it possible to create a new file buffer in this same manner via the API? If not, can this feature be added?
I have messed around with the API quite a bit in this area and if it is currently possible, it's not clear in the documentation.
I know you can do this:
window.openTextDocument(Uri.parse("untitled:c:\\project\\myfile.txt"))
  .then((document) => {
    window.showTextDocument(document);
  });

But this requires that you specify the file path for this new "untitled" file. When you hit save, it forces the file to be saved at "c:\project\myfile.txt". The user is not given the chance to specify where to save the file or what filename to give it.
To make a long story short, I essentially want the same functionality as going to File menu > New File. Does that make sense?

@bpasero is working on this

@jrieken the one (little) challenging thing is that in ensureDocumentData we seem to need the URI upfront, but if we have untitled:// the URI is only known at a later point. I would need to return the URI from $tryOpenDocument but that code runs async because it needs to talk to the main side where the untitled URI is basically being created.

Yeah, we could check if only the scheme is set and then immediately call another method that simple create a new document. Tho saying that makes me think if we should just expose that directly
on the API. Something like createTextDocument(language:string, ...)? That will be easier to understand than the scheme-only uri's

@jrieken I like the more explicit createTextDocument without URI, let me try to sketch something up so we can discuss further via PR.

@bpasero your proposal in #17917 sounds great. The only question would be the name of the file when the language is specified. The untitled document command right now creates documents as "Untitled-1", Untitled-2" ...
it would be nice to have an option to have different names for untitled document if it has specific language. For example for SQL documents it would be "SQLQuery-1", "SQLQuery-2" ...

Not sure a out that to be fair.

@bpasero re https://github.com/Microsoft/vscode/issues/12283#issuecomment-273187735 there is one catch it forget to mention. We have a rule that createXYZ-functions are ctor replacements for interfaces we own. The consequence is that they must return sync and cannot return a promise with the result. That might make things more complicated and if it becomes to hard we should thing another overload of openTextDocument

A new overload was added to the openTextDocument method that allows to open an untitled document with optional language. For example you can call:
openTextDocument({ language: 'xml' })
To create a text document with XML as language. If you leave out the language options, it will just create a text document with plain text language.

@bpasero  so the openTextDocument gets an uri now which has to be a valid path even if it's untitled. is it going to be the same or with the new option if I don't pass any uri it would be untitled?

@llali with the new API you no longer pass in a URI and you end up exactly in the same spot as if a user would have hit CtrlCmd+N to open a new untitled file. The optional language ID can be used to define the language of that document upfront.

[ ] To verify:
A new overload was added to the openTextDocument method that allows to open an untitled document with optional language. For example you can call:

openTextDocument({ language: 'xml' })
To create a text document with XML as language. If you leave out the language options, it will just create a text document with plain text language.


Add resourse for custom titles for reports

add parameters for custom title:

browser title
body title and body subtitle

add unit tests to check assertions for those parameters

Locust inline command
locust --autostart --autoquit 15 \
           --html /tmp/index.html \
           --html-browser-title "My Test Report" \
           --html-body-title "My API Test Report" \
           --html-body-subtitle "My API service subtitle" \
           -f examples/basic.py

report result

close   #2329

Hmm... sorry for not thinking about this right away, but I think this should be a "hidden" setting on the stats module instead of a command line argument. Because so few people will use it, it is not worth cluttering the "public" interface.
See https://github.com/locustio/locust/pull/2313 for an example of how it is done.
If you need to control these settings from command line (and dont want to hard code them in your locustfile), you can pass them via an env var, e.g.
MY_BROWSER_TITLE=thing locust ...
in locustfile:
locust.stats.BROWSER_TITLE = os.environ['MY_BROWSER_TITLE']

I didnt mean just adding a test with env vars, I meant removing the args/env vars alltogether and having the settings on the stats module.

@adrianovieira ?


Remove duplicate packages in debian build guide

Minor change removing duplicate packages in debian build guide

Many thanks 👍


New version: Hadamard v1.2.0

Registering package: Hadamard
Repository: https://github.com/stevengj/Hadamard.jl
Created by: @stevengj
Version: v1.2.0
Commit: 3f5615f32d4f1274c7989d43966884b98360b893
Reviewed by: @stevengj
Reference: https://github.com/stevengj/Hadamard.jl/commit/3f5615f32d4f1274c7989d43966884b98360b893#commitcomment-38261815

@stevengj Want me to manually merge this?


Add builder methods on the common objects

We have already added a few to the User class. Essentially just add some methods in the form:
public class Pojo {
    private String x;
    private String y;

    public Pojo x(final String x) {
        this.x = x;
        return this;
    }

    public Pojo y(final String y) {
        this.y = y;
        return this;
    }
}

The Pojo class can then be initialised like:
Pojo pojo = new Pojo().x("value of x").y("value of y");

For classes with lots of fields this will make it clearer than have lots of different constructors with different combinations of parameters. We should then be able to remove all of the constructors from the class. This approach could be applied to the majority of our simple classes like the Request classes.

Merged into develop.


Restoring broken functions

This PR fixes the update-balances and send commands.

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


upstream-community-operators intel-device-plugins-operator (0.20.0)

Thanks submitting your Operator. Please check below list before you create your Pull Request.
Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Submit operators to both upstream-community-operators and community-operators at once
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.

/hold cancel

/hold

/hold cancel

@J0zi @mvalarh I'm getting this CI error:
Run<EMAIL_ADDRESS>Sending webhook request to https://api.enterprise.redhat.com/hydra/umb-bridge/v1/publish
Error: Received status code: 400
Error: Received status code: undefined
(node:1524) UnhandledPromiseRejectionWarning: Error: Request failed with status code: undefined
    at error (/home/runner/work/_actions/joelwmale/webhook-action/2.1.0/dist/main.js:92:11)
    at /home/runner/work/_actions/joelwmale/webhook-action/2.1.0/dist/main.js:83:17
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:1524) UnhandledPromiseRejectionWarning: Unhandled promise rejection. 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(). (rejection id: 1)
(node:1524) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Is this caused by this PR or something is broken in CI?


Height Feature

The height option that is available in the visualizer does not exist in the documentation. Also it does not look like it is functioning.

Can you post a card sample that illustrates height not functioning?

Hey @utsavlathia do you have more details to share on this issue? Specifically about what doesn't seem to be functioning?
We've updated the schema docs to include the height property, maybe that resolves it? Closing for now, re-open if there's still issues around docs not being clear or anything :)


rule 6.2.4 with login banners

in one of the servers the /etc/profile has this block (full banner not displayed here):
# banner

echo -e "\e[34m
   ,e#####me        ,e######m,         ,a###########O     ##h       /e#######mJ

[=] Server : $HOSTNAME
[=] IP     : $(ifconfig | grep '192' | head -n1 | awk '{print $2}')
[=] Kernel : $(uname -r)
[=] Uptime : $(uptime | awk '{print $3 $4}')

Welcome back $USER
"

which causes the rule 6.2.4 evaluation to be confused since the dot_in_path is wrong and results in creating multiple files due to stdout registration:
[root@test-deploy ~]# /bin/bash --login -c 'env | grep ^PATH=' | sed -e 's/PATH=//' -e 's/::/:/' -e 's/:$//' -e 's/:/\\n/g'

   ,e#####me        ,e######m,         ,a###########O     ##h       /e#######mJ

[=] Server \n test-deploy
[=] IP     \n
[=] Kernel \n 3.10.0-1160.25.1.el7.x86_64
[=] Uptime \n 1\n04,2

Welcome back root

/opt/kafka/bin\n/usr/local/bin\n/opt/kafka/bin\n/usr/local/bin\n/usr/local/sbin\n/usr/local/bin\n/usr/sbin\n/usr/bin\n/root/bin\n/root/bin

An extra "grep "^PATH" before the sed commands seems to fix the issue

hi @antonatos
We wanted to reach out after looking over the issue and we have some questions. Would you be able to give us some detail on your /etc/profile? Looking at the changes suggested they do work, however they might deviate from some best practices, we would normally find the sort of setting you have in a profile.d script. If they are placed within /etc/profile.d, we don’t see the issue you are experiencing. At this time we are leaning towards this being something that is better addressed in your environment. However before we make that call we would like to take a poke at what you are using, so we can address as many options as possible without impact.
Thanks
uk-bolly

Hi,
I attach the /etc/profile file as found in one of the servers. You are true it does not happen if the contents are in /etc/profile.d
but I put the issue up in case you want to guard against edge cases.

On 6 May 2021, at 8:57 PM, uk-bolly @.***> wrote:
hi @antonatos https://github.com/antonatos
We wanted to reach out after looking over the issue and we have some questions. Would you be able to give us some detail on your /etc/profile? Looking at the changes suggested they do work, however they might deviate from some best practices, we would normally find the sort of setting you have in a profile.d script. If they are placed within /etc/profile.d, we don’t see the issue you are experiencing. At this time we are leaning towards this being something that is better addressed in your environment. However before we make that call we would like to take a poke at what you are using, so we can address as many options as possible without impact.
Thanks
uk-bolly
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ansible-lockdown/RHEL7-CIS/issues/225#issuecomment-833737615, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARD3BQ4EOBG2PKBAKZ4UTTTMLKAVANCNFSM44CW33KA.

Hi @antonatos
Thank you for your patience. Before making the decision, we have been waiting to see if anyone else has requested this either from the community or from our direct clients and we have not seen this appear again.
While it is very valid point there are many ways that people may be achieving their requirements and trying to allow for all the options and ways of achieving this is not something we could handle in each case.
However in this case, I have raised the PR as we are certain this is not an uncommon practice and it will be seen again.
Many thanks once again
uk-bolly


feat: Topology of pointwise convergence for continuous linear maps

[x] depends on: #11470
[x] depends on: #11600

Is there a reason you only setup the topology and not the uniform structure? If that's because it's too annoying, I agree, and I'd be happy to help.


Add new policy for checking insecure_ssl on github_repository_webhook

Add a new policy to the GitHub provider to check if insecure_ssl was set
to true on the github_repository_webhook resource.
Resolves #355

Thanks!


Missing Series: FIA Formula 4 Challenge

Hey, what used to be named "Formula D - Ricmotech iR-04 Challenge" is now "FIA Formula 4 Challenge", and that seems to make it disapear from the list.
The series id still the same for both the open and the fixed setup, but I will paste the info I got from the iRacing Series.do:
{
  "seriesName": "FIA Formula 4 Challenge",
  "seriesName_short": "FIA Formula 4 Challenge",
  "banner_img": "https://ir-core-sites.iracing.com/members/member_images/series/seriesid_497/banner.jpg",
  "col_gray_img": "https://ir-core-sites.iracing.com/members/member_images/series/seriesid_497/whats_hot.jpg",
  "col_color_img": "https://ir-core-sites.iracing.com/members/member_images/series/seriesid_497/panel_list.jpg",
  "exp_img": "https://ir-core-sites.iracing.com/members/member_images/series/seriesid_497/logo.jpg",
  "header_img": "https://ir-core-sites.iracing.com/members/member_images/series/seriesid_497/title_list.gif"
}

{
  "seriesName":"FIA Formula 4 Challenge - Fixed",
  "seriesName_short":"FIA Formula 4 Challenge - Fixed",
  "banner_img":"https://ir-core-sites.iracing.com/members/member_images/series/seriesid_498/banner.jpg",
  "col_gray_img":"https://ir-core-sites.iracing.com/members/member_images/series/seriesid_498/whats_hot.jpg",
  "col_color_img":"https://ir-core-sites.iracing.com/members/member_images/series/seriesid_498/panel_list.jpg",
  "exp_img":"https://ir-core-sites.iracing.com/members/member_images/series/seriesid_498/logo.jpg",
  "header_img":"https://ir-core-sites.iracing.com/members/member_images/series/seriesid_498/title_list.gif",
}

Fixed by https://github.com/bfiete/iStats/commit/28c113b748b5ffbfc21cb83cbec624187760139a


Auto default to one minute if time spent is less than a minute

Occasionally my team spends less than a minute on a project (entering a note, etc), but they have to wait until Jira Stopwatch registers that a minute has passed to push to Jira.  Is there a way to have the application automatically round to the next whole minute (or default to 1 minute is less than a minute is logged)?

I'd vote for always rounding up.  i think it fits how time reporting works in most places best (for my actual time reporting (in another tool) I round up to next 15 min interval - I know some people do per minute (maybe not devs, I know some lawyers do), but I doubt anyone does per second :)

I think it is a great idea, so @gsmith523 feel free to submit a pull request. My own time is unfortunately very limited at the moment, which will probably not change until around november.

Sorry, I am not familiar with the process.  I looked at adding a pull request but am not sure which options to choose.

The easiest way is:

Fork the repository to get your own copy into https://github.com/gsmith523/jirastopwatch
Work on this copy
Create a pull request with the changes - described here: https://help.github.com/articles/creating-a-pull-request-from-a-fork/

For a description on the entire flow, read https://gist.github.com/Chaser324/ce0505fbed06b947d962

I've just made it myself. :-)


Updated README.md file for tic_tac_toe game

Please fill all the details and checkbox, so we can merge PR faster.
Pull Request Template
script name -
What have you Changed
what you changed in the codebase. write here
Issue no.(must) -
Self Check(Tick After Making pull Request)

[ ] This issue was assigned to me.
[x] One Change in one Pull Request
[x] My file is in the proper folder
[x] I am following clean code and Documentation and my code is well-linted with flake8.
[ ] I have added README.md and requirements.txt with my script

If the issue was not assigned to you Please don't make a PR. It will mark as invalid.
Join Us on Discord:- https://discord.gg/JfbK3bS
acknowledgment

[x] I have tested the script and distributed it under an MIT license.

I have done all the changes that you will tell me. Please check and merge
my PR.
Thanks and Regards
On Sat, 8 Oct, 2022, 6:53 pm Deepak Raj, @.***> wrote:

@.**** requested changes on this pull request.
Please don't create a new README. only one README will show in GitHub
Desktop. Please make appropriate changes in the previous README.md
—
Reply to this email directly, view it on GitHub
https://github.com/codePerfectPlus/awesomeScripts/pull/590#pullrequestreview-1135224824,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVB7ZO4YQ7PQAVJBHDF7FHLWCFYUJANCNFSM6AAAAAARAHPG24
.
You are receiving this because you authored the thread.Message ID:
@.***>

--

#592 Merged, closing PR


35 support usdm data source in engine - additional changes to support cli

Updates include:

Changing USDMDataService.get_datasets to return a list of datasets in a format that corresponds with the get_datasets output format for other data services.  To support this change, I also did a bit of reorganization in usdm_data_service.py, for example:

To use different names for different things - e.g., only used "full_path" for the dataset path, changing to "content_path" for the JSONPath content pointers.
Renamed the datasets-with-JSONPath-pointers dictionary as dataset_content_index to differentiate it from the list of dataset-level metadata that's expected to be created by get_datasets.
Moved reading of the JSON file and creation of the dataset_content_index to the class level and cached it so that it's only done once.

Spoofing unique dataset names in a format that gets processed correctly downstream - i.e. <dataset_path>\<domain>.json (e.g., CDISC_Pilot_Study_dirty1.json\Study.json).  This was necessary because the engine looks like it's been designed with the expectation that each dataset will be in a separate file (even for Dataset-JSON), and it uses file name as dataset name.  When multiple datasets are in a single file (as for USDM) this causes problems because dataset name (i.e. file name) is used in the cache key.  I ended up using this format because:

Including the domain name makes a unique cache key (note that the cache always has to be used to access individual datasets because they can't just be re-read from a single file).
Including it at the end using os.path.join means that the original file name is listed as the "Origin" in the Excel report
The ".json" at the end is needed so that the correct data reader is used.

Updated things like get_dataset to accept the spoofed unique file name instead of the domain/entity name as dataset_name .
Adding a call to BaseDataService._replace_nans_in_numeric_cols_with_none to get_dataset to convert NaN to None in numeric columns (so that they're correctly picked up by operators such as empty).
Updating USDM.yml to include:

More mappings to support the USDM 2.6 file we want to use for the demonstration.
Two-tier mappings for attributes that can map to more than one entity.  I also updated __get_entity_name to use the parent entity to decide which of the multiple potential mappings is correct, which required changing its arguments and invocations to accept/pass node objects so that these can be navigated to find the parent.

Updating validate_single_rule in run_validation.py to pass dataset_paths to RulesEngine and RulesEngine.__init__ in rules_engine.py to accept it and pass it to DataServiceFactory.get_data_service (instead of DataServiceFactory.get_service), so that it can be used by USDMDataService.is_USDM_data to determine whether the JSON file contains USDM data (I also tweaked is_USDM_data so that it doesn't fall over if no dataset_paths is provided).
Updating get_dataset_variables in data_processor.py and _execute_operation in rule_processor.py both to use os.path.join instead of f"{}/{}" to create dataset file references (so that these match the cache keys used by USDMDataService).
Changing get_library_metadata_from_cache in script_utils.py not to fall over if there's no standard metadata available in the library cache.
Changing test_usdm_data.py to align with these changes.
Changed __get_record_data to assign False when dict or list value is empty.

Changes to consider:

To speed up execution, creation of self.json and self.dataset_content_index should only be created if needed (possibly move them back out of __init__ again).  At the moment, this time-consuming process is performed each time a USDMDataService instance is initialized but, if there's already a cache containing dataset content and metadata, json and dataset_content_index may not be needed.
DatasetMetadata should probably be changed to be a subclass of RepresentationInterface and the creation of the dataset metadata dictionary in get_datasets in the dummy, local and usdm data services should probably then be moved to a DatasetMetadata.to_representation.

Changes to consider:

To speed up execution, creation of self.json and self.dataset_content_index should only be created if needed (possibly move them back out of __init__ again).  At the moment, this time-consuming process is performed each time a USDMDataService instance is initialized but, if there's already a cache containing dataset content and metadata, json and dataset_content_index may not be needed.

Instead of moving creation of self.dataset_content_index out of __init__, it is now cached with dataset_name = "USDM_content_index". This reduces execution time from ~6mins to ~3mins because the second invocation of USDMDataService retrieves it from the passed cache instead of recreating it.

It's also our policy to resolve merge conflicts before approving PR

There is one item I don't quite agree with:

The ".json" at the end is needed so that the correct data reader is used.

It seems wrong to pretend that a single json file is multiple json files at the Engine level. I think it would be better to fix the engine to be able to handle different types of dataframe collections (folder of files, single file, cosmos collection of items, etc). But this might be a much bigger change, in which case the hack is okay for now and you can create a new ticket for it instead.

I think this is might be a bigger change.  Prior to USDM, it seems that the engine assumes that there is a 1-to-1 relationship between file name and dataset name - there are several places where dataset_name is expected to contain the file name, which doesn't work if a file contains multiple datasets. I think it will need a reasonably significant change to unpick this.


Windows xr plugin remoting

I can't connect remotely to the device (Hololens 1) using windows xr plugin remoting. I'm using unity 2019.4.0f5 with mrtk 2.3
Steps to reproduce the behavior:

Go to 'Window'
Click on 'windows xr plugin remoting'
emulation mode--> romote to device--> fill the IP of the remote machine
I got a visual c++ runtime library error and the application crash

There are some known issues with remoting and that plug-in at the moment. They're being worked on on the Unity side

https://forum.unity.com/threads/hololens-1-windows-xr-plugin-remoting-not-working.827970/

Same Issue, but it's working on unreal engine 4.

I have the same issue, has anybody found the solution?

I can't connect remotely to the device (Hololens 1) using windows xr plugin remoting

HoloLens 1 isn't supported with Windows XR Plugin remoting. Closing this as external.


Abort error when share is cancelled

Describe the bug
When closing a share dialog without selecting an option an exception is thrown in Safari.
Uncaught runtime errors:
×
ERROR
Abort due to cancellation of share.

Screenshots

Desktop (please complete the following information):

OS: Mac
Browser: Safari
Version: recent/latest

Additional context
Possibly wrapping navigator.share in a try/catch could avoid the issue.  Untested.
See this SO thread:
https://stackoverflow.com/questions/60510383/web-share-api-navigator-share-problem-when-canceling-share-dialog-ios-and-androi

Thanks for reporting! I am aware of this issue, but not sure how to handle it. Could wrap it in a try/catch but since I think it's a promise in of itself we could use a .then() and a .catch() to catch the error and surface console information for debugging:
 window.navigator.share({
      title: root.title,
      text: root.title + "\n" + window.location.href
    })
    .then(() => alert('The page was shared'))
    .catch((e) => console.log(e))

What do you think?

This looks good to me.  I just tested on my end and it works as expected in Safari, logs the error, but still working and toggling properly.


New length=64 of "address_city"  is not reflected in migrations

standard/ipn/migrations/0001_initial.py has such entry:
('address_city', models.CharField(max_length=40, blank=True)),
in fact PayPalStandardBase has:
address_city = models.CharField(max_length=64, blank=True)
and there are no further migrations, which reflecting this change

PayPalStandardBase has max_length=40, and always has AFAICS:
https://github.com/spookylukey/django-paypal/blob/master/paypal/standard/models.py#L99
Are you running from a modified copy perhaps?
I'm closing as this seems to be clearly incorrect. If there is something I'm missing, please re-open.


Refactor random number generation

Avoid creating new RNG every time values are generated
Combine with samplers?

RNG/Sampler struct for each thread?

Performance analysis shows not much speed improvements are available. Closed (for now? could make it prettier)


Not working properly in multiplayer

Other players using the texture pack have a weird white overlay on their face

Black eyes as well as other colors are still showing up in multiplayer on other players, even when I have skin transparency set to all skins. My skin is the only one that is normal.


skip metric if Cloudwatch timestamp is enabled and no metric data

if some CloudWatch metric returns no data and addCloudwatchTimestamp is enabled yace returns no timestamp and so, Prometheus is adding current timestamp automatically. This breaks metric ingestion order for metrics which are intermittently unavailable. This simple patch just skips metrics which has no data if addCloudwatchTimestamp is enabled

unfortunately this fix was invalid, sorry for that. I created https://github.com/ivx/yet-another-cloudwatch-exporter/pull/421 to fix it.


Add custom frequency config option for daily stats report & add manual trigger

Currently, chiadog can send a daily stats report, which is awesome.
Request:

Add a config field to set the frequency of this report, e.g. every 5 hours, every 1 hour, etc. This is especially helpful while troubleshooting issues with the farmer.

Add the ability to trigger a stats notifications manually. Again, this is helpful for troubleshooting. It would be extra nice if this were possible to call via CLI, a script, or cron.

+1 to this request.
In addition, I'd love to be able to get a notification when a proof is found, especially since chia's debug.log only goes back 8 files, and it rotates every ~20MB (which is my case is every 40 minutes), which means I only end up with 4-5 hours of logs.

+1 to this request.
In addition, I'd love to be able to get a notification when a proof is found, especially since chia's debug.log only goes back 8 files, and it rotates every ~20MB (which is my case is every 40 minutes), which means I only end up with 4-5 hours of logs.

There is a pull request ready for this functionality. It was briefly disabled due to Chia removing the log line from the debug log.
https://github.com/martomi/chiadog/pull/74

Currently, chiadog can send a daily stats report, which is awesome.
Request:

Add a config field to set the frequency of this report, e.g. every 5 hours, every 1 hour, etc. This is especially helpful while troubleshooting issues with the farmer.
Add the ability to trigger a stats notifications manually. Again, this is helpful for troubleshooting. It would be extra nice if this were possible to call via CLI, a script, or cron.

Regarding 1) so basically you'd like to have a user-defined interval for daily stats? Config would look something like this then:
daily_stats:
  enable: true
  start_at: 21:15
  interval: 3600 # interval in seconds or preset: [hourly, daily, weekly]

Regarding 2) I've been thinking of a way to implement this. Since Chiadog keeps its state in memory, I can think of two possible ways:

Write state to shared database and have a command stats.py --config config.yaml read from that database, send a notification and exit
Implement a keyboard event listener using keyboard and fire off a manual trigger when you press a specific key/combination (like ctrl+t) from the existing main.py process.

I'm leaning towards the second implementation... If anyone can think of any other ways, please elaborate on them here.

Regarding 2:
How about running main.py normally, wait for a small time (e.g. 30s) to aggregate some logs, and then send the stat report? This would be like your option 1, but without the shared database.
This mode could be triggered by an option --test-stats or so.

@greimela sounds a lot like what I also proposed here https://github.com/martomi/chiadog/pull/82#pullrequestreview-652641997 - maybe the ideas can be combined to some extend. But let's keep it very simple.
Simplest would be to have that option to send notification immediately and to also have interval_hours config that defaults to 24 but people can set it to e.g. 8 for morning, afternoon, evening notifications or to 1 for debugging stuff.


[Feature] Trace Sampling at agent side

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
I have seen source code of SegmentAnalysisListener,trace sampling at server side means huge burden on the network,even if on the local area network.
Use case
Can we modify source code of TraceSegmentServiceClient to trace sampe at agent side before sending to the oap server?
Related issues
None,just an idea in my head.
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

There is client sampling already. You could check the doc.


[CLI] Metrics of sweep runs are not shown with id in wandb.init

Description
The metrics used for hyperparameter optimisation with sweeps are not logged when id is passed to wandb.init method. Individual runs do not show their metrics either.
How to reproduce
Example of a run with such bug: https://wandb.ai/freefeynman123/ifsl-MTL_sweeps/sweeps/q9fxzeuo?workspace=user-freefeynman123
The code for this project can be viewed in: https://github.com/freefeynman123/ifsl/tree/develop
You can view MTL/trainer/meta.py for details of given code.
After changing the line
self.run_train = wandb.init(project=self.args.project_name, id=id, resume="allow", job_type='train', entity=USER_NAME)
to
self.run_train = wandb.init(project=self.args.project_name, resume="allow", job_type='train', entity=USER_NAME)
(essentially deleting id from wandb.init)
the metrics are shown, however tracking individual runs is lost and one cannot retrieve artifacts for given run.
Environment

Docker base image: nvidia/cuda:11.1.1-cudnn8-devel-ubuntu20.04
Environment: Kubernetes pod with RTX2080 GPU
Python Version: 3.8.5

Hi @freefeynman123 , thanks for reporting this. We're looking into it.

Hi @freefeynman123 , thanks for reporting this. We're looking into it.

Thanks, we should print a warning. ID can't be changed for sweeps. The sweep has already created the ID, so you can't change it. May I ask why you are setting the ID in this scenario?

Thanks, we should print a warning. ID can't be changed for sweeps. The sweep has already created the ID, so you can't change it. May I ask why you are setting the ID in this scenario?

I thought about recovering artifact from particular run within the sweep. As I can see currently I only have access to artifacts with my entity name, without particular sweep or run name.

To get the best model file, saved as an artifact, from a sweep:

Run a sweep. Don't set run IDs.
Open the sweep page in the UI. Sort by the columns you care about to find the best run for a given metric.
Click on the best run, and then click on the artifact tab. Download the artifact.

@annirudh could you describe how to do this from python

From the API, you could do something like this:
import wandb
api = wandb.Api()
sweep = api.sweep("<entity>/<project>/<sweep_id>")
runs = sorted(sweep.runs, key=lambda run: run.summary.get("val_acc", 0), reverse=True)
best_run = runs[0]
for artifact in best_run.logged_artifacts:
  # can download the artifact files here
  ...


Config all the things

This branch is based from #480 (so it should go first).
This expands upon what we've been building for a while, with each feature broken up into it's own little box.  This will add the ability for a user to disable a feature they don't want/care about.  It is built into how we create features (as a mandatory part of the interface), so even new features will work this way.
Some features are required for omnisharp-atom to function correctly (these are things like the dock, solution information, server information, etc), so they won't be configurable.  It's entirely possible we'll add another mandatory field in the future.

I'm not convinced that there is much point in having Code format, Find Symbols, Find Usages etc as config items.
If someone doesn't want to use them, they just won't use them :) Config should be for actions that are outside the users control.

While I agree, I would have put Code Lens in the same bucket too.  I just
figure instead of creating one-off configs as needed, if we make something
generic, that "just works", if there is a new feature someone doesn't want,
we can just turn it off.
If we feel like something shouldn't be configurable (Code Format for
example), we can flip the flag that says the feature is required, and it
won't show up in the config at all.  So I'm open to flagging more features
as required.
On Fri, Aug 28, 2015 at 8:44 AM, Jason Imison<EMAIL_ADDRESS>wrote:

I'm not convinced that there is much point in having Code format, Find
Symbols, Find Usages etc as config items.
If someone doesn't want to use them, they just won't use them :) Config
should be for actions that are outside the users control.
—
Reply to this email directly or view it on GitHub
https://github.com/OmniSharp/omnisharp-atom/pull/482#issuecomment-135765691
.

OK. Anything that requires a keybinding to activate doesn't need a config item.

Was using this all weekend, and didn't hit any snags that I know of, let me know if you have any issues pop up.


nexus-prisma types undefined when deploying to heroku

When deploying to heroku the app crashes with the error seen in the screenshot.
local build works without any problems.
Screenshot

Description
parts of my package.json file:
"scripts": {
    "start": "node .build/api/app.js",
    "postinstall": "prisma generate",
    "build": "tsc",
},
"dependencies": {
    "@prisma/client": "2.27.0",
    "apollo-server": "^2.25.2",
    "aws-sdk": "^2.939.0",
    "bcrypt": "^5.0.1",
    "cuid": "^2.1.8",
    "graphql": "^15.5.1",
    "graphql-middleware": "^6.0.10",
    "graphql-shield": "^7.5.0",
    "jsonwebtoken": "^8.5.1",
    "nexus": "^1.1.0",
    "nexus-prisma": "^0.30.0"
  },
 "devDependencies": {
    "typescript": "^4.3.5",
  },

This might be because the prisma client and nexus were not successfully built, because of #107

Facing the same issue.
On build step at Heroku I can see that prisma was successfully generated.
Attaching my build log and application log
build log
-----> Building on the Heroku-20 stack
-----> Using buildpack: heroku/nodejs
-----> Node.js app detected

-----> Creating runtime environment

       NPM_CONFIG_LOGLEVEL=error
       USE_YARN_CACHE=true
       NODE_VERBOSE=false
       NODE_ENV=production
       NODE_MODULES_CACHE=true

-----> Installing binaries
       engines.node (package.json):  14.x
       engines.npm (package.json):   unspecified (use default)
       engines.yarn (package.json):  unspecified (use default)

       Resolving node version 14.x...
       Downloading and installing node 14.17.5...
       Using default npm version: 6.14.14
       Resolving yarn version 1.22.x...
       Downloading and installing yarn (1.22.11)
       Installed yarn 1.22.11

-----> Restoring cache
       - yarn cache

-----> Installing dependencies
       Installing node modules (yarn.lock)
       yarn install v1.22.11
       [1/4] Resolving packages...
       [2/4] Fetching packages...
       info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
       info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
       [3/4] Linking dependencies...
       warning " ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>|| 2.18.x || 2.19.x || 2.20.x || 2.21.x || 2.22.x || 2.23.x || 2.24.x || 2.25.x || 2.26.x || 2.27.x".
       warning "xo ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>       [4/4] Building fresh packages...
       $ husky install
       fatal: not a git repository (or any parent up to mount point /)
       Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
       Done in 20.66s.

-----> Build
       Running build (yarn)
       yarn run v1.22.11
       $ yarn prisma:generate && NEXUS_SHOULD_GENERATE_ARTIFACTS=true node --loader ts-node/esm/transpile-only ./src/schema.ts && tsc
       $ prisma generate
       Prisma schema loaded from prisma/schema.prisma
       You can now start using Nexus Prisma in your code. Reference: https://pris.ly/d/nexus-prisma

       ✔ Generated Prisma Client (2.29.1) to ./node_modules/@prisma/client in 268ms

       ✔ Generated Nexus Prisma to ./node_modules/nexus-prisma/dist/runtime in 324ms
       You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
       ```
       import { PrismaClient } from '@prisma/client'
       const prisma = new PrismaClient()
       ```
(node:1651) ExperimentalWarning: --experimental-loader is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
WARNING: Peer dependency validation check failed<EMAIL_ADDRESS>does not officially support<EMAIL_ADDRESS>The officially supported range is: `2.17.x || 2.18.x || 2.19.x || 2.20.x || 2.21.x || 2.22.x || 2.23.x || 2.24.x || 2.25.x || 2.26.x || 2.27.x`. This could lead to undefined behaviors and bugs.
       Done in 11.93s.

-----> Pruning devDependencies
       yarn install v1.22.11
       [1/4] Resolving packages...
       [2/4] Fetching packages...
       info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
       info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
       [3/4] Linking dependencies...
       warning " ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>|| 2.18.x || 2.19.x || 2.20.x || 2.21.x || 2.22.x || 2.23.x || 2.24.x || 2.25.x || 2.26.x || 2.27.x".
       warning "xo ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>       [4/4] Building fresh packages...
       warning Ignored scripts due to flag.
       Done in 5.55s.

-----> Caching build
       - yarn cache

-----> Build succeeded!
 !     Unmet dependencies don't fail yarn install but may cause runtime issues
       https://github.com/npm/npm/issues/7494
-----> Discovering process types
       Procfile declares types -> release, web
-----> Compressing...
       Done: 104.3M
-----> Launching...
 !     Release command declared: this new release will not be available until the command succeeds.
       Released v9
       https://cheapoil.herokuapp.com/ deployed to Heroku

application log
2021-08-21T16:16:22.322915+00:00 heroku[web.1]: State changed from crashed to starting
2021-08-21T16:16:27.847214+00:00 heroku[web.1]: Starting process with command `node dist/server.js`
2021-08-21T16:16:30.540109+00:00 app[web.1]: WARNING: Peer dependency validation check failed<EMAIL_ADDRESS>does not officially support<EMAIL_ADDRESS>The officially supported range is: `2.17.x || 2.18.x || 2.19.x || 2.20.x || 2.21.x || 2.22.x || 2.23.x || 2.24.x || 2.25.x || 2.26.x || 2.27.x`. This could lead to undefined behaviors and bugs.
2021-08-21T16:16:30.559144+00:00 app[web.1]: file:///app/dist/schema.js:19
2021-08-21T16:16:30.559146+00:00 app[web.1]:     name: FuelStation.$name,
2021-08-21T16:16:30.559146+00:00 app[web.1]:                       ^
2021-08-21T16:16:30.559146+00:00 app[web.1]:
2021-08-21T16:16:30.559147+00:00 app[web.1]: TypeError: Cannot read property '$name' of undefined
2021-08-21T16:16:30.559147+00:00 app[web.1]:     at file:///app/dist/schema.js:19:23
2021-08-21T16:16:30.559148+00:00 app[web.1]:     at ModuleJob.run (internal/modules/esm/module_job.js:170:25)
2021-08-21T16:16:30.559150+00:00 app[web.1]:     at async Loader.import (internal/modules/esm/loader.js:178:24)
2021-08-21T16:16:30.559150+00:00 app[web.1]:     at async Object.loadESM (internal/process/esm_loader.js:68:5)
2021-08-21T16:16:30.599753+00:00 heroku[web.1]: Process exited with status 1
2021-08-21T16:16:30.727202+00:00 heroku[web.1]: State changed from starting to crashed

As a workaround installing all dependencies in heroku  and building again helped me
Procfile:
web: NODE_ENV=development yarn && yarn build && yarn start

@MikeYermolayev Indeed the generator is running, yet somehow your runtime does not have the result of that generated code.
Is there a way you can share what code is actually running? Not sure how helpful that info will be though.
After the build step, it seems that Heroku is not pulling in the modified version of node_modules.
Maybe there is a caching issue of some sort.
However, wonder why @prisma/client is working then...
I would be open to allowing users to customize where the nexus-prisma generated runtime is emitted to. However, that would add complexity for users and I want to only do that once we understand there is no other option.

Getting the same error. thought I was doing something wrong first time using nexus. anything I can provide to help?

@maks112v If you can share a repro-repo with that would help. I can then setup my own heroku app to run it and see the repro.

https://www.dropbox.com/s/18xphi1ygfidrky/api.zip?dl=0
It is a very basic api I just started it yesterday

The issue seems connected with https://devcenter.heroku.com/articles/troubleshooting-node-deploys#missing-modules
Setting YARN_PRODUCTION=false fixed it for me.
I doubt any actions are expected from nexus-prisma team except maybe adding to to troubleshoot section

@MikeYermolayev did you install nexus-prisma to dev dependencies?

Thanks @maks112v will try to look soon but might be a few weeks.

No. It's installed as dependency.
"dependencies": {
    "@prisma/client": "2.30.3",
    "date-fns": "2.23.0",
    "dotenv": "10.0.0",
    "envalid": "7.2.1",
    "fastify": "3.20.2",
    "fastify-plugin": "3.0.0",
    "graphql": "15.5.2",
    "mercurius": "8.1.3",
    "nexus": "1.1.0",
    "nexus-prisma": "0.31.0",
    "pino-colada": "2.1.0"
  },
  "devDependencies": {
    "@types/jest": "27.0.1",
    "@types/node": "16.7.10",
    "@typescript-eslint/eslint-plugin": "4.30.0",
    "@typescript-eslint/parser": "4.30.0",
    "eslint": "7.32.0",
    "eslint-config-prettier": "8.3.0",
    "eslint-plugin-jest": "24.4.0",
    "eslint-plugin-node": "11.1.0",
    "eslint-plugin-promise": "5.1.0",
    "eslint-plugin-unicorn": "35.0.0",
    "husky": "7.0.2",
    "jest": "27.1.0",
    "lint-staged": "11.1.2",
    "nodemon": "2.0.12",
    "prettier": "2.3.2",
    "prisma": "2.30.3",
    "ts-jest": "27.0.5",
    "ts-node": "10.2.1",
    "typescript": "4.4.2"
  },

no idea why it gets pruned

Running into this issue as well: Type error: Module '"nexus-prisma"' has no exported member 'Model' within the github action runner. I know this is still in early stages of development but wanted to report it.

@trey-m do you have a repro for that I can look at?

Running into a potentially similar issue as well: Type error: Module '"nexus-prisma"' has no exported member 'Model' within the github action runner. I know this is still in early stages of development but wanted to report it.

Manually run prisma generate after installing your dependencies as a workaround.

Running into a potentially similar issue as well: Type error: Module '"nexus-prisma"' has no exported member 'Model' within the github action runner. I know this is still in early stages of development but wanted to report it.

Manually run prisma generate after installing your dependencies as a workaround.

I currently have a postinstall script that calls prisma generate.

Seeing the same issue during a docker build where removing the part that prunes dev-dependencies fixes the issue. nexus-prisma is installed as a normal dependency though so i don't see how that could happen.
FROM mhart/alpine-node:14 as build
WORKDIR /app
ENV CI=true

RUN apk update && apk upgrade
RUN apk --no-cache add git make gcc g++ python3 openssl

# copy project
COPY . .

# Remove large unused packages
RUN rm -rf packages/client

# Install all dependencies
RUN yarn install --frozen-lockfile
RUN yarn lerna run build --scope=@app/server --include-dependencies

# Remove dev-dependencies
RUN yarn install --production --ignore-scripts --prefer-offline # Commenting out this line fixes the issue

leads to
/app/packages/server/dist/api/user/user.type.js:13
    name: nexus_prisma_1.User.$name,
TypeError: Cannot read property '$name' of undefined

Would just like to follow up on this issue, was having the same production deploy error as above, using Dokku:
TypeError: Cannot read property '$name' of undefined
Was able to fix it by setting YARN_PRODUCTION=false as mentioned, although long term would like to not have to use this flag - any updates on this weird interaction?

Would just like to follow up on this issue, was having the same production deploy error as above, using Dokku: TypeError: Cannot read property '$name' of undefined
Was able to fix it by setting YARN_PRODUCTION=false as mentioned, although long term would like to not have to use this flag - any updates on this weird interaction?

Did you ensure that you run prisma generate before any type checking?

I'm facing the same problem too when deploying to Heroku, I've tried changing the generator's output but it seems like nexus-prisma doesn't generate the types:

As you can see the generated folder isn't there only when using build command, this is my prisma file:
generator client {
  provider = "prisma-client-js"
}

generator nexusPrisma {
  provider = "nexus-prisma"
  output   = "../src/generated/nexus-prisma"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}
...

I'm facing the same problem too when deploying to Heroku, I've tried changing the generator's output but it seems like nexus-prisma doesn't generate the types:  As you can see the generated folder isn't there only when using build command, this is my prisma file:
generator client {
  provider = "prisma-client-js"
}

generator nexusPrisma {
  provider = "nexus-prisma"
  output   = "../src/generated/nexus-prisma"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}
...

yes because tsc command doesn't copy the .js  file by default you need to include
{
  "compilerOptions": {
    //...
    // add this option to your tsconfig.ts file will fix the issue
    "allowJs": true
  },
}

The issue comes from using yarn when Heroku starting Pruning devDependencies yarn rebuild fresh packages this means that the generated code by the prisma generate command will delete.

We have two solutions:
1 - Using npm  because it's using another strategy for Pruning devDependencies and delete only devDependencies and not rebuild all packages

2- Using a custom output path you will need to create a configuration file in one of the following locations
→ nexus-prisma.ts
→ nexusPrisma.ts
→ nexus_prisma.ts
→ prisma/nexus-prisma.ts
→ prisma/nexusPrisma.ts
→ prisma/nexus_prisma.ts
Then add the following code:
settings({
  output: './generated/nexus-prisma'
})

Because the output will be in .js you will need to include the .js files into your tsconfig.ts file by adding this prop.
{
  "compilerOptions": {
    ...
    "allowJs": true
  },
}

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on:

npm package (@next-major dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Feature/poetry update and poetry version patch 0 1 8

poetry update
poetry version patch

Solves #15


Update icons to meet correct accessibility spec

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes: #173
Summary:
Please summarize the scope of the changes you have submitted, what the intent of the work is and anything that describes the before/after state of the project.
The scope of this PR will address the following:

Update the generator script template to the correct a11y spec
Update the icon data to meet the new spec
Update related tests and linters
Add accessibility documentation

Type of change:

[ ] New capability
[x] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

The last part of this PR is to add accessibility documentation to the repo. The documentation requires a release in order to accurately portray its demos.
I recommend releasing this PR in its current state and the documentation will be a post-release addition.

:tada: This PR is included in version 4.20.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


bug: sidebar watch history typo

side bar have typing mistake it is Watch History instead of Watch Hostory

Please assign me


Datasets have different calendars / shapes

The datasets have different lengths of the time axis, different calendars, and different horizontal axes. This makes them difficult to group and work with.

CMIP6/CMIP/NIMS-KMA/KACE-1-0-G/historical/r1i1p1f1/Amon/ta/gr/v20191028
shape: (1980, 2, 2, 1), calendar: 360_day
CMIP6/CMIP/KIOST/KIOST-ESM/historical/r1i1p1f1/Amon/ta/gr1/v20191104
shape: (1980, 2, 2, 1), calendar: 365_day
CMIP6/CMIP/NCAR/CESM2-WACCM/historical/r1i1p1f1/Amon/ta/gn/v20190227
shape: (1980, 2, 3, 2), calendar: 365_day
CMIP6/CMIP/NASA-GISS/GISS-E2-1-H/historical/r1i1p1f1/Amon/ta/gn/v20190403
shape: (1368, 2, 1, 1), calendar: 365_day
CMIP6/CMIP/CSIRO/ACCESS-ESM1-5/historical/r1i1p1f1/Amon/ta/gn/v20191115
shape: (780, 2, 2, 1), calendar: proleptic_gregorian
CMIP6/CMIP/NOAA-GFDL/GFDL-ESM4/historical/r1i1p1f1/Amon/ta/gr1/v20190726
shape: (780, 2, 2, 2), calendar: 365_day
CMIP6/CMIP/CMCC/CMCC-CM2-SR5/historical/r1i1p1f1/Amon/ta/gn/v20200616
shape: (780, 2, 3, 2), calendar: 365_day
CMIP6/CMIP/CCCma/CanESM5/historical/r1i1p1f1/Amon/ta/gn/v20190429
shape: (1980, 2, 2, 1), calendar: 365_day
CMIP6/CMIP/BCC/BCC-CSM2-MR/historical/r1i1p1f1/Amon/ta/gn/v20181126
shape: (1020, 2, 2, 2), calendar: 365_day
CMIP6/CMIP/INM/INM-CM4-8/historical/r1i1p1f1/Amon/ta/gr1/v20190605
shape: (780, 2, 1, 2), calendar: 365_day
CMIP6/CMIP/NCC/NorESM2-MM/historical/r1i1p1f1/Amon/ta/gn/v20191108
shape: (780, 2, 3, 2), calendar: 365_day
CMIP6/CMIP/E3SM-Project/E3SM-1-1/historical/r1i1p1f1/Amon/ta/gr/v20191211
shape: (780, 2, 2, 2), calendar: 365_day
CMIP6/CMIP/CAS/FGOALS-f3-L/historical/r1i1p1f1/Amon/ta/gr/v20190927
shape: (780, 2, 2, 2), calendar: 365_day
CMIP6/CMIP/NASA-GISS/GISS-E2-1-G/historical/r1i1p1f1/Amon/ta/gn/v20180827
shape: (1368, 2, 1, 1), calendar: 365_day
CMIP6/CMIP/MPI-M/MPI-ESM1-2-HR/historical/r1i1p1f1/Amon/ta/gn/v20190710
shape: (780, 2, 2, 3), calendar: proleptic_gregorian
CMIP6/CMIP/AS-RCEC/TaiESM1/historical/r1i1p1f1/Amon/ta/gn/v20200623
shape: (1980, 2, 3, 2), calendar: 365_day
CMIP6/CMIP/INM/INM-CM5-0/historical/r1i1p1f1/Amon/ta/gr1/v20190610
shape: (780, 2, 1, 2), calendar: 365_day
CMIP6/CMIP/NASA-GISS/GISS-E2-1-G-CC/historical/r1i1p1f1/Amon/ta/gn/v20190815
shape: (1368, 2, 1, 1), calendar: 365_day
CMIP6/CMIP/CAS/FGOALS-g3/historical/r1i1p1f1/Amon/ta/gn/v20190818
shape: (804, 2, 1, 2), calendar: 365_day
CMIP6/CMIP/NUIST/NESM3/historical/r1i1p1f1/Amon/ta/gn/v20190630
shape: (1980, 2, 1, 2), calendar: gregorian
CMIP6/CMIP/CAMS/CAMS-CSM1-0/historical/r1i1p1f1/Amon/ta/gn/v20190708
shape: (900, 2, 2, 2), calendar: 365_day
CMIP6/CMIP/CMCC/CMCC-CM2-HR4/historical/r1i1p1f1/Amon/ta/gn/v20200904
shape: (780, 2, 3, 2), calendar: 365_day
CMIP6/CMIP/NCAR/CESM2/historical/r1i1p1f1/Amon/ta/gn/v20190308
shape: (1980, 2, 3, 2), calendar: 365_day
CMIP6/CMIP/CCCR-IITM/IITM-ESM/historical/r1i1p1f1/Amon/ta/gn/v20191226
shape: (780, 2, 1, 2), calendar: julian
CMIP6/CMIP/E3SM-Project/E3SM-1-0/historical/r1i1p1f1/Amon/ta/gr/v20191220
shape: (780, 2, 2, 2), calendar: 365_day
CMIP6/CMIP/AWI/AWI-CM-1-1-MR/historical/r1i1p1f1/Amon/ta/gn/v20181218
shape: (780, 2, 2, 3), calendar: proleptic_gregorian
CMIP6/CMIP/THU/CIESM/historical/r1i1p1f1/Amon/ta/gr/v20200417
shape: (1980, 2, 3, 2), calendar: 365_day
CMIP6/CMIP/NOAA-GFDL/GFDL-CM4/historical/r1i1p1f1/Amon/ta/gr1/v20180701
shape: (780, 2, 2, 2), calendar: 365_day
CMIP6/CMIP/FIO-QLNM/FIO-ESM-2-0/historical/r1i1p1f1/Amon/ta/gn/v20191204
shape: (780, 2, 3, 2), calendar: 365_day
CMIP6/CMIP/CCCma/CanESM5/historical/r1i1p1f1/Amon/ta/gn/v20190306
shape: (1980, 2, 2, 1), calendar: 365_day
CMIP6/CMIP/IPSL/IPSL-CM6A-LR/historical/r1i1p1f1/Amon/ta/gr/v20180803
shape: (1980, 2, 2, 1), calendar: gregorian
CMIP6/CMIP/NCC/NorCPM1/historical/r1i1p1f1/Amon/ta/gn/v20200724
shape: (1980, 2, 2, 1), calendar: 365_day
CMIP6/CMIP/HAMMOZ-Consortium/MPI-ESM-1-2-HAM/historical/r1i1p1f1/Amon/ta/gn/v20190627
shape: (780, 2, 1, 2), calendar: proleptic_gregorian
CMIP6/CMIP/MPI-M/MPI-ESM1-2-LR/historical/r1i1p1f1/Amon/ta/gn/v20190710
shape: (780, 2, 1, 2), calendar: proleptic_gregorian
CMIP6/CMIP/CAS/CAS-ESM2-0/historical/r1i1p1f1/Amon/ta/gn/v20200502
shape: (1980, 2, 2, 2), calendar: 365_day
CMIP6/CMIP/MIROC/MIROC6/historical/r1i1p1f1/Amon/ta/gn/v20190311
shape: (780, 2, 1, 2), calendar: gregorian
CMIP6/CMIP/MRI/MRI-ESM2-0/historical/r1i1p1f1/Amon/ta/gn/v20190308
shape: (780, 2, 2, 2), calendar: proleptic_gregorian
CMIP6/CMIP/SNU/SAM0-UNICON/historical/r1i1p1f1/Amon/ta/gn/v20190323
shape: (780, 2, 3, 2), calendar: 365_day
CMIP6/CMIP/NCC/NorESM2-LM/historical/r1i1p1f1/Amon/ta/gn/v20190815
shape: (780, 2, 2, 1), calendar: 365_day
CMIP6/CMIP/E3SM-Project/E3SM-1-1-ECA/historical/r1i1p1f1/Amon/ta/gr/v20200624
shape: (780, 2, 2, 2), calendar: 365_day
CMIP6/CMIP/BCC/BCC-ESM1/historical/r1i1p1f1/Amon/ta/gn/v20181217
shape: (1980, 2, 2, 1), calendar: 365_day
CMIP6/CMIP/CSIRO-ARCCSS/ACCESS-CM2/historical/r1i1p1f1/Amon/ta/gn/v20191108
shape: (780, 2, 2, 1), calendar: proleptic_gregorian
CMIP6/CMIP/EC-Earth-Consortium/EC-Earth3/historical/r1i1p1f1/Amon/ta/gr/v20200310
shape: (780, 2, 3, 3), calendar: proleptic_gregorian

That's good right? That's realistic. Actually this is what was leading to all the bugs before, and it's partly the reason I wanted to clean up some of the time handling code in the multi-model module.

It's not realistic if I the regridding and concatenation fails before the data even gets to the multimodel tests. At this point I'd rather have a dataset that must work with the multimodel test and expand from there.

Fixed by #7


Can't make button left on desktop center on mobile

Describe the bug
Hey, I can't make button left on desktop , center on mobile.
To Reproduce
  <mj-head>
  <mj-style>

        @media only screen and (max-width: 500px) {
            .hello {
                width: 200px !important;
            }
        }
  @media all and (max-width: 480px) {
        .align div {
          text-align: center!important;
  				align: center!important;

        }

      }

   @media all and (min-width: 480px) {

  			.balign td{
           align: left!important;
        }
      }

    </mj-style>

  </mj-head>
  <mj-body>
    <!-- Side image -->
<mj-section background-color="white">

  <!-- Left image -->
  <mj-column>
    <mj-image width="250px" src="http://placekitten.com/200/300" />
  </mj-column>

  <!-- right paragraph -->
  <mj-column>
    <mj-text
             font-size="28px"
             font-family="Roboto,Arial"
             color="#008BFF" align="left" padding-top="25px" css-class="align">
       <a href="www.wp.pl" style="text-decoration:none"> Lorem Ipsum is </a>
      </mj-text>
    <mj-text
             font-size="16px"
             font-family="Roboto,Arial"
             color="#18191A" align="left" font-weight="300" line-height="28px" css-class="align">
        Lorem Ipsum is simply dummy text of the printing and typesetting industry.
      </mj-text>

      <mj-text font-size="13px"
             font-family="Roboto,Arial"
             color="#8894AB" align="left" font-weight="300" line-height="16px"  css-class="align" >
         Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, b</mj-text>

     <mj-button font-family="Helvetica" background-color="#303F9F" color="white" padding-top="20px"  align="center" width="168px" height="35px"  font-size="16px" css-class="balign" >
         Read more
    </mj-button>
  </mj-column>
</mj-section>

  </mj-body>
</mjml>``

@iRyusa @ProdigyMaster
Hi,
It is possible to do it using media queries. Just check this out below. This is working for me.
<mjml>   <mj-head>     <mj-style>       @media all and (max-width: 480px) {       	.im-mobile-center,         .im-mobile-center table {           text-align: center !important;         }         .im-mobile-center table {           margin: 0 auto !important;         }       }     </mj-style>   </mj-head>   <mj-body>     <mj-section >       <mj-column > 				<mj-button font-family="Helvetica" background-color="#f45e33" color="white" align="left" css-class="im-mobile-center" width="230px">           Don't click me!          </mj-button>       </mj-column>       <mj-column > 				<mj-button font-family="Helvetica" background-color="#f45e33" color="white" align="right" css-class="im-mobile-center" width="230px">           Don't click me!          </mj-button>       </mj-column>     </mj-section>   </mj-body> </mjml>

It won't really work everywhere, but if it's fine for you go for it.

Could you please help me in understanding the reasons that prompted this reply? Is there any specific use case we are aware of, in which it won't work? I am seeing that it is working in all devices on Email On Acid.

Some mobile clients doesn't support media queries. And if a desktop client doesn't support media queries, you'll have an hybrid between your mobile & desktop version (MJML is mobile first, not desktop first).

I agree that this will work only with the clients that support media queries. I am getting a device coverage of 99%+ on EOA as of now with this solution.
But yes, I take your point.


Create a desktop entry to be included in linux package release

Create a desktop entry to be included in the linux release package so that the application can be located from the menu.
Currently on linux there are three options people actually use to install lite-xl:

compile the package from source and run make install
use the arch linux package manager
use the binary package provided in the release page

People using method 1 and 3 will miss a desktop entry.
We should add a desktop entry to be installed on linux when doing "meson -C build install" (or the same thing using ninja).

Hi Matthew @djmattyg007,
I thought you may contribute this for the 1.16.4 release.
I know you are quite active for the arch-linux package and I thought you might already have what you need on hand.

The AUR package uses a program named gendesk to automatically generate a desktop entry for lite-xl:
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=lite-xl#n26
It generates the following content:
[Desktop Entry]
Version=1.0
Type=Application
Name=Lite XL
Comment=A lightweight text editor written in Lua
Exec=lite %F
Icon=lite-xl
Terminal=false
StartupNotify=false
Categories=Utility;TextEditor;Development;
MimeType=text/plain;

This seems like a suitable starting point. More adjustments can always be made in future.
For the icon to work (see the Icon= line), a file (hopefully an SVG) needs to be placed into another folder. Currently the AUR package downloads an icon provided by lite:
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=lite-xl#n48
It would probably be worth bundling a copy of this or another icon with the source, to remove a dependency on lite.

@djmattyg007 thank you, I configured something simple to package the svg icon and the desktop entry in the build-package.sh script. Otherwise I left everything unchanged so you don't need to adjust the arch-linux build recipe.

@franko no problem. it would be ideal though if the desktop entry could be stored as a standalone file, so that the AUR package can make use of it directly. I can't see any reason for the AUR to be doing something special in this regard, and "The Arch Way" is always to make use of upstream where possible.

@djmattyg007 I am okay with this. The SVG icon file is already in the repository. For the desktop file do you want to make a PR to add it ? It is just a matter of copying what is in the build-package.sh, verify its content and copy the file in the "dev-utils" folder.

@djmattyg007 Done, the desktop file is now in dev-utils/lite-xl.desktop.

Thanks for all your hard work <3

Oh, thank you, but this one was not really that hard! :-)


file_readv_compat/file_writev_compat: Fix partial success handling

Summary
The problem has been inherited from the original libc readv/writev implementation. However, now it's exposed in more situations because this implemenation is used to back read/write as well.
I expect this fixes the regressions observed on the Espressif CI. https://github.com/apache/nuttx/pull/13498#issuecomment-2448031197
Note that, even with this fix, these "compat" readv/writev implementations are still inheritedly broken. (E.g. consider that a data boundary happens to match one of iovec boundaries) However, this fix is enough for read/write, where iovcnt is always 1.
Impact
read/write on character devices or such.
Testing
Tested on esp32-devkitc, with https://github.com/apache/nuttx/pull/14479 and other changes.

[Experimental Bot, please feedback here]
No, this PR does not fully meet the NuttX requirements.  While it provides a summary of the problem and the solution, it lacks crucial details required by the template.
Here's a breakdown of missing information:

Summary:  Missing a clear statement of what functional part of the code is being changed (e.g., fs/readv.c, libc implementation, etc.). The explanation of how the change works is also vague. "This fix is enough for read/write, where iovcnt is always 1" doesn't explain the actual code changes.  Crucially, the related NuttX issue number is missing.

Impact: The impact section is severely incomplete.  It needs to address all the points in the template with specific YES/NO answers and descriptions where applicable.  Simply stating "read/write on character devices or such" doesn't adequately cover the potential impact.  Consider impacts on backward compatibility, documentation needs, and whether this is a new feature, a bug fix, or a performance improvement.

Testing:  The testing information is insufficient. While a target is mentioned (esp32-devkitc),  the build host details are absent.  More importantly, there are no "Testing logs before change" and "Testing logs after change" as requested by the template.  Even a simple demonstration of the fix working would be beneficial.  Mentioning another PR adds complexity and makes it harder to assess the impact of this specific change in isolation.

To make this PR compliant, the author needs to:

Clarify the Summary: Specify the affected files and provide a more technical explanation of the code changes.  Include the related NuttX issue number.

Complete the Impact Assessment: Answer all the questions in the Impact section with YES/NO and provide details where necessary.

Provide Adequate Testing Information:  List the build host details (OS, CPU, compiler).  Include "before" and "after" logs demonstrating the fix, even if they are simple. Ideally, the test should be self-contained and not rely on other PRs.

@yamt do you have some suggestion to implement a fix that works for all cases?
@anchao @xiaoxiang781216 @pkarashchenko what do you think?

@yamt do you have some suggestion to implement a fix that works for all cases?

please read the commit message of https://github.com/apache/nuttx/pull/13498


Switch to faster String#indexOf method taking a char parameter.

Sorry, my last pull request missed two places. :(

Merged. Thanks again ;-)


Running entirely from c++?

Hi, and thank you for making this code available!
I would like to run an entire sfm pipeline from scratch using c++ only, with no python.
I see it is possible to link this code as a library, but the example.cc does not show how to run it.
Would it be possible to add a working c++ example please?
Thanks again!

Hi @antithing, the current C++ part lacks an implementation of dense feature extraction and storage, thus running pixsfm entirely from C++ is not possible. However, if you assume to have features stored in an h5 file, all other steps could be run from C++. At the moment I have not planned to write a tutorial for it, but I would be happy to answer any questions you might have about the C++ API.

Hi @Phil26AT I am digging back into this, would you be able to point me in the right direction to get started with a c++ only pipeline? What steps are needed, and where are the functions?
Thank you!

@Phil26AT nudging this, would you be able to give me a push in the right direction to build a fully c++ pipeline please?
Thanks!


update to new applet reply

This makes apdu-dispatch a non-optional dependency again, right?
I'd really like to avoid that.

Alright, back to iso7816 types, with apdu-dispatch only pulled in if its App trait is needed.
The PR can now be summed up as "make command/reply types configurably sized".


catalina - error: failed to run custom build command for shaderc v0.3.16

Compiling aho-corasick v0.7.6
error: failed to run custom build command for shaderc v0.3.16
Caused by:
process didn't exit successfully: /Users/johndpope/Documents/gitWorkspace/shadertoy-browser/test/release/build/shaderc-8859e5aa0099e6c0/build-script-build (exit code: 101)
--- stderr
thread 'main' panicked at '
couldn't find required command: "cmake"
', /Users/johndpope/.cargo/registry/src/github.com-1ecc6299db9ec823/shaderc-0.3.16/build/cmd_finder.rs:45:13
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace.
warning: build failed, waiting for other jobs to finish...
I tried appending  --target-dir to see if it helped - it didn't.
cargo build --release  --target-dir test

This lists the tools that are required to build shaderc: https://github.com/google/shaderc. You need cmake and python


ZEPPELIN-2035. BI directional RPC framework between ZeppelinServer and InterpreterProcess on top of thrift

What is this PR for?
This PR introduce the bi directional RPC framework between ZeppelinServer and InterpreterProcess on top of thrift, see the design doc here. https://docs.google.com/document/d/1B_4b7UuvE7RwbfpTjxV2RSxdDeF-p9vXVYC8ace76-Q/edit?usp=sharing
This PR is pretty big, most of the code changes is due to regeneration of thrift code.
Another improvement is introduce the builder pattern of InterpreterContext as the arguments of InterpreterContext constructor is too many.
What type of PR is it?
[ Improvement | Refactoring]
Todos

[ ] - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-2035

How should this be tested?

CI pass

Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

Thanks @zjffdu for the improvement.
Overall looks good to me. I'd like to see CI goes green before merge while it change code a lot.
One question. Let's say in the future, zeppelin have capability to run interpreter as a container in the remote machine for scalability. For example, run interpreter in in k8s cluster or docker host in remote machine. Initiating communication between ZeppelinServer and interpreter will require firewall setup, port export/mapping on container service.
What would be the simplest connectivity model in this case?
I guess initiating one connection from Interpreter -> ZeppelinServer is simplest way? Because of interpreter running in container on remote host doesn't need to allow incoming connection (no firewall, container port mapping). Only single known port of ZeppelinServer need to accept the connection from all interpreters running remotely. Will there be other connectivity model keep network configuration simple?
With the consideration with connectivity model that minimize user's network configuration, what would be the future direction of bidirectional rpc between ZeppelinServer and Interpreter?

There's 2 properties (zeppelin.server.rpc.portRange and zeppelin.interpreter.rpc.portRange) that could be used to constrain the portRange of zeppelin server rpc and interpreter process rpc. And user can config these 2 properties to use a fixed port so that user can just expose this fixed port on containers.  @Leemoonsoo  Is this what you concern ?

I was thinking the cases like a (or more) firewalls, NATs between Server and Interpreters.
And accepting range of ports on each side is more difficult to configure than accepting a single port in one side.
But for now, Interpreter runs in the same host where Server runs. So not a concern unless Zeppelin have ability to run Interpreter in remote machines.

For now yarn-cluster mode of spark interpreter is the only use case that run interpreter process in remote host. And we use property to config the portRange for the remote spark interpreter connect back to zeppelin server. In future we may runt all the other interpreters in containers which is another scenario of running interpreter in remote host. For this scenario, I think it is easy to expose one port when starting this container which is not difficult IIUC based on my limited knowledge on containers. BI directional RPC is very common pattern in distributed computing, I think it is worth to use Bi directional RPC in zeppelin with regarding its benefits mentioned int he design doc.  @Leemoonsoo  What do you think ?

Thanks @Leemoonsoo Any more comment ？

@Leemoonsoo If no more comments, I will merge it to continue the rest of the work


Lib/sys todo

[ ] platform: add pysince:

Changed in version 3.3: On Linux, sys.platform doesn’t contain the major version anymore. It is always 'linux', instead of 'linux2' or 'linux3'. Since older Python versions include the version number, it is recommended to always use the startswith idiom presented above.

Changed in version 3.8: On AIX, sys.platform doesn’t contain the major version anymore. It is always 'aix', instead of 'aix5' or 'aix7'. Since older Python versions include the version number, it is recommended to always use the startswith idiom presented above.

[ ] allow sys.stdout=None (for print doing nothing)

sys.tracebacklimit  (nodejs Error.stackTraceLimit)


selectTextStyle has wrong propTypes

If you set textAlign or color on the selectTextStyle prop, you get a warning:
Failed prop type: Invalid props.selectTextStyle key 'color' supplied to 'ModalSelector'.
I looked into the source code, and found that index.js:29 has this:
selectTextStyle:           ViewPropTypes.style,
should be:
selectTextStyle:            Text.propTypes.style
I'll put in a pull request for it if this looks like a valid bug to you

Hi @mienaikoe
A PR would be fantastic.  Can selectTextStyle be both a string and style object?  If so, add both as an array to PropTypes.oneOfType

hey @peacechen
I think selectTextStyle can only be a style object. The string for the cancel text would be set on the cancelText prop.
I'll do a PR

Merged. Thanks the the PR :+1: