Build: Missing dependency in build package

When installing YAWIK using a build package, following error occured when trying to login:
Zend\Math\Exception\RuntimeException

Nachricht:

    The RandomLib fallback pseudorandom generator is not installed. Please install it to support secure random numbers

That's because the build progress does not copy vendor/ircmaxell/random-lib and vendor/ircmaxell/security-lib

done in c547ef4fcebb088787b499f1c7c6e0c09d6fa90f


Update index.md

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

internal-3/index.md
:white_check_mark:Succeeded

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

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

Line 16: [Error] Restore nuget package W:\xulp-s.optemp\packages\opbuild.scripts.1.47.0-test-201803121019\tools\packages.config in folder:W:\xulp-s.optemp\packages failed, possibly due to transient errors from nuget servers. Please retry building your content. If the issue still happens, open a ticket in http://SiteHelp. Detailed error: The remote server returned an error: (502) Bad Gateway.
[Warning] Cannot find docset information for repository: 9f4d3881-3ba3-1ae4-b172-2118e88839ea and docset name: internal-2. Please make sure the docset is correctly provisioned
[Warning] Cannot find docset information for repository: 9f4d3881-3ba3-1ae4-b172-2118e88839ea and docset name: internal-3. Please make sure the docset is correctly provisioned
[Warning] No provisioned docset found in repository 9f4d3881-3ba3-1ae4-b172-2118e88839ea. Please provision or restore the docsets if you want to build them

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

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

internal-3/index.md
:white_check_mark:Succeeded

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

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

internal-3/index.md
:white_check_mark:Succeeded

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

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

internal-3/index.md
:white_check_mark:Succeeded

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


Rewrite CI

okay this time it should be fine
This PR completely rewrites the CI, changing the following:

All Linux and macOS wheels are now built on one Linux/macOS runner
Releases are uploaded to PyPI via trusted publishing

This will require trusted publishing to be setup on the PyPI page.
This doesn't require any PyPI credentials to be stored in the GitHub repo, making it a much more secure way of uploading releases via CI.

Utilizes an action for cibuildwheel, rather than installing it manually
Doesn't build a generic wheel without any compiled wheels

This fixes the issue of pytun-pmd3 not functioning on a device where a prebuilt wheel isn't available.

given the amount of spammy commit messages, you may want to consider squashing when merging lol

i'll try that now :)


Include flow-typed for native dependencies in ./app

The flow-typed install doesn't include native dependencies in ./app.
Would it be possible to add a flow-typed script to app/package.json and run it via npm install?
{
  "name": "electron-react-boilerplate",
  "productName": "electron-react-boilerplate",
  "version": "1.0.0",
  "description": "Electron application boilerplate based on React, React Router, Webpack, React Hot Loader for rapid application development",
  "main": "./main.prod.js",
  "author": {
    "name": "C. T. Lin",
    "email"<EMAIL_ADDRESS>    "url": "https://github.com/chentsulin"
  },
  "scripts": {
    "electron-rebuild": "node -r babel-register ../internals/scripts/ElectronRebuild.js",
    "flow-typed": "rimraf flow-typed/npm && flow-typed install --overwrite || true",
    "postinstall": "npm run flow-typed && npm run electron-rebuild"
  },
  "license": "MIT",
  "devDependencies": {
    "flow-bin": "^0.64.0",
    "flow-typed": "^2.3.0"
  },
  "dependencies": {
    "grpc": "^1.8.4",
    "react-native": "^0.52.1"
  }
}

If I npm run flow-typed here from app directory it puts the native dependency flow definitions in ../flow-typed, but am not sure about the proper way to call this from the root package.json.

Also, should we add <PROJECT_ROOT>/app/node_modules/* to ./flowconfig [ignore], otherwise flow is trying to evaluate app/node_modules.
Maybe should include a native module (something simple?) in the boilerplate to test this all?

I'd love a PR for that 😄


Can't run example from README under macOS

The following command:
docker run -ti -v /usr/src/nmrML/examples/MTBLS1/FIDs/ADG10003u_007/10/:/src -v $PWD:/data phnmnl/nmrmlconv:latest -l create -b -z -t bruker -i /src/ -o /data/ADG10003u_007_10.nmrml
gives the following output:

ACQUISITION_FILE not available or readable: /src/acqus

Where are your source files located in? If they are in the current directory and are .nmrml, try this:
docker run -ti -v $PWD:/data phnmnl/nmrmlconv:latest -l create -b -z -t bruker -i /data/*.nmrml -o /data/test.nmrml

Ok, my fault, I saw that nmrML repos was already cloned inside the docker image, and didn't look at the first -v option. With the following command:
docker run -ti -v $PWD:/data phnmnl/nmrmlconv:latest -l create -b -z -t bruker -i /usr/src/nmrML/examples/MTBLS1/FIDs/ADG10003u_007/10/ -o /data/ADG10003u_007_10.nmrml
It now works perfectly.

And with docker run -ti -v $PWD/nmrML/examples/MTBLS1/FIDs/ADG10003u_007/10/:/src -v $PWD:/data phnmnl/nmrmlconv:latest -l create -b -z -t bruker -i /src/ -o /data/ADG10003u_007_10.nmrml too.


tmux status not being disabled when entering zen mode

I just built the nightly, and am using nvim within tmux (zsh shell).
Isn't tmux status disable the defautl?

No, you need to add plugins = { tmux = true} to the config

Documentation suggests that tmux status line is disabled by default, but it's not.

@rorj @surmish you're right. The default settings were not correct in the README. I've updated the readme to reflect this.

Thank you both! Thanks also for the well thought out plugin. I have another quick question, do you know how to disable line numbers on entering zen mode? (And perhaps, restoring them (if they were enabled before) on exiting)

@surmish  uncomment the number=false and relativenumber

thanks, should've read the documents properly

running the commands here the font size does increase https://github.com/folke/zen-mode.nvim/blob/main/lua/zen-mode/plugins.lua#L40-L43
kitty @ --to unix:/tmp/kitty-1073 set-font-size +5


Throws unsupported schema error on seemingly valid schema from Schema.org

Library version: 0.31.17
JSON schema version: 2020-12
I won't contribute to fix the issue ❌
The current behavior
Fails with Error: Unsupported schema. Did not match any type of the parsers. Schema was: {"description":"The day of the week between Thursday and Saturday.","const":"Friday"}
The expected behavior
Should convert to Typebox schema.
Why does it happen? What/How to fix the issue?
No idea.
Content of minimal json schema file which causes the problem

Click to expand/collapse
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "schema:DayOfWeek",
  "title": "DayOfWeek",
  "description": "The day of the week, e.g. used to specify to which day the opening hours of an OpeningHoursSpecification refer.\n\nOriginally, URLs from [GoodRelations](http://purl.org/goodrelations/v1) were used (for [[Monday]], [[Tuesday]], [[Wednesday]], [[Thursday]], [[Friday]], [[Saturday]], [[Sunday]] plus a special entry for [[PublicHolidays]]); these have now been integrated directly into schema.org.\n      ",
  "type": "string",
  "oneOf": [
    {
      "description": "The day of the week between Thursday and Saturday.",
      "const": "Friday"
    },
    {
      "description": "The day of the week between Sunday and Tuesday.",
      "const": "Monday"
    },
    {
      "description": "This stands for any day that is a public holiday; it is a placeholder for all official public holidays in some particular location. While not technically a \"day of the week\", it can be used with [[OpeningHoursSpecification]]. In the context of an opening hours specification it can be used to indicate opening hours on public holidays, overriding general opening hours for the day of the week on which a public holiday occurs.",
      "const": "PublicHolidays"
    },
    {
      "description": "The day of the week between Friday and Sunday.",
      "const": "Saturday"
    },
    {
      "description": "The day of the week between Saturday and Monday.",
      "const": "Sunday"
    },
    {
      "description": "The day of the week between Wednesday and Friday.",
      "const": "Thursday"
    },
    {
      "description": "The day of the week between Monday and Wednesday.",
      "const": "Tuesday"
    },
    {
      "description": "The day of the week between Tuesday and Thursday.",
      "const": "Wednesday"
    }
  ]
}

Hey @mjp0, thanks for raising the issue! Fixed and released in the new version 1.6.2.
I checked schema.org but did not understand how to download the json schema for a given entitity. Could you tell me how to do that? E.g. how did you get the dayOfWeek schema for https://schema.org/DayOfWeek ?
Could think about adding more "integration tests" based on some schemas there.

Sorry for the late reply. I used schema-org-json-schemas  package to download the schemas.


Account Issues

Subject: Account Issues
Description:
Why was my account suddenly blocked? What's going on???? I even verified the phone number and the donation!!! What's going on? I just polished up some of my profile
Results:
What is going on here? I have never encountered such a strange problem!! Please solve it for me as quickly as possible. Remember, the fastest speed
Backend version: develop-e12be83f
Frontend version: develop-e12be83f
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Page: https://couchers.org/login?from=%2Fsearch
User:

Not a bug.

Dupe https://github.com/Couchers-org/couchers/issues/5054


SSL certificate

The userguide https://nd4j.org/userguide has a problem with ssl certificate.

Problem is it's hosted by github with a *github.com certificate.

@damianoporta Sorry about that. Could you remove https for the time being? So for example, just navigate to http://nd4j.org/userguide and it should work.
I'm going to acquire an SSL certificate for ND4J.org so it'll be fixed in the coming days.


Update from upstream

Updating from upstream so we can take a pending pull request

My merge commit is in there. Did I update this incorrectly?

Nah, I think it's correct because the master branch itself is stale.

Thanks! Another PR on the way now the master branch is updated


docs(kic) Replace product name with variables

Replaced any instances of "Kong Ingress Controller" with the variable {{site.kic_product_name}}.
Since KIC is notorious for having issues with naming, this will make it easier to update everything in one go when it inevitably gets rebranded again.
Note: For page titles, did not use the variable but instead wrote out the name directly. Variables don't get parsed in browser tab labels.
https://deploy-preview-2492--kongdocs.netlify.app/kubernetes-ingress-controller/1.0.x/introduction/

One thing to consider is the use of long and short variables, which is what we did at Confluent. It is a bit tedious to read out the entire long product name every time. The first instance in a topic is long, subsequent are short.

Good point - we did the same at SAP. For this PR, I only went through and changes instances of the full name to a variable, and any time it simply said "ingress controller", I left it alone. That could be a good candidate for the short name here. I'll note it as an improvement for the future.


return a 404 when a request is not found

when a requested resource is not found, return a 404 error (instead of a 500, internal server error)

@RedBrogdon @domesticmouse

Coverage remained the same at 78.455% when pulling 811bb62cd5388fad0aff51e4b57fcd3ab60e4d34 on http_500 into 6214d8ef63cef247c1589573bd013d942fac5a48 on master.


Update technet blog links

Docs Build status updates of commit d0df600:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sysinternals/downloads/process-explorer.md
:bulb:Suggestion
View
Details

sysinternals/downloads/newsid.md
:white_check_mark:Succeeded
View

sysinternals/downloads/process-explorer.md

Line 64, Column 45: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/answers/topics/windows-sysinternals-procexp.html' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Batch Checkout for hca dss download [wip]

Threads attempt to initiate checkouts before downloading data.
Does not force thread to stay with file as it attempts to 'retry' and get into the checkout bucket.
Queue file downloads by size of the file, smaller to larger.

Closing this PR; waiting for community review for presigned URLS.


ci(madge): add madge job for PRs against medplum/test-actions

Adds madge CI job to detect circular dependencies in modules like the ones found and fixed in #3742.
There are still some circular dependencies in the codebase but this job will only run in CI for PRs against the medplum/test-actions branch for now. This is so we can test it before it gets accepted into the standard suite of CI jobs that run on PRs against main.

@codyebberson Nope, this is only enabled on the medplum/test-actions branch for now. I wanted to test it first and then once we resolve the circular dependencies we can easily enable it on all PRs


Contribution of Flexible Conv Encoder/Decoder Base nn.Modules

Hi! @alawryaguila mentioned that you might be tackling this as an enhancement/future feature.
I can contribute this if you are interested, as I have some code that handles most cases, and unit tested.

Hi @NMontanaBrown, sounds great! Let's discuss your code, and how we can fit it into the existing framework, offline.


How to deal with deprecated options

Options for the various Jaeger components may become deprecated and eventually removed over time.
How should these be handled when a user specifies them in a CR? Especially if existing Jaeger instances are just upgraded through subsequent versions automatically by the operator?
Ideally we need the operator to:
(1) inform the user that the CR now includes deprecated or removed options, so needs to be updated
(2) until the updates are applied, where possible have the ability to modify the supplied configuration to one that is supported, before being applied to the underlying jaeger components (whether creating or updating).

There are two situations:

CR is created for Jaeger 1.1 and the operator gets upgraded version by version until, say, 1.10.
User creates a CR using a deprecated/removed option.

In the first case, the operator should change the CR whenever it's upgraded and a deprecated version is used. When the migration path isn't known, we should log and return an error (the upgrade mechanism should already abort on error).
For the second option, I think we should follow the same policy as Jaeger itself, keeping the option in the deprecated state for so long as the default underlying Jaeger version keeps it.

Not sure we should treat the situations differently, as it may complicate the logic. So even if the user themselves specify a deprecated option, the upgrade logic could still be used to identify a new option - but log the fact, so users may be informed (if they check the logs).

From the code's perspective, those are two different places. In one, we might use the current "normalize" function, while the upgrade logic would be on its version-specific source.


Chat: Do some basic error catching for invalid tokens

Can this crash the system? Where can invalid tokens come from?

Yes this crashes the frontend. Currently it happens because I did not supply a proper instance locator, but I think it can happen if a token is invalid, or if the chatkit server does not respond.

I have made a pull request #694 addressing this issue.

I see. great!

Addressed by https://github.com/source-academy/cadet-frontend/pull/694


remove live state from cluster

#544
#479  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @BelSasha and the rest of your teammates on  Graphite

Confirmed that sharing across users works. The following was run in a fresh environment with a different account:


Miscellaneous improvements to content adapters

These are all minor, and should probably be separated into individual issues at some point, but for now...
1) If a content adapter creates p1, attempting to create p1.md with hugo new causes a panic.
2) If p1.md exists, and a content adapter creates p1, the content adapter wins. It seems to me it should be the other way around; p1.md should override the content adapter. For example, a module provides content, and you need to override one of the pages provided by the module.
3) If p1.md exists, and a content adapter creates p1, the --printPathWarnings flag does not report a page collision.

The behaviour here is undefined; if you see a winner here, that is by chance. We sort the directories before we process them, but p1.md and _content.gotmpl is processed in separate Go routines, so who's the winner of p1.md and p1 from some _content.gotmpl is undefined.
I think there's an existing issue for this.

if you see a winner here, that is by chance

Understood. I'll add a "page collisions" (or something) section to https://gohugo.io/content-management/content-adapters/ to briefly describe this.


Update Composer dependencies (2021-10-20-00-02)

Visual regression test passed!
View the visual regression test report


Streaming export API

About this fork / pull request
Why this fork?
The export wrapper of the Mailchimp API wrapper "Gibbon" loads all the exported data first in memory, before returning it. Since with exporting data, there can be lots and lots of data, this seemed fairly inefficient. This fork solves this.
How is this fork different?
The changes are as following:

Instead of httparty, the basic net::http interface is used to stream data directly from the Mailchimp API.
The export API functions now require a &block to feed each row of data to.
The export test functions use webmock to fake and verify net::http requests.
Some re-arrangement of functions (parse_response at APICategory.rb)

What can I do with this fork?
All you can do with the normal Gibbon API Wrapper. Plus, parsing each row of exported data while it is being received from the export API:
    ge = Gibbon::Export.new("your_api_key")
    ge.list({:id => *list_id*}) { |row| *do_sth_with* row }

It is important to supply an explicit block / procedure to the export functions, not an implicit one. So, the preceding and following one will work. Please note this method also includes a counter (i, starting at 0) telling which row of data you're receiving:
    method = Proc.new do |row, i|
        *do_sth_with* row
    end
    ge.list(params, &method)

Please note, the following example gives a block that is outside of the function and therefore won't work:
    ge.list({:id => *list_id*}) do |row|
        *do_sth_with* row
    end

And, the original way of working with gibbon is still functional of course:
    list = ge.list({:id => *list_id*})

Some final words
Happy coding!

It looks like this change is backwards compatible (i.e. returns the array of JSON objects if no block is given) .. correct?
Also, the notes above say that this works:
ge.list({:id => *list_id*}) { |row| *do_sth_with* row }

while this doesn't:
ge.list({:id => *list_id*}) do |row|
     *do_sth_with* row
end

Aren't those functionally equivalent?
I'm +1 on the overall spirit of this pull request. I'm a little wary of the edge case handling since it's hard to test but I can't really see anything wrong at a glance

I'm traveling so it'll be a few days before I can look at this. So you know, I'm already working on version 2, which hits MailChimp's API 3.0 instead.

(And thanks for taking the time!)

Dear David and Amro,
Thank you for your quick replies. I was myself also more busy the past couple of days than expected, luckily now that's better.
In reply to the main points:

Indeed, I noticed (too late) that you were already working on version 2. The current patch is for version 1, maybe in the future we can port it to version 2. Of course, this depends on the setup of version 2 and how this differs from version 1.
Yes, this patch is backwards compatible. When no block is supplied, the results will simply be returned as an array, equally to how it was before.
About the notes. Somehow, and this is a ruby gimmick, these two examples on how to supply a block are not compatible. To my own surprise! Gave me some headache to figure this out... See here and, for more extensive documentation about blocks, here. The key here is to supply an explicit block that can be passed as an argument between functions. Proc.new and {} works for that, simple do ... end does not because it creates an implicit block.

I'll look into the detailed comments next.

Getting back to this. Thanks again for adding streaming support. I'll accept this patch and release it as a final version of 1.x, but I would like some minor changes. You removed a lot of examples, etc. from the README and changed the gemspec to reflect your fork, etc. I'd like the examples put back in the README and your examples added instead. And the changes to the gemspec relating to your fork reverted.

Thank you for accepting. The changes to the gemspec / readme were only for my fork, not for the master branch of course. I've made these updates now:

I reverted back gemspec. I still left the version on "Gibbon::VERSION" now, so one can also verify programmatically which version the gem has.
I reverted back the readme, and added my examples there.

Sorry if I'm a bit slow to respond -- I'm traveling. The Gibbon::VERSION change is just fine by me but it seems to be causing a build failure on CI. Could you fix that?

My bad. Fixed.

NP, thanks for contributing

I'll release after I do some testing. So you know, the next few days are hectic for me. My guess is I'll have time Thursday.

I just tried this and released version 1.1.6. Thanks @fsluis!


Update build-mogenerator-Info.plist.sh to use DERIVED_FILE_DIR instead of TMPDIR

TMPDIR is not well-defined, but DERIVED_FILE_DIR is during an Xcode build.
Also, make sure paths are quoted.

Thanks!


Fixed compile issue if importing scss files

Hi @noolan, did not know about compile issue. Can you please change 0 to 1 and I will merge your PR? It is a value that is glued at the beginning of the box-shadow string and let's at least make this value a real number (so that we would have 142vw instead of 042vw for example).

Done.
Sorry for the delay.
Must have missed the notification.

@noolan thank you, I also forgot about this one :)


Removed support of Python3.7

This PR removes supports and CI tests for Python3.7.

the name of the branch almost get me ;)

Indeed!


Where to see the implementation of material2 components's MDdirectives?

Hi,
Don't know if this is the right place for my question or not, but i want to know that whenever we use the material component's directive like Mdbutton, Mdcard etc., then that directive is replaced by the corrosponding component.
So i would like to know that where is the implementation of these MD Directives for corrosponding components.
I like to deep dive into it and create some  components in the material2.
Regards,
Prashant

Hello, you mean the source code ?
https://github.com/angular/material2/tree/master/src/lib

@juanpmarin-infocorp  I think i got the answer i will start my POC now.
Thanks man!  :-)


CODE RUB: InvalidConfigurationAIModelException Class Update v2.10.1

Updated InvalidConfigurationAIModelException class by removing constructors in which the error message was hard coded in. Updated all relevant service files to include message.

Closing Pull Request. Resolved in PR #551.


[#noissue] Unexpected Charset can be set for String encoding

Codecov Report

Merging #6853 into master will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #6853      +/-   ##
==========================================
- Coverage   39.18%   39.17%   -0.01%
==========================================
  Files        3220     3220
  Lines       95324    95324
  Branches    11891    11891
==========================================
- Hits        37352    37344       -8
- Misses      54978    54983       +5
- Partials     2994     2997       +3

Impacted Files
Coverage Δ

...tor/cluster/zookeeper/ZookeeperClusterManager.java
0.00% <0.00%> (ø)

...rp/pinpoint/rpc/packet/ControlHandshakePacket.java
51.51% <0.00%> (-24.25%)
:arrow_down:

...pinpoint/profiler/instrument/AccessorAnalyzer.java
57.14% <0.00%> (-8.58%)
:arrow_down:

...rc/main/java/com/navercorp/pinpoint/test/Item.java
66.66% <0.00%> (-6.67%)
:arrow_down:

...m/navercorp/pinpoint/rpc/client/ConnectFuture.java
80.00% <0.00%> (-5.00%)
:arrow_down:

...tor/metric/datasource/DefaultDataSourceMetric.java
75.00% <0.00%> (-3.13%)
:arrow_down:

...om/navercorp/pinpoint/rpc/codec/PacketDecoder.java
57.44% <0.00%> (-2.13%)
:arrow_down:

...cluster/zookeeper/ZookeeperClusterDataManager.java
52.90% <0.00%> (-1.94%)
:arrow_down:

...point/rpc/client/DefaultPinpointClientHandler.java
72.07% <0.00%> (-0.33%)
:arrow_down:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
80.98% <0.00%> (+0.70%)
:arrow_up:

... and 6 more

Continue to review full report at Codecov.

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


[FIX] Update syntax to fix deprication warnings

This removes some syntax that has become out of date since the retirement of python2 and fixes all the deprication warnings (including the ones mentioned in this issue: https://github.com/edickie/ciftify/issues/149)

I just noticed that issue found a syntax error I missed (only seems to show up for 3.9). I'll fix that one in another PR later and add a test suite for 3.9. This one will fix every issue for 3.5 - 3.8 for now


Error: Objects are not valid as a React child in Email Demo Preview

Describe the Bug
Environment

Operating System: Windows 10/11
React-Email version: canary
Build tool: esbuild with PNPM

Actual Behavior
An error occurs stating that an object is being incorrectly used as a React child:
Error: Objects are not valid as a React child (found: object with keys {$$typeof, type, key, ref, props}). If you meant to render a collection of children, use an array instead.
The issue seems to occur around the execution of vm.runInNewContext(builtEmailCode, fakeContext, { filename: emailPath }).

Preliminary Analysis
I have introduced additional logging to trace the output of fakeContext.module.exports following the VM execution, which consistently returns {}, resulting in fakeContext.module.exports.default being undefined. This indicates that React components or elements are not being recognized properly but are instead being treated as undefined objects. This issue could be associated with the manner in which the built email code is processed within the Node.js VM context. It suggests potential problems related to serialization or the handling of context isolation by the vm module, particularly under Windows environments.
Suggested Next Steps

Test whether this issue is consistently reproducible on different setups, particularly on other Windows machines as well as on Linux and macOS.
Inspect the esbuild configuration and the resulting output to ensure React components are correctly transpiled and bundled.
Examine if there are platform-specific behaviors in the Node.js vm module that could affect how execution contexts are handled.

Collaboration
I am open to a joint debugging session if other developers have experienced similar issues or have insights into the cause. This might help in identifying and resolving the issue more efficiently.
Which package is affected (leave empty if unsure)
react-email
Link to the code that reproduces this issue
https://github.com/resend/react-email/blob/canary/packages/react-email/src/utils/get-email-component.ts
To Reproduce
Steps to Reproduce

Clone/download the repository.
Run pnpm install and pnpm run build at the root.
Navigate to apps/demo.
Run pnpm run dev.
Access the local server to trigger the email rendering process.

Expected Behavior
Expected Behavior
The email content should render without errors in the virtual machine context used for SSR.
What's your node version? (if relevant)
20.9.0

I got this error a couple of times when switching between React 19 and React 18, did you switch around by any chance? This is particularly something that I expect with this error because the element structure changed a bit from React 18 to 19

Is this really specific to Windows? It seems to me like something to do with improper dependencies being installed, make sure that you didn't change the lock file.

I tested the pnpm install and pnpm dev from both Linux and Windows, none worked as expected. However, for Linux, the error was different, so I will log a separate issue for that.
And for the Windows, it was a bumpy ride. First, the pnpm install and pnpm dev never worked from root. What I did was to run a pnpm build from the root, with partial success.
The readme at the root of this project isn't really clear at telling what the localhost:3000 was supposed to render. e.g. the web & doc or the demo? so i then navigate to "apps/web" and "apps/demo" individually, and run pnpm dev. For "apps/web", it works as expected, I can browse the web and doc. However, for "apps/demo", it displays above preview issue.

Went through the exact steps and didn't get any error, but as I mentioned before, this error is probably because the demo is using X React and version and some component is using Y React version.

Went through the exact steps and didn't get any error, but as I mentioned before, this error is probably because the demo is using X React version and some component is using Y React version.

Thanks again for your insights, and I appreciate the direction you've provided. The different React versions definitely seem to be the root cause of the issue. I was able to get apps/demo running by using the following resolutions in package.json:
"resolutions": {
  "react": "18.2.0",
  "react-dom": "18.2.0"
}

This works as a temporary fix, but it does introduce some issues (e.g., with react-email-with-resend), so I consider this more of a workaround than a permanent solution.
Next Steps:
I'm happy to continue the conversation here, but if you feel it would be easier to address this complexity over discord/slack, I'm open to that as well. I’m keen to contribute however I can and would be happy to help with a PR or improvements to documentation once we’ve aligned on a direction forward.
Looking forward to your thoughts on how best to proceed.

@chuanxshi We can't do it through resolutions for now because the react-email app does not use React 19 yet for a few reasons that are too hard to explain in this comment.

I'm happy to continue the conversation here, or over discord/slack if you prefer, I can also help with a PR or improvements to documentation once we’ve aligned on a direction forward.

I've made a PR that should fix these sorts of issues on the future #1706. It should do the same as the pnpm.overrides, but only for the components, and for top-level dependencies.

@DwifteJB This issue is only on internal development, if you are having it while using React Email, you can use whatever React version you want.
https://github.com/resend/react-email/blob/ad2e6c46d54466f22338991b0d47b87300ec2ba5/packages/font/package.json#L33-L35
The error for this issue only happens because we use React 19 internally for our apps.

@DwifteJB This issue is only on internal development, if you are having it while using React Email, you can use whatever React version you want., you aren't fixed in any version, so your issue should be somewhere else other than React Email.
https://github.com/resend/react-email/blob/ad2e6c46d54466f22338991b0d47b87300ec2ba5/packages/font/package.json#L33-L35
The error for this issue only happens because we use React 19 internally for our apps.

If I use a new folder, with different node modules will it work fine for rendering with nextjs 19.0.0rc?


ARM64 support for bluegl

Adding ARM64 support for bluegl. Full Filament build has been verified on Jetson AGX Xavier on Ubuntu 18.04.
This resolves #1135 .
Some notes:

For libpng, Neon optimizations for ARM are turned off. Otherwise, I get a bunch of errors similar to:../../third_party/libpng/tnt/libpng.a(pngrutil.c.o): In function `png_read_filter_row':
pngrutil.c:(.text+0x3fd4): undefined reference to `png_init_filter_functions_neon'

Need to set -DFILAMENT_SUPPORTS_VULKAN=OFF.

Thank you! This is extremely useful! We'll probably use this as the foundation for Apple Silicon support.


Move tests to the top-level directory

Yes, we should care now!
From IRC godotengine-devel:
Akien: BTW, should tests stay in `main/tests/` or be moved to a top level `tests/` folder?
Xrayez: Moving to top level could really deliver a message that we do care about tests. :))
Akien: That's why they were in `main/` until now :P
RevoluPowered: top level would be nice

Thanks!


Feature Request: Import bearer token authentication from postman imports.

Insomnia Version: 6.1.0-beta.1
Operating System: All

Details
Insomnia and Postman both support similar authentication methods with similar options, and it's frustrating to have to re-enter all my authentication settings every time I have to re-import from a colleague's postman collection.
Support importing bearer token authentication from Postman v2.0 and v2.1 imports.

I have a PR in the works for this issue.


Can't import Bestiary 4 - Arcane Familiar (Scarlet spider)

Can't import statblock:
Arcane Familiar      CR –
Scarlet spider (Pathfinder RPG Ultimate Magic 252)
N Tiny magical beast (vermin)
Init +5; Senses darkvision 60 ft.; Perception +4
Defense
AC 19, touch 17, flat-footed 14 (+5 Dex, +2 natural, +2 size)
hp 4 (1d8)
Fort +2, Ref +5, Will +2
Defensive Abilities improved evasion; Immune mind-affecting effects
Offense
Speed 30 ft.
Melee bite +7 (1d3-4 plus poison)
Space 2½ ft.; Reach 0 ft.
Special Attacks poison
Statistics
Str 3, Dex 21, Con 10, Int 6, Wis 10, Cha 2
Base Atk +0; CMB +3; CMD 9 (21 vs. trip)
Feats Weapon Finesse[B]
Skills Acrobatics +13, Climb +13, Heal +1, Perception +4, Spellcraft -1, Stealth +17; Racial Modifiers +8 Acrobatics, +8 Climb, +4 Perception, +4 Stealth
SQ empathic link
Special Abilities
Darkvision (60 feet) You can see in the dark (black and white only).
Empathic Link (Su) You have an empathic link with your master.
Immunity to Mind-Affecting effects You are immune to Mind-Affecting effects.
Improved Evasion (Ex) No damage on successful reflex save; half on failed save.
Poison: Bite-injury (DC 10) (Ex) Bite—Injury; save Fort DC 10; freq 1/rd for 4 rds; effect 1 Str; cure 1 save.
Share Spells Spells with a target of "You" can be delivered by a familiar with a range of touch.

Used your latest module that was available as of about 10:30 am. I used Hero Lab to produce this statblock. For greater accuracy, you might want to use one of the online resources. Hero Lab can truncate some of the text -- or inject errors due to a lack of data. All the other statblocks from Bestiary 4 imported -- a total of more than 85% imported!


feat: Added a Ghost UI screen

Details

Adds a background screen with shimmer animation, when the chat is loading
It also adds an additional dependency react-content-loader for SVG based animation on components.

Fixed Issues

$ https://github.com/Expensify/App/issues/7081
Tests

[ ] Verify that no errors appear in the JS console

QA Steps

[ ] Verify that no errors appear in the JS console

Tested On

[ ] Web
[ ] Mobile Web
[ ] Desktop
[ ] iOS
[ ] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

@Luke9389 @parasharrajat, can you help me verify the loader condition. It seems that what I am using for the initial load is incorrect.
I have attached two screens for Ghost UI on Mobile as well as Web for reference.
https://user-images.githubusercontent.com/3069065/155564261-46fbbdcc-50ea-4a0a-92ef-84927b1680f3.mov

But when it transitions from Ghost screen to the chats, it switches one chat at a time, so I am guessing I am using an incorrect flag for the loader. Following is the attached ref video.
https://user-images.githubusercontent.com/3069065/155564385-197731ad-7444-4a43-8bdd-04f78de8ac1b.mov

This Onyx is updated multiple times during the app cycle. So maybe just create a state and update that only once when this is true. I don't know on this.

@mananjadhav did you close this intentionally? If so would you be willing to post your reason (can be brief). Just easier for everyone to follow. I see there's another PR. You can always link to that here as well.
Other PR: https://github.com/Expensify/App/pull/8042

Yeah @Luke9389. I closed the old PR because it didn’t have the new PR template checklist. Raised a fresh one with the same changes here #8042


[[Fix]] Do not disable ES6 when moz is set

Although environments implementing Mozilla extensions are not
necessarily ES6-compliant, they are not mutually exclusive. Ensure that
for configurations that specify both ES6 and moz, the semantics of
both environments are applied consistently.
Resolves gh-2785.

LGTM


Update to the latest inspec, liblzma, and libxslt

Pull in the latest omnibus-software that bumps liblzma and libxslt with a large pile of bugfixes.
Signed-off-by: Tim Smith<EMAIL_ADDRESS>

think you need to bump versions in omnibus_overrides.rb though?


Minified version needs explicit dependencies declared

schemaForm directive needs $parse and SchemaForm explicitly declared, otherwise minified version usage fail.

Any progress on this? The supplied fix looks okay to me, it should be a no-brainer...

@s100 if you make a PR with ng-annotate I'll merge and publish it. I'm too busy at the moment to put the time for it.


Macros prefixation

Fix #153.

@tristan0x ping, do you think I should add anything else in the PR? Please let me know.

@tristan0xdo you think I can enhance anything else in the PR? Please let me know.

@tristan0x do you think I can enhance anything else in the PR?

👋

I am closing this because the macro renaming changes needs to be done at two places outside this project : https://github.com/BlueBrain/mod2c and https://github.com/BlueBrain/nmodl. Given the complete code-reorganisation of this repo in #229, it would be better to re-do this.


support for ReservedConcurrentExecutions

CloudFormation supports specifying this, but SAM throws an error:
property ReservedConcurrentExecutions not defined for resource of type AWS::Serverless::Function

I know AWS doesn't provide ETAs, but any chance you could provide a rough estimate? About to create a custom cf resource as a workaround 🐼

@rgarcia Hey sorry for the late response. My queue is still backed up from when I was out.
Does soon work? :) The change is through CR and waiting to get a testing pass through. I would say a couple weeks, at very most, before it is live.

@jfuss no worries! We have a custom resource workaround that works for now. Will be happy to remove it in a couple of weeks when this is released

@rgarcia hi! I am running into the same problem, I was wondering what your workaround was?

@etapaza we created a custom cloudformation resource, here's the code https://gist.github.com/rgarcia/22484855cf7c18c961ab8d2dcad53f7f

This is now available. Checkout Release Notes


SelectField onChange event

I can't manage to add an onChange to SelectField, it seems to be ignored.

I've passed <Field onChange={this.onChange} ... instead of the new <Field input={{onChange: this.onChange}} ... syntax.


[sqlite-modern-cpp] update

Updates the version of SqliteModernCpp/sqlite-modern-cpp to the latest commit, as the previous one was more than five years old

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[x] The "supports" clause reflects platforms that may be fixed by this new version.
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

@microsoft-github-policy-service agree company="FileCloud"

Just putting it on record that I think this is good to go subject to the versioning discussion above. Paths forward:

Change to version-string (my proposal)
Change to version-date (possible alternative suggested by @ras0219-msft )
Change to version but encode a date as the last number so that it's still orderable with current versions (that is, 3.2.20240326) (possible alternative suggested by @ras0219-msft )

@darrenbane-fc which of these do you think is least confusing?

I agree that upstream seem to have stopped making full releases and expect to work off HEAD. I'll raise a ticket there just in case, maybe they would create a 3.3 tag, but I don't think it's a good idea to depend on this.
I think version-string will be easiest in future.  You lose the ordering, but I didn't even know that was a thing at the start, and version-string is like a hint that ordering is not a valid op now anyway?
So in conclusion I'd favour version-string, but like I said I'm not a vcpkg expert.

@vicroms version-string is kind of 'user experience hostile' so I prefer that we move away from it (and I prefer version-date)
@dan-shaw I agree with @vicroms
@ras0219-msft I agree with @vicroms but I agree with him more strongly than he put it. I believe this is the purpose of version-date and I think we should use it for all of these sort of rolling release cases. Importantly, it plays well with upstreams who decide to change to having real versions and back.
Result: @BillyONeal to change this to version-date and merge.

Thanks for the update @darrenbane-fc and sorry it took a bit for us to get the versioning in a good place :)


wip: full ng refacto

~~ WIP DON4T MERGE THIS~~

~~ WIP DON4T MERGE THIS~~

fix router problem with the angular-ui-router@next
add ava + jsdom testing
refacto to component first the root of the app
add routing to representation (url like : "nso/explore/express/dependency-graph")
add registry mocks for future testing
make a durty d3 implementation of the wanted behavior

Closes #9

:up:
@gregoryruiz I'm close to it :)

:up:


[fix] fix document link

Hi,
The previous URL pointed to a document page that resulted in a 404 error, this pull request updates it to a new accessible document page.

Thank you!


Correctly produce a raw transaction

I think all code is located in the transaction folder. Here we can find a general transaction builder, with high level methods to build a transaction with transparent and sapling inputs, but looks like not for orchard (unless this "zfuture" has something to do with it, still investigating).  This general tx builder groups the respective specific builders for the different types, sapling , transparent
The specific builders, generates a Bundle  object, which are then added to the final transaction data entity. Its curious, because there, we can also see the orchard bundle (apparently not present in the general builder). Orchard its the last key era, which uses a different underlying crypo technology (Halo2 zk prove system), which does not depend anymore from the initial crypto setup (params) of the blockchain. Maybe this is related and Orchard has other ways in code. Still investigating.

Looks like for the Orchard transaction data type, there are plans to include support in the general transaction builder commented before. Here are the relevant PRs in the Zcash repo:

https://github.com/zcash/librustzcash/pull/584
https://github.com/zcash/librustzcash/pull/583

I did not see wallets which currently supports Orchard transactions. Lets investigate further this later, as i am not fully sure.
So i think its OK going for the general transaction builder which already can create Sapling and Transparent transactions first, and then look for Orchard. Worst case, we need to create Orchard transactions with the specific builder.
Next steps

Provide test data generation for Sapling and Transparent transactions, by using the general builder.
Provide all new API implementations needed in the STATUS.md file. So we can start the API mapping for the missing types.

https://github.com/eigerco/uniffi-zcash-lib/pull/98 provides:

Adds examples for Transparent and Sapling transaction creation.
Updates STATUS.md with the needed entities for creating transactions.

Once approved:

We could start implementing the types added STATUS.md document by following the priorities described there.
Continue investigating the Orchard , once we have done the types for Sapling and Orchard.

Moving for review !

Looks like for the Orchard transaction data type, there are plans to include support in the general transaction builder commented before. Here are the relevant PRs in the Zcash repo:

zcash_primitives: Add Orchard to the transaction builder zcash/librustzcash#584
Add orchard bundle creation to zcash_primitives::transaction::builder::Builder zcash/librustzcash#583

Add orchard bundle creation to zcash_primitives::transaction::builder::Builder zcash/librustzcash#583 was sitting non-functional for a few months. I've been working on it actively again as of last week, I think it'll be ready to merge soon.

Many thanks for all the provided information @AloeareV !
For this project, i think we need to be aligned with main librustzcash repo. We would prefer to use the general transaction builder, as we think it would simplify implementation in our side, at least for covering basic use cases. Hope that PR gets merged soon. We will keep an eye on that. Again, thanks for your comment.

We have reached an initial draft implementation of all the needed types for the general transaction transaction builder. That means we currently can generate Sapling and Orchard transactions by using it.
Now we need to generate Orchard transactions. We are going to wrap the original Orchard bundle on its own builder and expose it through the UniFFI layer.
When the Orchard support for the transaction builder is merged, we might think on adding it to the current builder.

We added and merged transaction creation support for Transparent, Sapling and Orchard on this PR . We are proceding to close this issue and address the next ones in the milestone 4, which will complete the full transaction ecosystem implementation.


do not remove parent when adding bounding box

https://forum.babylonjs.com/t/question-on-gizmomanager/515/11
test PGs:
https://playground.babylonjs.com#0RFLMJ#4
http://localhost:1338/Playground/index-local.html#SG9ZZB
http://localhost:1338/Playground/index-local.html#DEYAQ5#47
http://localhost:1338/Playground/index-local.html#6E4LSB#15
http://localhost:1338/Playground/index-local.html#8GY6J8#20
http://localhost:1338/Playground/index-local.html#4TBMBR
http://localhost:1338/Playground/index-local.html#4TBMBR#1
http://localhost:1338/Playground/index-local.html#4TBMBR#2
http://localhost:1338/Playground/index-local.html#8MGKWK#25
Use the inspector

This pull request has been mentioned on Babylon.js. There might be relevant details there:
https://forum.babylonjs.com/t/question-on-gizmomanager/515/12


Tag second group of mods

Follow-up to #7542, the next most downloaded mods plus others that are related or have similar names.

#rebuild


Change character "class" to "specialization"

Character "Class" has some obvious drawbacks: class is vague and it's a reserved keyword in JavaScript and many languages.
I think the term "Specialization" might be appropriate to describe this.

Archers "specialize" in Archery
Magicians "specialize" in Magic
Rogues "specialize" in Stealth
Warriors "specialize" in War
etc.

Let's rename instances of Character "Class" in the project to "Specialization"

@njgrisafi would you like to take this one?

@mrpudn yes I'll take it!

hey btw, I'm trying to build this in more of a functional programming style, so it will probably look a bit crazy at first glance. I highly recommend this reading if you need to get a little acquainted:
https://drboolean.gitbooks.io/mostly-adequate-guide/
Some quick patterns to highlight:

Function currying is done using lodash's _.curry function, which I've aliased as util.curry.
Function composition is done using lodash's _.flowRight function, which I've aliased as util.compose
Function memoization is currently done by using lodash's _.memoise directly, but I need to get that aliased as util.memoise at some point

I'm trying to keep this kind of stuff aliased in util so that we have a bit more control over the functional programming bit - i.e. using compose() instead of flowRight() for the functional composition concept.
(I need to document this somewhere)

@mrpudn this is awesome I'll start reading into it. Also, I really like the idea of limiting the side-effects.
Maybe we can make a Developer guide doc? Where we can put references and useful development info...or is that the contributing doc

Awesome, yeah that's the kind of stuff we'd want to put into CONTRIBUTING.md, I'd think

@mrpudn Should we rename classes.yml to specialization.yml?
Then inside that data yml we will have something like:
specializations:

archery:
    name: Archery
    modifiers:
      strength: <int>
      intelligence: <int>
      dexterity: <int>
      endurance: <int>
      willpower: <int>
      luck: <int>

magic:
    name: Magic
    modifiers:
      ...


Update readme with progress and function overview

Marked milestone v0.1.1, even though 0.1.0 and 0.1.1 have no difference in surface area and were a result of manually testing the NuGet process.
For all intents and purposes, other than the published readme, they are equal.


Error running Makefile - controller-gen no such file or directory

Hello,
I've been trying to run the Makefile on a fresh Golang container (https://hub.docker.com/_/golang).  I set up kubectl and made sure it's connected to my cluster.
When I attempt to run the make file, I'm running into an issue on line 118:
https://github.com/Apicurio/apicurio-registry-operator/blob/master/Makefile#L118
Specific error message is:
root@091959c6e7c9:/go/apicurio-registry-operator# make build docker-push deploy
go: creating new go.mod: module tmp
Downloading<EMAIL_ADDRESS>go: added github.com/fatih/color v1.12.0
go: added github.com/go-logr/logr v1.2.0
go: added github.com/gobuffalo/flect v0.2.3
go: added github.com/gogo/protobuf v1.3.2
go: added github.com/google/go-cmp v0.5.6
go: added github.com/google/gofuzz v1.1.0
go: added github.com/inconshreveable/mousetrap v1.0.0
go: added github.com/json-iterator/go v1.1.12
go: added github.com/mattn/go-colorable v0.1.8
go: added github.com/mattn/go-isatty v0.0.12
go: added github.com/modern-go/concurrent v0.0.0-20180306012644-bacd9c7ef1dd
go: added github.com/modern-go/reflect2 v1.0.2
go: added github.com/spf13/cobra v1.2.1
go: added github.com/spf13/pflag v1.0.5
go: added golang.org/x/mod v0.4.2
go: added golang.org/x/net v0.0.0-20210825183410-e898025ed96a
go: added golang.org/x/sys v0.0.0-20210831042530-f4d43177bf5e
go: added golang.org/x/text v0.3.7
go: added golang.org/x/tools v0.1.6-0.20210820212750-d4cc65f0b2ff
go: added golang.org/x/xerrors v0.0.0-20200804184101-5ec99f83aff1
go: added gopkg.in/inf.v0 v0.9.1
go: added gopkg.in/yaml.v2 v2.4.0
go: added gopkg.in/yaml.v3 v3.0.0-20210107192922-496545a6307b
go: added k8s.io/api v0.23.0
go: added k8s.io/apiextensions-apiserver v0.23.0
go: added k8s.io/apimachinery v0.23.0
go: added k8s.io/klog/v2 v2.30.0
go: added k8s.io/utils v0.0.0-20210930125809-cb0fa318a74b
go: added sigs.k8s.io/controller-tools v0.8.0
go: added sigs.k8s.io/json v0.0.0-20211020170558-c049b76a60c6
go: added sigs.k8s.io/structured-merge-diff/v4 v4.1.2
go: added sigs.k8s.io/yaml v1.3.0
/go/apicurio-registry-operator/bin/controller-gen object:headerFile="hack/boilerplate.go.txt" paths="./..."
bash: line 1: /go/apicurio-registry-operator/bin/controller-gen: No such file or directory
make: *** [Makefile:118: generate] Error 127

I haven't seen anyone else with this issue but I'm puzzled as to what's causing the issue, and the Makefile script is kind of hard to follow.  If someone could point me in the right direction in troubleshooting this I'd appreciate it.

Hi, I think this is caused by controller-tools not supporting go 1.16 anymore and breaking compatibility. I've tried using go 1.17 and it seems to work, so I'll update the requirements. See https://github.com/kubernetes-sigs/controller-tools/issues/643 . Can you test if using 1.17 works for you?

Did you you the latest tag?


01.06.01

As a claimant, I want entered information to be remembered, so that I do not lose data.

Basic Flow:

The claim is saved after every change to a claim (creation, edit, delete, addition of expense)

Exceptions:

IO exceptions

This test might require the app in order to test.


testing for Guide is slow

any thoughts for speeding this up?

not critical but can be accelerated maybe

It's because of the high time complexity of VF2 algorithm counting node motif degree in preprocessing. Potential improvement is provided in #13.


feat(external-webui-redis): Add the possibility to use an external Redis Database

Signed-off-by: Lyonel Martinez<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If this PR will release a new chart version please make sure to also uncomment the following line:

/kind chart-release

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area falco-chart

/area falco-exporter-chart

/area falcosidekick-chart

What this PR does / why we need it:
Add the options to use an external database for the webui.
Now the Redis' values have an enabled member and the Webui's values have an externalRedis member, containing an enabled, an url and a port member.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Checklist

[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] CHANGELOG.md updated

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Lowaiz
To complete the pull request process, please assign leodido after the PR has been reviewed.
You can assign the PR to them by writing /assign @leodido in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

Welcome @Lowaiz! It looks like this is your first PR to falcosecurity/charts 🎉

Thanks. I will review in details asap. Can you just add in the descriptions of settings that the redis must have the redissearch module enabled, it's a requirement. Thanks

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Lowaiz
To complete the pull request process, please ask for approval from issif after the PR has been reviewed.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

I just think we need a way to make them exclusive
An exclusive test now is done in the beginning of the deployment-ui file.

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

Needs approval from an approver in each of these files:

OWNERS [Issif]

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

LGTM label has been added.  Git tree hash: 6317604b72ff0a89c1c7975cc14ab2521b96f759


Subgraph: Organization active

Adds active attr to Organization entity.
This is so we can filter by orgs that successfully completed the dao setup.
Note that for tracked orgs created outside GardensTemplate we set them as active on dao creation.

in which case happens that a dao didn't successfully completed the dao setup and is as inactive?

It requires 3 separate txs to create a garden, so when the dao is created through the first tx and the creators decide to not continue creating the garden for some reason.


Feature request: Add a select region for snapshots.

Your software looks very promising and it's the first video recorder that works this well with decent functions !
I'm missing one thing to make it my daily app:
I love the feature in Greenshot where you can draw your region to take a snapshot/screenshot.
I have set it as my Prt Scrn button.
So I need to keep on using Greenshot for screenshots, instead of Captura.
Could this be implemented?
PS:  Some bug: after restart the icons on the left got missing in action :)
https://i.imgur.com/rR1TT3h.png

Ability to draw region for screenshot is one of my priorities right now.
Will be doing it as soon as I have the time.
BTW, I have done a fix related to the icon missing error, but not released yet.
It happened for me after collapsing and then expanding the UI.
Here's a dev build to test: https://ci.appveyor.com/api/buildjobs/n9u0i6ys8bjgn9dh/artifacts/Captura-Portable.zip

Great ! Much better !!! :)

I've implemented something. 🎉
Please test dev build: https://ci.appveyor.com/api/buildjobs/ybc665w6s2hva0hk/artifacts/Captura-Portable.zip
A new option named Screenshot (Region) will be available in system tray menu.
A hotkey can be manually added (as of now) for this action.
Adding the hotkey

Go to Settings / Hotkeys.
Add new hotkey OR change task from dropdown of existing hotkey to ScreenShot (Region).
If you add new, make sure to check it to make it active, select action from dropdown and set keys by clicking on button.

So cool !!!!
Works, but not correct

I have 3 screens and when I screenshot region, it takes the next screen.
Also the drawing box is on the right side drawn. So it's always the next
screen on the right (these are my 3 screens)[image: 2018-09-16-12-56-15.jpg]

It would be handy to have a magnifier also like in greenshot. With pixel
size shown.

imgr upload gives error

But looking promissing so far ! Thanks for the quick response !
Met vriendelijke groeten | Bien à vous | Best regards,
Sven Godijn
Tel:// +32 (0)475/879 275
Skype: encountersmedia
Op za 15 sep. 2018 om 13:07 schreef Mathew Sachin<EMAIL_ADDRESS>
:

I've implemented something. 🎉
Please test dev build:
https://ci.appveyor.com/api/buildjobs/ybc665w6s2hva0hk/artifacts/Captura-Portable.zip
A new option named Screenshot (Region) will be available in system tray
menu.
A hotkey can be manually added (as of now) for this action.
Adding the hotkey

Go to Settings / Hotkeys.
Add new hotkey OR change task from dropdown of existing hotkey to ScreenShot
(Region).
If you add new, make sure to check it to make it active, select
action from dropdown and set keys by clicking on button.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MathewSachin/Captura/issues/261#issuecomment-421553191,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AlHLkl6uiTSUwpm1iJBIX-PZhkzqTx61ks5ubN9wgaJpZM4WpArR
.

I'm testing this. Might take some time simce i have only one monitor and cannot verify the issue.

I did not receive the image of your screens. Please upload them here on GitHub.

Got hold of a second screen. Did a fix!
Please test dev build: https://ci.appveyor.com/api/buildjobs/l2yxjox2ml0ax0r4/artifacts/Captura-Portable.zip
Still working on Magnifier...

Implemented Magnifier.
Please test: https://ci.appveyor.com/api/buildjobs/2wkxix8xkux4avcy/artifacts/Captura-Portable.zip

alright cool !

how can I turn on the magnifier? It doesn't work?
the imgr upload for screenshot doesnt work (did before) and I don't get
an url in the pasteboard either?

Met vriendelijke groeten | Bien à vous | Best regards,
Sven Godijn
Tel:// +32 (0)475/879 275
Skype: encountersmedia
Op ma 17 sep. 2018 om 16:01 schreef Mathew Sachin<EMAIL_ADDRESS>
:

Implemented Magnifier.
Please test:
https://ci.appveyor.com/api/buildjobs/2wkxix8xkux4avcy/artifacts/Captura-Portable.zip
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MathewSachin/Captura/issues/261#issuecomment-422028607,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AlHLklrRSwDgztFM_FLRFzgOQMtnAGciks5ub6tIgaJpZM4WpArR
.

Ow sorry, wrong version !
It works great ! :)
just that imgr isn't ploading like before
Met vriendelijke groeten | Bien à vous | Best regards,
Sven Godijn
Tel:// +32 (0)475/879 275
Skype: encountersmedia
Op ma 17 sep. 2018 om 16:01 schreef Mathew Sachin<EMAIL_ADDRESS>
:

Implemented Magnifier.
Please test:
https://ci.appveyor.com/api/buildjobs/2wkxix8xkux4avcy/artifacts/Captura-Portable.zip
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MathewSachin/Captura/issues/261#issuecomment-422028607,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AlHLklrRSwDgztFM_FLRFzgOQMtnAGciks5ub6tIgaJpZM4WpArR
.

maybe it would be better if the magnifier was left top next where you
start?
would be handy if you click the webcam thumbnail that it opens the big
preview?

Met vriendelijke groeten | Bien à vous | Best regards,
Sven Godijn
Tel:// +32 (0)475/879 275
Skype: encountersmedia
Op ma 17 sep. 2018 om 14:27 schreef Mathew Sachin<EMAIL_ADDRESS>
:

Got hold of a second screen. Did a fix!
Please test dev build:
https://ci.appveyor.com/api/buildjobs/l2yxjox2ml0ax0r4/artifacts/Captura-Portable.zip
Still working on Magnifier...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MathewSachin/Captura/issues/261#issuecomment-421994532,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AlHLkkWtMxQNBMirbXisPWDcetjBp5q5ks5ub5VMgaJpZM4WpArR
.

A 3 2 1countdown before recording would be handy?
Met vriendelijke groeten | Bien à vous | Best regards,
Sven Godijn
Tel:// +32 (0)475/879 275
Skype: encountersmedia
Op ma 17 sep. 2018 om 14:27 schreef Mathew Sachin<EMAIL_ADDRESS>
:

Got hold of a second screen. Did a fix!
Please test dev build:
https://ci.appveyor.com/api/buildjobs/l2yxjox2ml0ax0r4/artifacts/Captura-Portable.zip
Still working on Magnifier...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MathewSachin/Captura/issues/261#issuecomment-421994532,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AlHLkkWtMxQNBMirbXisPWDcetjBp5q5ks5ub5VMgaJpZM4WpArR
.

ow and cancel recording (or restart) is also handy :)
Met vriendelijke groeten | Bien à vous | Best regards,
Sven Godijn
Tel:// +32 (0)475/879 275
Skype: encountersmedia
Op ma 17 sep. 2018 om 14:27 schreef Mathew Sachin<EMAIL_ADDRESS>
:

Got hold of a second screen. Did a fix!
Please test dev build:
https://ci.appveyor.com/api/buildjobs/l2yxjox2ml0ax0r4/artifacts/Captura-Portable.zip
Still working on Magnifier...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MathewSachin/Captura/issues/261#issuecomment-421994532,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AlHLkkWtMxQNBMirbXisPWDcetjBp5q5ks5ub5VMgaJpZM4WpArR
.

just that imgr isn't ploading like before

This is working on my system. Are you behind a proxy, if so check your proxy settings in the app.

maybe it would be better if the magnifier was left top next where you start?

I suppose not. Having the magnifier next to mouse cursor, similar to Greenshot seems more handy.

would be handy if you click the webcam thumbnail that it opens the big preview?

This seems really handy, would do ASAP.

A 3 2 1countdown before recording would be handy?

There is a Start Delay option on Settings tab.

ow and cancel recording (or restart) is also handy :)

I think it's better to leave it as it is, i.e. stop and start again.

Nice job!
Dunno what's wrong with imgr, it worked before

About the Region video recording, would it be handier to have a frame region like ispring? Captura huge border is rather very intimidating on screen. You could add the functions to the lower bar like here: http://i.imgur.com/b4Nhe1O.jpg?2

You can start multiple instances of the same program, should be only 1

Copy output file path to clipboard => doesn't add the url to the copy paste function?

iSpring looks good, will give it a try.

I'm allowing multiple instances for users who might want to run multiple captures (preferably low FPS ones) on multiple monitors.

Url is copied to clipboard when image is now saved to file, in which case file path takes priority. It can be copied from the recent list.

PS I'm having some trouble making the webcam preview clickable. Will try my best still.

 Love it

If you have username, password check proxy authentication & enter credentials.

It's normal windows 10?

I meant to input the credentials in the app's proxy settings

yes I know but i don't have this, I only use Windows 10 so it should be no
problem with the imgr upload right?

I think I figured it out.
Please test this build: https://ci.appveyor.com/api/buildjobs/xly2swx8ip6o75p8/artifacts/Captura-Portable.zip

yes yes yes :)
it works now, thx, this is a very handy feature, because I share allot of screenshots to social media!

Now, regarding the webcam feature, why not just put the preview link/button on top of the app next to the small webcam thumb? If it doesn't work to overlay a blank button on top of the preview? :)

Ow, the IMGR link is not copied to the clipboard :)

I think the webcam stays active, even when the app is idle in the tray?

Ow, the IMGUR link is not copied to the clipboard :)

Have you turned on the Copy output file path to clipboard setting? It works for me.

yep it's on but I don't get the imgur url in the copy paste after screenshotting.
https://i.imgur.com/W4OdgoL.jpg
(If I click the messages tray with the url it does work.)

I think the webcam stays active, even when the app is idle in the tray?
It currently takes about a second to initialize the webcam. It is left active so that capture can be started immediately.

IMO the webcam should not be on all the time except when using the app for recording. Maybe set it to idle after few minutes?

There are 4 targets for screenshot saving (Disk, Clipboard, Imgur, Editor).
Is Clipboard active (disable this), if so Imgur link will not be put on clipboard

It's active, but it doesn't copy the link from imgur, instead it copies the clipboard file from memory. So I think it's one or the other. That works when disabling one.
https://i.imgur.com/axdb7Tj.jpg


python312Packages.bottleneck: 1.4.0 -> 1.4.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.bottleneck is: Fast NumPy array functions
meta.homepage for python312Packages.bottleneck is: https://github.com/pydata/bottleneck
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.4.2 with grep in /nix/store/723wdlijwgp0c7rb645kkg0b8q5551fp-python3.12-bottleneck-1.4.2
found 1.4.2 in filename of file in /nix/store/723wdlijwgp0c7rb645kkg0b8q5551fp-python3.12-bottleneck-1.4.2

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath

python311Packages.bottleneck
python311Packages.orange3
python311Packages.recordlinkage
python312Packages.bottleneck
python312Packages.orange3
python312Packages.recordlinkage

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/723wdlijwgp0c7rb645kkg0b8q5551fp-python3.12-bottleneck-1.4.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.bottleneck https://github.com/r-ryantm/nixpkgs/archive/ab20832614cb9332e92f8305309cdc4a80dfbed5.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ab20832614cb9332e92f8305309cdc4a80dfbed5#python312Packages.bottleneck

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/723wdlijwgp0c7rb645kkg0b8q5551fp-python3.12-bottleneck-1.4.2
ls -la /nix/store/723wdlijwgp0c7rb645kkg0b8q5551fp-python3.12-bottleneck-1.4.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 12 packages built:

python311Packages.bottleneck
python311Packages.bottleneck.dist
python311Packages.orange3
python311Packages.orange3.dist
python311Packages.recordlinkage
python311Packages.recordlinkage.dist
python312Packages.bottleneck
python312Packages.bottleneck.dist
python312Packages.orange3
python312Packages.orange3.dist
python312Packages.recordlinkage
python312Packages.recordlinkage.dist

Maintainer pings

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 362383

aarch64-darwin

:fast_forward: 4 packages marked as broken and skipped:

python312Packages.orange3
python312Packages.orange3.dist
python313Packages.orange3
python313Packages.orange3.dist

:x: 2 packages failed to build:

python313Packages.recordlinkage
python313Packages.recordlinkage.dist

:white_check_mark: 6 packages built:

python312Packages.bottleneck
python312Packages.bottleneck.dist
python312Packages.recordlinkage
python312Packages.recordlinkage.dist
python313Packages.bottleneck
python313Packages.bottleneck.dist


v0.5.0

I'd say we're a little overdue our next release. It would be good to close the following issues first:

[ ] https://github.com/PlasmaFAIR/fortitude/issues/95
[ ] https://github.com/PlasmaFAIR/fortitude/issues/29

Another minor problem: A fix diff is displayed for superfluous-implicit-none, and the output claims that running --fix will correct it, but this isn't yet implemented. There are a few possible solutions:

Implement fixes before the next release, possibly hidden behind the --preview setting
Edit the message to say fixes are coming soon
Hide the message for now

On the last point, maybe just remove the diff but keep the = help for now?

One more thing I think we should get in before 0.5:

[ ] https://github.com/PlasmaFAIR/fortitude/issues/118 revealed a bug in the config file reader, and though I attempted to fix it in https://github.com/PlasmaFAIR/fortitude/pull/119, this just seemed to add more bugs than it fixed. We should probably write a more robust config file reader and handle the merge with CLI args manually.

On the last point, maybe just remove the diff but keep the = help for now?

Perhaps, but I would like there to be a displayed diff at some point. I know ruff doesn't print diffs by default, but clippy does, and I find those more helpful than the sometimes-vague suggestions that ruff provides.

Sorry, yes I meant just hide it for now, but still display the = help


Adan/backward es5

We won't be adding support for 5.x Elasticsearch as this version of ES is not supported any longer and this library is no longer adding new features.


Create Entity Relational Diagram (ERD) for Receipt of Goods

Is your feature request related to a problem? Please describe.
Needed to set up DB schema.
Describe the solution you'd like
A third normal form ERD.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Initial ERD v1

ERD exists, refer to diagram.


Broken link

Link for GTM is not working anymore. Also, I think the sign in link should point to the Partner Center, since now this portal is the starting point when becoming a publisher.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 467c5737-af04-369d-b2a0-eaae886ad1d0
Version Independent ID: f65e4274-4bef-cbbf-a437-f2a14dd2d28e
Content: Go-To-Market Services - Marketing best practices
Content Source: articles/marketplace/gtm-marketing-best-practices.md
Service: marketplace
GitHub Login: @qianw211
Microsoft Alias: ellacroi

@miababii Thanks for bringing this to our attention. This issue is being assigned to the content author to review and update as appropriate.
@qianw211 FYI.

#please-close this issue is no repro, the link is working.  Thanks!


[php/array/array_intersect.js] Simpler option

[x] Have you checked the guidelines in our Contributing document?

Description
Wouldn't this be simpler?
export const intersection = (arr1, arr2) => {
  return arr1.filter(x => arr2.includes(x));
};

The problem with this is that this only compares array two with array one. If you look at the implementation, array_intersect() can take can take multiple arrays, and even objects, then compare all of them.
//   example 1: var $array1 = {'a' : 'green', 0:'red', 1: 'blue'}
//   example 1: var $array2 = {'b' : 'green', 0:'yellow', 1:'red'}
//   example 1: var $array3 = ['green', 'red']
//   example 1: var $result = array_intersect($array1, $array2, $array3)
//   returns 1: {0: 'red', a: 'green'}

Correct, this boils down to locutus.objectsAsArrays. When enabled we need to treat javascript objects as php arrays, enabling a larger compatibility surface.


Avoid deleting and setting identical voice commands

Bug Report
Currently, setting voice commands doesn't check for a diff of which voice commands are in the old and new lists. This results in a case where if voice commands are set like so:
voiceCommands = [command1, command2, command3]
voiceCommands = [command1, command2, command3, command 4]

What will happen is command1/2/3 will be set to the head unit, then command1/2/3 will be deleted from the head unit, then command1/2/3/4 will be set to the head unit.
Because voice commands can be so slow to process, we should diff and only set / delete what is necessary instead of taking an all-or-nothing approach.

Corresponding issues: iOS, JavaScript Suite


binjr 3 beta feedback

This is a thread to support discussions and feedback around the beta phase for binjr 3.

Replacing this with a discussion thread: https://github.com/binjr/binjr/discussions/107


Random seed in tf.keras.initializers.RandomNormal does not work in Tensorflow 2.7.0

Please go to TF Forum for help and support:
https://discuss.tensorflow.org/tag/keras
If you open a GitHub issue, here is our policy:
It must be a bug, a feature request, or a significant problem with the documentation (for small docs fixes please send a PR instead).
The form below must be filled out.
Here's why we have that policy:.
Keras developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.
System information.

Have I written custom code (as opposed to using a stock example script provided in Keras): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Google Colab
TensorFlow installed from (source or binary):
TensorFlow version (use command below): 2.7.0
Python version: 3.7.12
Bazel version (if compiling from source): N/A
GPU model and memory: N/A
Exact command to reproduce: N/A

You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with:
python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
Describe the problem.
Describe the problem clearly here. Be sure to convey here why it's a bug in Keras or why the requested feature is needed.
Describe the current behavior.
Two instantiations of tf.keras.initializers.RandomNormal(..) objects with the same seed does not produce the same sequence.
Describe the expected behavior.
From the documentation here:
 tf.keras.initializers.RandomNormal(
     mean=0.0, stddev=0.05, seed=None
 )

Regarding the seed parameter, the documentation states:

... Note that seeded initializer will not produce same random values across multiple calls, but multiple initializers will produce same sequence when constructed with same seed value.

I would expect that if I pass the same seed as a parameter into the two instantiations of initializers.RandomNormal, temp and temp2, both should give the same weights on the first call, which is what I'm observing in Tensorflow 2.3.0, 2.5.0, and 2.6.0 (example), but not 2.7.0.
Contributing.

Do you want to contribute a PR? (yes/no): No
If yes, please read this page for instructions
Briefly describe your candidate solution(if contributing):

Standalone code to reproduce the issue.
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
Using tensorflow version 2.7.0:
https://colab.research.google.com/drive/1paNe8kBRzwkrZHBi7QF0yhEX8pXO0f1w?usp=sharing
However, using tensorflow 2.6.0, this issue does not occur (note one has to restart the notebook after the pip install in the first cell before running the second cell):
https://colab.research.google.com/drive/10KrXpJtxiaAmnI2vKa61hDNheqjiJyu9?usp=sharing
Source code / logs.
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.

Yes, I have also observed this behaviour.
The problem is that the new codepath using the tf.random.Generator is not enabled:
https://github.com/keras-team/keras/blob/5d2993b78603bda911f0a4912d08b1e5f36eb633/keras/backend.py#L1752-L1757
so the legacy methods like tf.random.normal are used instead https://github.com/keras-team/keras/blob/5d2993b78603bda911f0a4912d08b1e5f36eb633/keras/backend.py#L1864-L1872
and these are stateful and do not return the same values for the same seeds.
Note that as a hack, you can "switch" to the new behaviour by using
import keras
keras.backend.enabled_generator_for_rng()

Adding @qlzh727 who authored the commits.
Note that the current behaviour is contradicting the documentation of the initializers
https://github.com/keras-team/keras/blob/5d2993b78603bda911f0a4912d08b1e5f36eb633/keras/initializers/initializers_v2.py#L257-L261
stating that

"but multiple initializers will produce same sequence when constructed with same seed value"

which is quite unfortunate.

See https://github.com/keras-team/keras/issues/15586 for more details. The short answer is that you either need to force the generator code path, which we will turn on by default soon, or you need to call tf.random.set_seed() in addition to make the generator to produce same sequence.

Close this bug since this is a duplicate with https://github.com/keras-team/keras/issues/15586


Iteration Planning Meeting - Well Established, Never Published

These are similar to SCRUM Spring planning sessions but have our own Tanzu Labs twist.

Closing this "stub". New version will be created by contributors soon.


Added overlap 36

Issue solved:
1.https://github.com/KwickerHub/WebCraftifyAI/issues/445
Description:
I have overlapblock/overlapblock_36_by_Sahaja_Thota.html.
Output Preview:
1.overlapblock_36

@MaverickDe, Thanks for reviewing my pull requests and merging them.
Thanks,
Sahaja


Monitoring Section Needs a ReadMe

Ask: As a consumer of AVS Monitoring automation, I need to understand what I am deploying. There are no screenshots or explanation of the portal experience. At minimum, there should be links to this.
Current Experience: Customer has to navigate to Brownfield Section which is not straightforward to find. They then have to click on each link in the monitoring section and review the Bicep or ARM.
Ideal experience:

Readme of why and how to use the automation with end result as a screenshot
[Optional] - Short video (10 mins or less) on how to deploy the monitoring.

@husamhilal Is this something you can help us?

@rybirk  could you please assist with this issue?

@prasad3017 I also created a story: https://dev.azure.com/CSUSolEng/Accelerator - AVS/_workitems/edit/29183/

@husamhilal Is this something you can help us?

Is help still needed?
If Yes, I can work on it.
Please let me know.

Yes sir. Please help
From: Husam Hilal @.>
Sent: Tuesday, June 27, 2023 12:36 PM
To: Azure/Enterprise-Scale-for-AVS @.>
Cc: Prasad Gandham @.>; Mention @.>
Subject: Re: [Azure/Enterprise-Scale-for-AVS] Monitoring Section Needs a ReadMe (Issue #270)
@husamhilalhttps://github.com/husamhilal Is this something you can help us?
Is help still needed?
If Yes, I can work on it.
Please let me know.

Reply to this email directly, view it on GitHubhttps://github.com/Azure/Enterprise-Scale-for-AVS/issues/270#issuecomment-1610030124, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQBLLY45SKKYGXZMNTNG4GTXNMRYTANCNFSM6AAAAAAZE7MJQU.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@husamhilal hope all is well. Kindly let me know if we can close this in Aug 2023.

On the backlog.


bugfix:  for #3740

Fix for #3740.
Motoko uses the syntactic tuple arity of a message return type to determine the message return arity.
actor {
  type Unit = ();

  public func f() : async Unit {
  };

  public func go() : async () {
    await f();
  };

}

This means that f and go have different signatures:

f returns 1 result that is a 0-tuple.
g returns 0 results.

Getting this to work correctly requires some additional impedance matching in the async lowering phase to deal with functions like f, which used to crash moc (but now don't).

I don't grok the fix yet. For me this is a problem of being a syntactic tuple in the return type or not. In the latter case it is a unary return, in the former the return arity is given by the syntactic arity of the tuple.

Yeah, I find it hard to get my head around this too and am not 100% confident about the fix though it seems to work.
The problem is that we lose the syntactic distinction  once we are in the IR and need to do some additional impedance matching.
I think fundamentally the problem is that `T.seq (T.as_seq (T.seq [()])) == [] <> [()]' and that is biting us here.

Would the problem only happen with first class unary tuple Unit, or other first class tuples as well?

Would the problem only happen with first class unary tuple Unit, or other first class tuples as well?

 I'll test tomorrow.

Would the problem only happen with first class unary tuple Unit, or other first class tuples as well?

I'd have expected a fix to be touching the desugaring, but not the IR - at the level of the IR I'd have hoped that no more syntactic disambiguaties remain.

Yeah, I did look there but wasn't able to spot the problem. I'm not super happy about this fix, but it was the only one I could make stick. I'll have another go tomorrow, after checking the tuple thing.

Ok, I've extended the fix to pairs and other tuples, including the tests. Although this might not be the right fix, it might be worth getting this in until I figure out what it is. Suggestions welcome ;->
PTAL @nomeata @ggreif

Is that something we can check in the IR checkers?

Is that something we can check in the IR checkers?

I'm not sure what to check, but the IR checker caught the bug in the first place (good thing we didn't turn it off by default)
I wonder if the ultimate problem is that async types don't have an n-ary payload at the moment, so we are losing too much info in the desugaring (or some transformation). On the other hand, I don't want to make them n-ary so we can later support some abstraction over them. Will mull it over...

@ggreif Just got another non-det failure in timer.mo... (ic-ref)
test-ic-ref-run> Some tests failed:
test-ic-ref-run> timer.mo
test-ic-ref-run> make: *** [Makefile:4: all] Error 1
test-ic-ref-run> make: Leaving directory '/private/tmp/nix-build-test-ic-ref-run.drv-0/test-run-drun-src/run-drun'
error: builder for '/nix/store/8q4rr1s0wh75v34gv9msppdizswzhn8v-test-ic-ref-run.drv' failed with exit code 2;
       last 10 log lines:
       > tailpositions-actor: [actor1.ic-ref-run.comp] [actor2.ic-ref-run.comp] [ic-ref-run]skipped (no drun)
       >
       > upgrade-hooks: [upgrade-hook.ic-ref-run.comp] [upgrade-hook0.ic-ref-run.comp] [upgrade-hook1.ic-ref-run.comp] [upgrade-hook2.ic-ref-run.comp] [ic-ref-run]skipped (no drun)
       >
       > upgrades: [upgrade.ic-ref-run.comp] [upgrade0.ic-ref-run.comp] [upgrade1.ic-ref-run.comp] [upgrade2.ic-ref-run.comp] [upgrade3.ic-ref-run.comp] [upgrade4.ic-ref-run.comp] [ic-ref-run]skipped (no drun)
       >
       > Some tests failed:
       > timer.mo
       > make: *** [Makefile:4: all] Error 1
       > make: Leaving directory '/private/tmp/nix-build-test-ic-ref-run.drv-0/test-run-drun-src/run-drun'
       For full logs, run 'nix log /nix/store/8q4rr1s0wh75v34gv9msppdizswzhn8v-test-ic-ref-run.drv'.
error:
nix-build-uncached: nix build failed: exit status 1

https://github.com/dfinity/motoko/actions/runs/4053633247/jobs/6974477511

Just got another non-det failure in timer.mo... (ic-ref)

Looks like making an originally intentionally deterministic tool non-deterministic because of time-based concurrency bites…

LGTM! will you write a follow-up issue?

I'll keep the original one open.


DLRM: save downloaded and generated files outside of Docker containers

The CPU and GPU Docker images are pretty bare bones. One needs to launch a container, and then run the corresponding kickstart.sh to clone repos, download a model, generate fake data, etc. If the container gets killed, one needs to start from scratch. Also, two different containers do not share the data. I believe this can be improved.

Suppose I want to experiment under WORKSPACE=/datasets/mlperf-inference-v0.7 by repeating commands from either kickstart.sh script.
Clone the training and inference repos
$ cd $WORKSPACE
$ git clone --progress --recurse-submodules https://github.com/mlperf/training.git
$ git clone --progress --recurse-submodules https://github.com/mlperf/inference.git
$ export DLRM_DIR=$WORKSPACE/training/recommendation/dlrm

Download the ~10GB model
$ cd $WORKSPACE/inference/v0.5/recommendation
$ mkdir ./model
$ curl https://dlrm.s3-us-west-1.amazonaws.com/models/tb0875_10M.pt --output model/dlrm_terabyte.pytorch
$ export MODEL_DIR=$WORKSPACE/inference/v0.5/recommendation/model

Generate fake data
$ cd $WORKSPACE/inference/v0.5/recommendation
$ python -m pip install numpy --user
$ cd tools/
$ ./make_fake_criteo.sh terabyte0875
$ mv fake_criteo/ ../
$ export DATA_DIR=$WORKSPACE/inference/v0.5/recommendation/fake_criteo

It's worth noting several things:

make_fake_criteo.sh calls quickgen.py which is also in the tools/ directory; hence, the need to descend there first;
quickgen.py needs NumPy;
the generated data is in fake_criteo/, not in fake_data/ (maybe only for terabyte0875?)

Now, I can build the CPU and GPU Docker images:
$ cd $WORKSPACE/inference/v0.5/recommendation
$ docker build -t dlrm-cpu docker_cpu/.
$ docker build -t dlrm-gpu docker_gpu/.

and launch either of them mapping the inference and training repos as follows:
$ docker run -it \
-v $WORKSPACE/inference:/root/inference \
-v $WORKSPACE/training:/root/training \
dlrm-cpu

root@8042646de2b5:~# ls -la
total 44
drwx------  1 root root 4096 May 21 00:06 .
drwxr-xr-x  1 root root 4096 May 21 00:06 ..
-rw-r--r--  1 root root 3166 May 20 18:42 .bashrc
drwxr-xr-x  1 root root 4096 May 20 18:45 .cache
drwxrwsr-x  2 root root 4096 May 20 18:45 .conda
-rw-r--r--  1 root root   34 May 20 18:42 .condarc
drwxr-xr-x  2 root root 4096 May 20 18:45 .empty
-rw-r--r--  1 root root  148 Aug 17  2015 .profile
drwxrwxr-x 11 1000 1001 4096 Apr 30 09:23 inference
-rwxrwxr-x  1 root root  978 May 20 09:14 kickstart.sh
drwxrwxr-x 17 1000 1001 4096 May 20 23:31 training

Finally, do a bunch of straightforward exports as above:
root@8042646de2b5:~# export WORKSPACE=/root
root@8042646de2b5:~# export DLRM_DIR=$WORKSPACE/training/recommendation/dlrm
root@8042646de2b5:~# export MODEL_DIR=$WORKSPACE/inference/v0.5/recommendation/model
root@8042646de2b5:~# export DATA_DIR=$WORKSPACE/inference/v0.5/recommendation/fake_criteo

Apologies if I've got at this at the wrong end. Maybe I was only supposed to do:
$ export DLRM_DIR=$WORKSPACE/training/recommendation/dlrm
$ export DATA_DIR=$WORKSPACE/inference/v0.5/recommendation/fake_criteo
$ export MODEL_DIR=$WORKSPACE/inference/v0.5/recommendation/model
$ cd $WORKSPACE/inference/v0.5/recommendation
$ ./run_and_time.sh pytorch dlrm terabyte0875 gpu
mkdir: cannot create directory ‘/datasets/mlperf-inference-v0.7/inference/v0.5/recommendation/output/pytorch-gpu’: Permission denied
Sending build context to Docker daemon  6.094GB
...

Even when I create $WORKSPACE/inference/v0.5/recommendation/output/pytorch-gpu/dlrm/ by hand, I get:
$ cat output/pytorch-gpu/dlrm/output.txt
docker: invalid reference format.
See 'docker run --help'.

Is this still an issue @psyhtest? you may want to tag Maxim. Otherwise please close this issue?


Hidden Quests

Allowing Hidden Quests: it might be helpful to allow quests to be hidden so that players cannot see them even if they are active. This would give the GM a tool to keep track of things without needing to keep them as inactive. Subquests of a hidden quest should not identify themselves as a subquest.

Shipped in 0.7.4 which is now available.


Add diffutils library to fix test failure messages

This is a dependency of Google truth library, but it is not pulled in transitively. When a test fails, instead of the textual diff we'd get a ClassNotFoundException.
Fix #2068
Checklist

[x] I have filed an issue about this change and discussed potential changes with the maintainers.
[ ] I have received the approval from the maintainers to make this change.
[x] This is not a stylistic, refactoring, or cleanup change.

Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.
Discussion thread for this change
Issue number: #2068
Description of this change

@googlebot I signed it!

Not sure why it wouldn't find my repository. I have two forks, one private and one public. The repository name in the public fork is not intellij, not sure if that's the problem:
# Updating existing repository mirror to find commit d68ce9cbb6b4993b1b5a0ee9dbd6a08ec2e6df17
--
  | $ git --git-dir /var/lib/gitmirrors/https---github-com-bazelbuild-intellij-git remote set-url origin https://github.com/bazelbuild/intellij.git
  | $ git --git-dir /var/lib/gitmirrors/https---github-com-bazelbuild-intellij-git fetch origin iuliand-db:upstream-port/diffutils-lib
  | fatal: Couldn't find remote ref iuliand-db

Closing as diffutils is added by https://github.com/bazelbuild/intellij/commit/28fa184052538042db44db83a3fb4ae2a84227b5


Fix PropTypes deprecation issue

This resolves the deprecation warning you get when using React 15.5

Thanks @paltman 👍 Unfortunately won't  be able to publish this until end of May as I'm away with just me phone


Styling updated dashboard

styling the updated dashboard (#60)
I styled the login and sign up components. Now you can switch between two components instead of stacking.

What a cool idea, thanks @anniethewebcoder 🙏


review HR and admin scopes

[ ] check what scopes should be added/removed
[ ] adjust it on dev
[ ] create migrations for demo

declaration_request:write is missing for HR

scopes has been reviewed by PO and applied to all the envs


Graceful shutdown

when calling jobrunner.Stop, does it gracefully wait for running jobs to stop,  or does it abruptly stop running jobs ?

@changwuf31  yes it's graceful.

Stop ALL active jobs from running at the next scheduled time


Add UseeTV EPG

Here's EPG of all channels on https://www.useetv.com/tv/live, by getting it's schedule from the TV On Demand page (https://www.useetv.com/tvod/metrotv). Even though some channels don't over TVOD, the schedules can still be seen on the page.
It only works for getting today's schedule only, no future schedules.

And I couldn't add the workflow config. Here's the one that I wanted to do.
name: useetv.com
on:
  schedule:
    - cron: '0 7 * * *'
  workflow_dispatch:
  workflow_run:
    workflows: [_trigger]
    types:
      - completed
jobs:
  load:
    uses: ./.github/workflows/_load.yml
    with:
      site: ${{github.workflow}}
    secrets:
      APP_ID: ${{ secrets.APP_ID }}
      APP_PRIVATE_KEY: ${{ secrets.APP_PRIVATE_KEY }}

Hello, @freearhey. Would it be possible to update the schedule to 0 7 * * * (00:00 GMT+7)? This website doesn't do future schedules, and having it on 0 0 * * * (17:00 GMT+7) would mean the today's schedule would only work for the next 7 hours.

Resolves #657 (Didn't see that issue beforehand lol)

Updated.

Please check xmltv-id again (case is also important).


chore(deps): update common-dev-assets digest to 5c14bd5

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
47749e1 -> 5c14bd5

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: