I'm curious. Will rawaccel increase mouse latency?

I mainly use the Rotation function to play electronic sports games. I am curious whether rawaccel will cause delays. Thank you!

i dont think so , it will decrease latencty because using aditional mouse cmd will add more delay but yea u can fix this buy using  xmousecontrol  here u can make the mouse click and release speed to 1ms
wait i will attach the software btw do u play valo ?
https://x-mouse-button-control.en.softonic.com/

i dont think so , it will decrease latencty because using aditional mouse cmd will add more delay but yea u can fix this buy using  xmousecontrol  here u can make the mouse click and release speed to 1ms
wait i will attach the software btw do u play valo ?
https://x-mouse-button-control.en.softonic.com/

Thank you! I'm playing r6s, apex and csgo now. I'm terrible at valorant.😭

So the delay it brings is about the same as the delay of the razer driver?

only way to fix  by playing it in 1000hz but i have doubt whether it will decrease latency or not

So the delay it brings is about the same as the delay of the razer driver?

Pretty sure the Razer driver only communicates to change sensor parameters. I don't think it processes any of the mouse movement. You are also stacking drivers on top of each other. So you would be stacking raw accel and razer drivers on top of each other. Still not noticable latency by the human eye.
If you are worried about latency, I'd be more worried about network latency, computer latency, and monitor latency.
8k polling rate mouse and etc.
I have 0 idea what IDIVASM is talking about though.

So the delay it brings is about the same as the delay of the razer driver?

Pretty sure the Razer driver only communicates to change sensor parameters. I don't think it processes any of the mouse movement. I believe it's windows handling the actual mouse movement. You are also stacking drivers on top of each other. So you would be stacking raw accel and razer drivers on top of each other. Still not noticable latency by the human eye.
If you are worried about latency, I'd be more worried about network latency, computer latency, and monitor latency.
8k polling rate mouse and etc.
I have 0 idea what IDIVASM is talking about though.

Thank you for your serious answer. I was planning to uninstall the Razer driver before.🤣


[Bug] fix yarn session address config loss

Purpose of this pull request
Sloved address lossing problem when edits config

@xxyykkxx  PTAL

the executionMode in cluster mode is (1:remode,3:yarn-session,5:k8s-session), wanna display the address just change

already changed

LGTM


HOCS-5674: Add QA PSU escalation points

Merged in https://github.com/UKHomeOffice/hocs-casework/pull/836


sticky widget location

id like the ability to place lockscreen widgets in any column and row without having them autosort into columns

This isn't really practical with how Lockscreen Widgets is designed.


refactor: parallelize go client script

Background
Currently, the go client script to create multiple cl positions in #4554 is slow.
Suggested Design
We need to parallelize it by issuing multiple messages from go routines and using sequence number
Acceptance Criteria

the script is improved to be parallel

Completed by @mattverse


doc : code of conduct file should add on repo

we need to add code of conduct file in repo

Sample: CODE_OF_CONDUCT

@Yeasir0032 assign this issue to me , and also add gssoc label /tag on issue

@officeneerajsaini
There already an issue exist.
Check here https://github.com/Yeasir0032/Discord-Clone/issues/6

@Yeasir0032  my bad


problems with export

Bug report
I'm unable to build or deploy a simple site using the versions below
Describe the bug
Build step will succeed, deploy will now fail.
I tried to switch to using a static build since serverless build was failing.
static also fails
so back to serverless, now that fails also.
To Reproduce
yarn run build # succeeds
yarn run export  # fails
Expected behavior
should be able to deploy a simple starter website
Screenshots
➜  rap git:(master) ✗ yarn run build
yarn run v1.13.0
(node:66685) ExperimentalWarning: The fs.promises API is experimental
$ next build
Creating an optimized production build ...

Compiled successfully.

 ┌ /
 ├ /_app
 ├ /_document
 ├ /_error
 ├ /about
 ├ /quizItem
 ├ /quizList
 └ /quizTop

✨  Done in 6.90s.
➜  rap git:(master) ✗ yarn run export
yarn run v1.13.0
(node:66717) ExperimentalWarning: The fs.promises API is experimental
$ next export
> using build directory: /Users/dc/dev/rikai/rabbit/rap/.next
  copying "static" directory
  copying "static build" directory
  launching 7 threads with concurrency of 10 per thread
{ Error: Cannot find module '/Users/dc/dev/rikai/rabbit/rap/.next/server/static/gTAnjqmstqLGU51V0PSue/pages/_document'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:571:15)
    at Function.Module._load (internal/modules/cjs/loader.js:497:25)
    at Module.require (internal/modules/cjs/loader.js:626:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at loadComponents (/Users/dc/dev/rikai/rabbit/rap/node_modules/next-server/dist/server/load-components.js:16:24)
    at work (/Users/dc/dev/rikai/rabbit/rap/node_modules/next/dist/export/worker.js:36:38) code: 'MODULE_NOT_FOUND' }
{ code: 'MODULE_NOT_FOUND' }
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

System information

OS: [e.g. macOS, Windows]
osx

Browser (if applies) [e.g. chrome, safari]

Version of Next.js: [e.g. 6.0.2]

➜  rap git:(master) ✗ now -v
14.0.0
➜  rap git:(master) ✗ npx next -v
Next.js v8.0.3
➜  rap git:(master) ✗ npm -v
6.7.0
➜  rap git:(master) ✗ node -v
v10.1.0

➜  rap git:(master) ✗ cat now.json
{
  "version": 2,
  "builds": [
    {
      "src": "package.json",
      "use": "@now/next"
    }
  ]
}%                                                                                ➜  rap git:(master) ✗ cat package.json
{
  "name": "rap",
  "version": "1.0.0",
  "description": "hsk app",
  "main": "index.js",
  "scripts": {
    "dev": "next",
    "build": "next build",
    "now-build": "next build",
    "start": "next start",
    "export": "next export"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "dependencies": {
    "next": "^8.0.3",
    "react": "^16.8.3",
    "react-dom": "^16.8.3"
  }
}
➜  rap git:(master) ✗ cat next.config.js
module.exports = {
  target: 'serverless',
  exportPathMap: function () {
    return {
      '/': { page: '/' }
    }
  }
}

Additional context
on trying to deploy with now
> Error! 1 build failure occured.
> Error! Check your logs at https://rap-qnuv0jhvl.now.sh/_logs or run `now logs rap-qnuv0jhvl.now.sh`.

related
https://github.com/zeit/now-builders/issues/155

@dcsan Try removing target: 'serverless', from next.config.js

oddly the build now seems to "just work"
previously, I had tried:
target: 'serverless',
and also
  "use": "@now/next"
  "use": "@now/static-build"


Add Support for loading large rasters

This issue was imported from CodePlex
mudnug wrote 2012-02-14 at 01:49
Allow loading several layers of large rasters piecemeal.
jartieda wrote 2012-05-16 at 09:00
hi,
I have modified GdalImage.cs so that big images are not loaded in memory for representation.
most of the modifications are on the GetBitmap method.
The work is istill unfinished as it only works now for not rotated rgb images.
However I would like to know your opinion about my approach.
Regards
Jorge
mudnug wrote 2012-05-16 at 21:15
I didn't understand why you use if (_dataset != null) in ReadBlock(...) instead of if (_dataset == null)
We were glad to see this contribution though there are a number of issues (visually and performance-wise), we're excited to see where you can take this!
jartieda wrote 2012-05-18 at 14:38
Hi,
I have some advances. I have added the overviews capabilities and solved some things.
I attach the files so you can see the progress and provideme some feedback
regards
jorge
mudnug wrote 2012-05-19 at 01:46
I notice you added an unsafe block. Is that the preferred way to call GDAL?
BTW, _red.GetOverview(_overview) is null, causing an exception in GetBitmap(...) with your new changes.
I add a constructor to GdalImageProvider so I can open a jpg to get this result.
    public GdalImageProvider()
    {
        GdalHelper.Configure();

        // Add ourself in for these extensions, unless another provider is registered for them.
        string[] extensions = { ".jpg" };
        foreach (string extension in extensions)
        {
            if (!DataManager.DefaultDataManager.PreferredProviders.ContainsKey(extension))
            {
                DataManager.DefaultDataManager.PreferredProviders.Add(extension, this);
            }
        }
    }
jartieda wrote 2012-05-21 at 16:30
Ok, a better version...
removed the unsafe block. I was a try to solve a problem with .net not freeing the big memory blocks. This way to call gdal avoids one memory copy (I think) but doesn't solve the memory segmentation problem. However the overviews solved it.
I had to remove the static identifier in some methods to access the _overview variable. I am not sure about the implications of this.
I have update the ARGB, grey and palleted readers but haven't tested them.
I am not sure why it tries to build pyramids when I load a gray scale .img file. The pyr. building method fails with big images.
The white stripes artifacts are only solved for images which can be read in stripe blocks.
Tiled images must be tested.
please let me know any comment you have or what else must be done to put this on the main branch
Thanks for your previous suggestions.
Regards.
Jorge
mudnug wrote 2012-05-22 at 00:20
I think you have made great advances, here. I'm checking in your contribution with only spelling changes, but I would like to see GetBitmap broken into several smaller methods, and additional features added.
We'll get this in the extension manager quickly so that users can start testing it.
Also, in GetColorPalette(), please dispose the ColorEntry if that is appropriate and dispose red in WriteArgb(...) to prevent memory leaks.
mudnug wrote 2012-05-22 at 00:25
Associated with changeset 67230.
gorchicity wrote 2014-05-28 at 00:03
Hi,I'm a beginner programmer and i have very problem :(I want to add an image to my map program and because its a large tiff file i want to use code that presented in this page. I read it and understated whole of code.So i add this code to my program.
but the big problem for me is that i don't know where i must to download gdal library and then add it to my program. My program returned an error on "Using OSGeo.GDAL".My program wrote by C# language. Please give me a related link for download OSGeo.GDAL
lib.regards,

DotSpatial supports loading\viewing large rasters (tested with 9 GB raster) using GDAL extension.


work with eclipse?

work with eclipse?

Yes, you can import the Sourcecode as a libary

Date: Mon, 17 Aug 2015 04:42:40 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>CC<EMAIL_ADDRESS>Subject: Re: [Fontinator] work with eclipse? (#4)
Yes, you can import the Sourcecode as a libary
—
Reply to this email directly or view it on GitHub
hi i get this when i try import
.

the pic not appears before 4 min
hi i get this when i try import


Rename UndefinedValiableTest to fix class lookup

Could not review pull request. It may be too large, or contain no reviewable changes.

In fact class lookup is not broken as based on class name which is correct.

Could not review pull request. It may be too large, or contain no reviewable changes.

I rebased the PR to handle the merge conflict.

This PR is now superfluous.


Use x86 hosted msvc on arm64 windows

There is currently no arm64 hosted msvc toolchain, but the x86 toolchain can be used.

Thanks! I've got a few quick questions before merging:

Do you know if there's future plans to have a native toolchain? One where perhaps we could test if a native toolchain exist, and fall back to the old x86 ones if it doesn't?
Could you add a comment about why aarch64 is using the x86 toolchain?
Is there a particular reason to avoid the x64 toolchain? Is the x86 one perhaps faster or something like that? (in emulation)

I added a comment. The reason to use x86 is because that is all that is available.
I would prefer not to add the check without there being a native toolchain to test with.

Yeah makes sense for sure, was just wondering if there was already something to test with, but apparently there isn't! In any case looks great in that case, thanks again!


feat: add testnet feedback form

Description
Added a feedback form component for testnet phase user feedback collection.
Changes

Created new FeedbackForm component
Added form validation with required fields
Integrated with existing design system
Added disabled state for submit button until form is valid
Placed form below main app content

Features

Rate experience (1-10)
Reading satisfaction rating (1-10)
Willing to pay amount (in APT)
Mainnet usage intention
Open feedback field

Design

Matches existing app styling
Full-width card layout
Consistent with other components
Responsive design

Testing

[ ] Form validation works as expected
[ ] Submit button state changes correctly
[ ] Toast notification shows on submit
[ ] Form resets after submission
[ ] Responsive on different screen sizes

Screenshots

where is the collected information stored, and how is this presented visually? The form aesthetic is not presentable with current design

where is the collected information stored, and how is this presented visually? The form aesthetic is not presentable with current design

i've updated the feedback form to store all submissions in localStorage with timestamps and IDs, making it easy to track and review feedback. The design has been simplified to match the site's aesthetic while remaining minimal and functional. Users can now view their previous submissions in a collapsible section below the form, and the layout has been improved for better readability and user experience.

There's no backend storage for this and your design completely did not consider storage issue at all. I'll have to reject this issue.

There's no backend storage for this and your design completely did not consider storage issue at all. I'll have to reject this issue.

Can i get further explanation of this, because i worked based on the issue description

how would you expect information to store in localhost while enabling site owner to get the feedback answers? the issue description was to use a service such as google form or typeform so to not have to store any data in backend. while only adding a small entry point like a icon on the website that does not obstruct current features and design.


Fix: remove development require

Small fix:
As this is a development dependency, the require should be removed from non development-specific files. Otherwise when running an app with this gem it will crash since the dependency is not being required.

Oh, Great bro! sorry for that mistake! 😢

We will miss u in this project @TimoPeraza 😢
Credits for @antoalconti who was the one who spotted the bug 👏

Great @antoalconti , you are a genius 😄


Original Form

Our team discuss about we should do the project from official original form of Plymouth court or keep going from the old one.
Request for Interpreter Services.pdf

See Trello card

Per @nonprofittechy on Trello - this is a form that GBLS started using to flag the need for an interpreter at the beginning of eviction cases. It's not a request for an interpreter at a specific event; just a form that is kept in the file and draws the clerk's attention.


words: know when to hold and when to fold

All In!

Sorry @tomholford - forgot this was open!

Sorry @tomholford - forgot this was open!

No worries m8


MassInstallAction: Install the TagBot workflow on this repository

This pull request sets up the TagBot workflow on this repository.

Codecov Report

Merging #6 (09cd340) into master (7f6321d) will increase coverage by 2.73%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master        #6      +/-   ##
===========================================
+ Coverage   97.26%   100.00%   +2.73%
===========================================
  Files           4         3       -1
  Lines         146       141       -5
===========================================
- Hits          142       141       -1
+ Misses          4         0       -4

Impacted Files
Coverage Δ

src/FoldingTrees.jl

src/foldingtree.jl
100.00% <0.00%> (+6.25%)
:arrow_up:

Continue to review full report at Codecov.

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


ATT: send a Read By Group Type Response in the case of BLE_HS_EMSGSIZE

Read By Group Type Response messages can raise BLE_HS_EMSGSIZE when the
response is large and the MTU is small. In this case the message built
by ble_att_svr_build_read_group_type_rsp() is valid and complete
(despite the error-looking return value), and should be sent to the
remote party.

This bug can be easily triggered by creating four primary services with 16-bit UUIDs. Connect to the BLE peripheral using a tool with an MTU of 23, 24, or 25, and issue a Primary services request (by issuing a Read By Group Type Request for UUID 2800).
Linux's gatttool in its default configuration will trigger this bug when issuing the "primary" command. The symptoms are that the request times out, and when inspecting Bluetooth packet logs the Read By Group Type Request is sent but no Read By Group Type Response is returned.
This bug appears to affect devel as well.

The code should read rc != BLE_HS_EMSGSIZE. I will update the pull request in a few hours.

Hi Mike,
In case you didn't see it, I responded to your email on the dev list<EMAIL_ADDRESS>Please let me know if you think this is still an issue.  Also, if you agree that the bug is fixed, could you please close this pull request?
Thanks,
Chris


content/blog/2022-11-07: Reverse hybrid blog post

Review as usual - this is a first draft so far but good to go as
soon as it is reviewed.
Contributions, please add yourself to authors

This is a great text. You could maybe add 1-2 sentences that our experience with this is so far mixed. It can work really well and we have at least 2 examples of this being successful, but also the feedback that we got from NL is that this didn't really work because interaction online was larger than interaction in-person.

but also the feedback that we got from NL is that this didn't really work because interaction online was larger than interaction in-person.

Which when you think about it is actually sort of amazing!  But for a different reason, it shows that we've made our course so good, it's obsoleted the idea of going and sitting in a classroom just for the sake of being in a course.  If you have friends or some better teams, then maybe it works better.

See latest addition.  Good to go after adding links to the previously-published posts.

Do you have a suggestion for a tweet text?

Suggestion: merge them in order, I at least these first ones.  some of the later will have links to the earlier ones once they are merged.

(but don't change anything now - it's ok, I should have specified)

Suggestion: merge them in order, I at least these first ones. some of the later will have links to the earlier ones once they are merged.

That's what I tried but I probably misunderstood the PR titles. It will help me if also others can help merging and if we have maybe a clear sequence in the PR titles.


Re-Render takes some time

I tried this and seems it fixed some of the FlatList issues but I noticed when I scroll back (top or bottom) (specially when I'm using images) it takes some time to re-render and display the blocks.
So it would be good if it has an offeset to pre-load some items before displaying in viewport in order to prevent the blank space between blocks  which doen't look good.
Any idea?

I noted the same issue on iOS. Interestingly, the React FlatList component wasn't having any performance issues on iOS but was extremely slow on Android. I created a new PlatformFlatList component that serves OptimizedFlatList on Android and it worked great - including on relatively underpowered Android devices that were really struggling.
https://gist.github.com/thame/a7e5c61e7bb3a6d56406db37da090a76

@thame, feel free to create a PR. I think that this solution also should be implemented.

@stoffern Would love to, complete git/React noob so no idea how :)
But, this is an awesome component, thank you!

@xempie is this issue only related to ios or android to?

@stoffern Sorry for the delay, I'm subscribed now. The performance issue I was having was mostly on Android (which is why I preferred the basic FlatList on iOS).

Quick and patchy fix for this you could guys try is to never hide the first items. Make sure to add enough to fill the screen but not much more.
So in our case maximum items is 3, so we will never hide the first 3 items to avoid this 2-3 seconds white screen when scrolling to top.
So the _updateItem function on OptimizedFlatList.js would look like this:
_updateItem(index, visibility) {     if (index != 0 && index != 1 && index != 2) {       if (!this.rowRefs[index].ref) {         return false;       }       this.rowRefs[index].ref.setVisibility(visibility);       return visibility;     }   }

This is still happening. Not fixed yet.

Quick and patchy fix for this is to never hide the first items. Make sure to add enough to fill the screen but not much more.
So in our case maximum items is 3, so we will never hide the first 3 items to avoid this 2-3 seconds white screen when scrolling to top.
So the _updateItem() function on OptimizedFlatList.js would look like this:
if (index != 0 && index != 1 && index != 2) {
  if (!this.rowRefs[index].ref) {
    return false;
  }
  this.rowRefs[index].ref.setVisibility(visibility);
  return visibility;
}

So basically: just wrapping the function content within an IF stating which items not to hide.

Thanks...! This solved another issue of not showing the 1st item when data resets (Refresh func).


Fix Uncaught Command Promise Error

This fixes an issue where the command promise gets rejected before V8 reaches the await - resulting in an Uncaught Promise Error.
Illustrating the issue with an absurd example:
async run(msg) {
    throw new Error('Promise rejected before reaching await.');
}

I cannot reproduce your issue - and it's not even possible at all, based on my understanding of how async/await works with the event loop.

It's certainly possible as long as the Promise gets rejected before the interpreter gets to the await keyword and waits for the Promise to resolve or reject - which can happen in Commando depending on how long the event emitter takes to process the event emitting.
I made this command:
module.exports = class PRRejCommand extends Command {
    constructor(client) {
        super(client, {
            name: 'prrej',
            aliases: [ ],
            group: 'fun',
            memberName: 'prrej',
            description: 'PR rej',
            guildOnly: false,
            throttling: {
                usages: 2,
                duration: 3
            }
        });
    }

    async run() {
        throw new Error('This was thrown and possibly not handled by the try-catch block.');
    }
};

and trying to run this gets me logged the following:
error: 2017/07/16, 20:50:41.768@ [DISCORD]: Error in command fun:prrej Error: This was thrown and possibly not handled by the try-catch block.
    at PRRejCommand.run (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\commands\fun\prrej.js:29:15)
    at CommandMessage.run (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\node_modules\discord.js-commando\src\comman
ds\message.js:174:33)
    at CommandDispatcher.handleMessage (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\node_modules\discord.js-comman
do\src\dispatcher.js:127:32)
    at NekoClient.CommandoClient.on.message (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\node_modules\discord.js-c
ommando\src\client.js:68:51)
    at emitOne (events.js:120:20)
    at NekoClient.emit (events.js:210:7)
    at MessageCreateHandler.handle (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\node_modules\discord.js\src\client
\websocket\packets\handlers\MessageCreate.js:9:34)
    at WebSocketPacketManager.handle (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\node_modules\discord.js\src\clie
nt\websocket\packets\WebSocketPacketManager.js:102:65)
    at WebSocketConnection.onPacket (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\node_modules\discord.js\src\clien
t\websocket\WebSocketConnection.js:330:35)
    at WebSocketConnection.onMessage (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\node_modules\discord.js\src\clie
nt\websocket\WebSocketConnection.js:293:17)
    at WebSocketClient.internalOnMessage (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\node_modules\uws\uws.js:103:
17)
    at native.client.group.onMessage (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\node_modules\uws\uws.js:57:15)
error: 2017/07/16, 20:50:41.773@ Uncaught Promise Error: Error: This was thrown and possibly not handled by the try-catch block.
    at PRRejCommand.run (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\commands\fun\prrej.js:29:15)
    at CommandMessage.run (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\node_modules\discord.js-commando\src\comman
ds\message.js:174:33)
    at CommandDispatcher.handleMessage (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\node_modules\discord.js-comman
do\src\dispatcher.js:127:32)
    at NekoClient.CommandoClient.on.message (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\node_modules\discord.js-c
ommando\src\client.js:68:51)
    at emitOne (events.js:120:20)
    at NekoClient.emit (events.js:210:7)
    at MessageCreateHandler.handle (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\node_modules\discord.js\src\client
\websocket\packets\handlers\MessageCreate.js:9:34)
    at WebSocketPacketManager.handle (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\node_modules\discord.js\src\clie
nt\websocket\packets\WebSocketPacketManager.js:102:65)
    at WebSocketConnection.onPacket (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\node_modules\discord.js\src\clien
t\websocket\WebSocketConnection.js:330:35)
    at WebSocketConnection.onMessage (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\node_modules\discord.js\src\clie
nt\websocket\WebSocketConnection.js:293:17)
    at WebSocketClient.internalOnMessage (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\node_modules\uws\uws.js:103:
17)
    at native.client.group.onMessage (Z:\Eigene Dokumente\Discord Bots\Charuru Commando\node_modules\uws\uws.js:57:15)

The first one from
client.on('commandError', (cmd, err) => {
        if(err instanceof FriendlyError) {
            return;
        }

        client.writeLog('error', `[DISCORD]: Error in command ${cmd.groupID}:${cmd.memberName}`, err);
    })

and the second from
process.on('unhandledRejection', (error) => {
    client.writeLog('error', 'Uncaught Promise Error:', error);
});

If I now add
.catch(err => {
    throw err;
})

to the command promise, I don't get an Uncaught Promise Error anymore.


StatusDurationName

---
---
init

Pipelines as Code CI/mvp-test-component-on-pull-request has failed.

StatusDurationName

✅ Succeeded
9 seconds
init

Pipelines as Code CI/mvp-test-component-on-pull-request has failed.

StatusDurationName

✅ Succeeded
9 seconds
init

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
9 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
2 minutes
build-container

✅ Succeeded
1 minute
sanity-inspect-image

✅ Succeeded
1 minute
deprecated-base-image-check

✅ Succeeded
3 minutes
clamav-scan

✅ Succeeded
4 minutes
clair-scan

✅ Succeeded
1 minute
sbom-json-check

✅ Succeeded
23 seconds
sanity-label-check

✅ Succeeded
22 seconds
sanity-optional-label-check

✅ Succeeded
7 seconds
show-summary

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
9 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
2 minutes
build-container

✅ Succeeded
1 minute
sanity-inspect-image

✅ Succeeded
1 minute
deprecated-base-image-check

✅ Succeeded
4 minutes
clair-scan

✅ Succeeded
3 minutes
clamav-scan

✅ Succeeded
1 minute
sbom-json-check

✅ Succeeded
22 seconds
sanity-optional-label-check

✅ Succeeded
23 seconds
sanity-label-check

✅ Succeeded
7 seconds
show-summary


upgrade pip dependencies and checkout action

Hi @MousaZeidBaker,
I just received a notification about the latest release of this project. I was surprised to notice that apparently some of the dependencies are outdated. So I used the plugin to upgrade it's dependencies.
I also thought about adding a Dependabot config file. But apparently there's no option yet to exclude the tests/ directory. So Dependabot would likely try overwrite the test data regularly by opening pull requests.
Maybe executing the plugin in CI workflow and using Dependabot only for the GitHub Actions might be a feasable alternative.
name: Upgrade pip dependencies

on:
  schedule:
   # every Monday at 05:05AM
   - cron: "5 5 * * 1"

jobs:
  upgrade:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout repository
        uses: actions/checkout@v3
        with:
          fetch-depth: 0

      - name: Setup Python 3.11
        uses: actions/setup-python@v4
        with:
          python-version: "3.11"

      - name: Install poetry
        uses: snok/install-poetry@v1
        with:
          version: 1.6.0

      - name: Install dependencies
        run: poetry install

      - name: Build
        run: poetry build

      - name: Upgrade dependencies
        run: poetry up

      # ... open a pull request if changes have been detected ...

Hope this PR might be helpful to you. I'd be very grateful if you could share your feedback below.
Regards,
Adrian

Hi @AdrianDsg,
Thanks for your contribution. I've previously thought about using the plugin itself in CI workflow but never had the time to actually implement it. I'd be very grateful if you like to take care of it. Cheers.


Use response-Headers in the different IPDFStream implementations

Given that the Headers functionality is now available in all browsers/environments that we support, see MDN, we can utilize "proper" Headers in the helper functions that are used to parse the response.

/botio test

/botio test

Thanks!


VitaApps Category, renaming games, and multiple themes (ENHANCEMENT)

I feel like there should be a category for the native built-in vita apps (Such as the trophy, video, music, and message app).
I often use the video and music app on my vita to either watch anime or to listen to music (I have a plugin that allows me to play music in the background of games and such).
As for the renaming games suggestion, OneMENU has the option to rename the games which is handy for the several games I have that are Japanese with English patches (PuyoPuyo Teris, Steins;Gate Elite, Taiko no Tatsujin V edition, etc.) or certain games with minor grammatical errors in their title ID (Cough cough, the missing space in Danganronpa 2, cough cough) which could cause games to appear outside of alphabetical order. I also noticed that after renaming the games via OneMenu, they still appear to have their original names listed as though I didn't change them.
Also had an idea for the use of multiple "themes", or to put it more simply, a folder for different background images and a folder for different background music that you can switch between in the options menu. (Perhaps even an option to set a custom background dependant on which menu you are in, so you can have a different background for SNES or NES Games.)
Also, one more thing of note I wanted to mention, I wanted to have an MP3 playing in the background, but every time I try I get an error message saying that it's an unsupported format. As far as I know .MP3 is the format it needs to be in, but it doesn't seem to work for me, perhaps it needs to be a specific bitrate or something, I don't know.

Addendum
Also, the option to change the text colors would be nice, I have a custom background and the white text labeling which system I'm looking at just so happens to be over a white part of my background, causing it to blend in.

Closing issue prior to archiving


[MM-18074] Format of Position in User Profile is incorrect

Summary
The format of the position string of text looks slightly off from the design. I'm not sure if this is the best fix, but to me, but increasing the size by a pixel (15px) looks a bit better:

Ticket Link
https://mattermost.atlassian.net/browse/MM-18074

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-3785.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

@bradjcoughlin I'll deter to @michaelgamble on the exact pixels, but it looks to have more vertical white space above the position string then below -  I'd expect it to be the same or a bit closer to the top than bottom

New commit detected. SpinWick will upgrade if the updated docker image is available.

Mattermost test server updated with git commit 032e63148d8cf7e89e6f50196a69c0c370ec631f.
Access here: https://mattermost-webapp-pr-3785.test.mattermost.cloud

@michaelgamble I've reduced the font size back down to 14px, and changed the padding/margin so that the white space appears equidistant.

Mattermost test server updated with git commit 7cffc8d7ebcb8797c37fcc551cbffc6e2fd54d1d.
Access here: https://mattermost-webapp-pr-3785.test.mattermost.cloud

New commit detected. SpinWick will upgrade if the updated docker image is available.

Mattermost test server updated with git commit ca86beb98730147052784681c013fa76489a8102.
Access here: https://mattermost-webapp-pr-3785.test.mattermost.cloud

@michaelgamble Implemented changes discussed offline. I'll file a new ticket to add the "role" icon.

Not sure if this had official QA review, but I took a look and this LGTM.

Test server destroyed


[DUOS-2969] Reorder columns and add newline

Addresses
https://broadworkbench.atlassian.net/browse/DUOS-2969
Summary
Reorder columns and add newline:

Have you read Terra's Contributing Guide lately? If not, do that first.

Label PR with a Jira ticket number and include a link to the ticket
Label PR with a security risk modifier [no, low, medium, high]
PR describes scope of changes
Get a minimum of one thumbs worth of review, preferably two if enough team members are available
Get PO sign-off for all non-trivial UI or workflow changes
Verify all tests go green
Test this change deployed correctly and works on dev environment after deployment

Love the simplicity and clarity this adds, great value in short turnaround. Thanks!


Explorer: Add content on page with editable zesty links

Overlay the the dom with highlights that let you edit, have ID reference to scroll to field in zesty manager


import * as APITypes from "types" in 12.5.0 breaks the build

How did you install the Amplify CLI?
yarn
If applicable, what version of Node.js are you using?
v18.17.1
Amplify CLI Version
12.5.0
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
I have pretty advanced configuration where I'm sharing amplify generated graphql resources with Lambda functions, so I can easily use types and methods inside those functions.
The build for Lambda is also customized
Describe the bug
The builds in 12.4.0 was working fine and 12.5.0 introduce breaking changes with
/* tslint:disable */
/* eslint-disable */
// this is an auto generated file. This will be overwritten

import * as APITypes from "types";
type GeneratedQuery<InputType, OutputType> = string & {
  __generatedQueryInput: InputType;
  __generatedQueryOutput: OutputType;
};

That import is not working in Node
Cannot find module 'types' or its corresponding type declarations.ts(2307)
Expected behavior
More standardized imports
Reproduction steps
amplify codegen
yarn amplify:createTrade
yarn run v1.22.19
$ npx projen amplify:createTrade
👾 amplify:createTrade | cd amplify/backend/function/createTrade && rm -rf lib/{amplify,projects} && rm -rf dist && yarn install && tsc -p ./tsconfig.json && tsc-alias -p ./tsconfig.json && cd -
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
success Already up-to-date.
src/generated/mutations.ts:5:27 - error TS2307: Cannot find module 'types' or its corresponding type declarations.

5 import * as APITypes from "types";
                            ~~~~~~~

src/generated/queries.ts:5:27 - error TS2307: Cannot find module 'types' or its corresponding type declarations.

5 import * as APITypes from "types";
                            ~~~~~~~

src/generated/subscriptions.ts:5:27 - error TS2307: Cannot find module 'types' or its corresponding type declarations.

5 import * as APITypes from "types";
                            ~~~~~~~

Found 3 errors in 3 files.

Errors  Files
     1  src/generated/mutations.ts:5
     1  src/generated/queries.ts:5
     1  src/generated/subscriptions.ts:5

Perhaps there is tsconfig option that can enable imports like that? Or perhaps this is a real bug.
Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

+1

I'm running into the same issue since the upgrade. The temporary workaround I found is to simply update the generated queries.ts and mutations.ts to fix the import path.
- import * as APITypes from "API";
+ import * as APITypes from "./API";

I am not sure if this is correct,
As a temporary fix I was able to get it to work by

Downgrade the version of the local environment

npm install -g<EMAIL_ADDRESS>

Temporarily change the settings in amplify.yml.
I was able to get it to work by specifying 12.4.0 as the version when it is automatically built by CI/CD.

backend: ```` backend
  phases:: build
    build: phases: build
      commands: npm install -g @
        - npm install -g<EMAIL_ADDRESS>        - amplifyPush --simple

Ok, I was able to reproduce with that path. That is unexpected, a custom path like should work. If you change the path to src/API.ts that will workaround the issue.


Howdy Jack

I've made a relatively minor, reverse-compatible tweak to how the addHandler() function works. Rather than having to pass positional arguments for 'ns', 'name', 'type', etc. You can now pass just two arguments. The handler function and a simple object literal that defines the other values you wish to filter by.
For example, rather than this:
this.connection.addHandler(
    this.handleMucMessage.bind(this),
    null, "message",
    "groupchat",
    null,
    room,
    {matchBare: true}
);

You can now do this:
this.connection.addHandler(this.handleMucMessage.bind(this), {
    name: 'message',
    type: 'groupchat',
    from<EMAIL_ADDRESS>    matchBare: true
});

For me, this solves the problem of having to check the docs each time to see which order to pass in the refining arguments. Also, this approach opens up the possibility of really expanding the matching capabilities of that addHandler() function. Potentially, it could be expanded to support more fine-grained matching of a stanza's children, etc.
Not sure if you're interested in messing with this API. But the way I wrote it, it maintains backward compatibility. So all existing code should still work, unmodified.
Anyways, just figured I'd do a pull request in case you liked my change.
Thanks for Strophe and your Pro XMPP book! Cheers @HenrikJoreteg

Thumbs up for all three ideas, simplifying how to pass arguments to addHandler, adding two different methods for permanent and one time handlers and built-in xpath.


Human Curation of content

Because crappy one-liner snarks that got bumped SHOULDN'T be included in the video.
And post-generation video snipping or editing is very inconvenient. Either:

Each post are a separate video where you can stitch them together with ffmpeg
There is a vetting function that allows you to pick posts before the video is generated

something like https://youtu.be/i2xSvOiHwiI?t=105 ?

The text selection should be manual, but the rendering should be on auto-pilot as much as possible.

while the text would be higher quality, I am not the kind to want to invest any time doing the selection

It should be an option, but not necessary if one wants to go easy like you said.


feat: info page

Pull Request

Description

Added information page with contributors, links, and roadmap items
Added contributors, loaded automatically via GitHub REST API
Added roadmap items, loaded semi-automatically via GitHub REST API
[ ] TODO?: save info to save file for access when rate limited?

Related Issue

Closes #189

Checklist

[x] I have added commit messages that are descriptive and meaningful.
[x] I have tested the changes locally.
[x] I have reviewed the code changes.

Screenshots

idk what to add for the GDPR/Cookie policy compliance

I somewhat feel like we should just hardcode the contributor list & roadmap - These things don't update often enough to really necessitate a live api call

yeah roadmap is probably fine for hardcoding.
For the contributors it only costs 1 point to fetch them all anyways so you would basically never hit the rate limit (60 points / hour)
also:

Dynamically pull the contributor icons/urls from github and display a list of them.
:ragey: but hardcoding is probably fine as well as long as we remember to update every so often

closing this now that you added the home page


Comment vanishes during parse when next line has leading semicolon

TypeScript Version:  4.0.0-dev.20200715

Search Terms: comment semicolon
Code
import * as ts from 'typescript'
// This comment is not lost
import * as fs from 'fs'
// THIS COMMENT IS LOST
// (but not if you remove the semicolon at the start of the next line, or add one on the line above)
;fs.readFile(__filename, 'ascii', (err, text) => {
	// This comment is not lost
	if (err) throw err
	const sourceFile = ts.createSourceFile(__filename, text, ts.ScriptTarget.ES2015, true, ts.ScriptKind.TS)
	console.log(ts.createPrinter().printNode(ts.EmitHint.Unspecified, sourceFile, sourceFile))
})

(There’s no good reason for the leading semicolon in this demo; the original had an IIFE there which therefore had a leading semicolon to prevent it from being interpreted as a call to the previous expresssion.)
Expected behavior:
Program should be pretty-printed with all comments:
import * as ts from 'typescript';
// This comment is not lost
import * as fs from 'fs';
// THIS COMMENT IS LOST
// (but not if you remove the semicolon at the start of the next line, or add one on the line above)
fs.readFile(__filename, 'ascii', (err, text) => {
    // This comment is not lost
    if (err)
        throw err;
    const sourceFile = ts.createSourceFile(__filename, text, ts.ScriptTarget.ES2015, true, ts.ScriptKind.TS);
    console.log(ts.createPrinter().printNode(ts.EmitHint.Unspecified, sourceFile, sourceFile));
});

Actual behavior: Comment below import statements disappears when pretty-printed.
Related Issues: #17665 describes a vaguely similar bug where a comment was getting swallowed into a previous statement due to ASI.

Comment preservation is "best effort" and you may lose comments during emit if they end up being attached to a token rather than a node. Do not rely on comments do be reprinted in every possible syntactic position; this is not an invariant of TS's emit process.

Good to know. Can you point me to where I’d find out what positions in the AST are acceptable for a comment to be emitted?
In particular, will the output of printNode always contain comments only in positions where they will be preserved if the result is reparsed and emitted again? (i.e., is a createSourceFile() → printNode() cycle idempotent?)

There are no guarantees per se, but you can be reasonably confident that any comments directly preceding a declaration will be preserved, since this is a big use case for .d.ts generation.

In particular, will the output of printNode always contain comments only in positions where they will be preserved if the result is reparsed and emitted again? (i.e., is a createSourceFile() → printNode() cycle idempotent?)

Honestly, I don't know. Probably?

I don't know. Probably?

LOL, fair. I guess that's good enough for the experiment I'm doing, though it sounds like I probably shouldn't rely on it for production. Thanks for the info!


removed pages names in all list pages

#105

Coverage remained the same at 64.937% when pulling bfd0a14fd3b544980ee4d73eb8672cf1824be32b on removing_page_names into e64296c4148a05ee201077ff2932bdb3f4d90c19 on master.


Initial actions workflow

Description
Uses Github actions to run unit tests for supported node versions.
Fixes #NUI-921
Types of changes

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

Checklist:

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

@jdelbick This PR wasn't ready for review... Hence there was no request for review yet...

Now it's ready for review!

also seeing some worker-pie errors in dep mod tests


[Feature Request] tf.keras expose align_corners

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
N/A
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
N/A
TensorFlow installed from (source or binary):
N/A
TensorFlow version (use command below):
N/A
Python version:
N/A
Bazel version (if compiling from source):
N/A
GCC/Compiler version (if compiling from source):
N/A
CUDA/cuDNN version:
N/A
GPU model and memory:
N/A
Exact command to reproduce:
N/A

Describe the problem
We need to expose align_corners in this Keras upsample
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/keras/layers/convolutional.py#L1935
See also https://github.com/keras-team/keras/pull/10994#issuecomment-430305648

I can take a look at this, in the meantime you could always use a Lambda layer:
Lambda(
  lambda x: tf.image.resize_bilinear(x, (H, W), align_corners=True), output_shape=(H, W, C))(data))

/cc @Shathe

@omalleyt12 Do you want to pass trough upstream keras or directly in tf.keras?

@ewilderj A classical opensource upstream downstream issue.
We are at risk that users and devs start to duplicate bugs against tf.keras interfaces and on the upstream Keras github repo.

@ewilderj I've saw this behavior but I've not annotated the tickets.
Also in theory general keras API could not be modified troughs direct PR against tf.keras right?
So I suppose that it is at high risk to become a chicken or eggs problem especially for FR where newcomers start to be exposed to tf.keras directly instead of coming from a Keras experience and I supposed this hypothesis it is not some much remote with the landing of TF 2.0 right?.

In the meantime probably could you create a specific tf.keras template?

@dksb do you think a separate keras template makes sense to simplify triage?

@bhack It is definitely possible to modify Keras via PR to tf.keras. We may ask for a mirror PR to keras-team/keras, but we are doing regular syncs, and contributions can move both ways.

@martinwicke Probably this topic needs to be better investigated cause we could have a tf.keras api with only 1 backend that break compatibility with Keras API with its own tensorflow backend. More and more users will be exposed to Keras trough tf.keras directly.

Nagging Assignee @omalleyt12: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @omalleyt12: It has been 31 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

@martinwicke @ewilderj This is just another bidirectional case example: https://github.com/tensorflow/tensorflow/issues/24009 VS https://github.com/keras-team/keras/pull/9898#issuecomment-380590161.
Could  we have divergent opinions?


ElasticSearch 5 Support

I was wondering if you are planning to add support for ElasticSearch 5. The Unit Tests don't seem to throw any errors when i upgrade the dependencies locally.
Dependencies
ongr/elasticsearch-dsl          v2.2.0
elasticsearch/elasticsearch     v5.1.0

Tests
PHPUnit 4.8.32 by Sebastian Bergmann and contributors.

Runtime:        PHP 7.0.12
Configuration:  C:\Users\Nevoxx\Desktop\plastic\phpunit.xml
Warning:        The Xdebug extension is not loaded
                No code coverage will be generated.

...............................................................  63 / 141 ( 44%)
............................................................... 126 / 141 ( 89%)
...............

Time: 804 ms, Memory: 16.00MB

OK (141 tests, 246 assertions)

yes you can submit a PR on the develop branch apparently things are working fine with ES5 ...


Service - ELK Helm Chart - create/use upstream

This can be closed once https://github.com/opendistro-for-elasticsearch/opendistro-build/issues/294 is implemented.

The original intention for this ticket was for use by clients, we'll still need to solve that for clients to deploy ES

We also need this before we can move one of our customers to lagoon.

We also need this before we can move some of our sites to Lagoon.

Specifically, for Elasticsearch in customer projects, the cluster-wide ES provided via a different chart.

This will be required for a large customer in APAC to move to native kubernetes on Lagoon 2. Flagging as a blocker on that.


[PDI-4048] Text file input cannot properly handle a fixed-length-of-b…

…ytes file. Reworked #2731

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -Dtestreports.dir=bin/reports/integration-test -f engine/build.xml jacoco-integration checkstyle publish-local
ant -Dtestreports.dir=bin/reports/unit-test -f ui/build.xml clean-all resolve jacoco && ant -Dtestreports.dir=bin/reports/integration-test -f ui/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/trans/steps/fileinput/text/TextFileInputMeta.java
  engine/src/org/pentaho/di/trans/steps/fileinput/text/TextFileInputUtils.java
  engine/src/org/pentaho/di/trans/steps/fileinput/text/messages/messages_en_US.properties
  engine/test-src/org/pentaho/di/trans/steps/fileinput/text/TextFileInputContentParsingTest.java
  engine/test-src/org/pentaho/di/trans/steps/fileinput/text/TextFileInputMetaLoadSaveTest.java
  engine/test-src/org/pentaho/di/trans/steps/fileinput/text/TextFileInputMetaNewInjectionTest.java
  engine/test-src/org/pentaho/di/trans/steps/fileinput/text/files/test-fixed-length-bytes.txt
  engine/test-src/org/pentaho/di/trans/steps/fileinput/text/files/test-fixed-length-characters.txt
  ui/src/org/pentaho/di/ui/trans/steps/fileinput/text/TextFileInputDialog.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.auth.core.impl.DefaultAuthenticationConsumerFactory

Branch Change: -7.14%:small_red_triangle_down:
Complexity Change: -7.69%:small_red_triangle_down:

org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change:  + .39%
Complexity Change:  + .51%
Instruction Change:  + .08%

org.pentaho.di.job.entries.evaluatetablecontent.JobEntryEvalTableContent

Branch Change: -1.01%:small_red_triangle_down:
Complexity Change: -1.06%:small_red_triangle_down:
Instruction Change: -.17%:small_red_triangle_down:

org.pentaho.di.job.entries.sql.JobEntrySQL

Instruction Change: -3.28%:small_red_triangle_down:
Line Change: -3.87%:small_red_triangle_down:

org.pentaho.di.trans.steps.calculator.CalculatorMetaFunction

Branch Change:  + 8.70%
Complexity Change:  + 3.08%
Instruction Change:  + .75%
Line Change:  + .89%

org.pentaho.di.trans.steps.constant.ConstantMeta

Instruction Change: -.10%:small_red_triangle_down:

org.pentaho.di.trans.steps.csvinput.CsvInputMeta

Instruction Change:  + .05%

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change: -.11%:small_red_triangle_down:

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Branch Change: -.63%:small_red_triangle_down:
Complexity Change: -.40%:small_red_triangle_down:
Instruction Change: -.49%:small_red_triangle_down:
Line Change: -.23%:small_red_triangle_down:

org.pentaho.di.trans.steps.excelwriter.ExcelWriterStepMeta

Branch Change: -1.28%:small_red_triangle_down:
Complexity Change: -.78%:small_red_triangle_down:
Instruction Change: -.08%:small_red_triangle_down:

org.pentaho.di.trans.steps.fileinput.text.EncodingType

Branch Change:  + 3.03%
Complexity Change:  + 3.45%
Instruction Change:  + 1.46%
Line Change:  + 2.63%

org.pentaho.di.trans.steps.fileinput.text.TextFileInputMeta

Complexity Change:  + 1.11%
Instruction Change:  + .38%
Line Change:  + .40%
Method Change:  + 2.00%

org.pentaho.di.trans.steps.fileinput.text.TextFileInputReader

Branch Change:  + 1.20%
Complexity Change:  + 1.12%
Instruction Change:  + 1.05%
Line Change:  + .53%

org.pentaho.di.trans.steps.fileinput.text.TextFileInputUtils

Branch Change:  + .92%
Complexity Change:  + .84%
Instruction Change:  + 1.07%
Line Change:  + 1.29%

org.pentaho.di.trans.steps.insertupdate.InsertUpdateMeta

Instruction Change: -.05%:small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change:  + 1.18%
Complexity Change:  + 1.35%

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change:  + .07%

org.pentaho.di.trans.steps.setvalueconstant.SetValueConstantMeta

Instruction Change:  + .14%

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change:  + .08%

org.pentaho.di.trans.steps.sort.SortRowsMeta

Instruction Change:  + .08%

org.pentaho.di.trans.steps.sortedmerge.SortedMergeMeta

Instruction Change:  + .18%

org.pentaho.di.trans.steps.symmetriccrypto.symmetriccryptotrans.SymmetricCryptoTransMeta

Branch Change: -3.33%:small_red_triangle_down:
Complexity Change: -1.85%:small_red_triangle_down:
Instruction Change: -.28%:small_red_triangle_down:

org.pentaho.di.trans.steps.synchronizeaftermerge.SynchronizeAfterMergeMeta

Instruction Change: -.04%:small_red_triangle_down:

org.pentaho.di.trans.steps.textfileinput.TextFileInputMeta

Branch Change:  + .53%

org.pentaho.di.trans.steps.webservices.WebServiceMeta

Branch Change: -1.79%:small_red_triangle_down:
Complexity Change: -1.19%:small_red_triangle_down:
Instruction Change: -.07%:small_red_triangle_down:

org.pentaho.di.ui.trans.steps.fileinput.text.TextFileInputDialog

Branch Change: -.01%:small_red_triangle_down:
Complexity Change: -.01%:small_red_triangle_down:
Instruction Change: -.01%:small_red_triangle_down:
Line Change: -.01%:small_red_triangle_down:


ddev start fails due to docker-compose version compare (docker edge channel - 18.09.1)

Describe the bug
ddev start fails due to docker-compose version comparison with message
The docker-compose version currently installed does not meet ddev's requirements: 1.24.0-rc1 is less than 1.21.0
To Reproduce
Steps to reproduce the behavior:

Install latest docker version 18.09.1 (edge channel)
ddev start

Expected behavior
Valid version compare even if docker-compose version is tagged with additional info (e.g. -rc1)

Duplicate of https://github.com/drud/ddev/issues/1431, but thanks for the report!


Update 095 errors

Closes #136

Do not merge yet, there are missing status errors like "Failure_Core_Link_Already_Exists". This file is autogenerated, let's wait until REST updates the latest status errors.


[Sunstone] Implement Datastore Tab on FireEdge Sunstone

Description
Implement the OpenNebula Datastore tab in FireEdge Sunstone
Related issues: https://github.com/OpenNebula/one/issues/6057 #5422

Progress Status

[ ] Code committed
[ ] Testing - QA
[ ] Documentation (Release notes - resolved issues, compatibility, known issues)

Related PRs:

Code (master): https://github.com/OpenNebula/one-ee/pull/2565
Code (one-6.6): https://github.com/OpenNebula/one-ee/pull/2566
Docs: https://github.com/OpenNebula/docs/pull/2532
Development: WIP


Lift versioned types out of functor in Vrf_lib.Standalone

This also switches the Lint_version_syntax ppx from warn to error for these files.
Checklist:

[ ] Tests were added for the new behavior
[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them:

The linter is flagging errors.


Add Adobe Photoshop CC 2015

I can produce some more formulae for Adobe apps if it's ok

This requires and uninstaller. @zacs might be able to help you there.

This is quite difficult, as the user-facing uninstaller name is an alias with a localized name (e.g.: /Applications/Utilities/Adobe Installers/Desinstalar Adobe Photoshop CC 2015 in Spanish), thus impractical to hard-code.
The actual uninstaller is located (in my system) at /Library/Application Support/Adobe/Uninstall/{2614BC86-757D-4293-9E25-E4E16F370A9E}/{2614BC86-757D-4293-9E25-E4E16F370A9E}.app, and I don't know if the GUID is specific for my machine, varies between languages or if it's shared among all Photoshop CC 2015 installations in the world.
Hence, I don't know how to approach this scripted uninstallation. I could just write the actual uninstaller path and hope no one reports an issue.

Here’s one of the casks devised by @zacs.

Does the uninstaller have to be silent?

It cannot call a GUI or require user input.

Not all Adobe uninstallers are created equal. It seems that the "Collections" all have an uninstall XML that can be called for silent operation (see the uninstall_preflight stanza in the original Adobe formulae for examples). This is the only way I've seen to uninstall silently.

Got it! The DMG comes with a folder named Deployment, that aptly contains a bunch of deployment files, one for each language. Each one of these can be used to trigger the installation in this way (example for Spanish install, pwd is the root of the dmg):
sudo "Adobe Photoshop CC 2015/Install.app/Contents/MacOS/Install" --mode=silent --deploymentFile="Adobe Photoshop CC 2015/Deployment/es_ES_Deployment.xml"

However, you can also use this same installer (not the uninstaller) to trigger the uninstallation, by simply feeding it this XML:

So, the course of action would be:
Install

Save the contents of the dmg
Run the installer in silent mode with a deployment file (English by default)

Uninstall

Locate deployment file and replace install for remove

Got it! The DMG comes with a folder named Deployment, that aptly contains a bunch of deployment files, one for each language. Each one of these can be used to trigger the installation in this way (example for Spanish install, pwd is the root of the dmg):
sudo "Adobe Photoshop CC 2015/Install.app/Contents/MacOS/Install" --mode=silent --deploymentFile="Adobe Photoshop CC 2015/Deployment/es_ES_Deployment.xml"

However, you can also use this same installer (not the uninstaller) to trigger the uninstallation, by simply feeding it this XML, which is basically the same one as the included in the dmg, but with the properties changed to keep user preferences and the action set to remove instead of install:
<?xml version="1.0" encoding="utf-8"?>
<Deployment>
	<Properties>
		<Property name="removeUserPrefs">0</Property>
		<Property name="mediaSignature">{2614BC86-757D-4293-9E25-E4E16F370A9E}</Property>
	</Properties>
	<Payloads>
		<Payload adobeCode="{2614BC86-757D-4293-9E25-E4E16F370A9E}">
			<Action>remove</Action>
		</Payload>
	</Payloads>
</Deployment>

So, the course of action would be:
Install

Save the contents of the dmg
Run the installer in silent mode with a deployment file (English by default, which is Adobe Photoshop CC 2015/Deployment/en_US_Deployment.xml)

Uninstall

Write the uninstall XML to disk (it would have to be hard-coded 😕)
Feed it to the installer previously saved

Not very difficult, but I lack the necessary knowledge to make this work in both ruby and cask. Could somebody help?

I've updated the PR so cask uses the silent install and uninstall, but I don't know how to create the uninstall.xml file.

It seems like the uninstall.xml should be created during the install. I'm assuming that in brew-cask it should get saved to the app's Caskroom, so it can be easily called for uninstall later. @vitorgalvao is there precedent for creation of files like this (and where to save them to)?

The file itself could be created for example in preflight stanza like this:
  preflight do
    file = File.open "#{staged_path}/uninstall.xml", 'w'
    file.puts '<?xml version="1.0" encoding="utf-8"?>
<Deployment>
    <Properties>
        <Property name="removeUserPrefs">0</Property>
        <Property name="mediaSignature">{2614BC86-757D-4293-9E25-E4E16F370A9E}</Property>
    </Properties>
    <Payloads>
        <Payload adobeCode="{2614BC86-757D-4293-9E25-E4E16F370A9E}">
            <Action>remove</Action>
        </Payload>
    </Payloads>
</Deployment>'
    file.close
  end

and call it during the uninstall:
uninstall :script => 'Adobe Photoshop CC 2015/Install.app/Contents/MacOS/Install',
          :args => %w[--mode=silent --deploymentFile="#{staged_path}/uninstall.xml"]

Not the best solution though.

Why not in uninstall_preflight? It's not needed until then, why pollute the folder?

I fully agree, that uninstall_preflight could be used. I just suggested an example.

Also, just realized the name of the cask should really include the Photoshop version, i.e.: adobe-photoshop-cc-2015. If not, what would happen when Adobe releases PS 2016, the formula is updated and someone tries to uninstall their previously installed PS 2015 only to find that that uninstallation procedure has moved to adobe-photoshop-cc-2015 and they're stuck with adobe-photoshop-cc, that uninstalls PS 2016?

In my opinion, there would be much better to avoid installer :script and uninstall :script in this case. Tha main reason is that #{staged_path} is not available there. At least if it even will work, the audit will always output warning messages. Those should be completely replaced by preflight and uninstall_preflight.
If considering how the user will be able to remove the previous version when it updates to 2016, then I'm thinking that it would much reasonable to use version :latest and sha256 :no_check instead of fixed ones. The problem will be solved at least from a perspective that the user won't be able to install the cask without uninstalling it first. However, he can always run the installation with the --force flag if he really wants to.
Additionally, I'm also thinking about the mediaSignature and adobeCode value. I don't like the idea that it's hardcoded in uninstall.xml. What happens if it changes? Of course, we could even extract it from en_US_Deployment.xml each time, but why to make thing more complicated? That is the reason why I'm thinking that the uninstall.xml file should be created during the installation. In this case, even if we update the cask with the hardcoded value, it won't affect the users who already have installed the cask before and can safely remove their current version even using the new updated cask with completely different hardcoded value.
cask :v1 => 'adobe-photoshop-cc' do
  version :latest
  sha256 :no_check

  url 'http://trials3.adobe.com/AdobeProducts/PHSP/16/osx10/Photoshop_16_LS20.dmg',
    :user_agent => :fake,
    :cookies => { 'MM_TRIALS' => '1234' }
  name 'Adobe Photoshop CC 2015'
  homepage 'https://www.adobe.com/products/photoshop.html'
  license :commercial

  preflight do
    file = File.open "#{staged_path}/uninstall.xml", 'w'
    file.puts '<?xml version="1.0" encoding="utf-8"?>
<Deployment>
    <Properties>
        <Property name="removeUserPrefs">0</Property>
        <Property name="mediaSignature">{2614BC86-757D-4293-9E25-E4E16F370A9E}</Property>
    </Properties>
    <Payloads>
        <Payload adobeCode="{2614BC86-757D-4293-9E25-E4E16F370A9E}">
            <Action>remove</Action>
        </Payload>
    </Payloads>
</Deployment>'
    file.close

    system '/usr/bin/sudo', '-E', '--', "#{staged_path}/Adobe Photoshop CC 2015/Install.app/Contents/MacOS/Install", '--mode=silent', "--deploymentFile=#{staged_path}/Adobe\ Photoshop\ CC\ 2015/Deployment/en_US_Deployment.xml"
  end

  uninstall_preflight do
    system '/usr/bin/sudo', '-E', '--', "#{staged_path}/Adobe Photoshop CC 2015/Install.app/Contents/MacOS/Install", '--mode=silent', "--deploymentFile=#{staged_path}/uninstall.xml"
  end
end

is there precedent for creation of files like this (and where to save them to)?

There is not.
I like the discussion and ideas, here, but in all honesty, and even though I don’t want to turn this into a rant, I wouldn’t be bothered if the whole Adobe family were absent from homebrew-cask (and from the whole graphic design industry as well, if I’m being honest, though that is not the point). Like in everything else they do, the (should be) simple matter of automating their install and uninstall processes is an obtuse, dumb, and suboptimal dance (not that doing it manually is pleasant, either), and is a thorn I’ve been faced with for too long.
@zacs did an amazing job with these in caskroom/versions, and I trust @Ngrd completely. I’ll support whatever solution you come up with (even if that means rejecting the cask and having someone else mount an Adobe-specific tap), as long as (if it stays in the main repos) the cask isn’t incomplete (i.e. missing uninstall).

Well, I agree with @Ngrd and copied his code. Tried it in my machine and both install and uninstall work just fine, totally silent. I wanted to add at least a couple more Adobe CC apps to cask as it's very practical, so it's up to @vitorgalvao if you want to merge this (and possibly more) into the main repo or if I should make a custom Adobe tap.

If they work, I have absolutely no quarrel with including them here. What kind of maintainer would I be if I let a personal quarrel be the sole reason to interfere with the experience of user?
@Ngrd Care to merge, if everything looks fine to you?

I think this can be merged for now. If some additional problems occur we can always make additional changes if required, but at the moment everything works quite fine.

Thank you for the contribution. It needed some fixes, so they were made in 6a2604331f02fbd8c81c37b7146d810b95f0ba22. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


Fix import test failing

What does this PR do?
Fix import test failing following configuration mock migration.
Describe how to test/QA your changes
Running the CI

/merge


Opens submenu multiple times if you click a child multiple times

I am double clicking on that DropdownMenuItem which opens that submenu twice

This is not fixed, I can still reproduce this with 2.3.0

Because I assume
  internal fun navigateTo(entry: CascadeBackStackEntry) {
    if (entry != backStack.lastOrNull()) {
      backStack.add(entry)
    }
  }
  ``` Each time I click, it creates another class thus the comparison fails, as its unique each time

Serves me right for not adding an automated test for this 🙂. Let me fix this (again).


[BugFix] Fix bug Async mv with sync mode lost config

Fixes #issue
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[x] 3.0
[x] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 4 / 4 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/scheduler/TaskManager.java
4
4
100.00%
[]

@Mergifyio backport branch-3.1

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5


Added CockroachDB to list of third-party DB backends.

I expected to find this here when looking for it today, so...

Incidental to the addition of CockroachDB, generally we've required the libraries listed here to be actively maintained.

ibm_db_django looks abandoned (no releases since 2018)
django-pyodbc-azure has moved to https://pypi.org/project/django-mssql-backend/
django-firebird seems to only support Django 1.11.x.
django-pyodbc doesn't have releases since 2017.

Thanks Tim. I updated the SQL Server URL.
There seems to be recent activity on both ibm_db_django and django-firebird from the last few days. Given that culling them wasn't on my agenda, I'll give them the benefit of the doubt for now, but I've made a note to check up on them again before 3.1 final (i.e. before we stop backporting docs fixes to stable/3.0.x).


Fix the issue that breaks the testnet1

Motivation
There were some commits that should not go to the master but should go to testnet2 because they are breaking the testnet1.
This PR reverts those commits from the master. The Poseidon sponge will return to a less standard version. And the Marlin verifier will return to be sort-by-value version. Both are good for security. It is just not compatible with the Marlin gadgets and wide use of Poseidon in testnet2.
This PR will go to master. Then, a new version will be cut, which will be used for snarkOS. Before this works out, I will firstly check if this PR indeed solves the problem in snarkOS.
Test Plan
I will wait for the CI and fix here and there. Then, I will compile a version of the snarkOS using this PR-ed branch as the patches, to see if it solves the problem.
Related PRs
This is related to https://github.com/AleoHQ/snarkOS/issues/1004

Note that this PR has the following side effects:

as a result of this fix, snarkVM 0.7.6 will no longer have a functional Marlin gadget or testnet2. Therefore, in this version, all the integration tests for testnet2 has been disabled, as well as the Marlin gadget test.

this is because testnet2 uses MarlinVerificationGadget, which will fail after the reversion of the fix.

This also means that we cannot directly merge the testnet2 to the master unless we are sure that testnet1 will not go up to the master again. Otherwise, we need to prepare for two copies of implementations.

Running snarkOS with the patched version shows that the issue is fixed---it can successfully process the blocks with PoSW.

After the merge of this, we can cut a release for 0.7.6, and I will ping Max.

Thank you for making the backport!


Many errors when restoring

I created a .mbox via https://takeout.google.com/ and then restored it via the --restore-mbox command. I have first done a complete restore (until I got the done) with this command and then I re-run this command another time to catch all the error message. To be able to identify the emails that weren't restored I have added this between the line 1683-1684 of gyb.py (this is supposed to only print the metadata of emails that weren't restored because the code already run the if request_id in messages_to_skip: to ignore the already restored email):
print(message.get_header(b'Subject'))
print(message.get_header(b'Date'))

Here is a summary of all the error/fails that I notice:

the worrying part: I notice that many emails that are not restored do not trigger an error message. Because I have added the lines above, I was able to identify some of them but not all of them. By chance (by inspecting my email to troubleshoot an error) I found one message that wasn't restored:  it did not trigger any error and the 2 prints above didn't catch it (maybe it was somehow added to the message that should be "skipped" even if it wasn't restored). So this means that the command doesn't restore all the emails and we have no way to know this. Many more email could be missing than the one I found.

I was able to see that some emails that fail are emails who have forbidden attachments ( .apk, .js, .exe  or .lnk and some .zip or .rar that contains those files). In my original Gmail these files had an Anti-virus warning added by Gmail. Some of these emails trigger the error  ERROR: 400: Skipping message restore, you can retry later with --fast-restore but not all of them. But many of these emails didn't trigger any error. I was only able to identify (some of?) them because of the 2 prints I have added. (cf this request for a better way to handle these emails)

All the emails which have a warning "unknown sender" added by Gmail were not restored. Sometime this email would trigger an error 400: Expected a single 'From' header - invalidArgument but not all the time (I could identify them only because of the 2 prints I have added)

many emails were not restored with their original date but with the date of the restore among others (without any errors or warning) :

all my chats/hangouts (I have seen this thread from 2016 which asks to  use the "format": "full" for chat/hangout and not the raw - any news since?)
email send from/to a mobile number  (ex with Text via email or Email via text from https://support.bell.ca/mobility/rate_plans_features/what_is_text_messaging_and_how_to_use_it?step=4)
messages sent from another email provider ( from 2006)

all the chats/hangouts are not threaded

some chats were sent to spam (when they contain a single line with a link)

some messages were printed by my 2 prints but there were already restored. Many didn't trigger any errors from your original code but a few triggered an error like 400: Expected a single 'From' header - invalidArgument (even though they were restored).

I confirm that:

I have upgraded to the latest GYB release from https://github.com/jay0lee/got-your-back/releases and I still have this issue.
I am typing the command as described in the GAM Wiki at https://github.com/jay0lee/got-your-back/wiki

I was able to extract some information from emails which have a buggy restored:

the email who are restored with the date of the restore and not their original date have either:
a two-digit year like this:  10 Aug 12 06:39:36 -0400  or this 09 Jul 12 11:47:15 -0400

I was able to extract some information from emails which have a buggy restored:

the email who are restored with the date of the restore and not their original date have either:

a two-digit year like this:  Date: 10 Aug 12 06:39:36 -0400  or this Date: 09 Jul 12 11:47:15 -0400
a date with the time zone that contains special characters in the date field like this: Date: Thu, 01 Jun 2006 21:38:24 +0200 (Paris, Madrid (heure d'été))  or Date: Fri, 02 Jun 2006 17:37:08 +0200 (Paris, Madrid (heure d'été)).

Here was able to identify a thread of several emails in my original inbox for which many emails weren't restored in the restored mail. I wasn't able to identify a cause so I have created this pastebin  with 2 successfully restored emails from this thread and 2 emails that weren't restore and for which I didn't get any warning (not from from code and not from the 2 prints I have added - cf my post above)


Can this project be run without RabbitMQ & Celery but with Waitress?

I want to run this project on Windows. Gunicorn is not compatible with Windows. Please help.

Maybe? I don't use windows and can't help you with getting it going.

rabbitmq and Celery is separate from Gunicorn + Waitress, afaik?


pidof: Return multiple PIDs while multiple program

fix #118
This commit fixed -s flag only output one result.
Before this commit:
❯ cargo run pidof -s zsh zsh zsh
218159

After:
❯ cargo run pidof -s zsh zsh zsh
218159<PHONE_NUMBER>59

The behavior of uutils' implementation are as same as GNU's implementation now.
❯ cargo run pidof -s zsh zsh zsh
218159<PHONE_NUMBER>59

❯ pidof -s zsh zsh zsh
218159<PHONE_NUMBER>59

Looks good, though there is a conflict with the changes from #123 :|

Thanks!


Updates for V1 RC Rest API

Made changes for RC V1 rest api.  Usage changes include methods for creating a channel.  Non functional changes include a caching object, configuration object, class for listing RC api routes.

@rynefagin I didn't see you had started working on an update to this until I went to submit my pull request. While looking over your code, I see we had some of the same ideas however we implemented them differently. Mind taking a look at mine and letting me know your thoughts?

closing this PR in favor of #5


How to build in production

First thank you for the beautiful program. I am using both https://github.com/Leosocy/EDCC-Palmprint-Recognition and this package and I am very sattisfied.
My question is about how I would build this in production
I am thinking of using docker.
Do I need to built it in every container of I can build in my computer and copy the binaries to docker.

I was thinking I can start out with OpenCV docker image and install both RobustPalmRoi and EDCC-Palmprint-Recognition to create another image then use the resulting image us the base image for my application
For example, because I am using NodeJS and Redis I would also need to install npm and node.
I would then create a docker-compose file to connect the application with Redis database.

Yes, that's a good idea. And you can refer to EDCC Dockerfile.
Recently, I have been using micro services to integrate EDCC and RobustPalmRoi, but I am not good at front-end technology. If possible, we can build these projects together. I can provide API or RPC back-end services through flask or GRPC, and you can use NodeJS to provide front-end services. Then we can deploy these services on Kubernetes.


Using ARM deployments I can deploy a string larger then 1024 characters

Using an ARM deployment of an automation variable I can deploy a string longer than 1024 characters.
The azure portal blocks  strings longer than 1024 so I'm unsure if I should be allowed to do this through the ARM templates

Yes.  The UX has an imposed limit of 1024 characters but the API allows string max which is 2GB if I recall correctly.


Support OpenBSD.

Prior separated PRs were closed in favor of this omnibus.
This PR implements functionality to properly support Dispatch on OpenBSD. This includes fixing some errors, portability cleanup, as well as a portable implementation of the Dispatch runloop and making sure that the kevent backend works properly and portably on kernels that may not support all kevent features (like user-driven kevents).
This PR influences the design of apple/swift-corelibs-foundation#3004 because CFRunLoop in Foundation peeks under the curtain of how the Dispatch runloop handles are implemented.

Closed smaller PRs in favor of this omnibus, so it is easier to track and will centralize any future review.

@etcwilde, mind reviewing?

@drexin, would you review?

@rokhinip, would you review?

Now that apple/swift-corelibs-foundation#3004 is merged and Dispatch is becoming more of a foundational library in Swift, it's all the more necessary that this gets some more eyeballs if at all possible.

I spoke to @rokhinip offline, and @rokhinip will try and review this week or early next.

Answered some of the questions with some AIs for me to make tweaks and re-test -- I'll answer the others after that.

FTR, also slightly unwound a little from the futex commit, as it was buggy, so that part of existing code is now unchanged. As mentioned, also performed the MATCHES suggestion based on your comment above.

While waiting for additional reviews, I made the following changes in this pr from cross-compiling and building this change on Linux:

Fixed a minor issue where the new dispatch_workqueue would work on OpenBSD but not Linux by making the test context a global.

Fixed an issue where dispatch_select would crash because it would run into stack size rlimits on OpenBSD but not Linux by moving the buffers in this test to the heap.

Fixed a cast to an integral type to match the format specifier, rather than a platform-specific type (like time_t)

Additionally, I ran the tests on Linux forcing the queue runloop to use the pipe2 implementation proposed in this pr rather than epoll; it seemed to work fine.


fix: handle chart-testing target branch correctly

Add dynamic target branch detection for chart-testing
Use github.base_ref for pull requests
Default to main branch for other events

Further updates are needed


error TS2304: Cannot find name 'MSStyleCSSProperties'.

TSC 1.5: I keep getting that error on all my existing code when transpiling:
error TS2304: Cannot find name 'MSStyleCSSProperties'.
What is the issue and how to resolve or is that a 1.5 bug?

This is caused by removing IE-specific types from lib.d.ts as part of 1.5 release. See breaking change notification for more information.
if you can share more code, i might be able to help with how to change it.

Thanks for the link.
Using https://github.com/Microsoft/TypeScript/blob/v1.5.0-alpha/bin/lib.d.ts did fixed the issue as explained in the article you sent me.
Code I was having the issue with can be cloned from https://github.com/awayjs
Thanks for the solution!


Fix array_count_values and add warning to easter_date

array_count_values() now passes all tests.
easter_date() now generates a warning if the year is outside the range for valid Unix timestamps as in PHP's documentation: http://php.net/manual/en/function.easter-date.php

Hey @shssoichiro, thank you so much for this PR. I am very sorry for the long wait after you put in this work. This project and my motivation were in a bad spot. I recently breathed new life into it (http://locutus.io/2016/05/announcing-locutus/). Unfortunately for your PR this also means it's currently outdated and cannot be merged as is.
I'll close this issues, but if this PR is still relevant to you, please re-open. You should then rebase with this project's master branch, make sure it complies with the contributing document (https://github.com/kvz/locutus/blob/master/CONTRIBUTING.md), and then we can merge this in, because the work really does look good to me.
Again, I'm very sorry for not having giving this the attention it deserves earlier, and putting you through all this extra hassle. That's all on me and being overrun by this project. I hope you'll agree though that the project was in a dead-end street, and with this new big push, we're going somewhere again.


travis build of staging branch is broken

Need to fix travis.yml file so that the test builds work.

Fixed


chore: try to fix ci

progress:

seems to make things better... the actual error is gone and tests now seem to be running somewhat.
dcos-cli tries to download https://downloads.dcos.io/cli/testing/plugins/dcos-core-cli/linux/x86-64/dcos-core-cli-2.2-patch.x.zip which gives access denied. there's a 2.1 version though 🤔
tried to convince CLI's CI to place according releases to the places dcos-cli is looking for them.

fixed CI by fixing CLI's CI! 🎉


JSON missing columns where the first value for a labelled column is empty

Unlike the other output formats, when outputting to JSON and the excel column does not have a value in the first row after the row header, that column is not included in the JSON.

I want the same problem

I have proposed a fix in this PR:
https://github.com/SheetJS/js-xlsx/pull/918

Why is this issue closed? It's 2023 and I still have this problem. When the value in the first data row is empty, the entire column is ignored.


oh！I wish Obsidian diagram plugin could support the iPad！

agree, that would be awesome if possible!


Fixes for running on mesa

Fixes from #41 for correctness issues.
You can also see the other changes required to run on mesa in https://github.com/kkartaltepe/vk_video_samples/tree/minimal-runnable that cover the other issues mentioned. But note minimal branch does not render correctly, as the dpb workaround is not correct.

Thank you, Kurt - we'll look at your proposed change very soon.

I have already applied these changes in a different form.


Add flake8 to our precommit hook!

Geopandas uses this:
https://github.com/geopandas/geopandas/blob/master/.pre-commit-config.yaml
It will be nice to catch tabs vs spaces in the commits!! let's add this as a pre commit

woah flake 8 catches a LOT!! this will be really really great for us to have. testing CI now

this has been implemented via #196 which was merged. closing


dataFile Requirements Clarification

Documentation reference (URL): https://github.com/ess-dive-community/essdive-water-soil-sed-chem/blob/main/templates/dataFile_template.csv
Submitter: Dylan O'Ryan
Justification (why is this change necessary?): Required fields for dataFile is not clear

I suggest the following changes:
Required fields on the dataFile should be marked with as asterisk (*) instead of noted with a blue text box.
When entering data, I found that asterisks and freezing the column of field names is a good way to easily track the required fields and the field names when entering the methods information and data.
Having asterisks are a good idea to as well as text box color will not transfer when converting to a CSV file.
Current dataFile Template:

Edited dataFile Template:

This issue has been addressed. Required fields on the data file template was clarified in the term list, additionally there are an optional and required data file templates uploaded as part of the reporting format.


expand bootstrap README and add test for /opt/Xilinx/14.7/ISE_DS/settings64.sh

Split up the scripts/README.md in to sections adding a bit more detail. Added missing step to make lm32-firmware.
Added test to scripts/setup-env.sh to test to see if /opt/Xilinx/14.7/ISE_DS/settings64.sh has previously been sourced and display error

Can you use a capital letter for the start of commit messages please? :-)

LGTM! Merging!


Copy test data files to the binary directory

ParquetReaderTest depends on the test data files in directory examples.
It is nice to copy it into the binary directory during the CMake project loading.

I reckon your original implementation was more idiomatic - @assignUser let us know what you think.

So file(COPY) as the more concise version is probably the better choice for now/this case.
@assignUser Thanks for your help. I've gone back to the file(COPY) way according to your and @kgpai  advice :)


Integrate Material-UI (MUI) into "intellectia" React Client with Default Dark Theme

Title: Integrate Material-UI (MUI) into "intellectia" React Client with Default Dark Theme
Description:
This GitHub issue serves as a guide to integrate Material-UI (MUI) into the "intellectia" React client while applying a default dark theme. This integration allows the utilization of Material-UI components and theming for enhanced user interface design with a dark theme by default.
Tasks:

Install Material-UI Packages:

[ ] Install the essential Material-UI packages, including core components and icons, as project dependencies. Execute the following command within the project directory:
npm install @mui/material @emotion/react @emotion/styled

[ ] Additionally, install Material-UI icons using the following command:
npm install @mui/icons-material

Wrap the App with Theme Provider:

[ ] Integrate Material-UI theming by wrapping the application with the Material-UI ThemeProvider.

[ ] Configure the ThemeProvider to use a default dark theme by importing and applying it as follows:
// src/index.js
import React from 'react';
import ReactDOM from 'react-dom';
import { ThemeProvider, createTheme } from '@mui/material/styles';
import App from './App'; // Import your main App component

// Define the default dark theme
const theme = createTheme({
  palette: {
    mode: 'dark', // Apply dark mode by default
  },
  // Add more theme customization options as needed
});

ReactDOM.render(
  <ThemeProvider theme={theme}>
    <App />
  </ThemeProvider>,
  document.getElementById('root')
);

Acceptance Criteria:

This GitHub issue provides a comprehensive guide for integrating Material-UI into the "intellectia" React client with a default dark theme.
All tasks are documented and clearly marked as [ ] or [x] to track progress.
Successful integration of Material-UI components and icons into the project.
Application of a default dark theme using the Material-UI ThemeProvider.
The GitHub issue is considered resolved when all tasks are completed and validated.

Additional Information:

If you encounter any challenges or have questions during the integration process, please don't hesitate to provide updates or seek assistance.
The integration of Material-UI enhances the user interface of the "intellectia" React client, offering a dark-themed appearance by default.

I would like to suggest shadcn ui instead of mui.

I would like to suggest shadcn ui instead of mui.

Okay! Please create a new issue regarding this


Enabling Developers to Start New Projects in Codespaces (Improved New Project Experience)

Summary
For individuals new to coding, as well as experienced developers, Codespaces simplifies the creation of a development environment. This enables learners to jump directly into learning, and experienced developers to focus on writing their code.
Currently, individuals must create a repository through Github and then create a codespace from that repository. This experience inhibits developers abilities to jump directly into development, and flips the development loop on its head.
Intended Outcome
Developers should expect to be able to jump directly into a codespace without requiring a dependency on a repository. New developers should be able to jump into learning scenarios without having to worry about setting up the environment they are learning in. Experienced developers should be able to immediately start writing their code. All developers should be able to create a repository when they are ready to publish their code and start sharing with the greater GitHub community.
How will it work?
Unpublished codespaces will become the default introduction to codespaces for all developers. Developers should be able to access a development experience without having to create a custom codespace just by having a GitHub account and accessing GitHub.com/codespaces.
Key Scenarios
Create:
We will maintain a set of template repositories for developers to use to create unpublished codespaces. These template repositories will contain all of the necessary dependencies for a developer to start building using the language or framework they desire.
Upgrade:
Once developers have developed their projects to a point where they are ready to share and publish their work, an upgrade experience to a repository should be available. Users will be able to upgrade their projects through their VCM.
Delete:
When a user wants to delete their unpublished codespace they will be able to delete it through the same process as deleting a codespace. A user will be able to go to github.com/codespaces, click the ellipses on their project, and select delete. If a user has unpublished changes in the codespace, or the codespace is unpublished, they will be prompted to confirm they want to delete a codespace with unpublished changes.
Export:
In the case of a user running out of entitlements, a user will be able to go to github.com/codespaces and publish the codespace to a new repo. This will enable the user to get access to their code through Git, and ensure that a user has access to their code if they run out of entitlements.

🚢 This has shipped! https://github.blog/changelog/2022-11-09-codespace-templates/


Showing slices on datasource edit form

Sometimes users get confused and re-point a datasource to a totally unrelated table and it breaks the associated slices. They may be thinking that only the slice they care about will be affected by the change in datasource, without thinking all other slices using this datasource may be affected.
This PR adds an "Associated Slices" form entry to the datasources edit form. Hopefully that makes it more clear that this datasource (table) object is linked to many slices and that those may break if you rewire this object.
Note that this will also prevent from deleting datasources that have slices associated with them, which is a good thing, though the related error message is cryptic.

Looks reasonable and prudent to me - LGTM!
I do think that it's necessary to also include a prompt upon saving if the saver != owner (I'm not sure we currently have 'owners' for a data source). The prompt might say something along the lines of,
"Note: You are altering and overwriting the datasource definition. All associated slices may be affected."

lgtm


Profile: Show natural width and height of avatars

Sometimes user cards and battle rooms show proper avatar but in profile it gets kinda weird example user:- Ashley The Pikachu

This won't work if the users avatar is bigger than 80x80, it would fill the screen.

Yeah i'm just going to close this.


Cannot use SpreadElement or experimentalObjectRestSpread

In version 5.0.0 it is not possible to use the spread operator.
When you try to use the following code:
{
  "parserOptions": {
    "ecmaVersion": 2018, // or 6
    "ecmaFeatures": {
      "jsx": true,
      "experimentalObjectRestSpread": true,
      "SpreadElement": true
    }
  },
...

I got this error: 31:18  error  Parsing error: Unexpected token .. on code:
let {x, y, ...z} = {x: 1, y: 2, a: 3, b: 4};
console.log(x); // 1
console.log(y); // 2
console.log(z); // { a: 3, b: 4 }

I just ran it through myself and it seems to be fine

I also encountered this problem, still 6.0.0 version

Have you found a solution?

Have you found a solution?


Initial build infrastructure

Heavily based on k8s.io/registry.k8s.io

@BenTheElder What the consensus on Github Action vs Prow ?
/approve

I had to tweak the ko command to not save tarballs, but instead to load locally into docker.  Otherwise we get an odd bug (?) in ko where it can't save the tarball with multiarch
2022/11/08 09:51:18 Using base distroless.dev/static:latest@sha256:4a58d5bcd0dcae2bfebf28f7ed9621c6d21838a5f343cdb9ee9450f1af478591 for sigs.k8s.io/porche/cmd/redirectserver
2022/11/08 09:51:18 Building sigs.k8s.io/porche/cmd/redirectserver for linux/arm64
2022/11/08 09:51:18 Building sigs.k8s.io/porche/cmd/redirectserver for linux/amd64
2022/11/08 09:51:19 Saving bin/redirectserver.tar
2022/11/08 09:51:19 failed to save "bin/redirectserver.tar": unable to calculate manifest: set of images is empty
Error: failed to publish images: error publishing ko://sigs.k8s.io/porche/cmd/redirectserver: failed to interpret sigs.k8s.io/porche/cmd/redirectserver result as image: &{0xc0001c4940 <nil> <nil> 0xc0001c2aa0 map[sbom:0xc0001c2a80]}
2022/11/08 09:51:19 error during command execution:failed to publish images: error publishing ko://sigs.k8s.io/porche/cmd/redirectserver: failed to interpret sigs.k8s.io/porche/cmd/redirectserver result as image: &{0xc0001c4940 <nil> <nil> 0xc0001c2aa0 map[sbom:0xc0001c2a80]}
exit status 1

We can see the github actions here: https://github.com/justinsb/porche/pull/1
I figure we should use github actions (with minimal logic actually in github actions) where we can, but for the image publishing or anything we need to be more trusted, those we run on prow.

Actions don't provide as strong of guarantees for testing and I'm sure we can offload this particular CI to an EKS cluster in the future so ... shrug? Worth understanding the limitations of actions before committing:

no way to /retest
no way to guarantee latest changes in target and PR branch are tested before merge

The CI for these repos is really small because we made the tests reasonable :-)

OK, those seem like pretty good reasons to use prow :-)
I created a few scripts that are called by the prow jobs (proposed in https://github.com/kubernetes/test-infra/pull/27935)
Currently these are still called by github actions, but we can move to prow - just not sure of the sequencing here!

/retest
(They must be some irony here)
/lgtm

/lgtm
/approve


app.views.current not taking navbar into account

Framework7 version: 3.2.1
Platform and Target: iOS/Android
Live Link or JSFiddle: PREFERABLY (IF YOU WANT YOUR ISSUE TO BE RESOLVED ASAP). You can start from forking the following JSFiddle template: JSFiddle

Describe the bug
app.views.current does not seem to take into account when a view is pushed through the nav
To Reproduce
Steps to reproduce the behavior:

Open files, in zip - or check screenshots
Click on tab2, check app.views.current = tab2 = correct
Click on tab1, check app.views.current = tab1 = correct
Click on link item1, check app.views.current = tab1 = is this correct?

Expected behavior
Upon clicking link item1 I had expected app.views.current to be item1
Actual Behavior
Upon clicking link item1 app.views.current is tab1
Screenshots
I've added screenshots of the step I ran through:

Here I had expected app.views.current to be item1, but it is tab1

Here I had expected app.views.current to be tab1, it is tab1, which is correct

Here I had expected app.views.current to be tab2, it is tab2, which is correct
I've included the smallest possible test case in the zip.
app-demo.zip

Don't mess View and Page. Page is what is loaded through router is not a View, it is a Page inside of View