Confirm emissions paths in user_nl_cam_p17c_mam7_2000

Use identical files to MAM3 runs where possible? What are the differences between the files in the default paths?

Having quickly explored the difference between the c090726emissions files (used by MAM3 by default) and the c120315emissions files (used by MAM7 by default) using cdo diffv  and ncdump -h, it would appear the only difference is that for the MAM7 files the date has been shifted using ncap -s date=date+20000000. Hence the emissions should be the same. I will use the MAM7 default c120315 emissions files for the MAM7 simulations.


Stop downloading wal if the security token expired

This prevent wal-e to try downloading wal indefinitely if the AWS security token expired.
See #314

hey, I recently hit this bug too. Did something happen to STS recently?

@fdr something happens to STS every 36h. It expires. =D

But why was it latent for years? Oh well.

@fdr We've been hitting this issue for years, just too rarely to bother fixing. Although given the size of the fix, perhaps we should have been more ambitious.


pyrealsense2 for Mac

I'm trying to install pyrealsense2 with pip and pip3 install on python 3.8 and get the next error:
ERROR: Could not find a version that satisfies the requirement pyrealsense2 (from versions: none)
ERROR: No matching distribution found for pyrealsense2
what can I do about it?

Hi @Roee1989   The pyrealsense2 pip packages are designed for PC computers with x86 / x64 processor architecture.
A RealSense user at https://github.com/IntelRealSense/librealsense/issues/9687 created a pre-built Mac version of pyrealsense2 with an automated installer that allows use of pip install pyrealsense2 on MacOS, though it was only tested with the Catalina and Big Sur MacOS versions so far.

@MartyG-RealSense Great! It worked for me since I'm using Catalina.
After installation I tried to use the camera with pyrealsense2 and encountered the following error:
pipeline.start()
RuntimeError: No device connected
I'm using the provided usb cable and when working on PC everything is working.

Is the case at https://github.com/IntelRealSense/librealsense/issues/10036 created by yourself under a different GitHub account name please, as it seems to describe the same situation.  Thanks!

How do I use the viewer on Mac?
I'm still having the same RuntimeError.
I tried to follow https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_osx.md as the thread you linked suggests.
I was able to install and build librealsense as described, I also ran "install_name_tool -change /usr/local/opt/libusb/lib/libusb-1.0.0.dylib @rpath/libusb-1.0.0.dylib librealsense2.dylib" command and copied the files to the framework dir (copied to /Library/Frameworks/Python.framework ) but still no change.
Seems like the installation had no effect.
Any suggestion?

Are you experiencing the error if you launch the Viewer by inputting realsense-viewer into the terminal?

When executing in terminal I get this error:
command not found: realsense-viewer

Is the Viewer built if you include the CMake term DBUILD_GRAPHICAL_EXAMPLES=true in the CMake build instruction to build tools that use graphics such as the Viewer and Depth Quality Tool?
So applying this to the suggested CMake instruction in the official Mac guide:
cmake .. -DBUILD_EXAMPLES=true -DBUILD_GRAPHICAL_EXAMPLES=true -DBUILD_WITH_OPENMP=false -DHWM_OVER_XU=false

Hi @Roee1989  Do you require further assistance with this case, please?  Thanks!

I passed the following flags:
cmake -DBUILD_EXAMPLES=true -DBUILD_WITH_OPENMP=false -DHWM_OVER_XU=false -DBUILD_GRAPHICAL_EXAMPLES=true
Than make -j2 and tried to run the viewer, still same result...
command not found: realsense-viewer

There was a Mac case at https://github.com/IntelRealSense/librealsense/issues/9319 where the RealSense user in that case also experienced ** command not found: realsense_viewer** on Mac when trying to launch the Viewer.  They eventually found that the realsense-viewer command worked if they built SDK version 2.44.0

I'm able to launch the viewer manually from folder. In the viewer I can't find a device.

I'm currently using viewer version 2.5. How do I downgrade it to 2.44.0?

May I first ask which RealSense camera model you are using with the Viewer?

L515

And is the camera detected in the Viewer if you unplug the micro sized end of the USB cable from the base of the camera, turn the connector around the other way and re-insert it into the camera (USB-C cables are two way insertion at the micro-sized end)

Tried the cable’s micro sized end turn, the viewer doesn’t detect a device.

I carefully researched how one might approach building an older version of librealsense from source code with CMake on Mac but could not find a clear guide for doing so and I do not have a Mac computer at my location to test with.  I therefore cannot offer advice on doing so with confidence in its correctness, unfortunately.
So to recap, you are using MacOS Catalina, so it is not a problem related to MacOS Monterey.  You also confirmed on a PC computer that your camera hardware works correctly.
Was the PC computer using Windows or Linux?
Can you confirm whether your Mac is an Intel model or a newer Apple Silicon M1 model?
Are you using the camera on a Mac with a USB 3 port?  In a discussion in the link below, a RealSense team member advises that an L515 might encounter problems on a Mac model without USB 3 ports - such as MacBook Pro - that has the camera connected via an adapter to a Thunderbolt port.
https://support.intelrealsense.com/hc/en-us/community/posts/4406814535699-Error-occurs-when-using-L515-on-Macbook

The PC is running on windows 10. The Mac is an intel model with 3.0 USB port.

Which firmware version is currently installed on your L515, please?  If it is not the current latest version (<IP_ADDRESS>), could you update the firmware to 1.5.81 on your Windows PC in the RealSense Viewer using the following procedure.

Download firmware version <IP_ADDRESS> as a 'bin' file from the L515 firmware page.

https://dev.intelrealsense.com/docs/firmware-releases-l500

Launch the Viewer on the Windows PC, go to the 'More' option in the Viewer side-panel and select the Update Firmware menu option.  A file selector window will pop up.  Navigate to the downloaded <IP_ADDRESS> firmware file's location on the computer and select it to commence the firmware update.

If you update the firmware, does it make a difference to whether the L515 is detected in the Mac version of the Viewer?

Hi @Roee1989  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.

Case closed due to no further comments received.

@MartyG-RealSense I also experienced the No device connected issue on pipeline start with version 2.50.0 of the librealsense library I have prebuilt for python (https://github.com/cansik/pyrealsense2-macosx/issues/2). Getting the current device count works, but starting the pipeline does not. With version 2.49.0, the device can still be opened and accessed. It seems that there is something wrong in the 2.50.0 code base, maybe also related to: https://github.com/IntelRealSense/librealsense/issues/9916#issuecomment-998684578

Hi @cansik  Thanks again for your excellent pre-built pyrealsense2 project for MacOS!
Thanks too for your report.  Can you add a comment about your 2.50.0 problems on Big Sur to https://github.com/IntelRealSense/librealsense/issues/9916 please so that it can be read by Intel when they investigate the Monterey issues, please?  Thanks!


Update to address warning about using java11

Using<EMAIL_ADDRESS>is giving a warning from SonarCloud bot:
The version of Java (11.0.17) you have used to run this analysis is deprecated and we will stop accepting it soon. Please update to at least Java 17. Read more here
See e.g. https://github.com/bcgov/nr-forests-access-management/pull/777#issuecomment-1675033663
We are NOT getting this warning when using the Sonar github action directly - e.g. SonarSource/sonarcloud-github-action@master

There was so little action in this repo that Dependabot went dormant!  Hopefully this is the fix: https://github.com/bcgov-nr/action-test-and-analyse/pull/23.
It's going out in the next release, which should be very soon.

Replaced by https://github.com/bcgov/nr-forests-access-management/issues/782


python3Packages.surepy: init at 0.5.0

Motivation for this change
Python library to interact with the Sure Petcare API
https://github.com/benleb/surepy
This is a Home Assistant dependency.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 112981 at b3f5d13a run on x86_64-linux 1

1 package built:

python38Packages.surepy


To fix memory leaks on CRUD

Travis build test failures will pass once wrp-c PR is merged and use latest git tag.
https://github.com/Comcast/wrp-c/pull/62


Ribbons representation not displaying for DNA

To reproduce:
mol = mdt.build_dna_helix('ACTGCGTA')
viewer = mol.draw(display=True)
viewer.ribbon()

got:

Result with moldesign 0.7.2 / nbmolviz 0.6.5:

@avirshup I might need to sit down with you for a minute tomorrow to look into this.  I'm not able to draw this directly in 3dmol.  Using the data from that molecule, then trying to set the style for the whole molecule to "cartoon" just results in a blank page (like you saw).
Do you remember if that's how you were originally drawing these?  With "cartoon"?  Anything else that might have gotten removed from the code?

Yeah - "cartoon" sounds right. Happy to sit down with this; it might be helpful to try comparing the 3DMol JSON data between the working and non-working versions.
I remember having this same problem a very long time ago when I first started working on the project, but I have no idea how it got fixed the first time. My guess would be that this has something to do with 3DMol not recognizing the molecular data specifically as DNA - maybe a naming issue or something?

Actually, I remember how I fixed this the first time - it was by writing the input files as PDB. I think 3DMol's PDB parser must be inserting some piece of metadata into its JSON representation that allows it to recognize a chain as a piece of DNA.

That was it!  I was able to render the cartoon dna via pdb.  It's a hard problem to get it to work with the rest of MDT though...  I'm going to try digging into the 3dmol source and see exactly why it doesn't work with json.  Ideally I can submit a PR to them to fix this, or as a fallback I can probably hack in the extra metadata in our code.


Element sizing

First stuff I love the new desing. Good job man!
What i'm here to describe is a problem already shown in #193, several pages and element, in the right main part of the layout not perfectly fitted for navigation without scrolling.
To be specific, this is a page where the page need a scroll:

and this is a page that not require scroll:

I understand that the stuff is related to the resolution/zoom/screen, etc... But It would be really beautiful if the fitting was dynamic.
Here for any clarification or help that I could provide.

I'm adding a list of page not correctly fitted for my case:

Logbook
Map
Statistics: Total
Export: PDF A4 (but I think that in this page a scroll is acceptable)
Export: PDF A5 (but I think that in this page a scroll is acceptable)
Settings: General (but I think that in this page a scroll is acceptable)

Hey! Thanks for the feedback! Yep, I still need to review some page elements. What is your screen resolution just for reference?

I found it in the previous #193 - 2880x1800 :)

can you show the screenshots for export pdf and settings pages?

I found it in the previous #193 - 2880x1800 :)

Fortunately I've upgrade my macbook, now is: 3024 x 1964. The issues is still present with 4K of my external monitor with a bit different behaviour.

I released some dynamic sizing for chart for the stats pages. Did it fix the issue at least a little bit? :)


Navigation state isn't saved when navigated back

Done in https://github.com/pokatomnik/MrakopediaReader2/pull/101


add transition to testimonials

Issue #152 📐

I Hanzalah Waheed have worked for #152

Guidelines 🔐
I accept the fact that I have followed the guidelines and have not copied the codes from around the internet

[x] Contribution Guidelines
[x] Code of Conduct

Issue to be closed 🛅

My pull request closes #152

Screenshots 📷
Here are the pictures of changes that I have made 🔽
Screencast from 2023-10-17 11-02-17.webm

Change Title to issue name

@warmachine028 I have made the requested changes. Please check if there is any other issue. Thanks!


Should the schema protect against trailing spaces in author names?

Spawned from https://github.com/citation-file-format/cff-initializer-javascript/issues/221

For context, is this about "cleaning up" user input from cffinit that may contain trailing spaces?
If so, I'm not sure but also don't have any strong opinion about whether this should be solved in the schema. Some points:

Given that a string contains trailing spaces, I'd assume that downstream clients/applications would be able to fix this just as well, and are perhaps in a better place to do so.
In fact, I think there's a good case to be made for cffinit cleaning up trailing spaces itself, as it is responsible for writing valid (and arguably also well-formed) CFF. From a user perspective, I wouldn't be surprised if such an app did this. But perhaps I don't understand any deeper issues in cffinit with this?
If we decide to fix this, this would be a breaking change I think, so would schedule this for v2.
Does it make sense to apply this to all strings? Do we want to guess if there are valid user inputs that should contain trailing spaces?

Given that a string contains trailing spaces, I'd assume that downstream clients/applications would be able to fix this just as well, and are perhaps in a better place to do so.

For sure this is possible, but difficult to do in a consistent manner across various tools. For example, I may use cffinit to write

Without realizing that there is a trailing space, even though it is visible in the yaml
cff-version: 1.2.0
title: Mytitle
message: Mymessage
type: software
authors:
  - given-names: 'Jurriaan H. '
    family-names: Spaaks

Even if I do notice it, it's not invalid according to the schema, so I'd say it's well formed and anyway, it's what cffinit gave me so I'm not gonna correct it as a user. But then, it's conceivable that another tool like cffconvert or ruby-cff could make different choices and assume the space is never there, potentially leading to minor errors for example when building the author's name from its constituent parts using concatenation.
Additionally, one could argue that it's odd to have a set of rules mandated by the schema, but then an additional set of rules local to a tool, which would be necessary for detecting duplicates via the schema's uniqueItems: true, for example when you have:

cffinit correctly (but counterintuitively) doesnt trigger a "duplicate item" warning because:
# This CITATION.cff file was generated with cffinit.
# Visit https://bit.ly/cffinit to generate yours today!

cff-version: 1.2.0
title: Mytitle
message: Mymessage
type: software
authors:
  - given-names: 'Jurriaan H. '
    family-names: Spaaks
  - given-names: Jurriaan H.
    family-names: Spaaks

If we decide to fix this, this would be a breaking change I think, so would schedule this for v2.

I had not realized that but I think you are correct

Does it make sense to apply this to all strings? Do we want to guess if there are valid user inputs that should contain trailing spaces?

At least we would need to go over all places that could be affected and think hard about them. Fun times.

Thanks, @jspaaks, for the explanations. I see the problem now.
I think that it would be safe to disallow trailing spaces in the author name fields (and potentially other places, to check). I'd be hard pressed to think of anywhere where trailing spaces would be valid and integral parts of a person's name.
So yes, I'd vote for implementing this, especially as it better supports deduplication.

Note:  the term "trailing whitespaces" is going to be abbreviated with TWS, in the following.

As a workaround, I would like to suggest to implement a TWS-checker in the validation tools.  This can be done quite easily with Git itself:
git grep [[:blank:]]$ CITATION.cff

If there should not be TWS on any line, the above command will exit with code 0x1 and thus fail.  If there should be at least one line containing TWS, the command will succeed with 0x0.
In my opinion, it is a sane assumption that most projects containing a valid CITATION.cff are versioned with Git, especially those requesting the validation GitHub Action.  Hence, cffconvert could run the above command and if it should succeed, there are TWS, thus cffconvert should fail.

I recommend relying on Git since grep is only available on UNIX systems and thus not on Windows.  The checking command should hence rely on a solution available to all operating systems.  Git is therefore the simplest solution.
For alternatives, just search the Rust package registry, for instance.  The Rust book itself recommends ripgrep as a portable replacement for grep.  The downside is that this approach requires not only the installation of the selected binary from source (as usual for Rust binaries) but also a Rust environment.  Thus, this will take more time than necessary when integrating this checking approach into the continuous integration workflows.  Since Git can be assumed to be installed on the CI-execution machines, it appears to me as the fastest solution when testing for multiple files and operating systems.  When just testing on Linux images against the CITATION.cff, grep will fulfill this task, as well.

I realize my nomenclature is a bit confusing, because the problem is not exacty the same as what normally goes for "trailing": I was referring to trailing, but inside the quoted string (which may lead to duplication problems that may go unnoticed by current tooling). With that interpretation of trailing, I don't think the git grep command would be a solution (although I confess I didnt try it out). Am I right in sayiung that such a command is more or less the equivalent of pre-commit's trailing-whitespace rule?:

Basically, yes, the named Git alias command is about the same idea.  But it is actually intended to identify those files which cannot be found by pre-commit's hook anymore.  This is the case when those files were checked in before the hook to reject files containing TWS was set up.  So it is basically a post-commit action to fix the associated bugs.

Anyway, the idea to protect the schema using a (different) regex seems a reasonable option to me.  Which regex constructs are allowed in the schema definition?    This regex would also reject strings with multiple blanks between the words which is also related to the topic of this issue.

FWIW I just made a PR that uses "^(\\S+)( \\S+)*$" which I think is conceptually the same as what @kevinmatthes wrote, comments welcome.

PR #466 was merged, closing this issue.


circle: make build

this is neccessary to build the Dockerfile:
Example failure in drone:
https://ci.ops.clever.com/github.com/Clever/postgres-to-redshift/master/67339d1b8bb981cd6c71037530ece3a7fe119156
Example failure in CircleCI:
https://circleci.com/gh/Clever/postgres-to-redshift/4

The failure is that the binary doesn't exist:
Step 4 : COPY bin/postgres-to-redshift /usr/local/bin/postgres-to-redshift
lstat bin/postgres-to-redshift: no such file or directory

LGTM, thanks!


Minor fixes in new doc in Quantization section

OPS Build status updates of commit 9c1c483:
:clock10: Preparing: average preparing time is 45 sec(s)

OPS Build status updates of commit 9c1c483:
:clock10: Full build: average full build time is 23 sec(s) [calculated from last 3 build(s)]

Note: A full build takes more time than an incremental build.  This is the expected behavior of the build system.

OPS Build status updates of commit 9c1c483:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/convert-model-winmltools.md
:white_check_mark:Succeeded
View

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

  This is the expected behavior of the build system.

OPS Build status updates of commit 23ffb9c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/convert-model-winmltools.md
:white_check_mark:Succeeded
View

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


question about storage_jdbc

Hi,
Could anyone give an example of a database I could use in an AWS environment?
I tried to put in a redis url, that didn't quite work and I am not sure if dynamodb is supported or how its jdbc URI would look like.
Thanks,
Itamar.

Hi,

For testing purposes you can use h2 (in-memory) database. When Lighter is launched without provided url, this database is used.
For Production environment on AWS we are using Amazon RDS for PostgreSQL
For any other SQL database you'd have to add additional JDBC driver here: https://github.com/exacaster/lighter/blob/master/server/build.gradle#L57
For any other storage, ApplicationStorage interface has to be implemented and contributed to the Lighter project :)

A thousand thanks!


Create a timeline

College student, active Student Council member, loves to read manwha, loves css and ui design but bored sometimes

draft changes

updated resume timeline


[WIP] bash -> rust

Don't make much sense rn. Will make sense soon.

Is this still relevant after #1899?

Yes it is. This is meant as api for rewriting bash tests in rust. I will have more progress tomorrow.

Yea, me and manmeet are working together on this to integrate the 2

(remember to add this in)

Finally working.
This can now setup a dev federation with all the daemons.
Next step is latency tests or tmuxinator.
I will try latency tests because I have most of the code already.

Reviewers: try running ./scripts/tmuxinator.sh

wasm tests are failing, probably some editing to nix or cargo files. will look into it later.

wasm tests are failing, probably some editing to nix or cargo files. will look into it later.

Yeap. Need to add the new crate dir to the dirs list for client-pkgs in flake.crane.nix.

Addressed the feedback.
Things to try locally: tmuxinator and latency tests


v1 improvements/clarifications

I went through the rule overrides inside index.js and here are my comments:

'react/jsx-handler-names': ['off'] - Isn't this one already off in airbnb-base, so no need to turn it off here? https://github.com/airbnb/javascript/blob/9c181108a7f11be1b97191f17c9ab2dc98e28c6e/packages/eslint-config-airbnb/rules/react.js#L83
'react/react-in-jsx-scope': 'error', - Isn't this one already error in airbnb-base, so no need to off it here? https://github.com/airbnb/javascript/blob/9c181108a7f11be1b97191f17c9ab2dc98e28c6e/packages/eslint-config-airbnb/rules/react.js#L229
'array-callback-return': 'warn' - I think this one would be nice to enforce to reduce confusion when reading code and prevent developer from forgetting to return a value
no-unused-vars - I think this should be on. I don't know the use case of having unused variables declared (if testing code, we can comment out instead, or eslint disable line)
'max-len': 'warn' - I don't like warnings in general, they tend to build up and then you just ignore them and never fix any of them. IMO either use error, or disable the rule altogether
key-spacing I understand that you really like the alignment of property keys, but I find this rule a bit anti-productive. Everytime when changing the longest key name, I need to also fix spacing on the other keys. Maybe it can be solved automatically with prettier or similar, we could look into that. Another issue is that it leads to unneccesarily long commit diffs.
quotes.allowTemplateLiterals: true - I'm not sure why this is desired? With the default value false it will still allow backticks when there is a variable inside or for multiline strings
comma-dangle why is this disabled for imports, exports and functions only? The default (always-multiline) reduces commit diffs in many cases when adding/removing lines of code
dot-notation IMO this is subjective, I don't think that state['asdf'] reads better than state.asdf
camelcase I'm guessing we are using different cAs_InG in a lot of code and it's too much work (and too risky) to change this? or you prefer mixing casing in variables?
no-console while it's ok for node.js apps to console.log, it's not generally true for browser/client apps like React, so I'm not sure if it should default to off for all projects
no-fallthrough I'm guessing too much work to enable this
node/no-path-concat - I think this one is a good rule as it can make code work on non-unix systems too (maybe not a priority for transloadit but it's a good practice). And it can prevent accidental paths joining with double or missing slashes. e.g. '/foo/bar/' + '/file.jpg' leads to /foo/bar//file.jpg and '/foo/bar' + 'file.jpg' leads to /foo/barfile.jpg
why is 'react/no-unused-prop-types': 'error' while 'react/prop-types': ['off'] ? can we remove the first one?
'react/require-render-return': ['off'] What's the reason for disabling this? Correct me if I'm wrong but I think react will crash if render() returns undefined so it's good to guard against?
'no-template-curly-in-string': ['off'] I'm sure there's a good reason for disabling it, but if not then this rule could prevent accidentally using ${variable} in a normal string instead of backticked string
'no-useless-escape': ['off'] - I think u\nn\e\cc\e\s\\ar\ily escapes makes it harder to read regexes and other code. why is this turned off?
'no-continue': ['off'] - I think continue can usually be rewritten to a function (return) or if statements but if you prefer using continue i'm not much against that either.
'arrow-body-style': ['off'] not a big issue but I'm not sure when it's useful to have a single long line with the return statement inside (if that was the usecase)
'no-cond-assign': ['off'] I agree that experienced developers should know the difference between = and ==/===, but in the years before eslint I did actually mistype this and pulling my hair out wondering why it doesn't work. Maybe we instead could  useeslint-disable-next-line explicitly when we know that we want to assign inside a conditional?
'react/jsx-closing-tag-location': ['off'] I think that XML reads better and is easier to navigate when end tag is aligned with starting tag. If eslint --fix causes breakage, maybe better to disable the rule for the offending project or file and not disable globally in our central config eslint
'import/extensions': ['warn'] maybe move this warning rule into projects that have a lot of require('xx.js')?
'no-alert': ['warn'] - alert is really not good to use in user-facing code, maybe should instead move this warn into files or projects that need to use "alert" (i'm guessing internal applications), and not have it a a global warn
'no-restricted-properties': ['warn'] I understand that many projects are using deprecated globals, but maybe this rule should be disabled on those projects instead of being disabled for all other (and new) projects as well
'default-case': ['warn'] not so fan of warnings as it will drown in a sea of other warnings. IMO either disable in offending projects or remove this rule completely

Also I see that typescript was added - why is it a necessary dependency?

'react/jsx-handler-names': ['off'] - Isn't this one already off in airbnb-base, so no need to turn it off here? https://github.com/airbnb/javascript/blob/9c181108a7f11be1b97191f17c9ab2dc98e28c6e/packages/eslint-config-airbnb/rules/react.js#L83
'react/react-in-jsx-scope': 'error', - Isn't this one already error in airbnb-base, so no need to off it here? https://github.com/airbnb/javascript/blob/9c181108a7f11be1b97191f17c9ab2dc98e28c6e/packages/eslint-config-airbnb/rules/react.js#L229

:+1:

'array-callback-return': 'warn' - I think this one would be nice to enforce to reduce confusion when reading code and prevent developer from forgetting to return a value
no-unused-vars - I think this should be on. I don't know the use case of having unused variables declared (if testing code, we can comment out instead, or eslint disable line)

Moved the warnings to the api repo, so we can fix and remove override locally

'max-len': 'warn' - I don't like warnings in general, they tend to build up and then you just ignore them and never fix any of them. IMO either use error, or disable the rule altogether

we could do that in a next major, but i think warnings are helpful as a grace period, we can't fix everything in one moment.

key-spacing I understand that you really like the alignment of property keys, but I find this rule a bit anti-productive. Everytime when changing the longest key name, I need to also fix spacing on the other keys. Maybe it can be solved automatically with prettier or similar, we could look into that. Another issue is that it leads to unneccesarily long commit diffs.

VS Code does this automatically upon save for me, i think fixing people's setups in this way prevents most of the friction while improving readability.

quotes.allowTemplateLiterals: true - I'm not sure why this is desired? With the default value false it will still allow backticks when there is a variable inside or for multiline strings

We have a lot of code defaulting to backticks, and that makes it easy to add errors or variables later on. Also it can look more consistent when you have 5 lines assigning values and only 3 of them use backticks but 2 use single quotes.

comma-dangle why is this disabled for imports, exports and functions only? The default (always-multiline) reduces commit diffs in many cases when adding/removing lines of code

:+1: changed

dot-notation IMO this is subjective, I don't think that state['asdf'] reads better than state.asdf

I think so too, which is also the point that Evgenia made, that I imported from the content repo. I think we are in agreement and it can remain off? Or maybe i misunderstand.

camelcase I'm guessing we are using different cAs_InG in a lot of code and it's too much work (and too risky) to change this? or you prefer mixing casing in variables?

I think there are a lot of cases in the api, where we take values like {assembly_id} from api communication with the outside world, can can then easily follow along that var, instead of assigning it to something else because: camel is better. I also think all transloadit coders have already established to use camel in other cases though. I haven't seen awkward casing in the wild when there wasn't a similar reason for it, i think.

no-console while it's ok for node.js apps to console.log, it's not generally true for browser/client apps like React, so I'm not sure if it should default to off for all projects

Agree :ok_hand:

no-fallthrough I'm guessing too much work to enable this

But also a question about its usefulness, i have seen legitimate cases for using fallthroughs and haven't seen a critical bug due to it yet i think :thinking:

node/no-path-concat - I think this one is a good rule as it can make code work on non-unix systems too (maybe not a priority for transloadit but it's a good practice). And it can prevent accidental paths joining with double or missing slashes. e.g. '/foo/bar/' + '/file.jpg' leads to /foo/bar//file.jpg and '/foo/bar' + 'file.jpg' leads to /foo/barfile.jpg

For the time being, our focus is on linux/macos/bsd:

I think a longterm goal can be fixing it, but it is adding a whole bunch of characters to our scripts until then while they won't be windows compatible even after adding them. I think maybe for a major v5, we can turn it back on for instance

why is 'react/no-unused-prop-types': 'error' while 'react/prop-types': ['off'] ? can we remove the first one?

Good catch, i mostly copied over Evgenia's setup from content regarding the react things, i have little experience there.

'react/require-render-return': ['off'] What's the reason for disabling this? Correct me if I'm wrong but I think react will crash if render() returns undefined so it's good to guard against?

Unsure, same reason as above, removed it.

'no-template-curly-in-string': ['off'] I'm sure there's a good reason for disabling it, but if not then this rule could prevent accidentally using ${variable} in a normal string instead of backticked string

iirc, it would prevent us from doing '{YOUR_AUTH_KEY}', but we have a lot of those, and escaping all of them is less favorable imho

'no-useless-escape': ['off'] - I think u\nn\e\cc\e\s\ar\ily escapes makes it harder to read regexes and other code. why is this turned off?

The autofix made an error corrupting code in an older release, we can try to enable it but the scars got me cautious around this one.

'no-continue': ['off'] - I think continue can usually be rewritten to a function (return) or if statements but if you prefer using continue i'm not much against that either.

For a later major, i agree,  it is also under  // perhaps enable in future release? for now however, continue is our bread and butter, and warnings is just too much, as is rewriting all our for/callback loops to functions in an instant.

'arrow-body-style': ['off'] not a big issue but I'm not sure when it's useful to have a single long line with the return statement inside (if that was the usecase)

i think an autofix rewrite ended up creating very long chains of this, which i thought were hard to make sense of when comparing to previous look

'no-cond-assign': ['off'] I agree that experienced developers should know the difference between = and ==/===, but in the years before eslint I did actually mistype this and pulling my hair out wondering why it doesn't work. Maybe we instead could  useeslint-disable-next-line explicitly when we know that we want to assign inside a conditional?

maybe, yes, i think this is a candidate for a later major, i have moved it there

'react/jsx-closing-tag-location': ['off'] I think that XML reads better and is easier to navigate when end tag is aligned with starting tag. If eslint --fix causes breakage, maybe better to disable the rule for the offending project or file and not disable globally in our central config eslint

The breakage caused was so significant, that i think it's not safe to use at all right now. I have moved this to next major.

'import/extensions': ['warn'] maybe move this warning rule into projects that have a lot of require('xx.js')?

okay, done

'no-alert': ['warn'] - alert is really not good to use in user-facing code, maybe should instead move this warn into files or projects that need to use "alert" (i'm guessing internal applications), and not have it a a global warn
'no-restricted-properties': ['warn'] I understand that many projects are using deprecated globals, but maybe this rule should be disabled on those projects instead of being disabled for all other (and new) projects as well
'default-case': ['warn'] not so fan of warnings as it will drown in a sea of other warnings. IMO either disable in offending projects or remove this rule completely

okay moved all these out to consuming repos

Also I see that typescript was added - why is it a necessary dependency?

i think a mistake on my part, trying to combat a peerDependency warning in the uppy repo, fixed it in master.
The rest of them lives in https://github.com/transloadit/eslint-c for review

here's my 2 cent:

dot-notation IMO this is subjective, I don't think that state['asdf'] reads better than state.asdf

I think so too, which is also the point that Evgenia made, that I imported from the content repo. I think we are in agreement and it can remain off? Or maybe i misunderstand.

Actually what I meant is that I think object.property.subproperty does read better than object['property']['subproperty']. You comment above the rule was:
    // It's true that we'd generally like to use object.property,
    // but this.state.formState is usually better read when we read
    // this.state.formState['property'].
    'dot-notation': ['off'],

I believe that is your subjective opinion, and my opinion is not very strong about tihs :)

no-fallthrough I'm guessing too much work to enable this

But also a question about its usefulness, i have seen legitimate cases for using fallthroughs and haven't seen a critical bug due to it yet i think 🤔

I remember having forgotten to put a break; several times between switch cases, but maybe I'm clumsy 😄 I think the thought behind the rule is that yes there are indeed legitimate use cases but then it's very easy to eslint disable next line in those cases. I don't have any strong opinion about this rule tho, as it's quite rare I use switch cases.

node/no-path-concat - I think this one is a good rule as it can make code work on non-unix systems too (maybe not a priority for transloadit but it's a good practice). And it can prevent accidental paths joining with double or missing slashes. e.g. '/foo/bar/' + '/file.jpg' leads to /foo/bar//file.jpg and '/foo/bar' + 'file.jpg' leads to /foo/barfile.jpg

For the time being, our focus is on linux/macos/bsd:
I think a longterm goal can be fixing it, but it is adding a whole bunch of characters to our scripts until then while they won't be windows compatible even after adding them. I think maybe for a major v5, we can turn it back on for instance

Maybe this one can be also not be turned off in our central config, but instead turned off in the projects that are using a lot of this? Because it also has the benefit of solving issues with missing or double slashes between path segments. (in new projects & new code)

'no-template-curly-in-string': ['off'] I'm sure there's a good reason for disabling it, but if not then this rule could prevent accidentally using ${variable} in a normal string instead of backticked string

iirc, it would prevent us from doing '{YOUR_AUTH_KEY}', but we have a lot of those, and escaping all of them is less favorable imho

It will not prevent you from doing '{YOUR_AUTH_KEY}', it will only prevent you from doing '${YOUR_AUTH_KEY}', but if you have a lot of such custom templates in strings then I understand. But it may make sense to also only disable this rule on the projects where it is relevant.
Also rule 17,18,19,20,21 it may make sense to disable these rules in only the repos that generate errors from these rules, then the central eslint-config-transloadit can still enforce the rules for the new or unaffected projects.

I believe that is your subjective opinion, and my opinion is not very strong about tihs :)

I agree with you, it is not my opinion, but Evgenia's, who felt strongly that in some cases, allowing [''] is helpful I think.

I remember having forgotten to put a break; several times between switch cases, but maybe I'm clumsy  I think the thought behind the rule is that yes there are indeed legitimate use cases but then it's very easy to eslint disable next line in those cases. I don't have any strong opinion about this rule tho, as it's quite rare I use switch cases.

I thought we had quite a few of these:

But maybe it's not so bad, upon first glance i can only find one in the api. I'm happy to revisit this one then for the next release :ok_hand:  (just published 1.2 before getting to this thread)

Maybe this one can be also not be turned off in our central config, but instead turned off in the projects that are using a lot of this? Because it also has the benefit of solving issues with missing or double slashes between path segments. (in new projects & new code)

oth yes, otoh, this is a transloadit standard, i don't think we are looking for others to adopt it. and so the nice thing is we can have rules in a central place, vs then have exceptions in all consuming projects. Cause i think all projects will turn this rule off. When this changes, that is the moment i agree a new release can be pushed out and exceptions in other projects can be made (?)

no-template-curly-in-string

I can agree to that reasoning yes, 1.3 then?

ah you are in luck, the publish failed, so they can make it in 1.2 :)


Migrate to tokenizer + fastchat conv templates

Realistically, doing our own is a losing battle, let's migrate to something maintained.

There is a start at this here: https://github.com/allenai/open-instruct/blob/main/eval/templates.py#L112
But more formal integrations with fastchat would be good. I think supporting more flexible generation in general is good. E.g. llama 3 with its multiple eos tokens.

I came aross this issue when I want to use a different chat template to train models. So, I made this PR. It should support user-defined chat templates.

Closing since #350 kinda resolves this.


correct calculation for RGB

Low byte was always ignored

Hi @SG5 - would it be possible to write tests to prove this is still working correctly and also tests around what it fixes please?


How do you make the opponent's notes go downscroll while the player's note go upscroll?

Describe your problem here.
How do you make the opponent's notes go downscroll while the player's notes go upscroll?
Here's an exact image if you don't understand what I mean

Is this possible with lua? (mainly because source never works with me). (ik the character on the right side sucks.)
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No.

You should search issues before opening one #9679


Add fetch() Web Implementation

Web implementation for https://github.com/rust-windowing/softbuffer/pull/104.

The test introduced in #104 isn't compatible with Wasm btw, because of inventory. I'm unsure of the motivations here, but it seems to me that this could be simplified.
Alternatively we can just disable the test for Wasm and I write a separate one for Wasm only.


sort state information

As far as I can see from examples & tutorial, ui-grid look to the columns to get the sort info.

    // Build the list of columns to sort by
    var sortCols = [];
    columns.forEach(function (col) {
      if (col.sort && !col.sort.ignoreSort && col.sort.direction && (col.sort.direction === uiGridConstants.ASC || col.sort.direction === uiGridConstants.DESC)) {
        sortCols.push(col);
      }
    });
// Sort the "sort columns" by their sort priority
sortCols = sortCols.sort(rowSorter.prioritySort);

is it possible to make this a function or something, so when we use external sorting, we can get this info easily. Now, I just created a function like this but I believe if it's on the library, it'd be better.
Thanks

Correction:
Seems that I cannot get the sort info from $scope.gridOptions.columnDefs. Is there a variable/function that I can get the current sort specs for the grid ?

You can close the issue, I fount it : self.getColumnSorting()


How to register elements that did not exist upon window load

Hi,
and first of all for making a great library!
I've so far only used the ResizeSensor and is very happy with it.
I'm working on a "office UI" where every dom element is created using javascript after window.onload.
And some parts of the UI is created at much later time (from user interaction). Am I right when I say that ElementQueries will not be enabled for elements created/added to the document after window.onload. If so, is there a way to make ElementQueries aware of new elements?
Thanks for any help or guidance!
Jørund Vier Skriubakken

I see function ElementQueries.setupElement exists.
Would it be enough to call this function with element and correct options?

No, please use ElementQueries.init(). This is executing all known css rules at the DOM to fetch newly created elements and attach only there the magic.

OK. Is it safe to call it many times?

Yes

OK. Thanks :+1.
I will try.


[Bug] Extra underscores added to schema causing failure

Is there an existing issue for this?

[x] I have searched the existing issues

Describe the issue
In creating the view, the final select statement adds underscores to my schema causing errors. I am just starting to work on supporting formula fields for my salesforce connectors so I am fairly new to dbt and have a setup that is pretty much copied from the examples.
My src_salesforce.yaml file looks like :
version: 2
sources:
  - name: salesforce #It would be best to keep this named salesforce
    schema: 'org_0cc6aa0e_salesforce' #Modify this to be where your Salesforce data resides
    tables:
      - name: fivetran_formula_model
        description: Used for the recommended Option 1 version of the formula solution.
      - name: fivetran_formula
        description: Used for options 2 and 3 of the original individual formula solution.
      - name: account
        description: SFDC account table
      - name: opportunity
        description: SFDC opportunity table

And my opportunity model looks like:
{{ salesforce_formula_utils.sfdc_formula_view('opportunity') }}
In the created queries, the schema in the FROM portion of my select statement turns from org_0cc6aa0e_salesforce -> org_0_cc_6_aa_0_e_salesforce which does not exist and therefore the run errors.
Relevant error log or model output
Some initial queries work correctly:
select
                model as value

            from "saasgrid"."org_0cc6aa0e_salesforce"."fivetran_formula_model"

            where object = 'opportunity'

            group by model
            order by count(*) desc

But ultimately the view materialization fails
SELECT mt.old_c,mt.owner_id,mt.contract_id,mt.lead_source,mt.security_request_required_c,mt.type,mt.se_notes_c,mt.churn_notice_received_date_c,mt.next_step,mt.fiscal_year,mt.marketing_source_c,mt.cabal_connections_c,mt.do_not_trigger_slack_c,mt.accounts_payable_name_c,mt.created_by_role_c,mt.brad_s_pipe_c,mt.id,mt.closed_loss_reason_c,mt.sales_loft_1_most_recent_cadence_name_c,mt.last_referenced_date,mt.trial_calendar_link_c,mt.mrr_c,mt.probability,mt.record_type_id,mt.original_source_drill_down_1_c,mt.managed_service_account_c,mt.closed_not_qualified_reason_c,mt.igm_deal_hub_create_subscription_c,mt.churn_notice_received_c,mt.closed_by_role_c,mt.mql_source_drill_down_2_c,mt.renewal_strategy_c,mt.deal_hub_create_subscription_c,mt.discovery_completed_c,mt.billing_frequency_c,mt.manager_forecast_category_c,mt.forecast_category,mt.next_steps_c,mt.executive_leadership_c,mt.marketing_sub_source_c,mt.last_viewed_date,mt.loss_reason_c,mt.unique_entry_current_endpoint_c,mt.trial_start_date_c,mt.win_reason_c,mt.last_amount_changed_history_id,mt.has_open_activity,mt.demo_date_c,mt.mql_source_c,mt.accounts_payable_phone_c,mt.fiscal_quarter,mt.security_questionnaire_request_date_c,mt.renewal_strategy_notes_c,mt.sdr_c,mt.date_of_prospecting_c,mt.latest_source_drill_down_1_c,mt.original_source_drill_down_2_c,mt.push_count,mt.account_id,mt.date_of_negotiating_c,mt.contract_start_date_c,mt.link_to_completed_sec_req_c,mt.latest_source_c,mt.lead_type_c,mt.custom_tos_c,mt.economic_buyer_c,mt.close_date,mt.finance_approval_c,mt.manager_next_steps_c,mt.last_modified_date,mt.use_cases_c,mt.trial_end_date_c,mt.opt_out_date_c,mt.pricebook_2_id,mt.budget_confirmed_c,mt.marketing_subsource_detail_c,mt.billing_type_c,mt.at_risk_c,mt.last_modified_by_id,mt.system_modstamp,mt.stage_name,mt.roi_analysis_completed_c,mt.loss_reason_notes_c,mt.last_stage_change_date,mt.deal_room_url_c,mt.campaign_id,mt.is_closed,mt.date_of_pending_c,mt.delta_arr_c,mt.date_of_qualifying_c,mt.last_activity_date,mt.champion_c,mt.pre_qualification_notes_c,mt.accounts_payable_email_c,mt.dh_arr_c,mt.latest_source_drill_down_2_c,mt.synced_quote_id,mt.is_won,mt.referring_partner_c,mt.sales_to_success_handoff_c,mt.fiscal,mt.onboarding_fee_c,mt.name,mt.contract_end_date_c,mt.lid_linked_in_company_id_c,mt.created_by_id,mt.billing_start_date_c,mt.is_private,mt.billing_status_c,mt.reason_code_c,mt.total_opportunity_quantity,mt.notified_of_renewal_c,mt.description,mt.has_overdue_task,mt.contact_id,mt.renewal_notification_sent_c,mt.competitor_c,mt.churn_details_c,mt.last_close_date_changed_history_id,mt.pandadoc_tracking_number_c,mt.sales_engineer_c,mt.is_deleted,mt.expected_revenue,mt.demo_outcome_c,mt.opt_out_c,mt.saasoptics_auto_process_c,mt.billing_complete_c,mt.opportunity_renewal_date_c,mt.marketing_ad_group_c,mt.amount,mt.date_of_trialing_c,mt.decision_process_c,mt.original_source_c,mt.term_c,mt.sales_loft_1_most_recent_last_completed_step_c,mt.months_c,mt.cs_renewal_forecast_category_c,mt.risks_red_flags_c,mt.unique_entry_ring_lead_last_processed_date_c,mt.gong_main_competitors_c,mt.se_sentiment_c,mt.has_opportunity_line_item,mt.security_questionnaire_status_c,mt.forecast_category_name,mt.sales_loft_1_primary_contact_c,mt.outbound_override_c,mt.unique_entry_ring_lead_app_field_c,mt.created_date,mt.identify_pain_c,mt.win_reason_notes_c,mt.mql_source_drill_down_1_c,mt.net_terms_c,null AS deal_hub_synced_quote_status_c,CASE WHEN (COALESCE(mt.stage_name,'')=COALESCE('Closed Lost','')) THEN mt.delta_arr_c ELSE CASE WHEN (COALESCE(mt.stage_name,'')=COALESCE('Closed Won','')) THEN (COALESCE(mt.dh_arr_c,0)*COALESCE(mt.probability,0)) ELSE CASE WHEN ((COALESCE(mt.delta_arr_c,0)<COALESCE(0.99,0)) AND (COALESCE(mt.delta_arr_c,0)>COALESCE((-0.99),0))) THEN (COALESCE(mt.dh_arr_c,0)*COALESCE(mt.probability,0)) ELSE (COALESCE(mt.delta_arr_c,0)*COALESCE(mt.probability,0)) END END END AS forecasted_arr_c,1 AS opportunity_count_c,CASE WHEN (mt.contract_start_date_c IS NULL) THEN mt.close_date ELSE mt.contract_start_date_c END AS reporting_start_date_c,jt1.customer_start_date_c AS customer_start_date_c,null AS dh_tcv_c,null AS cross_object_lookup_c,null AS created_by_manager_c,((((((mt.name||' - ')||'Q')||CONVERT( VARCHAR, CASE WHEN (COALESCE(((COALESCE(EXTRACT(MONTH FROM mt.close_date),0)-COALESCE(1,0))),0)/COALESCE(3,0))<0 THEN CEIL((COALESCE(((COALESCE(EXTRACT(MONTH FROM mt.close_date),0)-COALESCE(1,0))),0)/COALESCE(3,0)))-1 ELSE CEIL((COALESCE(((COALESCE(EXTRACT(MONTH FROM mt.close_date),0)-COALESCE(1,0))),0)/COALESCE(3,0))) END ))||' ')||CONVERT( VARCHAR, EXTRACT(YEAR FROM mt.close_date) ))||' PRO') AS naming_convention_c,null AS total_acv_c,CASE WHEN ((COALESCE(mt.type,'')=COALESCE('New Business','')) AND (mt.is_won=True)) THEN 1 ELSE 0 END AS new_business_won_count_c,CASE WHEN ((COALESCE(mt.type,'')=COALESCE('Expansion','')) AND (mt.is_closed=FALSE)) THEN 0 ELSE CASE WHEN (COALESCE(mt.stage_name,'')=COALESCE('Closed Lost','')) THEN ABS((COALESCE(jt1.original_arr_new_c,0)+COALESCE(jt1.expansion_contraction_lifetime_c,0))) ELSE CASE WHEN (mt.is_closed=FALSE) THEN jt1.current_arr_new_c ELSE (COALESCE(mt.dh_arr_c,0)-COALESCE(mt.delta_arr_c,0)) END END END AS opp_starting_arr_c,(COALESCE(((COALESCE(mt.mrr_c,0)*COALESCE(mt.months_c,0))),0)+COALESCE(mt.onboarding_fee_c,0)) AS tcv_c,(COALESCE(jt1.current_mrr_c,0)+COALESCE(mt.mrr_c,0)) AS new_managed_services_mrr_c,CASE mt.stage_name WHEN '1 - Prospecting' THEN 1 WHEN '2 - Qualifying' THEN 2 WHEN '3 - Trialing' THEN 3 WHEN '4 - Negotiating' THEN 4 WHEN '5 - Pending' THEN 5 WHEN 'Closed Won' THEN 6 ELSE 0 END AS stage_value_c,DATEDIFF( DAYS, CAST( mt.date_of_prospecting_c AS TIMESTAMP), CAST( DATE(mt.created_date)  AS TIMESTAMP)) AS days_in_prospecting_c,CAST(DATEADD( SECONDS, CAST ( ( 30 * 24 * 60 * 60 ) * -1 AS INTEGER ), CAST( mt.contract_start_date_c  AS TIMESTAMP) ) AS TIMESTAMPTZ) AS renewal_notification_date_30_days_c,(COALESCE(mt.mrr_c,0)*COALESCE(12,0)) AS arr_c,null AS record_type_name_c,DATEDIFF( DAYS, CAST( mt.date_of_qualifying_c AS TIMESTAMP), CAST(  CURRENT_DATE   AS TIMESTAMP)) AS days_in_qualifying_c,1 AS gong_gong_count_c,((((((CASE WHEN (COALESCE(LENGTH(COALESCE(jt1.billing_street,'')),0)>COALESCE(0,0)) THEN (jt1.billing_street||' ') ELSE '' END||'\n')||CASE WHEN (COALESCE(LENGTH(COALESCE(jt1.billing_city,'')),0)>COALESCE(0,0)) THEN (jt1.billing_city||', ') ELSE '' END)||CASE WHEN (COALESCE(LENGTH(COALESCE(jt1.billing_state,'')),0)>COALESCE(0,0)) THEN (jt1.billing_state||' ') ELSE '' END)||CASE WHEN (COALESCE(LENGTH(COALESCE(jt1.billing_postal_code,'')),0)>COALESCE(0,0)) THEN jt1.billing_postal_code ELSE '' END)||'\n')||CASE WHEN (COALESCE(LENGTH(COALESCE(jt1.billing_country,'')),0)>COALESCE(0,0)) THEN jt1.billing_country ELSE '' END) AS account_billing_address_c,mt.id AS x_18_digit_opp_id_c FROM org_0_cc_6_aa_0_e_salesforce.opportunity AS mt LEFT JOIN org_0_cc_6_aa_0_e_salesforce.account AS jt1 ON mt.account_id=jt1.id

  ) ;

22:41:30.817942 [debug] [Thread-1  ]: Postgres adapter: Postgres error: schema "org_0_cc_6_aa_0_e_salesforce" does not exist

22:41:30.818725 [debug] [Thread-1  ]: On model.fivetran_dbt.opportunity: ROLLBACK
22:41:30.897051 [debug] [Thread-1  ]: finished collecting timing info
22:41:30.897781 [debug] [Thread-1  ]: On model.fivetran_dbt.opportunity: Close
22:41:30.899781 [debug] [Thread-1  ]: Database Error in model opportunity (models/opportunity.sql)
  schema "org_0_cc_6_aa_0_e_salesforce" does not exist
  compiled Code at target/run/fivetran_dbt/models/opportunity.sql

Expected behavior
For the schema to not be altered in the construction of queries.
dbt Project configurations
name: 'fivetran_dbt'
version: '1.0.0'
config-version: 2
profile: 'fivetran_dbt'
model-paths: ["models"]
analysis-paths: ["analyses"]
test-paths: ["tests"]
seed-paths: ["seeds"]
macro-paths: ["macros"]
snapshot-paths: ["snapshots"]
target-path: "target"  # directory which will store compiled SQL files
clean-targets:         # directories to be removed by dbt clean

"target"
"dbt_packages"

Package versions
packages:

package: fivetran/salesforce_formula_utils
version: 0.8.0

What database are you using dbt with?
redshift
dbt Version
Core:

installed: 1.3.0
latest:    1.3.2 - Update available!

Your version of dbt-core is out of date!
You can find instructions for upgrading here:
https://docs.getdbt.com/docs/installation
Plugins:

redshift: 1.3.0 - Up to date!
postgres: 1.3.0 - Update available!

Additional Context
No response
Are you willing to open a PR to help address this issue?

[ ] Yes.
[X] Yes, but I will need assistance and will schedule time during our office hours for guidance
[ ] No.

Hey @teddy-ruby you beat me to it! You are correct that the SQL which seems to be throwing the error you are seeing is generated by the connector. As such, there is not much our team is able to do from the dbt package.
However, our engineering team will be able to help address any issues from the SQL generated within the fivetran_formula_model table. You can open a support ticket to have our customer support and engineering teams help you!

As this is an issue we won't be able to address within the dbt package, I will close the issue. Please be sure to reach out to our support team to help address the issue. Thanks!

Thanks Joe! Yep, I reached out to support and they are working to address the issue. Thanks for your response! Cheers


100% ram usage hanging the whole system

Hello, I can't seem to get past this part:

With these specs:

It hits 100% ram usage and just hangs the whole system...

Can't access the system anymore or even check the terminal.

My images are fairly high resolution, could that be the issue?

My images are fairly high resolution, could that be the issue?

was the issue


CrashLoopBackoff when using ./deploy_hpo.sh -c openshift

Container failing to come up when using ./deploy_hpo.sh -c openshift
seeing in the logs of container:
Traceback (most recent call last):
File "/home/hpo/app/src/service.py", line 18, in <module>
import rest_service, grpc_service
File "/home/hpo/app/src/rest_service.py", line 24, in <module>
from json_validate import validate_trial_generate_json
File "/home/hpo/app/src/json_validate.py", line 1, in <module>
import jsonschema
ModuleNotFoundError: No module named 'jsonschema'

I see jsonschema in the requirements and should be getting installe din https://github.com/kruize/hpo/blob/d7e024e2567478c957e52f9b0eee6aa1e5cc0230/Dockerfile.hpo#L55-L56
Wondering why the entrypoint appears to be working with docker but not on openshift as far as using right python environment where the package is correctly loaded


Remove horizontal scroll of side-nav

The line "padding: 0 45px 0 15px" caused horizontal scroll of the whole side-nav on desktop and mobile.

We've since fixed this.


Pure JS/TS Sdk

Interesting new approach from NEAR: https://github.com/near/near-sdk-js
Compiles QuickJS into WASM using emscripten

Worth a try, but still in an early stage I think. There are only a few documents about it.

@learnforpractice can you please check your telegram messages


Support jira label

Find a way to configure, or pass in a jira label on the command line.

Luckily, labels are pretty easy; there's some prior art in both jirafs, but maybe this will be a little more helpful: https://github.com/ralphbean/bugwarrior/blob/develop/bugwarrior/services/jira.py#L67.

Resolved in PR #13


Add sidebar. Set the default saving format to HTML, delete the styles related to impression clipping, and optimize the web code.

Add sidebar. Set the default saving format to HTML, delete the styles related to impression clipping, and optimize the web code.（增加侧边栏。设置默认保存格式为HTML。删掉印象剪藏有关的样式，优化网页代码）

Okay, it has been modified

The files in the sidebar are from My Repository and you can selectively delete them.

The files in the sidebar are from My Repository and you can selectively delete them.

For someone reading the chinese translated version of the page, your list is better than anything I could come up with. My only concern is the version numbers in the urls. With every new release of those files, TiddlyStow-ZH.html will need to be updated.
I'm fine with your pull requests and if I ever become a bottleneck or you just prefer to take full ownership of the chinese translation, you are free to maintain your own fork at your own github.io url.
Thanks for the contribution.

Thanks to your support and compliments, TiddlyStow-ZH.html will be maintained in this repository of mine: https://github.com/Zacharia2/TWPUB-BOOK/tree/gh-pages.
In addition to that there are files in the sidebar that are also in that repository.
（感谢您的支持和称赞，TiddlyStow-ZH.html将在我的此仓库进行维护：https://github.com/Zacharia2/TWPUB-BOOK/tree/gh-pages。除此之外还有侧边栏中的文件也在该仓库中。）


Set pytest as a dev dependency rather than a hard dependency

Even though it is the de facto testing library, make it so that a user who installs Phaser does not depend on pytest.

Seems like the way to do this with pip and requirements.txt files is to create a separate dev-requirements.txt that people would specifically pass to pip if they are doing development work.


Blacklist not working properly

Blacklist works with current buffer, so if the bubble is to be shown in current buffers its also shown in inactive buffers.

If you know how to fix this, please tell me, this seems to need a rework.

Related to #100


[BUG] validatingWebhookConfiguration that points to webhook capi endpoints exists on the local cluster

Rancher Server Setup

Rancher version: v2.8-35d6b4eedc3b0274c8c73b830d95bec30a1f2cbc-head
Installation option (Docker install/Helm Chart): Helm Chart (2.8.3-rc2)

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions: Admin

Describe the bug
validatingWebhookConfiguration that points to webhook capi endpoints exists on the local cluster
To Reproduce

Create a rancher server v2.8-head
Create a downstream cluster
Verify that the version of the webhook is as expected on both local and downstream clusters- v0.4.3-rc1
On both local and downstream clusters, Verify that there are no capi specific values/resources in the webhook chart/yaml/deployment/pod:

[✅] Webhook Chart: helm -n cattle-system get values rancher-webhook
[✅] Webhook Yaml in UI
[✅] Webhook Resources

Service webhook-service in namespace cattle-system should not exist
Secret rancher-webhook-tls in namespace cattle-system should not exist

[✅] Webhook Deployment: kubectl get deployment rancher-webhook -n cattle-system -o yaml

On the local cluster, Verify that validatingWebhookConfiguration that points to capi endpoints is no longer created: kubectl get validatingwebhookconfigurations.admissionregistration.k8s.io  validating-webhook-configuration

Result
validatingWebhookConfiguration that points to webhook capi endpoints exists on the local cluster
> kubectl get validatingwebhookconfigurations.admissionregistration.k8s.io  validating-webhook-configuration
NAME                               WEBHOOKS   AGE
validating-webhook-configuration   12         17h

> kubectl get validatingwebhookconfigurations.admissionregistration.k8s.io  validating-webhook-configuration -o yaml | grep -i "name: capi"
      name: capi-webhook-service
      name: capi-webhook-service
      name: capi-webhook-service
      name: capi-webhook-service
      name: capi-webhook-service
      name: capi-webhook-service
      name: capi-webhook-service
      name: capi-webhook-service
      name: capi-webhook-service
      name: capi-webhook-service
      name: capi-webhook-service
      name: capi-webhook-service
>

Expected Result
validatingWebhookConfiguration that points to webhook capi endpoints should no longer exist on the local cluster
cc @tomleb

I see that the name of the service is

  name: capi-webhook-service

The validation template  mentioned that the service webhook-service needed to be cleaned up, it didn't say anything about capi-webhook-service.
The reason this service is there is because we still need the CAPI webhook, but it was moved from inside webhook (in cattle-system) to outside webhook in another namespace.

Yes, you are right. I just checked and this is in namespace: cattle-provisioning-capi-system. Closing this issue


Fix LearnedElementwiseScaling forward func

FrEIA's module now feed input x in .forward(x) as a list and expects output as a list

Thank you once again, sir! You have fixed so many bugs we missed!
If we ever meet at a conference, please let me buy you lunch!


Switch Right and Middle click buttons

First thanks for these drivers! One question, is it possible to switch Right and Middle click buttons?

Hello @SreckoM  this is now possible.
Set pen_buttons_reverse = true in config file


CI integration

It would be nice to automatically check whether the build process fails or succeeds using CodeShip.

Do you want this for this project or for the generated projects?

There should be tests inside the project that must be run with npm test to see if the generated project is being generated as it should.
These tests should be executed with CodeShip or Travis. Example: https://travis-ci.org/PizzaPete/generator-ionic-incubator/

@PizzaPete Can you create a pull request for this? I would love to have a baseline for these kind of implementations.
Keep in mind that not every project needs this as a default implementation, can you make it optional?

@PizzaPete also look at issue #4 we can probably execute those tests with codeship?
@rburgt I think he means tests for the generator itself not the generated projects

You must have a subscribed (payed account) organisation to use builds on Codeship as a company.
I'm going to look into Travis CI now.

We do have a subscribed BAMBOO account, isn't that able to do the exact same thing?

Are the results of the Bamboo build open to everyone?

will check

Nope, doesn't work :(

@PizzaPete please make a pull request once its done :)

I've implemented a .travis.yml file and updated the README.md in: commit: #19
Although the build fails.

It seems to fail on older versions of node on the es6 notation in the gulp script. I think we should remove those versions from the Travis config.

looks like its fixed, i'll close this issue for now


Scala 3

Builds on top of #228, so the changes from there are included here as well.
Adds cross build for Scala 3 which is a bit tricky due to:

usage of shapeless' Sized. Luckily, the API surface used is very small, so I was able to "polyfill" it by defining some match types which mimic Sized, but represent the data as tuples internally (which would be the natural choice if this library was developed exclusively for Scala 3).
Custom macros. They were easy to port, but as Scala 2 doesn't allow macro calls from a trait, the companion objects using macros for their apply methods had be moved into Scala version-specific files. That works well, but tears the code a bit apart. Striving for as little changes as possible (tests actually compile on Scala 2 unchanged), this was the only solution I found. If in future the Name.apply and friends would vanish in favour of adopting Literally, this could become nicer again.

I'll comment on some interesting parts inline later.

The tests pass on my fork, so this version of minimal API surface changes is ready for review.
If the decision for Literally (which wouldn't work exactly straight-forward for Quantile) was a thing, I would update this PR instead of following up with another PR as much code would be moved back and forth. @ChristopherDavenport you mentioned Literally for this project on Discord some time ago, is that still something you want?

The case class additions are problematic from a type exposure perspective, would love if we could do without those.
Literally works for me but I'm happy to proceed with this.

The case class additions are problematic from a type exposure perspective, would love if we could do without those.
Literally works for me but I'm happy to proceed with this.

I fixed 1. by adding a private[epimetheus] def asJava method on each collector type. Also not ideal IMHO, but trying to pattern match in different ways always leads to compiler errors, especially on Scala 2.12 – that was the reason I introduced case initially. @ChristopherDavenport I hope this work around is acceptable, other options would be to drop 2.12 or try manually spell out a private unapply for each class and hope compilers are happy about it.

As Literally isn't a perfect fit (Quantile), I would then not migrate, at least not as part of this PR.


add github actions

:sparkles: Enhancements

Add GitHub Actions to project

:pencil: Documentation

Flow, checks code format, dependencies, and run tests

Resolves #2

Ready for review


Create Adaptive Cards with JavaScript?

Is it possible to create Adaptive Cards with JavaScript? I want to build my cards at run-time, both client and server, and use a builder library i.e. not have to hand write the JSON.  Hopefully, this question makes sense?

There's a microsoft-adaptivecards npm module that provides a library for constructing and rendering cards, but that's not going to prevent you from have to work with JSON. Alternately, with the .NET library you can create the card without using JSON, and then pass it back as JSON through serialization to the front-end. Then use the JS library to render it, while attaching whatever actions you need.

Thanks @szul for helping out! @iwaldman hopefully this answer your question, if not, please feel free to ask on Stack Overflow where it's easier for provide questions to answers:
https://stackoverflow.com/questions/tagged/adaptive-cards


has been supported firmware 1.5.0_0026

has been supported firmware 1.5.0_0026

Is it update or the gw came with this fw?

where did you get this firmware? update or hub from new batch?

@rezmus The production date is 2021.04 and the command can directly start telnet

@hbwy1314 if you have telnet access can you dump 1.5.0_0026 firmware? telnet to hub and send
dd if=/dev/mtd5 of=/data/mtd5.bin
dd if=/dev/mtd6 of=/data/mtd6.bin
wget -O /data/busybox "http://master.dl.sourceforge.net/project/mgl03/bin/busybox?viasf=1"
chmod +x /data/busybox
/data/busybox tcpsvd -vE <IP_ADDRESS> 21 /data/busybox ftpd -w / &

then use any ftp client (user admin, pass empty), download both files (mtd5.bin & mtd6.bin) from /data/ and share somewhere.

@rezmus I have dumped the file system. I can send you an email

You can upload for example here https://www.sendspace.com/

Or send it to my email<EMAIL_ADDRESS>

Thanks! Can you also show results for:
# cat /data/zigbee/coordinator.info
# cat /data/ble_info
# cat /etc/ble_info

发自我的iPhone
------------------ Original ------------------
From: Alex X @.>
Date: Wed,May 12,2021 7:53 PM
To: AlexxIT/XiaomiGateway3 @.>
Cc: hbwy1314 @.>, Mention @.>
Subject: Re: [AlexxIT/XiaomiGateway3] has been supported firmware 1.5.0_0026 (#325)
Thanks! Can you also show results for:
cat /data/zigbee/coordinator.info# cat /data/ble_info# cat /etc/ble_info
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@AlexxIT
{"sdkVer":"1.3.33","manufacturer":"silicon labs","hostVer":"1.14","hostDir":"","mac":"0xcc86ecfffe7b8eed","channel":20,"panId":"0x6f23","cloudLink":1,"timeZone":"GMT8","coorVer":"6.6.2-126.32","preLeave":0,"debugStatus":0,"gw_did":""}ncp_host_version=152
ncp_target_version=107
bootloader_version=100
ota=0
ncp_host_version=100
ncp_target_version=107
bootloader_version=100
ota=0

with new update work ble? thank you

@matteos1 yes

Is it recommended to upgrade my 1.4.6_0012 fw to this (1.5.0_0026)??? Are there any improvement/ new features?

Upgrading only makes sense if you have new devices that are not supported in 0012


LocationSimulator loads slowly

LocationSimulator takes a while to parse the GPX and start sending non-null locations, especially on Android in debug mode. You can see this if you run Squad Leader from Eclipse in debug mode.
Currently LocationSimulator reads the entire GPX into memory before sending any locations. We can experiment with sending each location as it is read (taking care with the timing) and either keeping them in memory or rereading them each time.

@garys-esri - Is this issue still valid?

Yes, it is valid but its priority is low.


Issues with AirFlow version

Hey there I'm building kube-airflow on Circle and when the docker build step got to  && pip install airflow[celery,postgresql,hive]==$AIRFLOW_VERSION \ it failed with 'no such version'. Had to remove the version requirement. AIRFLOW_VERSION was set in my environment. I'm actually not familiar with the %%AIRFLOW_VERSION%% syntax but presume that's grabbing the AIRFLOW_VERSION from the environment?
Also needed to add Cython to pip steps of Dockerfile, looks like a pandas dependency that's not getting built before pandas...
    && pip install pyasn1 \
    && pip install psycopg2 \
    && pip install Cython \
    && pip install airflow \

Sorry I figured it out that was being injected by your makefile, Dockerfile.template was obviously not the final Dockerfile, it still needed injection of AIRFLOW_VERSION and KUBECTL_VERSION.


fix(apigateway): recover remove apigateway locale messages

这个 PR 实现什么功能/修复什么问题:
修正: 恢复删除的apigateway i18n数据

是否需要 backport 到之前的 release 分支:

release/3.7

/cc @yousong

Codecov Report

Merging #9999 (9628e12) into master (7e69faa) will increase coverage by 2.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #9999       +/-   ##
==========================================
+ Coverage    5.97%   8.05%    +2.08%
==========================================
  Files         849     107      -742
  Lines      132265   12991   -119274
==========================================
- Hits         7897    1047     -6850
+ Misses     123667   11824   -111843
+ Partials      701     120      -581

Flag
Coverage Δ

aFlag
8.05% <ø> (+2.08%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/multicloud/aws/vpc_peering_connection.go

pkg/appsrv/cors.go

pkg/compute/models/elasticcache_joints.go

pkg/cloudcommon/cmdline/parser.go

pkg/monitor/alerting/conditions/suggestquery.go

pkg/appsrv/workers_watchdog.go

pkg/monitor/alerting/conditions/query.go

pkg/compute/models/host_health.go

pkg/hostman/system_service/kube_agent.go

pkg/compute/models/storagecaches.go

... and 732 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #9999 (9628e12) into master (7e69faa) will increase coverage by 2.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #9999       +/-   ##
==========================================
+ Coverage    5.97%   8.05%    +2.08%
==========================================
  Files         849     107      -742
  Lines      132265   12991   -119274
==========================================
- Hits         7897    1047     -6850
+ Misses     123667   11824   -111843
+ Partials      701     120      -581

Flag
Coverage Δ

aFlag
8.05% <ø> (+2.08%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/multicloud/aws/vpc_peering_connection.go

pkg/appsrv/cors.go

pkg/compute/models/elasticcache_joints.go

pkg/cloudcommon/cmdline/parser.go

pkg/monitor/alerting/conditions/suggestquery.go

pkg/appsrv/workers_watchdog.go

pkg/monitor/alerting/conditions/query.go

pkg/compute/models/host_health.go

pkg/hostman/system_service/kube_agent.go

pkg/compute/models/storagecaches.go

... and 732 more

Continue to review full report at Codecov.

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

/lgtm
/approve

/lgtm
/approve


Delete where value > 6000 not working on v2.7.4

I want to delete bogus values from a table, but the delete where is (still) not working.
# influx v1 shell
InfluxQL Shell dev
Connected to InfluxDB OSS v2.7.4
> use "nodered_0002"
> DELETE FROM "solar.grid.watt" WHERE value > 6000
Error: shard 1591: fields not supported in WHERE clause during deletion
No results

DELETE supports WHERE filtering with tags, but not with fields.  See documentation here

Can this be implemented? It is a mandatory functionality for many users.


Feature: Allow users to create a app/config/snowpacker.yml

Currently, only a top-level snowpack.config.json is supported.

This is no longer the case. Variables are set via an initializer to then be passed in as ENV Vars to the snowpack config.


Directive [xxx]. Property '[xxx]' is private and only accessible within class '[xxx]'

Please read https://github.com/edcarroll/ng2-semantic-ui/blob/master/CONTRIBUTING.md and search
existing issues (both open and closed) prior to opening any new issue and ensure you follow the instructions therein.
Bug description:
I'm using ng2-semantic-ui in my npm angular package. I'm getting an exception while building the package that says:
"Directive SuiCheckbox, Property '_checkboxClasses' is private and only accessible within class 'SuiCheckbox'."
Version of Angular, ng2-semantic-ui, and Semantic UI:
Angular: 7
ng2-semantic-ui: 0.9.7
Semantic UI: 2.4.1

+1

is there any workaround for this?

is there any workaround for this?

is there any workaround for this?

My workaround was to download the repository and adjust it on my own. Then I released a package onto my private npm repository (I'm using Verdaccio to host the repository on my server).
I am still using SemanticUI for some legacy code and vanilla js, but for new features development I switched to different UI library written in (and made for) angular, as I use angular on the project.

is there any workaround for this?

My workaround was to download the repository and adjust it on my own. Then I released a package onto my private npm repository (I'm using Verdaccio to host the repository on my server).
I am still using SemanticUI for some legacy code and vanilla js, but for new features development I switched to different UI library written in (and made for) angular, as I use angular on the project.

btw @venkateshwarans , as far as I remember the fix is already in the repository. It just wasn't released yet, so all you need to do is to release it yourself. You can read my discussion with anna-bass here: #431

btw @venkateshwarans , as far as I remember the fix is already in the repository. It just wasn't released yet, so all you need to do is to release it yourself. You can read my discussion with anna-bass here: #431


Did you force push on your master branch?

I had pinned this commit using dep: c4dbed65594871659ea7347a85e1b8dcd97b9990
And suddenly it doesn't exist on the master branch anymore.

I apologize for that. I was trying to setup Travis CI and accidentally switched from the development branch to the master branch and pushed a rebase of the development branch on master.
The affected history is: https://github.com/dsnet/compress/compare/bcd0d8906d9a6df7644892b456e94d2abbbb5177...c57be8a27eb955bb314e404d40f9adde726dc6c8. The changes prior to Dec 7 are identical to the old history, but their hashes are different (since they were originally added using git cherry-pick). The changes on Dec 7 are all the new changes I added for Travis support.
I've taken measures to prevent this in the future by enabling GitHub's branch protection on master.

I'm to close this since the measures taken should be sufficient to prevent in the future.


Game crashing on swap_buffers - Seemingly random

Godot version
4.0 Beta2
System information
OS: Windows 11 | CPU: AMD Ryzen 5 3600X 6-Core | GPU: AMD Radeon RX 5700 XT (Driver: <IP_ADDRESS>-221003a-384125E-AMD-Software-Adrenalin-Edition) | Rendering Backend: Vulkan
Issue description
From what I can tell from my search, this exact issue has not been reported. Very similar issues exist, but none that describe this particular crash.
Description
Every so often while my game is running it will crash my GPU with this error:

Error source link
And AMD's crash detection will show up with this message:

However, it doesn't seem to be any fault of mine. Even if there's nothing going on in-game, or it's just a blank window containing a scene with a single node, it will randomly crash my GPU and show that error.
It does seem to be a 3D issue, I've been unable to reproduce it in a project without 3D rendering.
I've tried out a few fixes from issues similar to this one:

#60979

But so far none of them have worked. 😢
Steps to reproduce
As far as I can tell, this is an AMD GPU specific issue. So reproducing it on other hardware will probably be impossible.

Create an empty project, and make a simple 3D main scene with one Node3D in it.
Run the project, and wait. After anywhere between 10 seconds and 8 minutes it should cause your GPU to throw an error and the project to freeze/crash.

Minimal reproduction project
No response

I am willing to join a voice call on Discord to show off the error and share more information if needed.

Recently got this in the log files as well, not sure if it helps
USER ERROR: Vulkan: Did not create swapchain successfully.
   at: prepare_buffers (drivers/vulkan/vulkan_context.cpp:2056) - Condition "err != VK_SUCCESS" is true. Breaking.
USER ERROR: Condition "err" is true. Returning: ERR_CANT_CREATE
   at: swap_buffers (drivers/vulkan/vulkan_context.cpp:2133) - Condition "err" is true. Returning: ERR_CANT_CREATE
USER ERROR: Condition "err" is true. Returning: ERR_CANT_CREATE
   at: _update_swap_chain (drivers/vulkan/vulkan_context.cpp:1746) - Condition "err" is true. Returning: ERR_CANT_CREATE

Same for me on beta11, nvidia gtx1060. It began happening after i played around with environment settings and skies. The editor even crashes when opening the scene containing that world environment.
Here's a stripped down project that also crashes on startup (this even locks up my whole pc for around 20s)
CrashProject.zip
(DefaultWorldMap.tscn under Shared/Art/Environments/Test is the offending scene)

Same for me on beta11, nvidia gtx1060. It began happening after i played around with environment settings and skies. The editor even crashes when opening the scene containing that world environment. Here's a stripped down project that also crashes on startup (this even locks up my whole pc for around 20s) CrashProject.zip (DefaultWorldMap.tscn under Shared/Art/Environments/Test is the offending scene, crashes/freezes reliably for me after having opened it the second time)

I can't reproduce this on 4.0.beta12 on with the project you linked (I've tried opening all 3 scenes):

Specs: Fedora 37, GeForce RTX 4090 (NVIDIA 525.60.11)

It freezes reliably on my pc (Win 10, 16gb ram, nvidia gtx1060 6gb (driver version 516.59)).
Here's a phone capture (screen capture didn't work obviously):
https://user-images.githubusercontent.com/8841352/212459616-3c929de7-1b71-4eaa-9b5d-71cd221cf355.mp4
This is right after opening the project from the project manager (the offending scene is set as main scene)

Can you try editing the .tscn/.tres files with a text editor and remove entries such as ssao_enabled = true until it opens successfully?

I'll try that later when I'm at my PC again. I already edited the environment resource earlier with the scene closed though, where it didn't seem to have any effect, but that could also have been the result of some caching

Ok, it happens when i add a Sky to the environment settings, even when i try to set it in the editor (freeze).
I'm now also using the newest nvidia drivers for my card (528.02), but that doesn't make a difference.

Have you changed any Sky settings from the default?

It happens right when I select new sky in the dropdown for the corresponding sky field directly inside the environment settings, i can't even get to its sub settings.

Once you've added a sky (maybe in a copy of the scene/project so that it doesn't freeze your main project) you should IIRC be able to edit its values in the scene file in any text editor

I was able to create a sky by using the steps mentioned above, deleting the worldenvironment, editing the env-resource and it seems the freeze happens when or as the sky is created with no sky material.
if i assign one (all of them work the same) and restart the project, it doesn't freeze, but when i delete the assigned material and restart the project it freezes again. Interestingly, before restarting in this case while a WorldEnvironment is still in the scene i can freely delete and reassign the sky material without it freezing.

It also freezes reliably with PanoramaSkyMaterial (with or without texture) assigned to the sky

My main project and the example do not crash anymore in beta16 under the same scenarios.

Having the same problem with AMD on Artix Linux. Just having the editor open is enough; it likes to happen when I'm not even at the computer. It happens about once per day. Takes out the entire desktop session.
Apr 13 21:06:12 greymon kernel: traps: gdbus[10754] general protection fault ip:7fe1989db537 sp:7fe196ffc420 error:0 in libc
.so.6[7fe198969000+15a000]
Apr 13 21:06:41 greymon kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to process the buffer list -22!

@RenaKunisaki Which graphics card model do you have, and which Vulkan driver are you using (RADV or AMDVLK)?

My system is ASUS ROG Strix G513QY, which has two GPUs: Radeon integrated with 512MB (its name seems to be just "AMD Radeon Graphics"), and Radeon RX 6800M with 12GB. By running DRI_PRIME=1 godot I can force it to run on the latter and that's when it's been crashing. So far using it without that option it hasn't crashed, but I'll report back if it does. I'm using AMDVLK.

Just had it happen again with the integrated GPU.
Apr 18 12:24:00 greymon kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* amdgpu_vm_validate_pt_bos() failed.
Apr 18 12:24:00 greymon kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to process the buffer list -22!
Apr 18 12:24:08 greymon root[28496]: ACPI group/action undefined: button/up / UP
Apr 18 12:24:12 greymon kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* amdgpu_vm_validate_pt_bos() failed.
Apr 18 12:24:12 greymon kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to process the buffer list -22!
Apr 18 12:24:12 greymon kernel: pagefault_out_of_memory: 1309 callbacks suppressed
Apr 18 12:24:12 greymon kernel: Huh VM_FAULT_OOM leaked out to the #PF handler. Retrying PF
Apr 18 12:24:12 greymon kernel: Huh VM_FAULT_OOM leaked out to the #PF handler. Retrying PF
Apr 18 12:24:12 greymon kernel: Huh VM_FAULT_OOM leaked out to the #PF handler. Retrying PF
Apr 18 12:24:12 greymon kernel: Huh VM_FAULT_OOM leaked out to the #PF handler. Retrying PF
Apr 18 12:24:12 greymon kernel: Huh VM_FAULT_OOM leaked out to the #PF handler. Retrying PF
Apr 18 12:24:12 greymon kernel: Huh VM_FAULT_OOM leaked out to the #PF handler. Retrying PF
Apr 18 12:24:12 greymon kernel: Huh VM_FAULT_OOM leaked out to the #PF handler. Retrying PF
Apr 18 12:24:12 greymon kernel: Huh VM_FAULT_OOM leaked out to the #PF handler. Retrying PF
Apr 18 12:24:12 greymon kernel: Huh VM_FAULT_OOM leaked out to the #PF handler. Retrying PF
Apr 18 12:24:12 greymon kernel: Huh VM_FAULT_OOM leaked out to the #PF handler. Retrying PF
Apr 18 12:30:07 greymon root[29265]: ACPI group/action undefined: button/up / UP
Apr 18 12:35:11 greymon root[29717]: ACPI group/action undefined: button/up / UP
Apr 18 12:36:22 greymon root[29835]: ACPI group/action undefined: button/up / UP
Apr 18 12:36:38 greymon kernel: godot.linuxbsd.[29853]: segfault at 1ab000001f9 ip 000001ab000001f9 sp 00007ffd40029f18 error 14 in godot.linuxbsd.template_release.x86_64[55fccb97f000+2a3000] likely on CPU 9 (core 4, socket 0)
Apr 18 12:36:38 greymon kernel: Code: Unable to access opcode bytes at 0x1ab000001cf.

Since my RAM usage is normally around 50% and there are no logs mentioning oom-killer, I assume either it was a VRAM allocation failure or godot somehow leaked 32GB within a few minutes. This crash actually seems to be accidentally exploiting CVE-2023-0047, at least in this instance.

Hi!
Could you test this version to see if you can still repro the problem? Thanks.


Completions not working for unions of errors

Consider the following:
type ErrX distinct error;
type ErrY distinct error;

type Err ErrX|ErrY|error<map<anydata>>;

public function main() {
    Err err = error ErrX("Foo");
    string message = err.<cursor>
}

Calling err.message(), err.cause() is allowed on unions of errors. Therefore, I think we need to provide those suggestions as well.

I think we need to consider the union of errors specially when providing the langlib methods via the typeSymbol.langLibMethods(). In the current implementation we only provide the symbols associated to the union type without considering the union members. If we consider the API user point of view, the user has to do explicit analysis of the type to capture the particular langlib methods.
@dulajdilshan @mohanvive @pubudu91 thoughts?


Unable to deploy

Whenever I try to deploy and enters the APP_ID and APP_CERTIFICATE, it shows me this message
** Item could not be created:
We couldn't deploy your app because the source code violates the Salesforce Acceptable Use and External-Facing Services Policy.**

@shahzad1 this looks like a heroku issue.
please read this thread for potential solutions
https://github.com/developeranaz/Mega-index-heroku/issues/28

@plutoless having the same issue, is it okay if you update the template here and in the official doc? We are having a presentation tomorrow and Agora is one of the main feature we need to deliver. Already have a previous project thus all I need is to finish the setup. Thanks


Consider adding a rollup type to header in order to choose validation rule to apply

          I really don't like those lines. It's exiting fast, and IMHO is very error prone. In general, I would like to see something like:

switch h.rollupType() {
	case based:
		// validation for based rollup
	case optimistic:
		// validation for optimistic rollup
	// ...
}

Originally posted by @tzdybal in https://github.com/rollkit/rollkit/pull/1026#discussion_r1243570478

Removed when enforcing centralized sequencer.


Issue with k8s.io/docs/tasks/configure-pod-container/pull-image-private-registry/

This link "https://index.docker.io/v1/" appears to be broken in the line:
"  is your Private Docker Registry FQDN. (https://index.docker.io/v1/ for DockerHub) "

According to https://www.docker.com/blog/registry-v1-api-deprecation/, the V1 API has been deprecated.

/triage accepted
/assign


Contains Predicate Issue

Issue description
CREATE SCHEMA mySchema;
CREATE COLUMN TABLE mySchema.SEARCH_TEXT( Content VARCHAR(20), Descrip VARCHAR(20), Comment VARCHAR(20) );
INSERT INTO mySchema.SEARCH_TEXT VALUES( 'Blue baseball cap', 'Vintage', 'Out of stock');
INSERT INTO mySchema.SEARCH_TEXT VALUES( 'Red car', 'Vintage', 'Taking orders' );
INSERT INTO mySchema.SEARCH_TEXT VALUES( 'Bluish sky', 'Retro', 'Discontinued' );
SELECT SCORE() AS SCORE,*
FROM mySchema.SEARCH_TEXT
WHERE CONTAINS(CONTENT,'cap',FUZZY(0.0))
ORDER BY SCORE DESC;
Showing only One Record that contains Red car.

Feedback Type (Optional)
None
Page Title on SAP Help Portal (prefilled)
CONTAINS Predicate
Page URL on SAP Help Portal (prefilled)
https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-sql-reference-guide/contains-predicate

Hi, thanks for pointing this out. The example itself is correct, but there is an issue with the fuzzy search. This has been reported.


Specifying parameters in openapi_extras overrides query parameters, rather than appending them

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
See the PR I opened with a fix: https://github.com/tiangolo/fastapi/pull/4267 It includes a test case that describes the use case.
Description
When specifying parameters in openapi_extras for an endpoint, they will overwrite the existing query parameters with the extra parameters, rather than appending the parameters to the spec. This is due to deep_dict_update in utils.py overwriting list types rather than merging them together.
I have created a PR already which has a fix and adds a test case: https://github.com/tiangolo/fastapi/pull/4267
These updates change the behavior to merge parameters together rather than overwriting.
If y'all agree that this seems like a bug, I'd appreciate a review on the PR. Thanks in advance! 😄
Operating System
macOS
Operating System Details
No response
FastAPI Version
0.70.0
Python Version
Python 3.9.7
Additional Context
No response

PR got merged! Closing now

Thanks for coming back to close it! ☕🍰


redirect to wallet app if it's mobile's browser

Redirect to Coinbase wallet mobile app using deeplink  if user use a mobile browser.

mike sales

Atomic works fine ..my region doesn’t support coinbase properly..
On Tue, 6 Apr 2021 at 08:52 zaeguerra @.***> wrote:

@.**** approved this pull request.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/walletlink/walletlink/pull/74#pullrequestreview-628593997,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS3AD2CN42OLVMGUCDBFQY3THKORVANCNFSM42H4E5TA
.

Seems like it’s worked I just have some network issues but i believe all
good .
On Fri, 2 Apr 2021 at 01:25 Kim @.***> wrote:

Redirect to Coinbase wallet mobile app using deeplink if user use a mobile
browser.
You can view, comment on, or merge this pull request online at:
https://github.com/walletlink/walletlink/pull/74
Commit Summary

redirect to wallet app if it's mobile's browser
return after redirect

File Changes

M js/src/relay/WalletLinkRelay.ts
https://github.com/walletlink/walletlink/pull/74/files#diff-702610af8357116ed9a6d0413bbb801e2e3f18aeb16822d0cf8237d739f3d349
(10)

Patch Links:

https://github.com/walletlink/walletlink/pull/74.patch
https://github.com/walletlink/walletlink/pull/74.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/walletlink/walletlink/pull/74, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS3AD2F4SAL255RPGOMIQ43TGTXGLANCNFSM42H4E5TA
.


rdp wrapper for Windows Server 2012R2

Hello
Does the Wrapper works with Windows Server 2012R2 too?
Yours Sincerely
Christian

If your termsrv.dll build number is listed in the supported section of README.md, then yes.


MailjetClient is not compatible with Mailjet\Client

MailjetClient is not compatible with Mailjet\Client
Fatal error: Declaration of Mailjet\MailjetBundle\Client\MailjetClient::post($resource, array $args = Array, array $options = Array) must be compatible with Mailjet\Client::post(array $resource, array $args = Array, array $options = Array): Mailjet\Response in /var/www/web/vendor/mailjet/mailjet-bundle/src/Client/MailjetClient.php on line 19
https://github.com/mailjet/mailjetBundle/blob/master/src/Client/MailjetClient.php
https://github.com/mailjet/mailjet-apiv3-php/blob/v1.5.5/src/Mailjet/Client.php

https://github.com/mailjet/mailjetBundle/pull/34

Hi,
Seems to be merged.
I think we can close it