Auto-update databases on a schedule

Use GitHub actions for this – https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#schedule

Alternative: have the tool, when locally installed, try and update the databases all by itself. That way a new version doesn’t need to be released.

I quickly knocked something up in #11 to tackle this.
Open questions regarding the implementation:

After having updated (with a locally changed package.json as a result), will a successive npm i -g @bramus/caniuse-cli work?
Will that actually work on Windows (I have only tested on macOS)?
What about yarn?
Maybe there are better ways to do this?

Requiring npm and invoking things like npm.commands.view doesn’t seem like a viable option, as it’d only work with NPM.

Open questions regarding when to trigger this:

Definitely not upfront.
Maybe automatically after caniuse was invoked?

But only once per week, perhaps

On a schedule?
Also: give users an option to opt-out?

/cc @tunetheweb

Some more things I found:

https://github.com/react-static/react-static/blob/85c232bb3d357e15b7efd04291ad43b4af2e976b/packages/react-static/src/commands/create.js#L219 invokes an execSync('yarnpkg --version', { stdio: 'ignore' }) to detect if yarn is present or not.
https://github.com/npm/pacote is a project that fetches directly from NPMJS and unpacks the .tgz instead of going through the npm install … route.
Lost the link, but some project allowed passing in your preferred package manager (npm, yarn, pnpm, bun) using a flag.


Migrate policy JSON template to an aws_iam_policy_document data source

This is an old module and as such, uses a JSON template for the policy. Instead, it should be defined in the Terraform itself via an "aws_iam_policy_document" data source. It's far more readable that way.

@brainsik should I open this in pivotal?

Nope! Looks like we're now using a bunch of features of the templating language in order to handle some crazy logic. So, I'll close this out. Thanks for asking.


do fetch failing due to checksum mismatch

Description
When I try to build an image after specifying the image type in local config as rpi-sdimg. The following files fail to be fetched.
IMAGE_FSTYPES = "tar.xz ext3 rpi-sdimg"
It looks like the checksums are mismatched. The expected checksum is
c687aa1b5127a8dc0773e8aefb1f009f24bf71ccb4c9e8b40a1d46cbbb7bee0c  (mentioned in the raspberrypi-firmware.bb file)
whereas the one I get is
702f10a5adca063df0d903af1e54c4925a6c5ab89cee5f33e42f3e17a386660f
Steps to reproduce the issue:

In local.conf set IMAGE_FSTYPE to rpi-sdimg
Run bitbake core-image-base

Describe the results you received:
`Initialising tasks: 100% |##################################################################################################################| Time: 0:00:03
Sstate summary: Wanted 117 Local 78 Network 0 Missed 39 Current 806 (66% match, 95% complete)
Removing 1 stale sstate objects for arch acu_rpi4_64: 100% |################################################################################| Time: 0:00:00
NOTE: Executing Tasks
WARNING: rpi-bootfiles-20210421-r3 do_fetch: Checksum mismatch for local file /home/aliraza/acu-rpi-yocto/yocto_downloads/raspberrypi-firmware-2ac4de4eaac5c1d1b25acec4a5e0a9fdb16f0c91.tar.gz
Cleaning and trying again.
WARNING: rpi-bootfiles-20210421-r3 do_fetch: Renaming /home/aliraza/acu-rpi-yocto/yocto_downloads/raspberrypi-firmware-2ac4de4eaac5c1d1b25acec4a5e0a9fdb16f0c91.tar.gz to /home/aliraza/acu-rpi-yocto/yocto_downloads/raspberrypi-firmware-2ac4de4eaac5c1d1b25acec4a5e0a9fdb16f0c91.tar.gz_bad-checksum_702f10a5adca063df0d903af1e54c4925a6c5ab89cee5f33e42f3e17a386660f
WARNING: rpi-bootfiles-20210421-r3 do_fetch: Checksum failure encountered with download of https://github.com/raspberrypi/firmware/archive/2ac4de4eaac5c1d1b25acec4a5e0a9fdb16f0c91.tar.gz;downloadfilename=raspberrypi-firmware-2ac4de4eaac5c1d1b25acec4a5e0a9fdb16f0c91.tar.gz - will attempt other sources if available
ERROR: rpi-bootfiles-20210421-r3 do_fetch: Fetcher failure for URL: 'https://github.com/raspberrypi/firmware/archive/2ac4de4eaac5c1d1b25acec4a5e0a9fdb16f0c91.tar.gz;downloadfilename=raspberrypi-firmware-2ac4de4eaac5c1d1b25acec4a5e0a9fdb16f0c91.tar.gz'. Checksum mismatch!
File: '/home/aliraza/acu-rpi-yocto/yocto_downloads/raspberrypi-firmware-2ac4de4eaac5c1d1b25acec4a5e0a9fdb16f0c91.tar.gz' has sha256 checksum '702f10a5adca063df0d903af1e54c4925a6c5ab89cee5f33e42f3e17a386660f' when 'c687aa1b5127a8dc0773e8aefb1f009f24bf71ccb4c9e8b40a1d46cbbb7bee0c' was expected
If this change is expected (e.g. you have upgraded to a new version without updating the checksums) then you can use these lines within the recipe:
SRC_URI[sha256sum] = "702f10a5adca063df0d903af1e54c4925a6c5ab89cee5f33e42f3e17a386660f"
Otherwise you should retry the download and/or check with upstream to determine if the file has become corrupted or otherwise unexpectedly modified.
ERROR: rpi-bootfiles-20210421-r3 do_fetch: Fetcher failure for URL: 'https://github.com/raspberrypi/firmware/archive/2ac4de4eaac5c1d1b25acec4a5e0a9fdb16f0c91.tar.gz;downloadfilename=raspberrypi-firmware-2ac4de4eaac5c1d1b25acec4a5e0a9fdb16f0c91.tar.gz'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/aliraza/acu-rpi-yocto/build/tmp/work/acu_rpi4_64-poky-linux/rpi-bootfiles/20210421-r3/temp/log.do_fetch.2004924
ERROR: Task (/home/aliraza/acu-rpi-yocto/sources/meta-raspberrypi/recipes-bsp/bootfiles/rpi-bootfiles.bb:do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2886 tasks of which 2775 didn't need to be rerun and 1 failed.
Summary: 1 task failed:
/home/aliraza/acu-rpi-yocto/sources/meta-raspberrypi/recipes-bsp/bootfiles/rpi-bootfiles.bb:do_fetch
Summary: There were 4 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
`
Describe the results you expected:
Smooth build process
Additional information you deem important (e.g. issue happens only occasionally):
meta-raspberrypi repo is on commit b4ec97e4eb8e36efd1f7e2f8ae020a9e55cfc239

@aliraza1944 seems like an annoying Github issue. I've seen people reporting this lately. Would you be able to push a patch?

Also, this is on master?

I suspect this is fixed -<EMAIL_ADDRESS>

I was going to say the same, found this last night.
https://github.blog/changelog/2023-01-30-git-archive-checksums-may-change/


CP 2077 Easy Installer

I know, the actual method is really easy, but many people are not really skilled with computer, so i've decided to create a EasyInstaller method in C#. Let me know if you wish use it, i can create a pull request !
How it works?

Just put the mod (and update) in the "Patch" folder
Open the EasyInstaller
Click on the button "Select Path" and follow the instruction

Some ScreenShot:

MetroFw is overkill I think, you should replace by your own components

I really prefer use it, cause have many useful tools!
I've created the repository on my GitHub (and correctly refers it to this repository). You can now use it, or pass it to your friend for the easy installation !
https://bit.ly/2K7y7Hp

Working on a new release

Feel free to make a PR with the easy installer.

Perfect, i am working for release the menu fixed, so the people can easy check or uncheck function directly on it. I will probably release it in 24h!


I could not save my file, and cannot find a way to change the name of the file

Error: Service Unavailable
Error: Service Unavailable
    at Request.<anonymous> (https://homebrewery.naturalcrit.com/homebrew/bundle.js:71831:19)
    at Request.Emitter.emit (https://homebrewery.naturalcrit.com/homebrew/bundle.js:1764:20)
    at XMLHttpRequest.xhr.onreadystatechange (https://homebrewery.naturalcrit.com/homebrew/bundle.js:72140:10)
{
  "status": 503,
  "method": "POST",
  "url": "/api/newGoogle/"
}

I'm not sure what to do to change it.

See discussion #1580 for a solution regarding saving. To change the title, go to the meta data editor, which can be found in the snippet bar, furthest icon to the right.
If the linked discussion doesn't fix the issue, let us know

I clicked the little tab for the title and description of the document and entered the title. It appeared in the top bar, but did not allow it to save.

@Avarice-fist Did you take a loot at Discussion #1580 for the saving issue? Renaming your document won't have any effect if you don't resolve the saving issue first by refreshing your Google Drive credentials.

I signed in again with Google, checked my Google Drive and signed into it again. This hasn't solved the problem either.

Did you make sure to fully log out before signing in again? It may be helpful to clear your cookies as well before trying.
If it still doesn't work I can try something else.

I'll try that. Though it might be a minute before I do so.

@Avarice-fist just want to check back on this and see if you are all good to go, or if need to keep this open and take a second look?

Will close this issue due to no response, but it can be re-opened if the above steps did not help and still having issues.


Grid item to with expand/collapse capability

Not a bug, just a question - I want to implement grid items to behave like window panels with expand and collapse buttons. When expand button is clicked, I'd like the targeted grid item to go on top of other grid items (which stay where they are without being re-positioned) and expands to full size within the container it is in. When collapse button is clicked, the grid item would go back to its original size and position. Is it possible? Any pointer is greatly appreciated.

I'm looking for a similar functionality. Is there a way we can make the grid item take up all the available space in the canvas?
Thanks.

Hi, @tpham
I recently implemented the expand/collapse on the grid item when the user clicks the expand button.
To achieve this, I have set some height(say 30px) for grid item(i.e height when collapsed). and then the 'h' property in the layout is set to 1(i.e show 30px).  when user clicks on the expand button then we update the height to 2(if we want 60px) or any other value depending on your expanded area.
I hope, this will help you with your need.
Regards
Nitesh Jain

@s-kris , to make your gird item expand and cover the whole canvas area. You can set the w(width) and h(height) property of layout for that particular item to max value;
Max value for width will be: w = number of columns (depending on a current breakpoint) or try Infinity
h = this you need to find out by hit and trial I guess. or by mathematics.
Regards
Nitesh Jain

Use window.dispatchEvent(new Event('resize')); when you want that react-grid-layout resize dynamically. After you listen the collapse event from your awesome component run window.dispatchEvent(new Event('resize')); this will make to react-grid-layout to trigger a resize listener and will automatically resize the grid container.
Please close this issue if that work for you.

in the meantime does there exist a better solution to this problem? window.dispatchEvent(new Event('resize')); did not work for me.

Implmeneted a solution with ResizeObserver (so it automatically rescales the grid items):
useResizeObserver() Hook:

const {ResizeObserver} = window;

export const useResizeObserver: () => [(value: (((prevState: (Element | null)) => (Element | null)) | Element | null)) => void, ResizeObserverEntry] = () => {
  const [observerEntry, setObserverEntry] = useState<ResizeObserverEntry>({} as ResizeObserverEntry);
  const [node, setNode] = useState<Element | null>(null);
  const observer = useRef<ResizeObserver | null>(null);

  const disconnect = useCallback(() => observer.current?.disconnect(), []);

  const observe = useCallback(() => {
    observer.current = new ResizeObserver(([entry]) => setObserverEntry(entry));
    if (node) observer.current.observe(node);
  }, [node]);

  useLayoutEffect(() => {
    observe();
    return () => disconnect();
  }, [disconnect, observe]);

  return [setNode, observerEntry];
};

Use Intermediary Component for each grid item (so within grid ) which contains:

  const getContentRect = useCallback(
    () => {
      if(contentRect){
        // Set Layout State of grid with new height measured by ResizeObserver
        // ... Code to get new Layout state
        innerProps.setLayout(newLayout);
      }
      },
    [contentRect]
  );

  useEffect(() => getContentRect(), [getContentRect]);


Remove 'IMPROVED' from required attribute fields that must exist in FC

Completed and tested.  Tool runs even if the field still exissts.


Console warning: ''[Violation] Added non-passive event listener to a scroll-blocking  event. Consider marking event handler as 'passive' to make the page more responsive."

Using Svelte 4.0.3

See:
https://chromestatus.com/feature/5745543795965952

Hey,
Thanks for using the library!
Can you be a little bit more specific?
Thanks!

@caseyplummer4haliontech can you please elaborate on this issue? Which browser are you using? Where and when are you seeing this issue? I cannot reproduce on the doc site!

I am closing this as I cannot reproduce. Reopen it when you have time to give me some insights ;)

This is happening to me also in a clean project on Chrome Version 117.0.5938.92 (Official Build) (64-bit) (Linux), but not in Firefox.

This issue is fixed in the version 3 (still in beta)


Changed example for Mina 1.0.0 compatibility

We don't need to create folders ourselves for sockets and pids ourselves with new version of Mina, it's enough to set them in shared_dirs and they will created automaticaly on setup.
https://github.com/mina-deploy/mina/blob/8e75979923f7ccb75c9527d533afc5585ea252a6/tasks/mina/deploy.rb#L72

@lnikell thanks and sorry it took so long to merge this :)


build pip installer changes

I have attempted to make the appropriate changes to make this library pip compatible.
Needs to be tested but if it is confirmed working by others please consider using it to put this library into the python pip package manager ecosystem.

I will test this and get back to you ASAP.


CASMINST-6649-release-1.5 enable smartmon on storage nodes before upgrading first storage node

Description
When storage nodes are upgraded to CSM 1.5, smartmon is enabled on storage nodes. Node-exporter daemons on non-upgraded storage nodes get into a bad state because the non-upgraded storage nodes do not have the neccessary rpms installed. This change installs smartmon and the needed rpms on storage nodes before they are upgraded so node-exporter does not error.

Checklist

[x] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[x] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[x] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

This also needs a backport to 1.6, right?

This also needs a backport to 1.6, right?

This shouldn't need a backport. This is being introduced in CSM 1.5. Which is why it is important to install it before upgrading from CSM 1.4 to 1.5. However, it will already be installed by the time we upgrade to CSM 1.6 so it shouldn't be needed in an upgrade from CSM 1.5 to 1.6.


Gyro sensitivity defines were updated reversed

in Adafruit_FXAS21002C.h I thought that the sensitivity defines looks a bit strange, as it implies that the precision goes up as the range is increased:
#define GYRO_SENSITIVITY_250DPS  (0.0625F)    // Page 9 of NXP datasheet FXAS21002C
#define GYRO_SENSITIVITY_500DPS  (0.03125F)   // ..
#define GYRO_SENSITIVITY_1000DPS (0.015625F)  // ..
#define GYRO_SENSITIVITY_2000DPS (0.0078125F) // ..
After checking the datasheet it seems that the update was done in reverse order, as can be seen in table 35 on page 40:
Table 35. Selectable Full Scale Ranges
FS1	FS0	Range (dps)	Nominal Sensitivity (mdps/LSB)
0	0	±2000		62.5
0	1	±1000		31.25
1	0	±500		15.625
1	1	±250		7.8125

Ugg, just fixed this and ticked the version up. Thanks for taking the time to raise an issue.


{0} in ignored settings description

Version: 1.43.0-insider (user setup)
Commit: 595f98455be0aac7372a0ae7841efae9b91b848e
Date: 2020-02-18T13:52:42.988Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.19041

I don't see it

Are you on latest insiders?

It appears you fixed it in 62265b4ee2f0131ea53f6d3aa69247f61ebe16eb, however I still see it in today's Windows Insiders build somehow?

No clue. Could be your installation is corrupted?

Yeah I'll assume it's an issue with the install, I should reinstall.


[Bug] User Setting - Mentor error when entering comma or space or semi colon label

Expected a Comma or Semi colon or Space
Actually got a error : query is undefined at http://localhost:9991/webpack/app.js:55128
Steps - Open web app, click gear top right, click setting, in Your account scroll down to Mentor, type a comma or semi colon or space.
Development environment Newest - Git commit id: aff58ed9d95e2ad7e0eda57e29cfe84ff343b200
Using - web app
IMPORTANT - You can bypass this bug by typing your comma then quickly typing more characters - the error is only caused if the first character is comma or space or semi colon

Some related conversation here on czo.


"you may want to hold off for a while" - Details?

Back in May, this info was added to the project readme:
IMPORTANT
If you are planning on commencing a new project to introduce Gender Pronouns in Microsoft 365 you may want to hold off for a while.
Is this because a native solution is coming? If so, is there a timeline or roadmap entry we can watch?
Thanks!!!

Here are the Microsoft roadmaps: https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=pronouns
Looks like they are adding it natively to Teams and Outlook. I'm curious if this Github solution modifies the same user attributes or something else.
Pronouns on profiles: https://support.microsoft.com/en-us/office/pronouns-on-your-profile-in-microsoft-365-232c3bfb-a947-4310-86db-b22d63663d85

Here are the Microsoft roadmaps: https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=pronouns
Looks like they are adding it natively to Teams and Outlook. I'm curious if this Github solution modifies the same user attributes or something else.
Pronouns on profiles: https://support.microsoft.com/en-us/office/pronouns-on-your-profile-in-microsoft-365-232c3bfb-a947-4310-86db-b22d63663d85

It does not. This implimentation uses a custom User Property in SharePoint named "Pronoun" as well as a CustomAttribute entry for the Profile Contact Card and syncs with a ExtensionAttribute in Azure AD.
It is an arguably better implimentation than Microsoft's implimentation because it can be managed directly from Delve along with the rest of the user profile info and because it is addressable by API, where Microsoft's version is not.


Navbar elements get hidden after page back animation

If I open a page then get back, "sometimes" the navbar title and icons do not appear again, until I open another page then get back again! this was not happening before update to 1.5.2 for me.
Im using CrossWalk Webview on Android 5.1.
Problem not exist from PC, only in the web view.

I found the problem but I don't know the reason yet, I'll share and hope this help you fix it:
When I face this problem there is a class added called cache or cached I don't remember, and it cases the problem that the navbar elements get hidden sometimes when I click "back", I found that I was doing:
var mainView = myApp.addView('.view-main', {dynamicNavbar: true, domCache: true});
I changed domCache to false and the problem is gone.
To remind you, this bug is strange, because sometimes clicking BACK doesn't cause the problem and sometimes it happens, both from Firefox on MAC and from CrossWalk WebView.
Thanks.


MySQL - Multiple alter statements per alter table

It seems there's an issue adding a column to a MySQL table, using the following syntax
ALTER TABLE foo
  ADD COLUMN bar VARCHAR(100) NULL DEFAULT NULL;

The error give is:
<column constraint real> expected, got ','

thats not the issue, the issue is a list of alters isnt allowed

Ah good catch, sorry about that


nitro db import should work on compressed DB backups

Description
Importing a compressed DB backup (.sql.zip) as generated by Craft results in an error:
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR: ASCII '\0' appeared in the statement, but this is not allowed unless option --binary-mode is enabled and mysql is run in non-interactive mode. Set --binary-mode to 1 if ASCII '\0' is expected. Query: 'PK'.
read unix @->/run/docker.sock: read: connection reset by peer

Error: exit status 1

Additional info

Nitro version: 1.0.1
Multipass version: 1.4.0+mac

@benface this is a duplicate of #132. Closing out in favor of that ticket.


[FEATURE REQUEST] - Create folders by adding "//" behind the filename template.

It's all in the title, and maybe it already exists by another way :)
My goal is to put my VODs in a single new folder for each VOD. That way I can put every assets I used for this single stream in this single folder.
Thanks a lot for this great tool !

That is an oddly specific usecase. I don't see how the majority of users would benefit from such an implementation. I think there are much more important features in the queue. You still need to manually insert the assets yourself, so just creating a folder while doing so is not much more work. This feature provides too little advantages and would be used by such a small fraction of the userbase that I don't want to put any time in it.


Question: is there a data table crud example for tamagui?

Current Behavior
No response
Expected Behavior
No response
Tamagui Version
1.0

Reproduction
1.0

System Info
No response

Apologies for not closing sooner


Upgrading to draft-js 0.10.0 and to the new Entity API

Hi,
draft-js 0.10.0 contains a new feature that I miss today, the ability to paste paragraphs from HTML or Word while keeping their structure.
See the pull request merged in 0.10.0 : https://github.com/facebook/draft-js/pull/828
So I propose the upgrading from 0.9.1 to 0.10.0. This is not a breaking change (see  https://github.com/facebook/draft-js/issues/839 ), I've only seen warnings, that I fixed with replacing some instructions with the new API.
Entity.get(entityKey)
become
contentState.getEntity(entityKey)
Tests are ok !
I hope you'll be able to merge this soon !

Hi @mdarcemont,
There is a brach with initial work, but your pull request is welcome.
Could you please fix the docs?
In the custom entities docs:
197:  const {url} = DraftJS.Entity.get(this.props.entityKey).getData();

Done !

Thank you!
Did you see my branch? You should fix the Entity.create() too.
https://github.com/globocom/megadraft/commit/d333be05eb1542e030601992b1854f15fb863d4c#diff-e007c62f341ba9b8108617f3d82d21c8L161

Sorry for missing that !
It's ok now (I hope)

Hi @mdarcemont, thanks for contributing to Megadraft!


Fix phishing check for local services and fix empty phishing blank page

Fixes #107

Seems ok now. A block screen appears, and the link "continue" works. Though, the link for "see the list of domains" did not work for me.


[Android] [v10] OfflineManager.deletePack is not implemented

Describe the bug
Android-Only. iOS works perfectly.
OfflineManager.deletePack is not implemented.
https://github.com/rnmapbox/maps/blob/main/android/rctmgl/src/main/java-v10/com/mapbox/rctmgl/modules/RCTMGLOfflineModule.kt#L333
To Reproduce
Android-only: Call OfflineManager.deletePack('pack-name')
import React from 'react';
import {StyleSheet, View} from 'react-native';
import MapboxGL from '@rnmapbox/maps';

const styles = StyleSheet.create({
    mapView: {flex: 1},
});

class BugExample extends React.Component {
    async componentDidMount() {
        console.log('>>>>>>>>>>start creating pack', );
        await MapboxGL.offlineManager.createPack(
            {
                name: 'field-1', // any
                bounds: [[32.23782523101579, 46.39912398458027], [33.43887899585923, 47.041693870480955]], // any LARGE area
                styleURL: MapboxGL.StyleURL.Street,
                minZoom: 10,
                maxZoom: 12,
            },
            (pack, status) => {
                console.log('>>>>>>>>>>pack progress', pack.name, status.percentage, status.completedTileCount);
                if (status.state === 'completed') {
                    MapboxGL.offlineManager.deletePack('field-1');
                    // throws error where deletePack is not a function (android only)
                }
            },
            (pack, error) => {
                console.log('>>>>>>>>>>pack error', pack.name, error);
            },
        );

        // always shows a single pack without metadata nor identifier (name)
        console.log(MapboxGL.offlineManager.getPacks());
    }

    render() {
        return (
            <View style={styles.mapView}>
                <MapboxGL.MapView
                    ref={(c) => (this._map = c)}
                    onPress={this.onPress}
                    style={styles.mapView}
                >
                    <MapboxGL.Camera
                        zoomLevel={10}
                        centerCoordinate={[33.43887899585923, 47.041693870480955]}
                    />
                </MapboxGL.MapView>
            </View>
        );
    }
}

export default BugExample;
}

Expected behavior
deletePack should be implemented.
Actual behavior
deletePack is not implemented and throws a JS function is undefined error.
Versions (please complete the following information):

Platform: Android
Platform OS: Android 12
Device: Samsung S21 Ultra
Emulator/ Simulator: emulator & physical device
Dev OS: macOS Monterey
@rnmapbox/maps Version @rnmapbox/maps#main
Mapbox GL version 10.6.0
React Native Version 0.68

Additional context
deletePack is a necessity otherwise a pack can never be invalidated/re-downloaded; however, there are more offlinemanager functions not yet implemented on Android:

deletePack
invalidatePack
resetDatabase
invalidateAmbientCache
clearAmbientCache
setMaximumAmbientCacheSize
mergeOfflineRegions

fixed with above PR


TestUp Window Blank

When I open the TestUp Window it comes up completely blank. The Ruby Console does say "Reloaded 21 files!
MiniTest TestUp Extension discovered..." if I reload which tells me it does see the tests. Am I using this wrong or is there a bug?

SKUI was not included when I cloned the repo so I downloaded it directly from your SKUI repo

@Achill113 - SKUI is referenced as a sub-repo. When cloning TestUp you must make sure to also clone the sub-repos. Most git GUI clients will do this automatically, but if you use the command line you must add some additional parameters.


npx create-llama is producing bugged apps

The command "npx create-llama@latest" is creating bugged apps. (Probably next.js frontend bug - both next.js and python backend versions produce the error)
Reproduction:
Create app with that command and following settings:

Which template would you like to use? » Agentic RAG (single agent)
√ Which framework would you like to use? » FastAPI (Python)
√ Would you like to generate a NextJS frontend for your FastAPI (Python) backend? ... No / Yes
√ Would you like to set up observability? » No
√ Please provide your OpenAI API key (leave blank to skip): ... sk-proj-20hNz4BZK1S6QjCBKdsUT3BlbkFJ4yaaSAef1yT3Y47b7nyf
√ Which data source would you like to use? » Use an example PDF
√ Would you like to add another data source? » No
√ Would you like to use LlamaParse (improved parser for RAG - requires API key)? ... no / yes
√ Would you like to use a vector database? » No, just store the data in the file system
√ Would you like to build an agent using tools? If so, select the tools here, otherwise just press enter » Weather
√ How would you like to proceed? » Generate code, install dependencies, and run the app (~2 min)

then next.js frontend will throw following error:
⨯ TypeError: Promise.withResolvers is not a function
at webpack_require (C:\app.next\server\webpack-runtime.js:33:42)
at webpack_require (C:\app.next\server\webpack-runtime.js:33:42)
at webpack_require (C:\app.next\server\webpack-runtime.js:33:42)
at eval (./app/components/ui/chat/widgets/PdfDialog.tsx:8:80)
at (ssr)/./app/components/ui/chat/widgets/PdfDialog.tsx (C:\app.next\server\app\page.js:459:1)
at webpack_require (C:\app.next\server\webpack-runtime.js:33:42)
at eval (./app/components/ui/chat/chat-message/chat-sources.tsx:14:76)
at (ssr)/./app/components/ui/chat/chat-message/chat-sources.tsx (C:\app.next\server\app\page.js:338:1)
at webpack_require (C:\app.next\server\webpack-runtime.js:33:42)
at eval (./app/components/ui/chat/chat-message/index.tsx:18:71)
at (ssr)/./app/components/ui/chat/chat-message/index.tsx (C:\app.next\server\app\page.js:382:1)
at webpack_require (C:\app.next\server\webpack-runtime.js:33:42)
at eval (./app/components/ui/chat/chat-messages.tsx:12:71)
at (ssr)/./app/components/ui/chat/chat-messages.tsx (C:\app.next\server\app\page.js:404:1)
at webpack_require (C:\app.next\server\webpack-runtime.js:33:42)
at eval (./app/components/ui/chat/index.ts:9:72)
at (ssr)/./app/components/ui/chat/index.ts (C:\app.next\server\app\page.js:448:1)
at webpack_require (C:\app.next\server\webpack-runtime.js:33:42)
at eval (./app/components/chat-section.tsx:8:66)
at (ssr)/./app/components/chat-section.tsx (C:\app.next\server\app\page.js:250:1)
at Object.webpack_require [as require] (C:\app.next\server\webpack-runtime.js:33:42)
digest: "1927380740"
GET / 500 in 90ms
Happens on windows 11 x64

Sorry for the trouble fixed in<EMAIL_ADDRESS>

@Arputikos please revoke your OpenAI key posted above


tinyproxy: init at 1.8.4

Motivation for this change
Tinyproxy is great 😄
This should compile for all platforms.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] 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)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg  build tinyproxy

Failure on x86_64-linux (full log)
Attempted: tinyproxy
Partial log (click to expand)
a2x: ERROR: "xsltproc"  --stringparam callout.graphics 0 --stringparam navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 0  "/nix/store/s2xd83mkhjmck3jf491mq96ygnrg2q4x-asciidoc-8.6.9/etc/asciidoc/docbook-xsl/manpage.xsl" "/build/source/docs/man5/tinyproxy.conf.xml" returned non-zero exit status 5
make[3]: *** [Makefile:522: tinyproxy.conf.5] Error 1
make[3]: Leaving directory '/build/source/docs/man5'
make[2]: *** [Makefile:342: all-recursive] Error 1
make[2]: Leaving directory '/build/source/docs'
make[1]: *** [Makefile:392: all-recursive] Error 1
make[1]: Leaving directory '/build/source'
make: *** [Makefile:333: all] Error 2
builder for '/nix/store/s2c6w8090706pvy5k8y4w77gpws40lic-tinyproxy-1.8.4.drv' failed with exit code 2
error: build of '/nix/store/s2c6w8090706pvy5k8y4w77gpws40lic-tinyproxy-1.8.4.drv' failed

Failure on aarch64-linux (full log)
Attempted: tinyproxy
Partial log (click to expand)
a2x: ERROR: "xsltproc"  --stringparam callout.graphics 0 --stringparam navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 0  "/nix/store/k4ppgng6ccadfbij08r8dp551azz5p3q-asciidoc-8.6.9/etc/asciidoc/docbook-xsl/manpage.xsl" "/build/source/docs/man5/tinyproxy.conf.xml" returned non-zero exit status 5
make[3]: *** [Makefile:522: tinyproxy.conf.5] Error 1
make[3]: Leaving directory '/build/source/docs/man5'
make[2]: *** [Makefile:342: all-recursive] Error 1
make[2]: Leaving directory '/build/source/docs'
make[1]: *** [Makefile:392: all-recursive] Error 1
make[1]: Leaving directory '/build/source'
make: *** [Makefile:333: all] Error 2
builder for '/nix/store/2411syid1dx7wagl26sr9jnwq6y1dicr-tinyproxy-1.8.4.drv' failed with exit code 2
error: build of '/nix/store/2411syid1dx7wagl26sr9jnwq6y1dicr-tinyproxy-1.8.4.drv' failed

Looks like building the manpages fails.

Success on x86_64-darwin (full log)
Attempted: tinyproxy
Partial log (click to expand)
make[2]: Nothing to be done for 'install-data-am'.
make[2]: Leaving directory '/private/tmp/nix-build-tinyproxy-1.8.4.drv-0/source'
make[1]: Leaving directory '/private/tmp/nix-build-tinyproxy-1.8.4.drv-0/source'
post-installation fixup
gzipping man pages under /nix/store/lbljdqn2ac0a9f4sbz0wlrz5rswqqas0-tinyproxy-1.8.4/share/man/
strip is /nix/store/qfxcr8c4fg7lkybrny9n2sb77bmippdx-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/lbljdqn2ac0a9f4sbz0wlrz5rswqqas0-tinyproxy-1.8.4/sbin
patching script interpreter paths in /nix/store/lbljdqn2ac0a9f4sbz0wlrz5rswqqas0-tinyproxy-1.8.4
moving /nix/store/lbljdqn2ac0a9f4sbz0wlrz5rswqqas0-tinyproxy-1.8.4/sbin/* to /nix/store/lbljdqn2ac0a9f4sbz0wlrz5rswqqas0-tinyproxy-1.8.4/bin
/nix/store/lbljdqn2ac0a9f4sbz0wlrz5rswqqas0-tinyproxy-1.8.4

Thanks for reviewing @xeji, I’ll revisit this and fix the manpages issue

Please also make sure you build packages locally with sandboxing enabled. This makes it much more likely that if it builds locally, it will also build on our CI.

Managed to reproduce by turning off my internet connection:

It happens because xsltproc can't find some DTDs (apparently) and reaches to the internet to get them. However just adding a nonet option and a native dependency on docbook_xsl should fix it (testing locally seems fine using NixOS).
Thanks again @xeji

@GrahamcOfBorg build tinyproxy

Success on x86_64-linux (full log)
Attempted: tinyproxy
Partial log (click to expand)
make[1]: Leaving directory '/build/source'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/vc67fwpmrhy521kvcffisf2fira8n1cr-tinyproxy-1.8.4
shrinking /nix/store/vc67fwpmrhy521kvcffisf2fira8n1cr-tinyproxy-1.8.4/sbin/tinyproxy
gzipping man pages under /nix/store/vc67fwpmrhy521kvcffisf2fira8n1cr-tinyproxy-1.8.4/share/man/
strip is /nix/store/1hi76hr87bd1y1q1qjk0lv8nmcjip1c8-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/vc67fwpmrhy521kvcffisf2fira8n1cr-tinyproxy-1.8.4/sbin
patching script interpreter paths in /nix/store/vc67fwpmrhy521kvcffisf2fira8n1cr-tinyproxy-1.8.4
checking for references to /build in /nix/store/vc67fwpmrhy521kvcffisf2fira8n1cr-tinyproxy-1.8.4...
moving /nix/store/vc67fwpmrhy521kvcffisf2fira8n1cr-tinyproxy-1.8.4/sbin/* to /nix/store/vc67fwpmrhy521kvcffisf2fira8n1cr-tinyproxy-1.8.4/bin

Success on x86_64-darwin (full log)
Attempted: tinyproxy
Partial log (click to expand)
make[2]: Nothing to be done for 'install-data-am'.
make[2]: Leaving directory '/private/tmp/nix-build-tinyproxy-1.8.4.drv-0/source'
make[1]: Leaving directory '/private/tmp/nix-build-tinyproxy-1.8.4.drv-0/source'
post-installation fixup
gzipping man pages under /nix/store/q1r0011bng15jvl2rpj4b9xrp5d5h9g9-tinyproxy-1.8.4/share/man/
strip is /nix/store/qfxcr8c4fg7lkybrny9n2sb77bmippdx-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/q1r0011bng15jvl2rpj4b9xrp5d5h9g9-tinyproxy-1.8.4/sbin
patching script interpreter paths in /nix/store/q1r0011bng15jvl2rpj4b9xrp5d5h9g9-tinyproxy-1.8.4
moving /nix/store/q1r0011bng15jvl2rpj4b9xrp5d5h9g9-tinyproxy-1.8.4/sbin/* to /nix/store/q1r0011bng15jvl2rpj4b9xrp5d5h9g9-tinyproxy-1.8.4/bin
/nix/store/q1r0011bng15jvl2rpj4b9xrp5d5h9g9-tinyproxy-1.8.4

Success on aarch64-linux (full log)
Attempted: tinyproxy
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/gxmxx3x112gzxvkziwbwcnijynjiv44a-tinyproxy-1.8.4
shrinking /nix/store/gxmxx3x112gzxvkziwbwcnijynjiv44a-tinyproxy-1.8.4/sbin/tinyproxy
gzipping man pages under /nix/store/gxmxx3x112gzxvkziwbwcnijynjiv44a-tinyproxy-1.8.4/share/man/
strip is /nix/store/zrs21zqcchgyabjf4xfimncdq16njizc-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/gxmxx3x112gzxvkziwbwcnijynjiv44a-tinyproxy-1.8.4/sbin
patching script interpreter paths in /nix/store/gxmxx3x112gzxvkziwbwcnijynjiv44a-tinyproxy-1.8.4
checking for references to /build in /nix/store/gxmxx3x112gzxvkziwbwcnijynjiv44a-tinyproxy-1.8.4...
moving /nix/store/gxmxx3x112gzxvkziwbwcnijynjiv44a-tinyproxy-1.8.4/sbin/* to /nix/store/gxmxx3x112gzxvkziwbwcnijynjiv44a-tinyproxy-1.8.4/bin
/nix/store/gxmxx3x112gzxvkziwbwcnijynjiv44a-tinyproxy-1.8.4

Thank you, LGTM now.

Managed to reproduce by turning off my internet connection:

That's one reason to enable sandboxed builds on your local machine. The sandbox denies network access, so you would have caught this error right away.


Endpoint to get NLU threshold (or policy)

Rasa Core version: 0.13.2
Pretty sure there is no endpoint yet to get the policy, just like it used to have a /config endpoint for the NLU.
My usecase is that we are logging the confidence + intention to Rasa-ui, and with the current implementation there is no way for the user to know if the detected intent have a greater confidence than the threshold, or if it's a "miss match".
Did I miss a way to get this threshold, or is this something that you plan to implement ?
If not, I'll look for an another solution, but it would be great.
Thank you !

Thanks for raising this issue, @wochinge will get back to you about it soon.

@huberrom What would be the NLU policy?
You can get the NLU confidence when you are sending a parse request to it: http://localhost:5000/parse . From Rasa Core you could use the tracker to get NLU confidence levels for the latest messages: https://rasa.com/docs/core/server/#operation/getTracker . Does that help you?

Hum not really, maybe I didn't explain well enough.
What I need is the NLU threshold set in the policy config.
Before we could request the config (including the pipeline) of the nlu, it would be nice if we could request the policy of the core

Okay, I see 👍 Yeah, that would make totally sense. Would you be up for implementing this?

Maybe we'll put it as a task in our project, I'll let you know if you're going to implement it soon

Sorry, I don't think I'll have enough time to implement this.
It's still an idea if anyone want to implement this one day.
Thank you for your answer tho


refactor: style errors from productivity measurement PR

What kind of change does this PR introduce?

refactoring to fix style errors in productivity PR
Summary

Checklist

[x] My code follows the style guidelines of OpenAdapt
[x] I have performed a self-review of my code
[x] If applicable, I have added tests to prove my fix is functional/effective
[x] I have linted my code locally prior to submission
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (e.g. README.md, requirements.txt)
[x] New and existing unit tests pass locally with my changes

Looks great, from here @Mustaballer we have to figure out why it is failing despite passing flake8 and black locally.

Once https://github.com/OpenAdaptAI/OpenAdapt/pull/477 is merged, and this PR is updated, the status checks should pass. Also I don't believe that this should trigger a version bump(from the 'fix' in the PR title). Could you rename the PR title to refactor: style errors from productivity measurement PR

Thank you @angelala3252 ! 🙏


"Use spaces, not tabs." Column Index

(function (i) {
	console.log(i);
}(0));

The console.log line is indented by one tab character. When I ran JSLint on it, I noticed the "Use spaces, not tabs." warning object had a column index of 1 instead of zero. Is this intentional?

JSLint requires you to use spaces instead of tabs in indents. It is best practice to use 4 space characters as opposed to 1 tab character.
If you wish to disable this complaint, use the 'white' directive (i.e. /*jslint white:true */).
For more directives, see the help page: http://www.jslint.com/help.html

Personally, I don't use tabs, but that's not the issue. The warning itself
is pointing to the character "c" (column 1) instead of the tab character
(column 0).
On Mon, Apr 25, 2016 at 6:45 PM, Karim Alibhai<EMAIL_ADDRESS>wrote:

JSLint requires you to use spaces instead of tabs in indents. It is best
practice to use 4 space characters as opposed to 1 tab character.
If you wish to disable this complaint, use the 'white' directive (i.e. /*jslint
white:true */).
For more directives, see the help page: http://www.jslint.com/help.html
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/douglascrockford/JSLint/issues/182#issuecomment-214456613

The full message is probably this:
 #1 Use spaces, not tabs.
    console.log(i); // Line 3, Pos 1

It has "Pos 1" because the tab character is the first character in that line.

I was a bit vague describing the issue actually, apologies.
Thing is, I'm using the jslint.js file as a Node.js module. I feed it JS source code and it returns an object for each warning.
One of the properties this warning object has is the column property, which holds a number that points to the character in question.
It appears to be zero-indexed because I get 0 from it when the warning is at the first character.
When it's a "Use spaces, not tabs." object, however, column is set to 1, which is the character after the tab. Hence, I thought there might be an off-by-one error.

It is the location of first token after the bad whitespace.


Release v1.1.301.1

This release includes the following changes.

changed the condition for dev and master branches (#140)
disable ARR affinity in pp (#141)
merge dev into feature branch (#142)

merge error abandoned


Add completion sources separate from edited ledger file

Until such a time as this app is a 100% robust and feature complete hledger file editor (not the foreseeable future), I foresee keeping my main ledger data files separate and keeping a mobile only ledger file for data entry that I can sync/merge into the full fledged ledgers from a computer. This is also the workflow I'd want for quick mobile data entry (especially for my wife) that I expect to want to touch up later with perhaps missing tags or other extra information.
That puts completions (both payee and account) in an awkward position. For desktop editing I use a plugin that reads payees from a generated file that sees all the possible payees and a curated list of defined accounts (predefined so I can lint ledgers and reject ones that are not predefined).
I would like to use these sources on mobile too. This probably means being able to read a separate ledger and extract payees and accounts from there while editing a different file. That way the mobile ledger data could be periodically flushed out and moved to other files without loosing access to the payee and account completions.

I could add an extra setting for this, but it's probably pretty low on the priority list in relation to the other issues in this repo currently.

Sure, it would be behind edit/delete for me too. I can always pre-poppulate a ledger with some common accounts in a dummy transaction as a stand-in.
Realistically this is probably easier to add than the urgent edit/delete though ;-) Good luck! Sorry I'm not great with Android stuff.


unplayable..

any idea how long till this get updated? in my location the game literally unplayable without this, i even choked on single weave

According to those over at XIVLauncer/Dalamud, there's quite a few new changes which need to be accounted for. Dalamud update still hasn't rolled out either. I'd thus like to imagine that this is why XIVAlexander isn't ready.

I have the same issue and my static is doing reclears in less than 24 hours. I can do a single weave about 80% of the time, but the other 20% they often don't even go off.

don't wanna speak in behalf, but please be patient since they're already working on this for free

Be patient. Your reliance on a tool doesn't equal to an emergency on the dev. You use it knowingly that it can break anytime.
Devs are people too.

There's no need to ask when this is going to be available. The base game being unplayable is of no consequence to the dev of xivalex. Be patient.

we will just have to wait, whoever made this add-on, we owe him a lot, he made it free and made the game much more enjoyable.

lmao. ppl getting mad over OP because they themselves are madly waiting.

Be mad at the devs at SE who made an online game that can't handle latency. The functionality of XIVAlexander is something that should already come with the base game.

we will just have to wait, whoever made this add-on, we owe him a lot, he made it free and made the game much more enjoyable.

They haven’t updated it in over half a year. They don’t respond to issues or comments anymore after I proved them wrong about XIVAlex corrupting game files for some reason and it not being a failing hard drive issue that was causing it. Who knows if they will even update it now or if they are even working on it

They haven’t updated it in over half a year.

The releases builds only comes when it's necessary to release them.
Opcodes for 6.3 where changed hours after game update at 7993fd3
So don't say that the devs are unaware of the changes that needs to be made.

They haven’t updated it in over half a year.

The releases builds only comes when it's necessary to release them. Opcodes for 6.3 where changed hours after game update at 2786e10 So don't say that the devs are unaware of the changes that needs to be made.

Perhaps you should learn how to read before you comment in response. I never said they aren’t unaware. I said who knows if they are even actively working on the project when they haven’t in half a year and have since stopped replying to any and all comments/issues after I proved them wrong about the program corrupting game files. Like I said, learn to read before you comment in response.

Leaving the passive agressive tone aside, I'd argue they do have a point as we actually do not know if they will work on an update anytime soon.
We're not entitled to anything, I get it, and this is free tool, but other devs for dalamud/act all provided even small updates along the line of "shit's broken, working on fixing"
Since there's no discord or social hub to exchange with the devs outside of github issues, and provided they haven't answered to any of these  since the update (afaik?), one can be concerned as to if devs are or will be working on a fix.
And I guess anyone who would want to eventually fork it would like to know as well beforehand

We got opcodes patch code morning so there was at least some kind of activity, if it wasn't automation. But yea, no communication I've seen about a fix being in the works or even acknowledgement of the problem.

idk why people acted so aggressively to someone merely asking if there is some kind of ETA or 'dw worry guys we are working on it'. Some here behaved like OP was asking for the devs' firstborns.


Track code version with model version

Currently we don't track code version with the model version this can lead to inability to re-produce results.

Use git python package to get commit tag.
Add git commit tag as a prefix when saving model files
Add git commit tag to logs
Add git commit tags to yaml config files at exp_dir

Addressed here https://github.com/moabitcoin/cherry-pytorch/pull/32

The models are saved as agent-{step}-{gitsha}.pth


export support - files to json / zip json for import back into SimpleNotes

Could be used to import (non-nested) flat directory of text files (*.txt and *.md) into:

Simplenote
quillpad - https://github.com/quillpad/quillpad which has a similar json format (different enough where separate support would be needed)

notallyToQuillPad.py

Use json file to retain create timestamps if creation time lost from file system?

TODO add option to sort the content of the json file by modify time (initially any order).


loading

Environment data

VS Code version: XXX
Extension version (available under the Extensions sidebar): XXX
OS and version: XXX
Python version (& distribution if applicable, e.g. Anaconda): XXX
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): XXX
Relevant/affected Python packages and their versions: XXX
Relevant/affected Python-related VS Code extensions and their versions: XXX
Value of the python.languageServer setting: XXX

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]
Expected behaviour
XXX
Actual behaviour
XXX
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

XXX

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

Can you please open a new issue with the template filled in? Unfortunately we need such information in order to help you.


Add facility to backup the test pack after each test.

This will allow the identity server pack to be backed up after tests with the test data to a given location. To enable this. Uncoment following line in automation.xml
<!--<parameter name="backup-test-pack" value="true"/>-->
<!--<parameter name="backup-location" value="<Absolute path for backup location with trailing foreword slash>"/>-->

Fixed with: https://github.com/wso2/product-is/commit/951920231fa00ee1fa674619edded309afdfcc75


Support cross deployment links?

Hi,
Does cf-operator have a plan to support cross deployment links?
We have a scenario that consumer deployment is apart from the provider deployment under the same namespace(such as auto-scaler with cf-deployment). I found that BOSH supports this feature that the provider is ready for consumption cross deployment after the provider deployment deployed and consumer instance can get the right link information.
Did we have an item to discuss this or we did not support this feature? If the second is yes, we need to update doc about this.
Thanks.
/cc @aqan213

Closed by: https://github.com/cloudfoundry-incubator/cf-operator/pull/647


Fix for Removing Correct Selected Items if MultiSelect Array Allows for Duplicates

See https://github.com/shentao/vue-multiselect/pull/614 for details. Credit to @Jtorrecilla for this fix.
This is a branch with the code from PR- https://github.com/shentao/vue-multiselect/pull/614 that fixes issue https://github.com/shentao/vue-multiselect/issues/282, that hopefully can be easily merged in the next release.
Happy to make any changes needed / requested.

Thanks @dannynicolas , I didn't realized about your previous comment!

Id like to see this merged in, would fix issue #282 for our team using this package

I'd also like to have this fix. Experiencing issue #282 as well.

If you’re experiencing issue #282 it probably means you operate on an array of objects and forgot to pass the required label and track-by props.
Please read the docs: https://vue-multiselect.js.org/#sub-single-select-object
Not accepting this PR. Sorry.


Update for IntAct plugin for web VEP

Requirements
IntAct is a new VEP plugin that reports variants effect on molecular interaction. We will add this plugin in release 107 to web VEP.
Description
We want to put external links that will navigate user to relevant IntAct page where he/she can get more information about the molecular interaction. Hence, we wish to add url template to add the external links which will be used by IntAct (through public plugins - see https://github.com/Ensembl/public-plugins/pull/523)
Views affected
IntAct interaction ac column in web VEP result with IntAct plugin turned on.
sandbox url - http://wp-np2-11.ebi.ac.uk:7070/Tools/VEP
test data -
1       5890912 297808  C       T
1       9975672 982555  C       T

Possible complications
Nothing comes to mind.
Merge conflicts
tested in sandbox.
Related JIRA Issues (EBI developers only)
https://www.ebi.ac.uk/panda/jira/browse/ENSVAR-3250

@diegomscoelho , @dglemos can you please check this PR.

Can you please confirm this is going to master and not 106?

Hello @jyothishnt , yeah this PR is going to be for e107 instead of e106.

Hi @nakib103 is everyone happy with the changes and ready to be merged?

The change looks good, it can be merged.


Will add interview problems on Dynamic Programming

Please assign me this task to add problems based on knapsack

I am assigning you to this Issue. Make sure you have read the Contributing Guidelines

Please assign me some good first issue.. @abirbhattacharya82


Update .travis.yml

Avoids keys decryption for pull requests.
Please, @raulraja could you review? Thanks!

LGTM


Weird coloring with 1.0 release

My terminal is just set to white on black (not white on gray like some people like it).  It used to work fine, but now that I've upgraded, the colors are all wacky:

That is pretty strange. Maybe your terminal doesn't support 256 colors? In any case, you can probably change the colorscheme to simple to fix it.

This is the default Ubuntu 16.04 terminal.  I realized I do need to reboot after some installs... possibly that'll fix this problem.  I'll try that later today when I get to a good stopping point, and update the bug with any further information.

I think you should possibly also run $ export TERM=xterm-256color to enable 256 color mode. In any case the colorscheme you had before was renamed to simple so you probably want to use that one anyway.

I'm seeing the same problem on iTerm 3 beta on mac (and I would suspect on other versions of iTerm).  I've confirmed that it has nothing to do with my customized colors (changing them doesn't affect the behavior).
Using export TERM=xterm-256color before running micro doesn't affect the behavior at all.
If there's anything I can do to help, let me know.  @zyedidia - this is an awesome project you've got going here!

BTW, I tried updating my color scheme, and it didn't make a difference either.

Oh! I know what the issue here is. It's a problem with the yaml syntax file which hasn't been updated to use the colorscheme feature yet. I'll get on that right away.
@joshuawarner32 were you also editing yaml?

I was just going to post that it looks like it's only YAML :)

@zyedidia I'm editing bash/sh (a gentoo ebuild file, actually).  And technically, if it's relevant I'm am running micro on a linux box, which I'm ssh'd to from my mac.  Terminal config should be coming from my mac though.

Could you tell me what micro identifies the filetype to be? Just run > show filetype.

> show filetype gives ebuild

I'm going to close this issue because it really just means more syntax files need to be updated.

I can confirm this is working on master (for ebuild files, at least).  Thanks for the super-quick response!

huzzah, fixed for yaml for me, too.


epic files mistakenly treated as if west longitudes

Billy ran into this; Ferret reads epic files and should be prepared to use them - and convert to modern data formats.  The file with this file header (attached below),
> ncdump -h epic_EQ_sst_xt_hf.cdf
netcdf epic_EQ_sst_xt_hf {
dimensions:
        time = 2510 ;
        depth = 1 ;
        lat = 1 ;
        lon = 27 ;
variables:
        int time(time) ;
                time:FORTRAN_format = "" ;
                time:units = "True Julian Day" ;
                time:type = "EVEN" ;
                time:epic_code = 624 ;
        int time2(time) ;
                time2:FORTRAN_format = "" ;
                time2:units = "msec since 0:00 GMT" ;
                time2:type = "EVEN" ;
                time2:epic_code = 624 ;
        float depth(depth) ;
                depth:FORTRAN_format = "" ;
                depth:units = "m" ;
                depth:type = "EVEN" ;
                depth:epic_code = 3 ;
        float lat(lat) ;
                lat:FORTRAN_format = "" ;
                lat:units = "degree_north" ;
                lat:type = "EVEN" ;
                lat:epic_code = 500 ;
        float lon(lon) ;
                lon:FORTRAN_format = "" ;
                lon:units = "degree_east" ;
                lon:type = "EVEN" ;
                lon:epic_code = 502 ;
        float T_20(time, depth, lat, lon) ;
                T_20:name = "T" ;
                T_20:long_name = "TEMPERATURE (C)" ;
                T_20:generic_name = "temp" ;
                T_20:FORTRAN_format = "f10.2" ;
                T_20:units = "C" ;
                T_20:epic_code = 20 ;

// global attributes:
                :Data_Source = "Global Tropical Moored Buoy Array Project Office/NOAA/PMEL" ;
                :File_info = "Contact<EMAIL_ADDRESS>;
                :missing_value = 1.e+35f ;
                :_FillValue = 1.e+35f ;
                :beg_EQ = 850113 ;
                :end_EQ = 1190520 ;
                :b2k_EQ = 19850113 ;
                :e2k_EQ = 20190520 ;
                :CREATION_DATE = "06:21 23-MAY-2019" ;
}

gets interpreted as if the longitude axis is west-longitudes instead of east-longitudes.  Here's what's in the file, intended to be treated as 135E, 140E, etc.
> ncdump -v lon  epic_EQ_sst_xt_hf.cdf
...
data:

 lon = 135, 140, 145, 150, 155, 160, 165, 170, 175, 180, 185, 190, 195, 200,
    205, 210, 215, 220, 225, 230, 235, 240, 245, 250, 255, 260, 265 ;
}

but,
yes? use epic_EQ_sst_xt_hf
yes? sh dat
     currently SET data sets:
    1> ./epic_EQ_sst_xt_hf.cdf  (default)
 name     title                             I         J         K         L
 T_20     TEMPERATURE (C)                  1:27      1:1       1:1       1:2510

yes? list x[gx=t_20]
             VARIABLE : X
                        axis LON
             FILENAME : epic_EQ_sst_xt_hf.cdf
             SUBSET   : 27 points (LONGITUDE)
 95E    /  1:   95.0
 100E   /  2:  100.0
 105E   /  3:  105.0
 110E   /  4:  110.0
 115E   /  5:  115.0
 120E   /  6:  120.0
 125E   /  7:  125.0
 130E   /  8:  130.0
 135E   /  9:  135.0
 140E   / 10:  140.0
 145E   / 11:  145.0

That should be,  135E, 140E, ...
The tar file:
epic_lon_data.tar.gz

This is fixed in cd_get_1_axis.   The code was looking for an optional attribute lon:positive="west" and when that attribute is not found, treating the axis as west anyway.


Thread locking

This should be done in the front end.
We need to be careful because the front end calls its own functions. So we should acquire the lock just before calling the back-end function in the switch statement.

Thread locking is now done in the front end based on pthread.h (see pthread_mutex_init/destroy)
TODO: Check that it works properly for HDF5 back end and implement trexio_hdf5_lock/unlock if it does not


Add comments about keeping types in sync with runtime.

Part of https://github.com/mono/mono/pull/18054.

I don't think this will be useful in the future given the repo consolidation, closing :)

I was asked to..


Change default charset & collation to utf8mb4_unicode_ci

Changing to mb4 requires 4 bytes of index per character, which means a varchar(255) can no longer be indexed.  Can't apply this to every field.


Usage of "alt" property throws error on SvelteKit + TypeScript

Hi, folks!
I'm creating a website on SvelteKit + TypeScript, and I'm trying to use the HTML alt property on an Icon.

The website runs fine, but TypeScript is throwing an error because the property doesn't exist.

This is a bug or am I doing something wrong?
Thanks a lot.

alt attribute is for images rendered as <img> to show text if image fails to load or cannot be viewed.
For <svg> attribute you are looking for is title.

YOU. ARE. THE. BEST.
Thanks a lot 🙂


Reference Time

Optionally override TodayLine with a Reference Time around which everything is happening in the timeline calendar... i.e. a deadline, or a crucial moment after which things change significantly (see demo). If you have a reference time instead of Today, then hovering over the TodayLine uses InfoLabel to show the timestamp along with its Label.
This is my first attempt at a Pull Request for someone else's project... I do not expect to have got everything right about it, but I hope you see value in the feature... it was very useful for a project I was working on.

Thank you very much for this contribution however I'm going to close this PR.  I don't see much clamoring for this feature and I would like to redo how these reference lines (CurrentTime, Cursor, etc) are handled.


Update README.md

fixing the world (broken hyperlink)

eagle eyes!

i was just clicking the links! read the docs!


Motion for Leave to file answer

Is this for the individual motion for leave to file answer? Still open?

Is this for the individual motion for leave to file answer? Still open?

Individual!

Being tracked in #303 with other motions

Based on what I know from progress and atm, this will not be standalone and will be made live as a part of motion tester - changing accordingly

#507

Already incorporated into EDDE, awaiting live with motion tester in #507


Split docker workflows

Having one workflow per docker image to build allows us to have more fine grained control when to actually trigger the workflow.

I always merge with alpha at first by accident which triggers the sla bot :(. About time we make beta the default branch


PEP Layout is broken

Hi,
Thanks for your docset.
Please take a look at this issue: https://github.com/Kapeli/Dash-User-Contributions/issues/3284
Currently the PEP layout is broken as you can see on the screenshot in the link above.

Seems like it's a CSS/JS problem ? If you open the html with like open pepdash/PEPs.docset/Contents/Resources/Documents/www.python.org/dev/peps/pep-0008/index.html it's perfectly rendered and linked on browser. (I've followed your README.md steps to recreate the index).

Well, it seems everything is working if you add the local docset manually after running your README instructions!


RuleSet - Check risky

Please rebase, solve raised issue and :+1:

i let myself fix the testcase

thanks for the help @keradus :)

Thank you @SpacePossum.

Thank you @SpacePossum.


[SPARK-8297] [YARN] Scheduler backend is not notified in case node fails in YARN

This change adds code to notify the scheduler backend when a container dies in YARN.

This is an updated version of #7243, which also works in yarn-client mode.
/cc @mridulm @tgravescs
I ran a bunch of tests on yarn client and cluster modes, but I don't have a test that specifically exercises the bug, so take that with a grain of salt.

Merged build triggered.

Merged build started.

Test build #37412 has started for   PR 7431 at commit 04dc112.

Looks good to me ! If Tom does not come back with objections I am +1 on this.

Test build #37412 has finished for   PR 7431 at commit 04dc112.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class Pmod(left: Expression, right: Expression) extends BinaryArithmetic
      final class SpecificRow extends $

Merged build finished. Test PASSed.

The changes look good.  To manually test this can't you just remove/kill a nodemanager that has an executor on it?  Perhaps there is a race between when yarn tells us and when we recognize?
If you don't have a cluster I can try it out later today.

I can try it out (I'll also add some logging in my internal build to make sure the code is actually being exercised).

So now that I tried the new code path (which works), I'm a little skeptical that sending a message back to the driver is really needed. The driver already removes the executor when the RPC connection is reset:
15/07/16 12:30:15 WARN TaskSetManager: Lost task 3.0 in stage 0.0 (TID 4, vanzin-st1-3.vpc.cloudera.com): ExecutorLostFailure (executor 3 lost)
15/07/16 12:30:15 WARN ReliableDeliverySupervisor: Association with remote system [akka.tcp://sparkExecutor@vanzin-st1-3.vpc.cloudera.com:36279] has failed, address is now gated for [5000] ms. Reason: [Disassociated]
15/07/16 12:30:15 INFO DAGScheduler: Executor lost: 3 (epoch 0)
15/07/16 12:30:15 INFO BlockManagerMasterEndpoint: Trying to remove executor 3 from BlockManagerMaster.
15/07/16 12:30:15 INFO BlockManagerMasterEndpoint: Removing block manager BlockManagerId(3, vanzin-st1-3.vpc.cloudera.com, 37469)
15/07/16 12:30:15 INFO BlockManagerMaster: Removed 3 successfully in removeExecutor

The new message ends up being a no-op:
15/07/16 12:30:18 ERROR YarnClientSchedulerBackend: Asked to remove non-existent executor 3

See CoarseGrainedSchedulerBackend::DriverEndpoint::removeExecutor.
So I'm a little confused about how this change is fixing anything. The bug talks about "repeated re-execution of stages" - isn't that the correct way of handling executor failures? You retry tasks or stages depending on what the failure is.
Perhaps the real issue you ran into is something like #6750 instead?

(BTW to test this, killing the NM is not enough, since that doesn't seem to cause child containers to be killed.)

Yeah it seems like a race condition between the two detection code paths. If they are both guaranteed to be called, then we're always going to end up with ERROR: Asked to kill non-existent executor. Is there a case when the disconnection detection fails?

https://issues.apache.org/jira/browse/SPARK-8297?focusedCommentId=14583560&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14583560
has more information. (timeout's for heartbeat is increased due to gc issues we see in spark)
I'm guessing there might be situations it doesn't recognize the disconnect right away.  Either way I don't think this change hurts anything and it covers any weird cases that might happen.   The error message I assume only happens in a few cases when you hit the exact race.  Otherwise I would expect one side or the other to win. Generally I would expect the spark scheduler recognizing disconnect first and cause it to be removed from our list and not even call it.  I didn't verify that in the code though, @vanzin  do you happen to know if that is true, otherwise I'll check tomorrow.

I'm guessing there might be situations it doesn't recognize the disconnect right away.

That's the only case in which this code might help; but does that really happen? The executor process is already gone (otherwise YARN wouldn't notify the AM). The disconnection message has to go through the akka queues to get to the destination, but so do the messages being sent here.
So with this code, unless the disconnect message can somehow be lost, you'll always end up with that ERROR log, because the two code paths and sort of redundant.

thats not necessarily true.  if a NM goes away for long enough the RM will assume all containers on it are gone too so you would get the notification saying they are gone.  If that executor was somehow in a weird state we would want it removed.

If that executor was somehow in a weird state we would want it removed.

Feels to me like Spark's own heartbeat would take care of that failure mode. The NM being in a bad state does not mean the executor is in a bad state.
I'm just trying to understand why the change is needed. I haven't seen anything that really requires it yet - seems like other safeguards in Spark already take care of the failure modes that have been identified so far. I'm also not against adding it, but perhaps if we do we should demote that log message to be less scary (error is too strong when we expect it to happen).

It doesn't necessarily mean executor is in bad state but it could be in a bad state.  I've seen very weird things happen on machines before so personally I don't think it hurts putting this in and it covers those weird cases that could come up.  I'm fine with changing log message to less scary.

Merged build triggered.

Merged build started.

Test build #37851 has started for   PR 7431 at commit 537da6f.

Test build #37851 has finished for   PR 7431 at commit 537da6f.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Jenkins retest this please.

Merged build triggered.

Merged build started.

Merged build triggered.

Merged build started.

Test build #44 has started for   PR 7431 at commit 537da6f.

Test build #37967 has started for   PR 7431 at commit 537da6f.

Test build #37967 has finished for   PR 7431 at commit 537da6f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test build #44 has finished for   PR 7431 at commit 537da6f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Jenkins retest this please.

Merged build triggered.

Merged build started.

Test build #81 has started for   PR 7431 at commit 537da6f.

Merged build triggered.

Merged build started.

Test build #38233 has started for   PR 7431 at commit 537da6f.

Test build #38233 has finished for   PR 7431 at commit 537da6f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test build #81 has finished for   PR 7431 at commit 537da6f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

the last change was just log level change so this lgtm.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Jenkins retest this please.

Merged build triggered.

Merged build started.

Test build #139 has started for   PR 7431 at commit 3b262e8.

Merged build triggered.

Merged build started.

Test build #38747 has started for   PR 7431 at commit 3b262e8.

Test build #139 has finished for   PR 7431 at commit 3b262e8.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class Abs(child: Expression) extends UnaryExpression with ExpectsInputTypes

Merged build finished. Test FAILed.

Test build #38747 has finished for   PR 7431 at commit 3b262e8.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Jenkins retest this please.

Merged build triggered.

Merged build started.

Test build #38772 has started for   PR 7431 at commit 3b262e8.

Merged build triggered.

Merged build started.

Test build #142 has started for   PR 7431 at commit 3b262e8.

Test build #38772 has finished for   PR 7431 at commit 3b262e8.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test build #142 has finished for   PR 7431 at commit 3b262e8.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
 public static class StructWriter
case class Abs(child: Expression) extends UnaryExpression with ExpectsInputTypes
case class CreateStructUnsafe(children: Seq[Expression]) extends Expression
case class CreateNamedStructUnsafe(children: Seq[Expression]) extends Expression
case class TungstenProject(projectList: Seq[NamedExpression], child: SparkPlan) extends UnaryNode

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38794 has started for   PR 7431 at commit d4adf4e.

Test build #38794 has finished for   PR 7431 at commit d4adf4e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38900 has started for   PR 7431 at commit 471e4a0.

Test build #38900 has finished for   PR 7431 at commit 471e4a0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged to master.


Move CONTRACT doc strings on light client module functions to doc.go

Summary
Move the CONTRACT: ...  godoc strings to the doc.go file for each light client module.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

@damiannolan ,I would like to work on it


feat: Add SSL/TLS support

This makes it possible to use the iRODS storage plugin to connect to iRODS environments that enforce use of SSL/TLS

Thanks! I've included the suggested changes in the commit


Improve confirmation prompt

It should specifically buffer and wait for \n in all cases. Right now it's hit and miss and arbitrary, based on the data event alone.

Thank you for creating this issue!
Please note that – in order for us to be able to handle each feature request with care – we have to consume all of them through a unified pipeline that makes it easier for us to prioritize, track and progress on the features our user base is interested in.
In turn, the Issues tab on this repository is best only be used for reporting bugs, which we can immediately act on.
For well-explained feature requests (like the one you just posted), please contact us at<EMAIL_ADDRESS>so that we can consider adding it to our roadmap.


Mobile - Reporting

Users shall be able to report other posts and users with a note.

Necessary UI adjustments were made and functionality was provided. Now users can report other users, their posts and bunches with a note.


prow test 2

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jmguzik
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

Test name
Commit
Details
Required
Rerun command

pull-prowtest-build
cd4130186fbbd87b0562414cf42ef2cd409b9a11
link
true
/test pull-prowtest-build

Full PR test history. Your PR dashboard.

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

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

Test name
Commit
Details
Required
Rerun command

pull-prowtest-build
cd4130186fbbd87b0562414cf42ef2cd409b9a11
link
true
/test pull-prowtest-build

pull-prowtest-test
cd4130186fbbd87b0562414cf42ef2cd409b9a11
link
true
/test pull-prowtest-test

Full PR test history. Your PR dashboard.

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

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

Test name
Commit
Details
Required
Rerun command

pull-prowtest-build
cd4130186fbbd87b0562414cf42ef2cd409b9a11
link
true
/test pull-prowtest-build

pull-prowtest-test
cd4130186fbbd87b0562414cf42ef2cd409b9a11
link
true
/test pull-prowtest-test

pull-prowtest-test-2
cd4130186fbbd87b0562414cf42ef2cd409b9a11
link
true
/test pull-prowtest-test-2

Full PR test history. Your PR dashboard.

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


Ocean tiles culled at edges of frustum

Describe the bug
Ocean tiles are culled at edge of frustum when they shouldn't be.
Screenshots / video

Versions
4.4 and higher. Not sure if earlier. Looks like all pipelines.
To Reproduce
In the boat.unity, weigh in the global spectrum to increase turbulence which will help with exposes culling issues.
Platform

Editor and Standalone
Windows and Mac

Hardware
i7 and GTX 1080Ti
Additional context
I disabled the culling done in LateUpdateTiles and disabled occlusion culling in camera and on tile renderers just to rule them out, but the issue still appears. It might have something to do with the displacement of the tiles pushing tiles that would be culling into the frustum?

Thanks for reporting
The gerstner waves are supposed to report the amount of horizontal displacement they're generating to the ocean renderer, and then the ocean chunk renderers should then expand the bounds of the tiles to cover all possible vert positions, so they don't cull if they could be on screen.
If the tile GOs are made visible and the draw bounds option is enabled on the ocean chunk renderer, it should draw expanded bounds, and the amount of expansion should depend on amount of chop in gerstner waves. Turning down the gerstner waves should result in the bounds reducing in size.
That's the theory - I tried looking into it and encountered multiple layers of things I don't understand. Maybe these systems have rotted over time and there might be a few bugs. Or I was just seeing dodgy things and need to reimport the project or something.
I ran out of time to look into it for now. If you feel like digging @daleeidd feel free, or I'll pick it up next time.

Will do. I'll just post what I find as I work it out. In the following I disabled the renderer for one tile and enabled it's draw bounds option:

In play mode, if I toggle the problem chunk renderers (disable then enabled), they fix themselves and now scale with the chop correctly.
I found that all bounds have the correct values, but for some reason are not reflected in rendering.
A solution is the not use a shared mesh. In the Start function, if I changed from sharedMesh to mesh, it works fine. This breaks instancing (SPI should still work fine though).
I wonder if this is a bug in Unity because of the first sentence above.
I am going to start exploring DrawMesh and DrawMeshInstanced.

Oh, well found. That could indeed be a unity bug. Yes that sounds like a plan.
So it seems like we're forced to not use shared mesh then for now?

Terrible idea but is toggling renderer.enabled on/off once on startup enough to bring it to life? Just wondering if theres a hacky workaround.

I have looked further into this and I think I have come to the correct conclusion this time round.

So it seems like we're forced to not use shared mesh then for now?

That would be the quickest and simplest way to solve this.
It appears that shared meshes also have shared bounds. The last LOD tiles to assign to the bounds controls the size. It appears that when I toggle the LOD_0 chunk renderers in play mode, all I am doing is changing the ordering and making them the controllers of the shared bounds. I was focused on the smaller LODs so I didn't notice the change in the larger ones. We already noticed this issue in #549.
We could find a way to manage mesh bounds outside of the shared mesh, and only assign to the shared mesh when needed like in PreCull. I am not sure if this would work as it depends how culling is done in relation to the event (after all have executed at once or after each event). I'll have to give this a go.

I am going to start exploring DrawMesh and DrawMeshInstanced. Getting it working for testing if easy enough, but didn't make things any better.

I was mistaken here. I had some other debug code that interfered. If we went with this route, we would be controlling the frustum culling ourselves I believe. It looks like DrawMeshInstanced works one-to-one except I have noticed jitters.

Hmm it's tempting to frustum cull ourselves. We're already doing some types of culling anyway.
It's a bit annoying as if we do this there's almost no point having tile game objects at all. The thing we do get from mesh renderers is the render pass setup including lighting values, reflection probes, etc. I can't see how we could do our own setup for the different pipelines and maintain it over time.
I think we should just move back to mesh from shared mesh. We could optionally post on the unity forum that the bounds should be on the renderer, not the mesh, but maybe there are reasons they have it like this.

Sounds good.


Doesn't work on Windows

I installed gfortran from mingw, added the binary folder to my PATH and tried to compile this project.
error: failed to run custom build command for `lbfgsb-sys v0.1.0 (C:\Imeka\lbfgsb-sys)`
process didn't exit successfully: `C:\Imeka\lbfgsb-sys\target\debug\build\lbfgsb-sys-f76ce81dffa63f64\build-script-build` (exit code: 101)
--- stdout
Running: "mingw32-make" "dylib" "OUTPUT=C:/Imeka/lbfgsb-sys/target/debug/build/lbfgsb-sys-3705fb3a64faf030/out" "OSNAME=Windows"

--- stderr
Makefile:29: *** missing separator.  Stop.
thread 'main' panicked at '`"mingw32-make" "dylib" "OUTPUT=C:/Imeka/lbfgsb-sys/target/debug/build/lbfgsb-sys-3705fb3a64faf030/out" "OSNAME=Windows"` failed: exit code: 2', build.rs:37:13

The problem is that there are 4 spaces instead of one tab at line 29.

Hey, thank you for merging @fmorency branch. Sadly you missed one commit (a fix for WSL). With this, we will be able to use your lib again, and crates.io if you publish your changes.
Btw  @noshu do you plan to work on this lib or at least read the issues and PR? If not, could you please add someone as the maintainer? Three persons have forked this project and contributed: @fmorency, @nilgoyette or @jturner314 (disclaimer: I didn't ask for his opinion).

Hey @nilgoyette thanks for your response. Currently i have no plan to work on this library. I created this repo to use it with my rustimization library. Further more i have another repo which is the rust binding of conjugate gradient descent algorithm. If you want i can make you  and the other two the maintainer of these three repositories.

We (fmorency and I) don't have much plan either, but we do want to answer issues and PR when they arise, so I'll accept the maintainer role. Don't add the others, I'll add them myself if need be.


46 feat add workloadlistener

I am remaking this PR as the previous one becamea mess because of failed rebases.
The WorkloadListener is a struct that spawns a thread. This thread will continuously send workload's status through a Sender, the associated receiver is given to the API and will come in a future PR.

(And you have to rebase your PR)


TypeError: Cannot read property 'stack' of undefined for Action on google node module

I am using Firebase cloud functions as webhook for my action-on-google dialogflow fulfilment.
I am showing only part of My index.js file  as below
process.env.DEBUG = 'actions-on-google:*';

var requestcall = require('request');
var date = require('date-and-time');
var promise = require('promise');
var AmazonDateParser = require('amazon-date-parser');
var moment = require('moment-timezone');

var accountnum;
var accessToken;
var timePeriod;
var acctnums =[];

const OUT_CONTEXT = 'output_context';
const ACCOUNT_ARG = 'info';
const ACCOUNT_NUM = 'myAccountNum';
const AccountNums = 'AccountNums';
const CURRENCY_SYMBOL = 'CurrencySymbol';
const TIME_ZONE = 'TimeZone';
const STATS_ARG = 'nextStatsData';

const {dialogflow} = require('actions-on-google');
const functions = require('firebase-functions');

const {
  SimpleResponse,
  BasicCard,
  Image,
  Suggestions,
  Button
} = require('actions-on-google');

const app = dialogflow(

{debug: true,clientId: 'xxxxxxxxxxx.apps.googleusercontent.com'});

app.intent('Default Welcome Intent', (conv) => {

  console.log('Request headers: ' + JSON.stringify(conv.headers));
  console.log('Request body: ' + JSON.stringify(conv.body));
  accessToken =conv.body.originalDetectIntentRequest.payload.user.accessToken;
   console.log('accessToken: ' + accessToken);

  if (accessToken !== null) {

      return  getaccountDetails(conv).then((entity)=>{
      return getMessageFromAccount(entity,conv);
      });

  }
  else{

     return conv.close(new SignIn('To get your account details'));

  }

  });
exports.stats = functions.https.onRequest(app);

My package.json file is as below
  "description": "Cloud Functions for Firebase",
  "scripts": {
    "serve": "firebase serve --only functions",
    "shell": "firebase experimental:functions:shell",
    "start": "npm run shell",
    "deploy": "firebase deploy --only functions",
    "logs": "firebase functions:log"
  },
  "dependencies": {
    "actions-on-google": "^2.12.0",
    "amazon-date-parser": "^0.1.5",
    "date-and-time": "^0.6.3",
    "dialogflow": "^0.6.0",
    "firebase-admin": "^6.5.1",
    "firebase-functions": "^3.9.0",
    "moment-timezone": "^0.5.31",
    "node-pre-gyp": "^0.15.0",
    "promise": "^8.1.0",
    "request": "^2.88.2"
  },
  "engines": {
    "node": "10"
  },
  "devDependencies": {
    "firebase-functions-test": "^0.2.1"
  },
  "private": true,
  "version": "1.0.0",
  "main": "index.js",
  "author": "",
  "license": "ISC"
}

I am getting the following error while testing my actions-on-google
    at standard.then.catch (/workspace/node_modules/actions-on-google/dist/framework/express.js:37:32)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Error is not in my index.js. The error is in actions-on-google npm modules library at express.js.
I deleted my node modules and installed again and rebuild the code. still same error coming.
Please help me in solving this issue.

Can you provide the full stacktrace? The snippet provided doesn't include an error message. When does this error happen? Before deploying to Firebase?

Hi @Fleker the error occurs for my first call only. When i start Talk to my action..then account linking happening successfully and after that i am getting error saying that your action is not responding. Then i went to firebase to check the logs and i got this error log. That is the full stack trace  is
TypeError: Cannot read property 'stack' of undefined
    at standard.then.catch (/workspace/node_modules/actions-on-google/dist/framework/express.js:37:32)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Previously my action was working fine,recently i changed my firebase function node js version to 10 and again i updated all my node modules to the latest which you can see in pacakge.json.
Its strange for me to, i don't understand where the error is coming, but as per the log it is happening inside actions-on-google node module at express.js.

This line is throwing an error in your code, but haven't determined why.

So what is the solution for this @Fleker. Please guide me as my action is deployed and people will be using it.

I'm investigating this at the moment

I am unable to reproduce the error you're facing even with replicating your Default Welcome Intent. Are there any other logs like the request header/body when this happens, which may be able to help diagnose why this may happen?

Yes @Fleker  i have both request header and body. Please check below for both
Request Header
{"host":"us-central1-click-and-pledge-air.cloudfunctions.net","user-agent":"Google-Dialogflow","transfer-encoding":"chunked","accept":"*/*","accept-encoding":"gzip,deflate,br","content-type":"application/json","forwarded":"for=\"<IP_ADDRESS>\";proto=https","function-execution-id":"q7lw68klo13t","x-appengine-country":"ZZ","x-appengine-default-version-hostname":"l70a2a9e459fc4366-tp.appspot.com","x-appengine-https":"on","x-appengine-request-log-id":"5f3d212500ff0d291d7ae3441e0001737e6c373061326139653435396663343336362d7470000134323231326565613265383762663265346233383062316438303765306431643a313834000100","x-appengine-timeout-ms":"599999","x-appengine-user-ip":"<IP_ADDRESS>","x-cloud-trace-context":"436f4dc10cf95d7835ba35293bee0cf4/771850088506812945;o=1","x-forwarded-for":"<IP_ADDRESS>","x-forwarded-proto":"https","connection":"close"}

Request Body
{"responseId":"2e726734-6621-4799-a2e5-df354e83c05a-d794dba9","queryResult":{"queryText":"GOOGLE_ASSISTANT_WELCOME","action":"input.welcome","parameters":{},"allRequiredParamsPresent":true,"outputContexts":[{"name":"projects/click-and-pledge-air/agent/sessions/ABwppHF8prJHi40mkHEvjyMO0UnXA1kZfAdL8k8YFYeHJYHk-vr-hNlYsyltJszRb5vM6GmT7_sW9UTIfJqkPxGEaBA/contexts/actions_capability_media_response_audio"},{"name":"projects/click-and-pledge-air/agent/sessions/ABwppHF8prJHi40mkHEvjyMO0UnXA1kZfAdL8k8YFYeHJYHk-vr-hNlYsyltJszRb5vM6GmT7_sW9UTIfJqkPxGEaBA/contexts/actions_capability_audio_output"},{"name":"projects/click-and-pledge-air/agent/sessions/ABwppHF8prJHi40mkHEvjyMO0UnXA1kZfAdL8k8YFYeHJYHk-vr-hNlYsyltJszRb5vM6GmT7_sW9UTIfJqkPxGEaBA/contexts/actions_capability_screen_output"},{"name":"projects/click-and-pledge-air/agent/sessions/ABwppHF8prJHi40mkHEvjyMO0UnXA1kZfAdL8k8YFYeHJYHk-vr-hNlYsyltJszRb5vM6GmT7_sW9UTIfJqkPxGEaBA/contexts/actions_capability_account_linking"},{"name":"projects/click-and-pledge-air/agent/sessions/ABwppHF8prJHi40mkHEvjyMO0UnXA1kZfAdL8k8YFYeHJYHk-vr-hNlYsyltJszRb5vM6GmT7_sW9UTIfJqkPxGEaBA/contexts/google_assistant_input_type_voice"},{"name":"projects/click-and-pledge-air/agent/sessions/ABwppHF8prJHi40mkHEvjyMO0UnXA1kZfAdL8k8YFYeHJYHk-vr-hNlYsyltJszRb5vM6GmT7_sW9UTIfJqkPxGEaBA/contexts/google_assistant_welcome"},{"name":"projects/click-and-pledge-air/agent/sessions/ABwppHF8prJHi40mkHEvjyMO0UnXA1kZfAdL8k8YFYeHJYHk-vr-hNlYsyltJszRb5vM6GmT7_sW9UTIfJqkPxGEaBA/contexts/__system_counters__","parameters":{"no-input":0,"no-match":0}}],"intent":{"name":"projects/click-and-pledge-air/agent/intents/5e1ffcfe-48d1-4bf0-84b4-4b7506a0666c","displayName":"Default Welcome Intent"},"intentDetectionConfidence":1,"languageCode":"en"},"originalDetectIntentRequest":{"source":"google","version":"2","payload":{"user":{"accessToken":"eyJhbGciOiJSUzI1NiIsImtpZCI6IjYxMTk2Q0YzRTY5NzQ0QUE4QUUwMzgxNkE5NzRDNUZFMzg1NjBFQTkiLCJ0eXAiOiJKV1QiLCJ4NXQiOiJZUmxzOC1hWFJLcUs0RGdXcVhURl9qaFdEcWsifQ.eyJuYmYiOjE1OTc4Mzk0NDIsImV4cCI6MTU5Nzg0MzA0MiwiaXNzIjoiaHR0cHM6Ly9hYWFzLmNsb3VkLmNsaWNrYW5kcGxlZGdlLmNvbS9pZHNlcnZlci8iLCJhdWQiOiJodHRwczovL2FhYXMuY2xvdWQuY2xpY2thbmRwbGVkZ2UuY29tL2lkc2VydmVyL3Jlc291cmNlcyIsImNsaWVudF9pZCI6Ikdvb2dsZUFzc2lzdGFudCIsInN1YiI6InBhbGxlLnNpdmFzYW5rYXJyZWRkeUBjbGlja2FuZHBsZWRnZS5jb20iLCJhdXRoX3RpbWUiOjE1OTc4Mzk0MzgsImlkcCI6ImxvY2FsIiwic2NvcGUiOlsib3BlbmlkIiwicHJvZmlsZSIsIm9mZmxpbmVfYWNjZXNzIl0sImFtciI6WyJwd2QiXX0.d_sCxPmfGIp-XBkCiepsXaSJL5SCVOok2sHeFETzGPgkQHlaVb2pik3owJTcEBSUYSeTirYfvXrC8cL58duGI39GAz4SbpiyRaym5k2IhJJ6hkOzS2Xmss6PB6AdSEd6MZ8R-HBBrRkSfeaynnJlHVtY41dpb6kt8V-dNLZ2-jj6qshrOiWkVJ7s-jkIebyQAtXl70jEuCd1GU_vjxWU2r2rVgFFOR0uwSU29nzI4T_H1uPEOv6YgcTVeMrol7hAhun8aSYGCwNbba5pKPn4lYlz_PWUdidQFvudkPiO8BSKQD24Z1oEakb4cgjwO9OwTSjVTeFzNgubkuy5fE-m4A","locale":"en-US","userVerificationStatus":"VERIFIED"},"conversation":{"conversationId":"ABwppHF8prJHi40mkHEvjyMO0UnXA1kZfAdL8k8YFYeHJYHk-vr-hNlYsyltJszRb5vM6GmT7_sW9UTIfJqkPxGEaBA","type":"NEW"},"inputs":[{"intent":"actions.intent.MAIN","rawInputs":[{"inputType":"VOICE","query":"Talk to Click & Pledge"}]}],"surface":{"capabilities":[{"name":"actions.capability.MEDIA_RESPONSE_AUDIO"},{"name":"actions.capability.AUDIO_OUTPUT"},{"name":"actions.capability.SCREEN_OUTPUT"},{"name":"actions.capability.ACCOUNT_LINKING"}]},"isInSandbox":true,"availableSurfaces":[{"capabilities":[{"name":"actions.capability.AUDIO_OUTPUT"},{"name":"actions.capability.SCREEN_OUTPUT"},{"name":"actions.capability.WEB_BROWSER"}]}],"requestType":"SIMULATOR"}},"session":"projects/click-and-pledge-air/agent/sessions/ABwppHF8prJHi40mkHEvjyMO0UnXA1kZfAdL8k8YFYeHJYHk-vr-hNlYsyltJszRb5vM6GmT7_sW9UTIfJqkPxGEaBA"}

Hope this will help you solve the issue.

I am not encountering this error when trying this on my own example project.


[Automated] Merge main into stara-krc

Automated Pull Request from 'main' into deployment branch

foul merge...process suspended for now


Optimize Route matching

Matching the request URL to a route is currently done via a looped Regex.
Nikita wrote about how using one Regex to match all routes can speed up Route matching, which is also used in Symfonys Router.
Is this a change that would be of interest to the framework?

btw, we could also switch to using FastRoute, it's a tried and tested package. But it's also fun trying to solve this ourselves :)

I would love to see if I can implement it, might take me 1-2 weeks to find the time.

I think that's fine. The current implementation works for now, and it's all internal code anyway, it shouldn't have an impact on any public API.
So feel free to spend some time on it when you have the chance 👍


[tf.data] Add more precise processing accounting

The execution time of a synchronous captured function is currently approximated by the total elapsed time (including queueing time) rather than only measuring execution time. Time in queue is ~10ns per op or more and may increase under load. Mirroring the asynchronous captured function implementation, this commit pushes the accounting into the executor. Processing time now only measures time spent executing.

@jsimsa

gbaned@ could you please let us know what is this PR blocked on? thanks

@jsimsa there was some error while migrating, now this is resolved ,can you please approve this internally.


chore: add version pre/post npm scripts

Coverage remained the same at 100.0% when pulling bc49b7d0b6669f2df8b0085ac76a4da875a1fd63 on chore/version_scripts into 3f62eb9ca12b4aa46e0b55ff3de0ffe771a93beb on latest.


Clone filtered operation

The filtered operations should be cloned because the first time the parameters are filtered, the original operations are also modified.
Note that this PR also prevent the filtered operation to create an empty array of parameters which does not exist in the original operation.

@frantuma Does this PR miss something in order to be reviewed?

eventually.. thanks!


MNT: Updated some of the pinned versions

Closes https://github.com/conda-forge/suitesparse-feedstock/pull/10
Bumps the OpenBLAS pinning and rebuilds.
cc @grlee77 @jjhelmus

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

LGTM.  ready to merge?

Go for it.


Linux 32 bit

Hi, we're using this component for a cross platform application. In a form we're using it to query some data from internet to display a QR code. It works on Linux 64 but I'm having issues on Linux 32. The QR is never displayed.
Can you confirm wthread works correctly on Linux 32? I'm using Ubuntu 16.04

Apparently what is not triggered is the OnFinish event of the TTask. But I'm not sure if it's just in my project or not.

Tested one of your test project, and OnFinish is executed, so the fault is our code...

Hi!
Please show your code.

Hi, I solved the problem using normal threads, too much time trying to find the problem. But your component works, only our code was not adapted to it and we can't find any other solution than switching to normal threads.

Hi!
I would like to fix the problem if it exists in my code. Or I could help solve it.

Hi ok. Is just on Linux 32 so you need to use a VM or a machine with it.
If I'm right the problem was starting a TTask from OnFinish event.
But again, the demos provided works on Linux 32 so the problem was that I described or something else.

Is this example enough to reproduce the problem?
unit Unit1;
{$mode objfpc}{$H+}
interface
uses
Classes, SysUtils, Forms, Controls, Graphics, Dialogs, wcthread;
type
{ TForm2 }

TForm2 = class(TForm)
    Task1: TTask;
    Task2: TTask;
    WCThread1: TWCThread;
    procedure FormCreate(Sender: TObject);
    procedure Task1Execute(const Sender: TTask; const Msg: Word; var Param: Variant);
    procedure Task1Finish(const Sender: TTask; const Msg: Word; const Param: Variant);
    procedure Task2Execute(const Sender: TTask; const Msg: Word; var Param: Variant);
    procedure Task2Finish(const Sender: TTask; const Msg: Word; const Param: Variant);
private

public

end;

var
Form2: TForm2;
implementation
{$R *.lfm}
{ TForm2 }
procedure TForm2.FormCreate(Sender: TObject);
begin
Task1.Start;
Caption := 'Task1 Started';
end;
procedure TForm2.Task1Execute(const Sender: TTask; const Msg: Word; var Param: Variant);
begin
Sender.WaitMs(1000);
end;
procedure TForm2.Task1Finish(const Sender: TTask; const Msg: Word; const Param: Variant);
begin
Task2.Start;
Caption := 'Task1 Finished, Task2 Started';
end;
procedure TForm2.Task2Execute(const Sender: TTask; const Msg: Word; var Param: Variant);
begin
Sender.WaitMs(1000);
end;
procedure TForm2.Task2Finish(const Sender: TTask; const Msg: Word; const Param: Variant);
begin
Caption := 'Task2 Finished';
end;
end.

That also works.

I'm sorry that  I can't provide a demo that fails
The problem is that it requires a full application that is private and I can't share
Is something that happens with bugs these only appear on certain conditions

Understand. I'm sorry we didn’t solve the problem.