Support Wildcard in IP Filtering

Right now, it's easy to say "I want to allow all traffic except for these IPs"
Right now, there's no way to say "I want to disallow all traffic except these IPs"
Most ACLs (like firewalls) support wildcards for this purpose. We should support wildcard matching of IPs to make this more flexible. Example:
   <ipFiltering>
      <ipAddresses>
        <add address="<IP_ADDRESS>" />
        <add address="<IP_ADDRESS>" denied="true" />
        <add address="*" denied="true" />
      </ipAddresses>
    </ipFiltering>

These rules should then be applied sequentially

Closing as wont do. This can be re-opened if we do.


[Bug] Vertical alignment

add a .verticalAlignment parameter so the text can be either centered on top, center or bottom of the position point.
or improve the .alignment parameter to accept a 2 size String Array for both alignments: [Horizontal, Vertical]

I was using .center() to center everything to the position point, but when I change the text value, it decenters...

ok, seems like .baseline is the verticalAlignment... well, it's not working... seems to only align it to the first line and not the whole text.

Hi @joex92, I will be looking into this soon, thanks for opening the issue

nice thanks... I believe instead of a new parameter better fix how .baseline works on a multiline text... It's working like in the original Two.Text object, which aligns vertically on 1 line (because Two.Text is only 1 line of text), but in this case it should align vertically across all the lines... +1

Yes indeed, after looking deeper at your issue, it looks like it's not about a bug with how baseline works but more about requesting a new feature that would set a vertical anchor point to the whole text. « Baseline » does refer to a single line alignment so changing its behavior as you propose would be semantically confusing.
I believe this is not in the scope of this library and should be done using the methods already provided by Two.js. For instance, to vertically and horizontally center a whole text on point (200; 200):
const position = new Two.Vector(200, 200)
const text = new MultilineText('Hello\nWorld', 0, 0, { alignment: 'center' })

// Get the rendered bounding rect of the text
const rect = text.getBoundingClientRect()

text.translation.x = position.x - rect.width / 2
text.translation.y = position.y - height / 2

it shouldn't be confusing, because this is a MultilineText object, so it should make sense that .baseline should anchor vertically across all the lines...
the original Text object shouldn't fix this, because the Text object is not intended for multiple lines, so it will only work for 1 line and it wouldn't need a fix for something that is not intended for, otherwise MultilineText wouldn't even exist...
It actually is more confusing to do extra steps just to have an anchor center vertically... 🤷🏼♂

I'm sorry, I truely insist on my previous point, please read the linked wikipedia page for more informations about the strict meaning of "Baseline".
In twojs you would have to do those "extra steps" to center basically any shape. I'm trying to keep this library consistent with the API it lives in. Feel free to fork and edit it though.


Installation fails on Apple Silicon (M1)

Diagrams rules.
I love diagrams, long since replaced using dot native.
recently I upgraded to an M1 mac, and unfortunately diagrams doesn't seem to work on M1.
npm install -g diagrams
fails due to an electron dependency.
Electron will only work with 11.0 or above on m1 - so I checked out this diagrams repository and replaced the dependency, and install npm install . but then it says it installs fine, yet does not / diagrams doesn't work.
I'm not a node developer and the chance of me figuring this out and contributing a solution is very low.
I write in case anyone else has successfully gotten diagrams to install on M1.

i am also facing similar issue

<EMAIL_ADDRESS>postinstall /usr/local/lib/node_modules/diagrams/node_modules/electron
node install.js

internal/modules/cjs/loader.js:905
throw err;
^
Error: Cannot find module '/usr/local/lib/node_modules/diagrams/node_modules/electron/install.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
at Function.Module._load (internal/modules/cjs/loader.js:746:27)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:75:12)
at internal/main/run_main_module.js:17:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/diagrams/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!


proposal: log/syslog: Discussion of connect() connections for Dial (or alternative)

As a continuation of https://github.com/golang/go/issues/64165#issuecomment-1813527171.

I don't think connect should establish a connection in Dial, but to ensure that it's available, consider adding a Ping to verify it.
Of course, for backward compatibility, we can not adjust the original function of Dial, we can add a new method, such as Open to solve this problem.

We don't use the issue tracker for discussions.
What's being proposed here?

Example: https://github.com/golang/go/pull/64326/files
package syslog_test

import (
	"fmt"
	"log"
	"log/syslog"
)

func main() {
        // If host:port is actually unavailable
	syslog, err := syslog.Open("tcp", "host:port", syslog.LOG_WARNING|syslog.LOG_DAEMON, "tag")
	if err != nil {
		log.Fatal(err)   // <-----  There will be nil
	}

	if syslog.Ping() != nil {
		log.Fatal(err)  // <-----  There will be an error
	}

	syslog.Info("This is a daemon warning with tag.")
}

Operation error. Merged above ignored


[Bug]: Appsmith Cloud Deployed App: Reports not rendering

Is there an existing issue for this?

[X] I have searched the existing issues

Description
I have 2 HTML reports in my App.  One is in an iFrame, one is in a Custom Widget.  They render when I am in Edit mode.  Once I deploy the app and click on the tabs containing the reports, they do not render.  The Edited version is here and<EMAIL_ADDRESS>should have access:  https://app.appsmith.com/app/custom-widget-learn/cw-report-65cff18b3b4d031a736a6472/edit/widgets/tfrv61xqwo
Steps To Reproduce

Go to the link (edit mode)
Pick a date from select widget at top.
click on the Report tab.  (Report should render)
click on the CW Vanilla tab.  (Report should render)
Deploy the App.
Repeat steps 3 and 4.

Public Sample App
https://app.appsmith.com/app/custom-widget-learn/cw-report-65cff18b3b4d031a736a6472/edit/widgets/tfrv61xqwo
Environment
Deploy Preview
Issue video log
https://www.loom.com/share/a7665cd45ca441d9acc0d4dd734e65a4?sid=e0ea77c3-1f6a-474d-8f08-360b7526e9a3
Version
Cloud (Latest?)

https://theappsmith.slack.com/archives/C0341RERY4R/p1709102932216419?thread_ts=1708940270.741669&cid=C0341RERY4R

I got this trying the link:
[cid:032a3051-1e41-4854-bd9e-a1dba9278d1b]

From: balajisoundar @.>
Sent: Wednesday, February 28, 2024 12:50 AM
To: appsmithorg/appsmith @.>
Cc: pchambless @.>; Author @.>
Subject: Re: [appsmithorg/appsmith] [Bug]: Appsmith Cloud Deployed App: Reports not rendering (Issue #31288)
https://theappsmith.slack.com/archives/C0341RERY4R/p1709102932216419?thread_ts=1708940270.741669&cid=C0341RERY4R
—
Reply to this email directly, view it on GitHubhttps://github.com/appsmithorg/appsmith/issues/31288#issuecomment-1968339627, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKWYZBLHFOBL4IOIMSK57SLYV3HTFAVCNFSM6AAAAABD2JJJAOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRYGMZTSNRSG4.
You are receiving this because you authored the thread.Message ID: @.***>


Cannot install in El Capitan

I've been working on this for a while and it's the simplest thing....I NEED to simply install express so I can move on and actually work.  No matter what I do I get this same error and express won't install:
`➜  ~ npm install -g express
npm WARN checkPermissions Missing write access to /Users/revjtanton/.nvm/versions/node/v0.12.2/lib/node_modules/express
/Users/revjtanton/.nvm/versions/node/v0.12.2/lib
└──<EMAIL_ADDRESS>npm ERR! Darwin 15.6.0
npm ERR! argv "node" "/Users/revjtanton/.nvm/versions/node/v0.12.2/bin/npm" "install" "-g" "express"
npm ERR! node v0.12.2
npm ERR! npm  v3.9.3
npm ERR! path /Users/revjtanton/.nvm/versions/node/v0.12.2/lib/node_modules/express
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! Error: EACCES, access '/Users/revjtanton/.nvm/versions/node/v0.12.2/lib/node_modules/express'
npm ERR!     at Error (native)
npm ERR!  { [Error: EACCES, access '/Users/revjtanton/.nvm/versions/node/v0.12.2/lib/node_modules/express']
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   path: '/Users/revjtanton/.nvm/versions/node/v0.12.2/lib/node_modules/express' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! Please include the following file with any support request:
npm ERR!     /Users/revjtanton/npm-debug.log`
I've managed permissions, cleaned caches, tried installing with sudo (which doesn't produce an error...but I'm still not able to use express).

try sudo chown -R $(whoami) /Users/revjtanton/.nvm.  It is clearly a permissions problem.
FWIW, I am not sure why you would ever want to install express globally, so I would also caution you to drop the -g and install it in the project in which you are using it, which would also avoid this issue.

I have tried that exact command and also tried installing express in the app I'm building with npm install express --save and neither seem to fix this.


Pending faucet request

It's an amazing project!
I tried sending in some faucet to the address below and it's been showing pending for 30mins now. Thanks
tb1qwgp4x4c90da5pk300ws9ut2clmuche35qnz5fz

Hi @Graceruchi1, this isn't an Explorer issue. You'll find help at the #support Discord channel.


Why autocompletion doesn't works

To others that might be interested in this issue. It's not implemented.
I don't really know how to deal with this, we'd have to dive into the code of sqlite-cpp, but the maintainer is a very cool person, I'm sure they'd help us with this :)
Anyone! Feel free to tackle it, I'm always around to  help answering questions


Request to add DOM Manipulation Coding Challenges for JavaScript

Is your feature request related to a problem? Please describe.
No, my feature request isn't related to a problem.
Describe the solution you'd like
I want a dedicated section for DOM Manipulation to learn it. I feel it's an important topic to learn but there's no section to learn it here. Kindly add that Learning Section as it would be beneficial for us.
Describe alternatives you've considered
I haven't considered any alternatives for this feature.
Additional context
No response

Hello there,
Thank you for taking the time to open this.
We do have this on the roadmap for the new curriculum. For now, we have the following sections on DOM manipulation:

https://www.freecodecamp.org/learn/front-end-development-libraries/#jquery
https://www.freecodecamp.org/learn/front-end-development-libraries/#react
https://www.freecodecamp.org/learn/data-visualization/#json-apis-and-ajax

As such, I am closing this as on the roadmap.

I had meant DOM Manipulation in JavaScript.

I had meant DOM Manipulation in JavaScript.

https://www.freecodecamp.org/learn/data-visualization/json-apis-and-ajax/handle-click-events-with-javascript-using-the-onclick-property
Also, jQuery is a JavaScript library, and React is a JavaScript framework.


*: fix not and ! restored

Signed-off-by: wjhuang2016<EMAIL_ADDRESS>
What problem does this PR solve?
What is changed and how it works?
Fix https://github.com/pingcap/tidb/issues/17791
Check List
Tests

Unit test

Code changes
Side effects
Related changes

Need to cherry-pick to the release branch

/merge

/run-cherry-picker


Does Custom Training train model from scratch or use transfer learning?

Want to ask a question:
Does Custom Training train model from scratch or use transfer learning?
I am using tensorflow hub's retrain example to train an Image classification but the accuary doesn't meet my need, wonder if ImageAI's Custom Training would do a better job.
from imageai.Prediction.Custom import ModelTraining

model_trainer = ModelTraining()
model_trainer.setModelTypeAsResNet()
model_trainer.setDataDirectory("Datas/Research")
model_trainer.trainModel(num_objects=2, num_experiments=100, enhance_data=True, batch_size=32, show_network_summary=True)

It depends. On the code sample you are providing, it train from scratch.  Checkout the docs on how to do this.


Change Person to Student

Person model is currently used to represent a student. It might be better to refactor this to Student for easier understanding.

Might be better to move to early v1.5 instead?
I don't think we have the time to fit a chonky refactor like this into the tight v1.4 timeline. Might be better doing the refactor as the first thing for v1.5.

Yes, you are right. Let's move this to v1.5.


ghes support in gei

[ ] Did you write/update appropriate tests
[ ] Release notes updated (if appropriate)
[ ] Appropriate logging output
[ ] Issue linked

Looks like we're on the same page! I have some of these changes in our wip PR as well: https://github.com/github/gh-gei/pull/221

abandoning this change, may come back to it in the future as a refactoring to move the base URL to GithubClient


BUG: Unable to send magic link in the latest release development

Bug description and reproduction:
Go to login > enter your email in the first field for the magic link > submit > page reloads

Expected behavior:
The user should be informed that an email has been sent over to their mail.

Additional details:
When checking the logs, the following errors show.

Running the project locally doesn't result in this issue, this issue only occurs when running it through docker or docker compose.

the user get informed, when the page redirects to the NuxtAuth's confirmation page.

the user get informed, when the page redirects to the NuxtAuth's confirmation page.

This is the expected behavior, however it is still not happening.


Modify TeXFoldText to deal with '*' in sections.

Yeah, everything is in the title.
I made a small change so sections written like that "\section*{something}" would keep showing nicely.
The little '*' is for sections without a number showing.

Looks good, thanks!


Check storage format tests for regressions

We validate the stability of the storage format through tests that ensure that a key produced by an older version can still be read by a newer version. Expand abi_check.py to complain if such tests are removed. Resolves #4481.
Design: make a list of the test data lines (lines with function_name:parameter1:parameter2:…) of generated PSA test cases in the old version and in the new version. Complain about lines in the old version that are missing from the new version.
Status: works, with minor issues. But I'm not completely sure about the design.

Needs documentation updates, at least the storage format test strategy.
The brief output for storage format errors is not brief.
Currently the validation looks at all generated test cases. Should it look at manual test cases? Should it restrict itself to read-old-data tests, as opposed to format-of-new-data?

Needs backport to 2.28. It's less critical there because the outputs are in the repository, but still useful because it removes the risk of forgetting to check that the outputs aren't regressing.

Notes from a discussion with Ronald:

Currently the validation looks at all generated test cases. Should it look at manual test cases? Should it restrict itself to read-old-data tests, as opposed to format-of-new-data?

This PR introduces a common technical solution to two problems:

Backward compatibility: ensuring that the library can read keys created by itself or past versions. This concerns all storage read tests, regardless of where they come from (dynamically generated or stored in the repository).
Coverage preservation: ensuring that we don't accidentally lose coverage because the script is suddenly emitting fewer test cases (e.g. because it's collecting fewer inputs, or as an unintended effect of a code change). This concerns all dynamically generated tests, regardless of what they're about.

So the script should look at all generated tests, and also at static read tests. There are currently no static read tests (technically, just one, which is just there to be able to fiddle with the test function independently of the test case generation), but it's likely that there will be in the future. In fact, every test key that isn't something that the library would currently write is a candidate for not being automatically generated. For example, we could now freeze the test cases with {SIGN,VERIFY}_HASH without {SIGN,VERIFY}_MESSAGE. And when we switch to format version 1, we could straight away freeze the version 0 test cases.

Minor comments, could go ahead without addressing them.


feat: implement the new iam interface in artifact-registry

This PR implements the new IAM interface in the atifact-registry module (#2605)
In order to have a consistent interface across the different modules, this update will cause a delete/create of the existing permissions set in the iam variable:
  # module.artifact_registry.google_artifact_registry_repository_iam_binding.authoritative["roles/artifactregistry.reader"] will be created
  + resource "google_artifact_registry_repository_iam_binding" "authoritative" {
      + etag       = (known after apply)
      + id         = (known after apply)
      + location   = "europe"
      + members    = [
          + "allUsers",
        ]
      + project    = "xxredactedxx"
      + repository = "public"
      + role       = "roles/artifactregistry.reader"
    }

  # module.artifact_registry.google_artifact_registry_repository_iam_binding.bindings["roles/artifactregistry.reader"] will be destroyed
  # (because key ["roles/artifactregistry.reader"] is not in for_each map)
  - resource "google_artifact_registry_repository_iam_binding" "bindings" {
      - etag       = "xxredactedxx" -> null
      - id         = "xxredactedxx" -> null
      - location   = "europe" -> null
      - members    = [
          - "allUsers",
        ] -> null
      - project    = "xxredactedxx" -> null
      - repository = "projects/xxredactedxx/locations/europe/repositories/public" -> null
      - role       = "roles/artifactregistry.reader" -> null
    }

Checklist

I applicable, I acknowledge that I have:

[x] Read the contributing guide
[x] Ran terraform fmt on all modified files
[ ] Regenerated the relevant README.md files using tools/tfdoc.py
[ ] Made sure all relevant tests pass

Thanks a lot for this. Can you also add relevant examples and inventories to the README? The contributing guide explains how those work, or ping here if you need a quick leg up.

Working on the tests sorry


Bump jnr-posix from 3.1.5 to 3.1.9

Bumps jnr-posix from 3.1.5 to 3.1.9.

Commits

86bb153 [maven-release-plugin] prepare release jnr-posix-3.1.9
a3ecdb3 [maven-release-plugin] prepare for next development iteration
8475ce1 [maven-release-plugin] prepare release jnr-posix-3.1.8
573eed3 Update jnr-ffi
a3a3276 Revert to update jnr-ffi
61598ef [maven-release-plugin] prepare for next development iteration
eebd429 [maven-release-plugin] prepare release jnr-posix-3.1.8
591ee06 Merge pull request #171 from headius/defensive_alloc_posix_spawn_file
abbc4e5 Set up the defensive copy in constructor
1e1024c Defensive copy of posix_spawn file paths
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Author: dependabot[bot]. Timestamp: 2021-09-17T18:14:35Z

Superseded by #18.


No homework milestones

Add homework milestones and add my two issues to it

@laserlab Professor, I had three milestones created here for my project. Do I had to create more milestones? Here is the image  of my milestones created for homework. I might not had understood what I should be doing.

Professor  I created more milestones on home works now.


Using holoviews tries to load plotly even if it is not installed

Describe the bug
When I import holoviews, there is an error, marimo seems to be calling hv.renderer that tries to import plotly even if it is neither installed nor used.
Could not find a 'plotly' renderer, available renderers are: 'bokeh'.'

The error seem to be located here :
https://github.com/marimo-team/marimo/blob/e634a8dd5ee3dd1ed9af38b654bf9d6ae4274339/marimo/_output/formatters/holoviews_formatters.py#L61-L66
I wrote a patch that I currently use (it is working for me):
https://github.com/mb-915/marimo/commit/5c2e324936703146bb01c6db4ed817b23701b06e
but I couldn't get the tests to pass and I’m not sure if adding bokeh in DependencyManager is right. Therefore, I'm not opening a PR for now.
Environment
{
  "marimo": "0.8.7",
  "OS": "Linux",
  "OS Version": "6.9.8-zen1",
  "Processor": "",
  "Python Version": "3.11.8",
  "Binaries": {
    "Browser": "--",
    "Node": "--"
  },
  "Requirements": {
    "click": "8.1.7",
    "importlib-resources": "missing",
    "jedi": "0.19.1",
    "markdown": "3.5.2",
    "pymdown-extensions": "10.7.1",
    "pygments": "2.17.2",
    "tomlkit": "0.13.2",
    "uvicorn": "0.30.6",
    "starlette": "0.38.4",
    "websockets": "12.0",
    "typing-extensions": "4.10.0",
    "ruff": "0.5.7"
  }
}

Code to reproduce
(in an environment without plotly)
import marimo as mo
import holoviews as hv

thank you for filing @mb-915! the patch looks correct (not sure why the tests would not pass). do you want to open a PR with that patch or would you like me to? I can look at the test failure reasons, if it does end up failing.

i opened a PR #2199
The failing tests do not seem to be linked to the modification. There might be something in my dev environment.


Allow API access to private decks and favorites

At the moment it is possible to send ajax requests to retrieve public decks (api/public/decklist/number)
I am prototyping a tool and would like to access the favorites, list of private decks, and deck info of private decks by a javascript ajax call. Of course I would include the authentication cookies.
Problems:

no json, would need to parse html
missing CORS header (by design ?)

I am not familiar with OAuth. How much effort is it to implement on server-side? Is it appropriate for a tool in prototyping status and a localhost debug url? Would you even provide OAuth access for a tool which might never see the day of light?
Thanks
Simon

Hello Simon,
Did you look at the API documentation at http://thronesdb.com/api/doc? There’s already endpoints to get the list of private decks and the info of one deck. I guess I can add an endpoint to get the list of favorite decklists, it’s no big deal.


WS2812 SPI first LED misbehaving

Describe the bug
When driving a strip of WS2812B LEDs from the IMXRT1040 SOC using the WS2812_SPI driver the first LED is not controlled
To Reproduce
Setup a board based on an IMXRT series process with an overlay which configures the ws2812-spi driver, example configuration:
&lpspi1 {
    led_strip: ws2812@0 {
        compatible = "worldsemi,ws2812-spi";

        /* SPI */
        reg = <0>; /* ignored, but necessary for SPI bindings */
        spi-max-frequency = <6000000>;
        reset-delay = <70>;

        /* WS2812 */
        chain-length = <6>; /* arbitrary; change at will */
        spi-one-frame = <0xF8>;
        spi-zero-frame = <0x60>;
        color-mapping = <LED_COLOR_ID_GREEN
                         LED_COLOR_ID_RED
                         LED_COLOR_ID_BLUE>;
    };
};

Run the LED strip driver sample.
See LEDs sequencing through colours except the first LED remains off.
Expected behavior
All LEDs including the first LED should go through the intended colour sequence.
Impact
In tree patch created, can bring the driver out of tree until fix is implemented/adopted
Logs and console output
N/A
Environment (please complete the following information):

OS: Windows
Toolchain Zephyr SDK 0.16.3
Zephyr 64f41309d104b161b1960bcc20e2ff6bd58c6355

Additional context
I have investigated the problem and create a patch which can resolve the problem in my case, but I am unclear why a similar feature is not already in tree, unless I am missing something... which I probably am 😄
What I found was that the SPI MOSI had LED data shifted out as expected but at the start of the burst the transition was not graceful so the LEDs appear to ignore the first LED worth of data. Below is a logic analyser capture of the line activity:

The fix I discovered was to add some bus low time at the start (80uS) to trigger a reset on the LED. After this reset the burst of data can be sent and all LEDs behave well. I achived this by adding a head an tail of zeros onto the SPI data which is sent on ws2812_strip_update_rgb, in my case 64 byte of zero which translated to around 85uS of low on paper and ~82uS in practice on my hardware. This yields a bus behaviour which looks like this:

Patch: WS2812.patch
This patch is not tidy enough to merge but it is functional, I imagine any production ready implementation would expose the head and tail delay parameters as device tree parameters for per SOC tweaking similar to the spi-one-frame and spi-zero-frame values.
One thing I did not understand when reading through the driver was this line https://github.com/zephyrproject-rtos/zephyr/blob/596ef0a519eec584e2c403927543b130a7166a45/drivers/led_strip/ws2812_spi.c#L132
It says reset delay, but the bus is not being driven at this time so they delay does not actually cause the intended 50uS of bus low time the datasheet calls for:

The end effect of that line is the driver just waits 50uS while doing nothing with the bus, in most cases the bus will be driving the MOSI line high during this time nullifying any useful effect.

Related with #66664

Thanks @simonguinot for the quick response, I'll take a look at the NXP reference manual and zephyr SPI driver and see if I can adjust the SPI to behave in that manner, I see a few NXP forum threads wanting similar things with mixed results so it may  be possible 😄.
Side note, perhaps if this a somewhat common issue as MOSI is not necessarily defined when the bus is idle, would it be worth having some kind of mitigation in the driver toggleable on a 'as needed' basis e.g. kconfig default'd false.
It seems that we all agree manually inserting start/stop frames does in fact work, I agree with your comments about RAM waste, but there are more optimal ways to implement the same behaviour without growing the buffer.

FYI I am going to resume working on this and the associated PR


Two pointer

Description:
Given an array arr[] of size N, the objective is to find the longest subarray in which all elements are distinct and time and space complexity is O(n).
Checklist:

[x] Contributor in GSSoC-ext
[x] Want to work on it

Affected Algorithm:
I want to update the Two pointer algorithm with the new question with efficient time and space complexity.

can you please assign this issue to me?

/assign

@Sridevi0321 assigned


Lua runtime

Might not be enough demand but Lua 5.1.4 is in the AMI

For me it would be very useful to change legacy old monolitic servers to lambdas and remove unuseful code.
First demand 😄


Handle negative values on lifetime variable

if for some reason a negative value reach the lifetime it will be an unexpected/undesired 410 on the nginx processing

Hello @jlalfonso21 . Thank you for the fix!
Let's make a quick adjustment here: I suppose if something goes wrong and we get a negative value, we should not generate unlimited link, because the link won't be expired at all. It might be a developer issue who uses this package and unexpectedly pass negative lifetime (settings issue, total_seconds calculation issue when we use storage.url(lifetime=x)) , but it's critical to avoid such scenario and protect private files by not generating unlimited private link.
Solution: It' would be obvious to raise a ValueError exception and do not generate link at all.
Can you please adjust your fix using described solution?
P.S. We are going to put contribution guide, but what's import - lets' create new fixes directly to dev branch + adjust unittests.

changes are up @HackoDev, let me know if you find something else please

Closing PR since I think will be easier for you to handle the project description files, when changing to dev branch it just added more changes than the expected by me

@jlalfonso21 , just updated dev branch, i think you can reopen it


physics_pipeline_active not tested when time_dependent_number_of_timesteps is false

Commit 1b2ff037 introduced a regression when time_dependent_number_of_timesteps is false.
In this case physics_pipeline_active is not tested, and physics simulation cannot be paused.
I will provide a PR for that

Fixed by #42.


PDF view doesn't work on android mobiles

Hi Breno,
The plugin works fine for the ios devices. However when tested on android phones (Nexus 5X / API 28), the PDF view is not working. To cross check, your demo url is opened in the android's default browser(not chrome) and found that the PDF is not getting rendered.
When analysed more, it was found that the iframe containing blob protocol for the src attribute have some issues on cordova android. Though the allow-intent and allow-navigation tags are set to href="*", it is still not working.
Any thoughts.

I'll be closing the issue because i just don't have the ways to proper test it and develop it, if possible open a pull request :)


CLA Corporate Console only shows last 4-5 events

Details
The URL of where it occurred: organization.lfx.linuxfoundation.org
Steps to Reproduce
Setup:
Test Organization
Test CLA Manager
Signed CLA on Test Project
Many events generated in event log (can add/remove cla managers, approval list to generate more events)
Steps:

On a test account, log into organization.lfx.linuxfoundation.org
Click on a project for which your test org has signed a CLA
In the Event log section - see only 4 events returned and the info column very small

Expected Result (why you are opening this ticket - why is this a defect?):
I would expect to see more than 4-5 items at a time,
I would expect to be able to scroll back to older events.
I would expect the info column adjusted to be wider to better see the information.

duplicate


The Job Cards are not appropriate for User Interface

Description
The User Interface of the Jobs Cards are not looking appealing as the User Interface and which in return, it degrades the User Experience. The User interface is one of the major component of the visitors count and in such a competitive environment User Interface needs to be appealing to attract users.
Steps to Reproduce

Open the Website
Move to header
Click on Jobs
Scroll Down to job cards

Expected Behavior
The Job Cards will be looking appealing and the styling and font will be in such way that it could be clearly visible tot he User and doesn't have unnecessary dimensions just to accommodate the content.
Actual Behavior
The Jobs Cards are not looking appealing and having very huge font with long width which is not necessary as the content is not mush to show and can be adjusted in shorter width with required height and width to adjust the content.
Screenshots
Screenshots

Additional Information
@aditya-bhaumik Please assign this issue to me under hacktoberfest and gssoc-ext with the necessary labels. Please assign this issue to me @VanshGarg06 as soon as possible.
hacktoberfest-accepted, gssoc-ext,level3
What browser are you seeing the problem on?

[ ] Firefox
[X] Chrome
[ ] Safari
[ ] Microsoft Edge

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

@aditya-bhaumik I want to contribute to this project on this particular issue. Please assign it to me!

@VanshGarg06 sure go ahead

Make sure to join the discord server for further communication
Don't forget to star the repository
Complete the task in next 2 days and kindly mention your issue # in your pr like:
Closes #IssueNumber

Note: the level of the issue may change based on the quality of the PR code


Support Azure OpenAI API

Could you make it support Azure OpenAI API?

Perhaps there is no plan for this at the moment, and we may consider adding Azure OpenAPI key after the stability of subsequent functions. Currently, our priority is to improve the effectiveness of conversations and enhance functionality.

Is it possible to support custom openai_url? In this way, access to Azure openai can be realized through other projects.
There are many proxy projects from Azure openai api to openai on GitHub.

Sure， you can change the openai_url  in  chatfiles-ui/utils/app/const.ts.

Sure， you can change the openai_url in chatfiles-ui/utils/app/const.ts.

In Azure , change OPENAI_API_HOST to Azure endpoint ?

It's not that simple, the authentication methods of azure api and openai api are different.
But there are many projects on github that convert Azure api to openai api. Through these projects, the azure api can be converted to the same as that of openai, except that the endpoint is different.
In theory, after this conversion, you can use Azure api in this project, but I feel that only changing the front end is not enough.
I am also trying, it is best to define the endpoint as an independent variable.

我尝试使用代理，用的这个项目https://github.com/stulzq/azure-openai-proxy
但是没有成功，有没有大佬已经实现，我想使用azure的key

Hello everyone, ChatFiles has been refactored with Langchain and now supports Azure OpenAI Service. #81


update version to 1.0.0-preview.1

a minor error that updates version to 1.0.0-preview.1

FYI @JimSuplizio


Possible to have NerdTreeToggle re-use existing NerdTree buffer?

From a high level, I would like to be able to switch tabs within a single vim session and have the nerdtree buffer always be the same.  Currently the nerdtree buffer is maintained within each individual tab, so when I close/open with NerdTreeToggle the expanded directories are maintained; but if I switch to a new tab, it is a new NerdTreeBuffer.
currently the only nerdtree specific things I have in my vimrc is this mapping
map <Leader>n :NERDTreeToggle<CR>

Ideally I would like <Leader>n to open the same NerdTree buffer for every tab within a single vim instance.
Environment

Operating System:
Ubuntu

Vim version :version:
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jul 26 2017 20:13:43)

NERDTree version git rev-parse --short HEAD:
a172d7c

Process

:NerdTreeToggle ::make some changes::
Switch to another tab/buffer in same instance of VIM
:NerdTreeToggle

Current Result

The NerdTree buffer will be fresh and not contain any of the expanded directories (closing and opening works fine within a single tab/buffer)
Expected Result

The ability to share a single nerdtree buffer between all tabs.

After your first :NERDTreeToggle, you can use :NERDTreeMirror on new tabs to make use of the original NERDTree buffer. You might also consider using the vim-nerdtree-tabs plugin, as mentioned in the NERDTree README.

NERDTreeMirror is exactly what I needed, thank you


Cut v1.22.2+k3s1

Summary:
Task covering patch release work.
Dev Complete: 09/08/2021
List of required releases:
To release as soon as able for QA:

v1.22.2-rc1+k3s1

To release once have approval from QA:

v1.22.2+k3s1 (Never release on a Friday unless specified otherwise)

Prep work:

[ ] PM: Dev and QA team to be notified of the incoming releases - add event to team calendar
[ ] PM: Dev and QA team to be notified of the date we will mark the latest release as stable - add event to team calendar [ONLY APPLICABLE FOR LATEST MINOR RELEASE]
[ ] QA: Review changes and understand testing efforts
[ ] Release Captain: Prepare release notes in our private release-notes repo (submit PR for changes taking care to carefully check links and the components, once merged, create the release in GitHub and mark as a draft and check the pre-release box, fill in title, set target release branch, leave tag version blank for now until we are ready to release)
[ ] QA: Validate and close out all issues in the release milestone.

Vendor and release work:

[ ] Release Captain: Vendor in the new patch version and release rancher/kubernetes
[ ] Release Captain: Tag and release any necessary RCs for QA to test K3s and KDM on the Rancher side
[ ] Release Captain: Tag and release when have QA approval

Post-Release work:

[ ] Release Captain: Once release is fully complete (CI is all green and all release artifacts exist), edit the release, uncheck "Pre-release", and save.
[ ] Release Captain: Prepare PRs as needed to update KDM in the appropriate dev branches.
[ ] PM: Close the milestone in GitHub.

Closing this in favor of: https://github.com/k3s-io/k3s/issues/3781


Installing Bundler using redmine instructions

What did you do?
I ran the command /usr/local/bin/bundler install --without development test postgresql sqlite

(as instructed using these install process for Redmine: http://www.redmine.org/projects/redmine/wiki/HowTo_Install_Redmine_25x_on_Ubuntu_1404_with_Apache2_Phusion_Passenger_MySQL_and_Subversion)

What did you expect to happen?
I expected Bundler to...

Install correctly. Note that when the instruction is executed under SUDO, it recommends not doing so because it will affect non-root users.

What happened instead?
Instead, what happened was...

It failed.
"Unfortunately, an unexpected error occurred, and Bundler cannot continue."
Error details
Errno::EACCES: Permission denied - (/tmp/bundler-compact-index-20161125-3026-18qn8w8/versions, /home/lbyrnes/.bundle/cache/compact_index/rubygems.org.443.29b0360b937aa4d161703e6160654e47/versions)
  /usr/lib/ruby/1.9.1/fileutils.rb:519:in `rename'
  /usr/lib/ruby/1.9.1/fileutils.rb:519:in `block in mv'
  /usr/lib/ruby/1.9.1/fileutils.rb:1515:in `block in fu_each_src_dest'
  /usr/lib/ruby/1.9.1/fileutils.rb:1531:in `fu_each_src_dest0'
  /usr/lib/ruby/1.9.1/fileutils.rb:1513:in `fu_each_src_dest'
  /usr/lib/ruby/1.9.1/fileutils.rb:508:in `mv'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:55:in `block in update'
  /usr/lib/ruby/1.9.1/tmpdir.rb:83:in `mktmpdir'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:29:in `update'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:65:in `update'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:56:in `update_and_parse_checksums!'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/fetcher/compact_index.rb:67:in `available?'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/fetcher/compact_index.rb:15:in `call'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/fetcher/compact_index.rb:15:in `block in compact_index_request'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/fetcher.rb:157:in `use_api'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/source/rubygems.rb:332:in `block in api_fetchers'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/source/rubygems.rb:332:in `select'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/source/rubygems.rb:332:in `api_fetchers'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/source/rubygems.rb:337:in `block in remote_specs'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/index.rb:10:in `build'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/source/rubygems.rb:336:in `remote_specs'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/source/rubygems.rb:83:in `specs'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/definition.rb:261:in `block (2 levels) in index'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/definition.rb:259:in `each'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/definition.rb:259:in `block in index'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/index.rb:10:in `build'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/definition.rb:256:in `index'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/definition.rb:250:in `resolve'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/definition.rb:174:in `specs'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/definition.rb:162:in `resolve_remotely!'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/installer.rb:225:in `resolve_if_need'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/installer.rb:78:in `run'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/installer.rb:24:in `install'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/cli/install.rb:71:in `run'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/cli.rb:189:in `install'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/cli.rb:20:in `dispatch'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/cli.rb:11:in `start'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/exe/bundle:34:in `block in <top (required)>'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/lib/bundler/friendly_errors.rb:100:in `with_friendly_errors'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/exe/bundle:26:in `<top (required)>'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/exe/bundler:4:in `load'
  /var/lib/gems/1.9.1/gems/bundler-1.13.6/exe/bundler:4:in `<top (required)>'
  /usr/local/bin/bundler:23:in `load'
  /usr/local/bin/bundler:23:in `<main>'

Environment
Bundler   1.13.6
Rubygems  1.8.23
Ruby      1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]
GEM_HOME  /var/lib/gems/1.9.1
GEM_PATH  /var/lib/gems/1.9.1:/home/lbyrnes/.gem/ruby/1.9.1
Git       1.9.1
  Bundler settings

without
Set for your local app (/usr/share/redmine/.bundle/config): "development:test:postgresql:sqlite"

Please review the permissions at /home/lbyrnes/.bundle/ and make sure that Bundler and the user has permissions to write to that location.
Did you run bundler as root or any other user at any stage?

thanks - must be an issue with install, that directory doesn't exist... will recheck if i've missed a step.
Yes, I did attempt to install as root a few times to see if that resolved the permissions issue, but to no avail.

(pre-written response)
Closing as a duplicate of the other Permission denied issues. A suite of permission errors have been addressed by https://github.com/bundler/bundler/pull/5007 which will release in Bundler 1.14. Until 1.14 releases, the team doesn't have the capacity to deal with, or deploy more fixes for, the quantity of permissions errors we receive.
I'm sorry you are experiencing issues and I hope you can get them resolved!!! Feel free to continue commenting on this issue in the meantime.


A7riii !

hi,
Is there any new way to bypass the video limit  for the a7riii series
Thanks!

https://github.com/ma1co/Sony-PMCA-RE/tree/v0.18
You can use this source if you have some sense of programming. I tried it, and it works perfectly!


Opentelemetry usage breaks browser build

Description
Unable to use Faro with latest version of Vite (which is using latest version of Rollup).
Seems that a dependency (open-telemetry) is using a Node package in the browser:
https://github.com/open-telemetry/opentelemetry-js-contrib/issues/1892
error during build:
RollupError: "normalize" is not exported by "__vite-browser-external:path", imported by "node_modules/<EMAIL_ADDRESS>    at error (file:///Users/.../project/node_modules/rollup/dist/es/shared/parseAst.js:337:30)

Steps to reproduce
Use Vite 5 and Rollup 4 to bundle a project.
Expected behavior
Build succeeds
Actual behavior
Build breaks
Environment
  System:
    OS: macOS 14.1
    CPU: (12) x64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz
    Memory: 94.07 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.14.2 - ~/.nvm/versions/node/v18.14.2/bin/node
    Yarn: 1.22.21 - ~/.nvm/versions/node/v18.12.0/bin/yarn
    npm: 9.5.0 - ~/.nvm/versions/node/v18.14.2/bin/npm
  Browsers:
    Chrome: 120.0.6099.216
    Firefox: 100.0
    Safari: 17.1
  npmPackages:
    @grafana/faro-web-sdk: 1.3.5 => 1.3.5
    @grafana/faro-web-tracing: 1.3.5 => 1.3.5
    vite: 5.0.11 => 5.0.11

Demo
Error output as above. I think the dependency issue linked is all that is potentially blocking this.
Context

this is a known issue in the otel js contrib repo - hopefully the release today/tomorrow fixes this. I will update this thread with any details.
thread with more details

Hi @seanlail
As a workaround till the deps are fixed, you can pin the version of the @opentelemetry/instrumentation package in you package.json.
If you use yarn:
 "overrides": {
        "@opentelemetry/instrumentation": "0.45.0"
    }
 }

If you use yarn:
 "overrides": {
        "@opentelemetry/instrumentation": "0.45.0"
    }
 }

Let us know if the workaround may work for you.
Cheers

@seanlail
The wonderful otel folks released a fix. ❤
We updated the otel deps and are currently releasing a new Faro version.
Cheers


Nested elements not updating in live preview

It appears that nested references don't update as you type while top level elements do
graphql query
query {
        pageCollection(where:{ slug:"${slug}" }, preview: true, limit: 1){
            items{
                sys{
                    id
                }
                title
                slug
                meta{
                    title
                    description
                    image{
                        ... on Asset{
                            url
                        }
                    }
                }
                components:componentsCollection{
                    all:items{
                        ... on HeroComponent{
                            __typename
                            sys{
                                id
                            }
                            title{
                                json
                            }
                            gallery:galleryCollection{
                                items{
                                  ... on Asset{
                                    url
                                  }
                                }
                            }
                        }
                        ... on MessageComponent{
                            __typename
                            sys{
                                id
                            }
                            msgtitle:title
                            description{
                                json
                            }
                            editor{
                                sys{
                                    id
                                }
                                title
                                name
                                avatar{
                                    url
                                }
                            }
                            button{
                                sys{
                                    id
                                }
                                label
                                location
                            }
                        }
                        ... on OfferingComponent{
                            __typename
                            sys{
                                id
                            }
                            featuretitle:title
                            featuresCollection(limit:9){
                                items{
                                    sys{
                                        id
                                    }
                                    title
                                    description
                                    icon{
                                        url
                                    }
                                }
                            }
                        }
                    }
                }
            }
        }
    }

component 'MessageComponent'
import ErrorPage from 'next/error'
import { useRouter } from 'next/router'
import { documentToReactComponents } from '@contentful/rich-text-react-renderer'
import { BLOCKS, MARKS } from '@contentful/rich-text-types'
import { useContentfulInspectorMode, useContentfulLiveUpdates } from '@contentful/live-preview/react'

import styles from './offering.module.css'

export default function OfferingComponent(props) {

    const updatedProps = useContentfulLiveUpdates(props)
    const inspectorProps = useContentfulInspectorMode({ entryId: props.sys.id })
    const router = useRouter()
    const options = {}

    if (!router.isFallback && !updatedProps) {
        return <ErrorPage statusCode={404} />
    }

    return (

{updatedProps.featuretitle}

                    {updatedProps.featuresCollection.items.map((item, i) => (

                                {updatedProps.featuresCollection.items[i].title}

                                {updatedProps.featuresCollection.items[i].description}

                    ))}

    )
}

if you edit or change the value of 'featuretitle' in live preview it updates in realtime
If you edit or change the value of 'updatedProps.featuresCollection.items[i].title' in live preview it does not update in realtime
i should also note that if you click the 'refresh' icon 'updatedProps.featuresCollection.items[i].title' does update

Hi! Thanks for submitting this bug report. Could you tell me which version you are running of the SDK? Could you update to the latest version?
Are these references inside of a rich text component? We recently fixed an issue that should update these

currently installed<EMAIL_ADDRESS>These references are not related to rich text but are a reference field type

I tried passing the query as a parameter to the hook but I'm getting an error on build. But in my case I'm using graphql from gatsby. Does the SDK support this as well? I'm having the same issue with nested elements not updating.

We currently are still working on supporting Gatsby, since they are using a different GraphQL structure than our standard GraphQL API. There's an example in the examples directory, but only a few fields are working with live updates for now. Inspector mode should work fine

Hi, have some updates about this? I'm trying to use this same approach but with the same issue.

@brcaua Sorry I don't have an update yet, we are working on improving the SDK (and eventually adding support for Gatsby), so keep an eye out!

@YvesRijckaert - We are currently using Gatsby4 with Contentful and React in our codebase, previously it was Gatsby2. Our preview is built with old package called as Contentfully https://github.com/nascentdigital/contentfully which is not working well after the upgrade to Gatsby4. Since you have mentioned above that Gatsby support is still under development, is there any other method by which we can build our own preview while the live updates SDK is made fully functional? Our content editors use Contentful preview for content change on a daily basis and we would like to get it fixed asap as it is causing a lot of inconvenience and discrepancies while previewing the content changes. Any alternate suggestions will be really helpful. Thank you!

Hello @dpatilctct,
Unfortunately, I can't provide insights on the Contentfully plugin as we have not tested it yet with our live preview SDK. Our support for the default gatsby-source-contentful plugin is in the pipeline, mainly because it does not integrate with the official Contentful GraphQL API. The functionality of our live preview SDK is tailored to match the response format of the official Contentful GraphQL API.
Here's what we've noted so far when comparing the two:

The gatsby-source-contentful obfuscates the sys.id and converts it into contentful_id.
The rich text response format differs.
Variations are also seen in long text fields (including the markdown editor), assets, and references.
However, other fields, such as short text fields, should be functional as of now.

For the time being, a manual page refresh could serve as a temporary fix. Also, inspector mode should be fully functional with Gatsby. We're planning to extend our framework support in Q4. Keep an eye out for updates!

Thank you @YvesRijckaert for the detailed insights on the comparison between the two, it's very helpful. We'll keep an eye out on the updates. Any chances we would have them by this year?


Add an exploration of type-safe system calls.

This document proposes a more-type-safe syscall ABI for Tock and looks at its pros and cons versus the Tock 2.0 syscall ABI.
Rendered

The interface feels very flexible, but what I'm really missing is a sense of why this is all necessary. What's broken in TRD104 that this fixes? That would help judge whether it's doing a good enough job or not.

I significantly expanded on the first section of the document, to further explain its purpose.

The motivation section you fleshed out really helps this make sense to me. Thanks!

I think it might be helpful to look at all commands, command returns, and upcalls that we currently have and see what is being used. I have a feeling (but no data) that in practice we only use the simple versions (eg one u32), rarely use u64, and only use pointers in memop.

I agree. Unfortunately, we don't consistently document these types so we would have to dig through the implementations of all the syscall drivers to do that.
Pointers are also used by subscribe, yield, and the allows.


Add ability to configure executable for redshift service

Motivation for this change
The redshift package provides a redshift executable as well as a redshift-gtk executable, however the redshift module only uses redshift and provides no option to change the executable.
Things done

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

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

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

@Infinisil I have seen you on other reviews for redshift. Can you talke a look or do I need somebody else to look?

@yegortimoshenko @globin it looks like you are listed as maintainers for redshift. Is this something that you could review? Thanks!

A better way of doing this I think, would simply to have an option that can but set to something like this: "${pkgs.redshift}/bin/redshift"

@rissson is your suggestion to make the executable parameter default to ${cfg.package}/bin/redshift and then use that in the ExecStart?
Do you know of any other examples of something similar to this? (I'm new to this, so I don't really know where to look.)

Yes, that's what I meant. I wasn't able to find another example of this, I'll leave a review as an example of how it could be done.

I guess it does not have to be so generic. I can change over to having a useGtk option maybe.

Actually, what if we did it like the shells: Have pkgs.redshift.binaryPath be "/bin/redshift" by setting that in a passthru. Then this module can just use ${cfg.package}${cfg.package.binaryPath or "/bin/redshift"} as the executable, and we won't need an additional option, meaning this is a one-line change. The user could then make it use the gtk version with:
{
  package = pkgs.redshift // { binaryPath = "/bin/redshift-gtk"; };
}

How the shells do this: https://github.com/NixOS/nixpkgs/blob/37eb705a65b487046b7200dd960d549b9493cf2b/pkgs/shells/bash/5.0.nix#L124-L126 https://github.com/NixOS/nixpkgs/blob/37eb705a65b487046b7200dd960d549b9493cf2b/nixos/lib/utils.nix#L26-L29

@Infinisil I like how your suggestion is generic and scales. Surely redshift won't be the last time we see this issue.

@Infinisil I like that idea, but I'm a bit confused as to why an option is not required? Also, do I have to add that passthru set somewhere?

As someone who currently uses a bit of a hack to accomplish this, I'm excited to see this get merged! I was wondering what the benefits were to the passthru solution vs having the executable option. It seems like the passthru option suffers from being non-discoverable since it would never show up when searching through available options on the Redshift module. Would the lack of discoverability be a big benefit for just using the executable option? I was also wondering whether the Redshift package itself needed to add the passthru or if the "or" in ${cfg.package}${cfg.package.binaryPath or "/bin/redshift"} would take care of handling that case already. Would it be reasonable to drop the "or" in the expression above and just assert that Redshift packages must define the binaryPath?

@sumnerevans This is all that's required for that to work:
diff --git a/nixos/modules/services/x11/redshift.nix b/nixos/modules/services/x11/redshift.nix
index 21b0b33553a..77a5eb3b32b 100644
--- a/nixos/modules/services/x11/redshift.nix
+++ b/nixos/modules/services/x11/redshift.nix
@@ -114,7 +114,7 @@ in {
       partOf = [ "graphical-session.target" ];
       serviceConfig = {
         ExecStart = ''
-          ${cfg.package}/bin/redshift \
+          ${cfg.package}${cfg.package.binaryPath or "/bin/redshift"} \
             -l ${providerString} \
             -t ${toString cfg.temperature.day}:${toString cfg.temperature.night} \
             -b ${toString cfg.brightness.day}:${toString cfg.brightness.night} \

With this you could set this in your configuration.nix:
{ pkgs, ... }: {
  services.redshift.package = pkgs.redshift // { binaryPath = "/bin/redshift-gtk"; };
}

@jhgarner Yeah discoverability won't be great with this. So I think the current approach might be better after all.
In addition, what we need here is different than the shell packages I talked about above: The shell packages have one canonical binary path, meaning users shouldn't ever need to change that binary path. However in redshift's case, there are multiple binaries, and users are expected to switch between them. This is another reason for making this a separate option.
I'll just go ahead and merge this now, I think there are good enough reasons for doing so.


win32-x64\electron-webpack-win32 Error: gyp failed with exit code: 1

electron-forge make

√ Checking your system
√ Resolving Forge Config
We need to package your application before we can make it
√ Preparing to Package Application for arch: x64
/
|
\ P
reparing native dependencies: 0 / 1gyp: Undefined variable napi_build_version in binding.gyp while trying to loa
× Preparing native dependencies: 0 / 1
An unhandled error has occurred inside Forge:
node-gyp failed to rebuild 'C:\Users\hello\AppData\Local\Temp\electron-packager\win32-x64\electron-webpack-win32
Error: gyp failed with exit code: 1
Error: node-gyp failed to rebuild 'C:\Users\hello\AppData\Local\Temp\electron-packager\win32-x64\electron-webpac
Error: gyp failed with exit code: 1
at ModuleRebuilder.rebuildNodeGypModule (D:\code\system-operate-tools\node_modules\electron-rebuild\src\modu
at processTicksAndRejections (internal/process/task_queues.js:86:5)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>make: electron-forge make
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>make script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:

modify node_modules\sqlite3\binding.gyp
add
"napi_build_version%":"3"

to binding.gyp
for example:
{
  "includes": [ "deps/common-sqlite.gypi" ],
  "variables": {
      "sqlite%":"internal",
      "sqlite_libname%":"sqlite3",
      "napi_build_version%":"3"
  }
}

modify node_modules\sqlite3\binding.gyp
add
"napi_build_version%":"3"

to binding.gyp
for example:
{
  "includes": [ "deps/common-sqlite.gypi" ],
  "variables": {
      "sqlite%":"internal",
      "sqlite_libname%":"sqlite3",
      "napi_build_version%":"3"
  }
}


Keyboard overlays popover when using forms

Ionic version:  (check one with "x")
[ ] 1.x
[ ] 2.x
[x] 3.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
So I need to add a small form inside a popover. It's a "add to wishlist" popover. So the user either selects an existing wishlist or creates a new wishlist and add the item at the same time. When I tried that in the device, I got a weird result where the keyboard was overlaying the popover and the form couldn't be seen.
Image: http://imgur.com/a/payjQ
Expected behavior:
I'm not sure if that is somewhat achievable, but it would be nice if there was a scroll, just like in a normal page with input forms.
Steps to reproduce:
Create the popover component and try it out on a device
Related code:
.html
<ion-content>
	<ion-list>
		<ion-list-header>Wishlists</ion-list-header>
		<button ion-item *ngFor="let wishlist of wishlists" (click)="addToWishList(wishlist.id)">{{wishlist.name}}</button>
	</ion-list>
	<div *ngIf="!showInput">
		<button ion-item detail-none (click)="create()" class="pink add-button">Create <ion-icon name="add" class="right"></ion-icon></button>
	</div>
	<div *ngIf="showInput">
		<ion-item>
			<ion-input placeholder="Name.." [(ngModel)]="wishlistName" maxlength="25"></ion-input>
		</ion-item>
		<button ion-button clear (click)="createNewWishlist()" class="right">Add</button>
	</div>
</ion-content>

.ts
import { ViewController } from 'ionic-angular';
import { Component } from '@angular/core';
@Component({
  selector: 'wishlists-popover',
  templateUrl: 'wishlists-popover.html',
})
export class WishlistsPopover {
  showInput = false;
  wishlistName = "";
  wishlists = [
    {
      id: 1,
      name: "Dream's adventure"
    },
    {
      id: 2,
      name: "Weekend",
    },
    {
      id: 3,
      name: "Family Time"
    },
  ];

  constructor(public viewCtrl: ViewController) { }

  create() {
    this.showInput = true;
  }
  createNewWishlist() {
    this.wishlists.push({ id: 5, name: this.wishlistName });
    this.showInput = false;
    this.wishlistName = "";
  }

  addToWishList(id) {
    console.log("added to " + id);
  }

  close() {
    this.viewCtrl.dismiss();
  }
}

Cordova CLI: 6.3.1
Ionic Framework Version: 3.0.1
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.3.0
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Linux 4.4
Node Version: v6.9.1
Xcode version: Not installed

Hello, thanks for opening an issue with us! Any reason you're using a popover for this instead of a modal or select?

Hey Justin, Yes, the main reason is the feature was requested by the client.


Rename horizontal_* to reduce_*

as suggested here: https://rust-lang.zulipchat.com/#narrow/stream/257879-project-portable-simd/topic/.22pointwise.22.20and.20misc.20bikesheds/near/275036376

This looks fine now. I think we will want to change the guide a bit more, but we can do that when we make the next pass over this.

Thank you!


(XS) Event picker for adding posts

Better UI - Creates an easier way to assign an event to a post than a text field, displays event IDs and names in a dropdown menu.

LGTM


Please update the Cargo.lock file before releases

I've been packaging releases for Arch Linux, and one thing we always try to do is create reproducible packages. That way anybody can verify that the binary artifacts in a release were indeed generated from the sources they were supposed to be. This also catches a lot of other problems with the build process.
One blocker for this project is that the Cargo.lock file is not getting updated properly. Ideally this this should be updated regularly during the development process, especially when any dependencies change in the Cargo.toml manifest or you want to pin new minor releases of dependencies. But at the very least it should be updated prior to tagging releases. That way the app can be built using cargo build --locked using a known-good set of dependency versions. This serves end users in case some dependency updates are inadvertently breaking, secures things in case of crate compromises, enables reproducible builds, etc.
Getting this done is pretty easy, just cargo update and commit the resulting Cargo.lock file. This should be done at a minimum after bumping the release version in Cargo.toml. It would probably be good to do it sometime shortly before the release, test with the pinned dependencies, then bump the version, then make sure the build runs with cargo build --locked.
CI should probably be adapted to run --locked too.

Currently we are not checking in the Cargo.lock files as per Rust guidance. Though it looks like the policy has changed lately. https://blog.rust-lang.org/2023/08/29/committing-lockfiles.html
I still don't have a clear understanding of the implications and what this means, will ask around and get back to you in a bit.

I think you've completely misunderstood the guidance, and it has not changed relative to this project. This project is not just a library, it is a whale app and ships several CLI binaries. The guidance on this scenario has always been to check in the lockfile. The only change is that the new guidance is that some pure-library crates should consider tracking lock files as well.

In our release environment, it's a little more complicated as we have an internal build process that mirrors some of what you see here. This is due to the need for signing on the windows and OSX releases and building matching server-side libraries that pair with the client release components.  We want one Cargo.lock for this larger piece.
To work with your request, however, we will separate out the git-xet program from the general xet-core workspace, and this part will have its own Cargo.lock file checked in to the environment.  Hopefully this will make the build process easier on your end.

No matter how complicated your build process and release sequence it shouldn't be hard to keep a lock file updated. The lock file is not linked to what build targets or build options or features or even platform is being used. It includes everything. Anywhere you run it cargo update should get the lock file in sync and then you can build anywhere with any options you like as long as the dependencies don't change versions. The same goes for cargo fetch, it fetches every dependency for every platform, even architectures you may not support at all. Then when a cargo build --locked happens no matter what the platform or target or build options the same lock file should be valid for everything.
All that to say I'm pretty confident you don't need to split anything into a separate workspace for this to get fixed without any downsides to any workflow you need. Even if you didn't want to do a locked build somewhere (which is a dubious need) you could still just not use --locked with no downside to having an up to date lock file for the whole workspace.

This has still not been properly addressed. The v0.14.3 release (and possibly others before it) does not build with locked deps because the lock file is out of date.

I'm not sure what you are seeing.  Checking out the v0.14.3 tag and running cargo build in gitxet, libxet, and rust/ shows that all the committed Cargo.lock files are up to date.  Could you describe what your process is and what you're seeing is out of date?

I'm not sure what you are seeing. Checking out the v0.14.3 tag from a clean directory and running cargo build in gitxet/ and libxet/ shows that both of the committed Cargo.lock files are up to date. Could you describe what your process is and what you're seeing is out of date?

I'm using the source tarball (git archive generated by GitHub) to download the tag, then switching to the rust/ directory and running cargo build --frozen --release. You can't test this with cargo build, you need cargo build --frozen.
Historically that is where everything has been (git-xet, xetcmd, xetmnt), but it looks like git-xet moved to gitxet/. I don't know what libxet is yet in relation to the rest of the workspace.

v0.14.4 continued to manifest this problem. The gitxet builds okay with --frozen, but the stuff in rust does not and must be cargo updated before cargo build --frozen will run.


Simple sample form MWEM not working

Hi, I have been exploring one of the example notebooks here: https://github.com/opendp/smartnoise-samples/blob/master/whitepaper-demos/5-ml-synthetic-data.ipynb
After fitting MWEM synthesizer I get a strange erro when sampling, could that be fixed. I am using a Mac M1 with anaconda.

We've added M1 support in the latest release of smartnoise-synth.

Fixed


No data available in cache after Redisson version upgrade from 3.9.1 to 3.17.4

Dear Team,
We have upgraded our Redisson Java client version from 3.9.1 to 3.17.4. Post upgrade we noticed that the redisson java client is reporting "No data in cache" even though the data is available in the cache. To confirm this, we have issued direct redis-cli commands and found that the data is available in the redis cache. Your support on this issue would be of great help because this has a direct impact on workloads.
Thanks in advance for your support in this regard.

Default codec has changed since 3.10 version. Now it's MarshallingCodec.

Hi @mrniko, Thanks so much for your response.
I am a little confused about the next steps.
Kindly advise us on how to resolve this issue.

you can back to 3.9.1 version and then read data using default codec and store it into structures using MarshallingCodec manually.

You can copy its source from the current version.


Adding SEO changes for front page and campaigns pages

Source doc here - https://goo.gl/MzYSo9
Enabling metatag_views module
Exporting metatag node and global settings to metatag module

@angaither

@blisteringherb add the module to drupal-org.make file too https://github.com/DoSomething/phoenix/blob/dev/lib/profiles/dosomething/drupal-org.make

The metatag_views module is part of the metatag module package so it doesn't get downloaded separately.  Does it still need to be added to the drupal-org.make file?

ahh, i see :+1:


Seeming to be a BAD error when using streaming on release 6.0.3

I haven't checked for prior releases, but since I haven't seen this before 6.0.3, I suspect this may be tied for the rewrite of monk -- but not sure.
The issue is that code like:
  (<any> tasks).find({}, {stream: true})
    .each((taskData: TaskData) => {
      if (taskData._id) {
        mapTasks.set(taskData._id, taskData);
      }
    })
    .catch((err: any) => {
      console.error(processErrorMessage(err.toString()));
      reject(err);
    })
    .then(() => {
      console.log('tasks #:', mapTasks.size());
      resolve(true);
    });

doesn't get the full TaskData from the database.  It does get all of the items, but ONLY the id's.  I was using 'stream: true' because I can have many thousands of items and don't want all of them in memory and the same time.
BUT the code:
  (<any> tasks).find({})
    .then((docs: TaskData[]) => {
      docs.forEach((taskData: TaskData) => {
        console.log('listData:', listData)
        mapTasks.set(taskData._id, taskData);
      });
      console.log('docs:', docs.length);
    })
    .then(() => {
      console.log('tasks #:', mapTasks.size());
      resolve(true);
    });

works properly!
This should be fairly easy to add to your tests, since the mapTasks and all the rest can be ignored.

I suspect this may be the same bug as reported i #208


Open suggestion for "How to use CI/CD for publishing packages"

Current way is using lerna to manage & publish packages, lerna-changelog to create CHANGELOG


add blocks github link does not go to correct URL

Describe the bug
In the add blocks dialogue within MakeCode, there are links to the various github repositories to be imported from. When I clicked on one of these links (joystick, as in the image below) it took me to https://github.com/pxt-jacdac :

Expected
Links should redirect to the actual github repository.

Fixed by https://github.com/microsoft/pxt/pull/8489


Fixed a bug that caused an infinite wait for Bluetooth premission

Maybe we should waiting for the changes of Bluetooth and Motion State in Background

My solution doesn't work.
See more #161 .


combine bower dependencies in 1 js file, to allow 25+ students to access firebase hosting at the same time

Closing in favor of #58.


Intervention \ Image \ Exception \ NotReadableException Image source not readable

Hola amigos tengo el siguiente error al guardar una imagen en laravel con intervention image, alguna solucion?
Hello friends I have the following error when saving an image in laravel with the image of the intervention, the solution of the solution?
public function storage (Request $request)
{
# carga de fotografias
$file  = $request->file('lugarsiniestro');
$fileName = time() . '-' . $file->getClientOriginalName();
$file->move('uploads', $fileName);
$img = Image::make($file->getRealPath())
->resize(300, 240)
->save('public/uploads/', $file->getClientOriginalName());
}

Oh,  I have the same problem as you. That images url is very long and have other code, I don't know if this is the reason.

Hola amigos tengo el siguiente error al guardar una imagen en laravel con intervention image, alguna solucion?
Hello friends I have the following error when saving an image in laravel with the image of the intervention, the solution of the solution?
public function storage (Request $request)
{
carga de fotografias
$file = $request->file('lugarsiniestro');
$fileName = time() . '-' . $file->getClientOriginalName();
$file->move('uploads', $fileName);
$img = Image::make($file->getRealPath())
->resize(300, 240)
->save('public/uploads/', $file->getClientOriginalName());
}

heeeee,  I just found out the reason for this problem, I don't know if it is similar to your situation.
When the images url have chinese string, that error will appear

Replace
$resize = Image::make('storage/app/public/'.$user->image)->resize(300,300);
with
$resize = Image::make(storage_path('app/public/'.$user->image))->resize(300,300);
Give storage full path will solve the problem.

Replace
$resize = Image::make('storage/app/public/'.$user->image)->resize(300,300);
with
$resize = Image::make(storage_path('app/public/'.$user->image))->resize(300,300);
Give storage full path will solve the problem.


[BUG] "-windows" TargetFramework requires "Microsoft.WindowsDesktop.App" and can't be deployed to Azure

Library name and version
Azure.Identity 1.10.4
Describe the bug
When you create a "Windows" specific Web Application like that:
<Project Sdk="Microsoft.NET.Sdk.Web">

  <PropertyGroup>
    <TargetFramework>net6.0-windows</TargetFramework>
    <Nullable>enable</Nullable>
    <ImplicitUsings>enable</ImplicitUsings>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Azure.Identity" Version="1.10.4" />
  </ItemGroup>

</Project>

Then the resulting project will require the WindowsDesktop runtime:
{
  "runtimeOptions": {
    "tfm": "net6.0",
    "frameworks": [
      {
        "name": "Microsoft.NETCore.App",
        "version": "6.0.0"
      },
      {
        "name": "Microsoft.WindowsDesktop.App",
        "version": "6.0.0"
      },
      {
        "name": "Microsoft.AspNetCore.App",
        "version": "6.0.0"
      }
    ],
    "configProperties": {
      "System.GC.Server": true,
      "System.Reflection.Metadata.MetadataUpdater.IsSupported": false,
      "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization": false
    }
  }
}

Reason is the dependency Microsoft.Identity.Client, which will add WebView2 and other stuff to the dependency tree:

The problem:
a) It was quite suprising that the target runtime dependency has changed.
b) This WindowsDesktop Runtime is not available on Azure (e.g. App Service).
Expected behavior
It seems wrong that the TargetFramework "net6.0-windows" is treated like "the application will be run on a desktop environment".
I always thought that "net6.0-windows" is for applications that uses Windows Specific APIs, which might be a Web Application. With the current behavior we had to use "net6.0" (which is in the end a good thing, but feels a bit drastic just because one NuGet package has a weird feature backed in).
Actual behavior
The desktop runtime is required.
Reproduction Steps

Create a MVC App and use "net6.0-windows" (or net8.0-windows) as TargetFramework
Add Azure.Identity
Deploy to azure

Result:
You must install or update .NET to run this application.

App: C:\inetpub\wwwroot\primedocs\Service\PrimeDocs.Service.Host.dll
Architecture: x64
Framework: 'Microsoft.WindowsDesktop.App', version '6.0.0' (x64)
.NET location: C:\Program Files\dotnet\

No frameworks were found.

Learn about framework resolution:
https://aka.ms/dotnet/app-launch-failed

Environment
Azure App Service

This issue has been transferred to the repository where the Microsoft.Identity.Client library is maintained as #4525.


Deprecation (logger, tracer, metrics): End Of Support of Node.js 12 runtime

Note
AWS Lambda has updated the table of Supported Runtimes to reflect that the deprecation has been delayed to Mar 31, 2023.

Description of the feature request
Problem statement

AWS is ending support for Node.js 12 in AWS Lambda. This follows Node.js 12 End-Of-Life (EOL) reached on April 30, 2022.
Starting November 14, 2022, Lambda will no longer apply security patches and other updates to the Node.js 12 runtime used by Lambda functions, and functions using Node.js 12 will no longer be eligible for technical support. In addition, customers will no longer be able to create new Lambda functions using the Node.js 12 runtime.
~Starting December 14, 2022, customers will no longer be able to update existing functions using the Node.js 12 runtime.~
Summary of the feature

Remove support and references of Node.js 12 included but not limited to:

CI/CD pipelines
Documentation (readme, docs)
Examples

Code examples

Benefits for you and the wider AWS community

Migration to the latest stable Node.js runtime with improved performance and new features.
Describe alternatives you've considered

N/A
Additional context

~AWS recommends that customers upgrade their existing Node.js 12 functions to Node.js 16 before November 14, 2022.
End of support does not impact function execution. Customer's functions will continue to run. However, they will be running on an unsupported runtime which is no longer maintained or patched by the AWS Lambda team.~
The following command shows how to use the AWS CLI to list all functions in a specific region using Node.js 12. To find all such functions in an AWS account, customers can repeat this command for each region:
aws lambda list-functions --function-version ALL --region us-east-1 --output text --query "Functions[?Runtime=='nodejs12.x'].FunctionArn"
For more information, refer to the AWS Lambda runtime deprecation policy.
Related issues, RFCs
N/A

IMPORTANT: this unit of work should be released only after the deprecation takes place for customers, so after December 14, 2022.

Note for implementer.  Please check if we can also update the target from ES2019 to a newer version. It was implemented in this PR: https://github.com/awslabs/aws-lambda-powertools-typescript/pull/925

I think we should instead drop support on November 14 (a month before) & indicate the last release before then as the last supporting NodeJS 12. In the messaging shared via email (& that you copied above) it says that after this date it worn't be possible to create new functions using the runtime. This means we won't be able to run e2e tests after that date.
In theory we could modify our e2e tests to reuse an existing Lambda function instead of creating a new one, but personally I don't think it's worth the effort.
As additional data point:

The AWS SDK v3 for NodeJS will deprecate the runtime a month and half before that (1 November) - link.
Depending on where we stand with the upcoming utilities (Idempotency & Parameters), if we were tu support NodeJS for longer, we'd be doing so without official support of the main dependency (aws-sdk).

My vote would be to align with the AWS SDK v3 timeline instead.

Deprecation date has been postponed to Mar 31, 2023 so we can put this task on hold.
I have updated the issue body to reflect the change. We'll revisit this later on.

CDK has marked the runtime as deprecated (2.43.0): https://github.com/aws/aws-cdk/commit/b8c2abf06ba14f9c356864aba91180a55cbd9c3b
Jest has dropped support for Node 12 with 29.x: https://github.com/facebook/jest/releases/tag/v29.0.0-alpha.0

Hi everyone, just wanted to share that AWS Lambda Powertools for TypeScript is planning on officially dropping support for Nodejs 12.x by the end of the year. This means that v1.5.0 will be the last release that supports the runtime.
At the time of writing, AWS Lambda plans to end support for the runtime at the end of March 2023. Similar to what done by a large portion of the Nodejs ecosystem, other AWS projects like CDK and the SDK v3 have already either marked the runtime as deprecated or removed support for it.
By following this path we'll be able to continue implementing the new Parameters and Idempotency utilities, which depend on AWS SDK v3, and also continue run full integration tests on each merged PR, a process that relies on CDK.
For those of you who are still using the Nodejs 12.x runtime, we strongly recommend you to upgrade your Lambda functions to Nodejs 16.x or later.


Feature: To collect FFDC for OpenBMC systems

Basically for each test case failure, Would like to collect relevant data like
Journalctl
PS
BMC version
OS Version - if it is related
TOP output - if it is performance issue
Hostboot state - output of obmcutil state, obmcutil bootprogress etc..

@gkeishin - George working on it already

Currently planned in 3 subsequent commits

Initial generic code library and supporting base supports basically a Robot Resource lib code

Default and custom log support - Default generic logs and User defined logs per test case on demand

Enable FFDC into the existing test cases - Plug into Teardown  ( 190 + test cases )

There could be limitation in some of the cases where we need to look into writing our own user library robot keywords to address those...

some of restructuring needed as pre work are addressed with https://github.com/openbmc/openbmc-test-automation/issues/41

Will use this ticket to drop the base infrastructure support code for open BMC FFDC.
A sample FFDC log is attached here..
The FFDC directory structure
logs/testSuiteName/testcaseName/openbmc_ffdc_report.txt
Example
$ tree logs
logs
└── TestSampleSuite
└── Verifyconnection
└── openbmc_ffdc_report.txt
2 directories, 1 file
openbmc_ffdc_report.txt

Current FFDC performance collection is 6 seconds...
==============================================================================
Test Sample
Verify Connection                                                     F
FFDC Collection Started 2016-07-20 00:46:42,185863
FFDC Collection Completed 2016-07-20 00:46:48,010589
Verify Connection                                                     | FAIL |
testing != OOPS
Test Sample                                                           | FAIL |

Mailing list posted https://lists.ozlabs.org/pipermail/openbmc/2016-July/004272.html


feat: adds cardTypes for custom bin validation

Description

feat: adds cardTypes for custom bin validation

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Odata version 4

Do you have plans add support Odata version 4 spec?
From - version 3
Note: OData Version 4.0 is the current recommended version of OData. OData Version 4.0 has been standardized by OASIS and has many features not included in OData Version 3.0.
Odata version 4 spec

Yes, there are parts of the query syntax I would like to implement, there are a couple of bits in v3 which I haven't yet implemented either.
Is there something in v4 which is preventing you from using this library or are you just wanting to use some of the new data types and methods?

For example: In v3 -  "substringof" function is the same "contains" in v4. But v4 doesn't support "substringof".

Closing this now as work has started on OData 4 support - check the milestone and branch for further info.


Tweaked the CircleCI instructions

Reflects current state of CircleCI.  Also adjusted the xdebug.ini editing script so we don't need as many lines

Looks good. @acorncom Before merging this, is this change still current?

Well, I'd rather merge this now and please make another PR if there was some update.

@tmatsuo Nope, these instructions still are up to date, I'm using them actively for several clients :-)


set handshake failure exception in connectionReadyPromise

Hi dear jchambers,
I found that from the cause method for connectionReadyPromise we never get the SSLHandshakeException even though there do have a handshake failure occured because we used a bad certificate to send notification and get this log in ApplicationProtocolNegotiationHandler
logger.warn("{} TLS handshake failed:", ctx.channel(), cause);

What we always get from the cause method for connectionReadyPromise when handshake failure occur is the IllegalStateException created in closeFuture's listener in ApnsClient:
new IllegalStateException("Channel closed before HTTP/2 preface completed.")

I think we need to call
super.handshakeFailure(context, cause);

behind ctx.close() in the handshakeFailure method of ApplicationProtocolNegotiationHandler. In this way we never got this problem ever.
What do you think?

Sounds good to me! Please pardon the slow reply, and thanks for the fix!


Visual preview of action outcome

Solution for issue #40
For every stat I created 2 preview gameobjects (for left and right swipe outcome) which I set after new card is spawn. These gameobjects have Canvas Group component with which I set alpha depending on current card position (same way text on card is shown/hidden).
Each preview gameobject has 2 stat images. These images show current stat and change this action will yield. Here is an image of how that looks.

I think with the whole stat bar lighting up green or red, it may be hard to tell by how much the stats are going to change. Can we highlight just the difference in green or red? slightly less vibrant colours would be a plus, too.

of course. Would something like this look better?

Definitely! And with brighter, less saturated colours, too, so they blend into neither the background nor the current level :)


brut.common.RootUnknownFileException: Absolute Unknown Files is not allowed

Information

Apktool Version (apktool -version) - Latest 2.4
Operating System (Mac, Linux, Windows) - Linux
APK From? (Playstore, ROM, Other) - Playstore

I get that error while trying to rebuild an apk that was disassembled with apktool

I would need the APK to investigate this further. This is a security protection to prevent extracting from overwriting files in crucial places, so files that are explicit with a root path like that are denied - and for good reason. You wouldn't want a file in root called "deviceinsight-collector". It may be intended for root of application, but need APK to investigate.
Marking as waiting on issuer.

https://www.apkmonk.com/download-app/com.schwab.mobile/4_com.schwab.mobile_2019-10-07.apk/
Here's a download link to the app
On Fri, Oct 25, 2019 at 11:39 PM Connor Tumbleson<EMAIL_ADDRESS>wrote:

I would need the APK to investigate this further. This is a security
protection to prevent extracting from overwriting files in crucial places,
so files that are explicit with a root path like that are denied - and for
good reason. You wouldn't want a file in root called
"deviceinsight-collector". It may be intended for root of application, but
need APK to investigate.
Marking as waiting on issuer.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/iBotPeaches/Apktool/issues/2201?email_source=notifications&email_token=AGAM4XATBFYOQVFV3MD6XXDQQMHJRA5CNFSM4JEKFRH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECIXOSI#issuecomment-546404169,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGAM4XAA5PBFU2RHPXQLTT3QQMHJRANCNFSM4JEKFRHQ
.

https://www.apkmonk.com/download-app/com.schwab.mobile/4_com.schwab.mobile_2019-10-07.apk/
Here's a download link to the app

I replicate. The root issue is useless. We normalize the path so anything in /root would just become root in the root of the application. Will fix that up.

Tempted to close as no-fix. I attempted a PR, but it won't work because windows.
➜  2201 unzip -l com.schwab.mobile_2019-10-07.apk
Archive:  com.schwab.mobile_2019-10-07.apk
  Length      Date    Time    Name
---------  ---------- -----   ----
      536  1969-12-31 19:00   /deviceinsight-collector-javascript-6.6.0-0.pom
    66648  1980-00-00 00:00   AndroidManifest.xml
     1456  1980-00-00 00:00   META-INF/CERT.RSA
   399994  1980-00-00 00:00   META-INF/CERT.SF

This is just a bad apk. It has a root reference.

➜  2201 apktool d com.schwab.mobile_2019-10-07.apk -f
I: Using Apktool 2.5.1-d1c006-SNAPSHOT on com.schwab.mobile_2019-10-07.apk
I: Loading resource table...
I: Decoding AndroidManifest.xml with resources...
I: Loading resource table from file: /home/ibotpeaches/.local/share/apktool/framework/1.apk
I: Regular manifest package...
I: Decoding file-resources...
I: Decoding values */* XMLs...
I: Baksmaling classes.dex...
I: Baksmaling classes2.dex...
I: Baksmaling classes3.dex...
I: Baksmaling classes4.dex...
I: Copying assets and libs...
I: Copying unknown files...
W: Skipping file /deviceinsight-collector-javascript-6.6.0-0.pom (Absolute Unknown Files is not allowed)
I: Copying original files...
➜  2201

PR up for above.


Multiple calls to Message at the same time result an error

[ ] I'm sure this does not appear in the issue list of the repository

Basic Info

Package Name And Version<EMAIL_ADDRESS>Browser: chrome97.0.4692.99
Reproduction Link: https://arco.design/vue/component/message

What is expected?
no error
Steps to reproduce
<script lang="ts" setup>
import { Message } from '@arco-design/web-vue'
Message.error('添加失败')
Message.error('添加失败')
</script>

@jinxinkai This problem will appear on the first simultaneous call, creating multiple instances, this version will fix it


Readme routing fix

bitbag_sylius_cms_plugin:
    resource<EMAIL_ADDRESS>
to
bitbag_sylius_cms_plugin:
    resource<EMAIL_ADDRESS>    prefix: /admin

Thank you, Jan!


Readme bumps

This PR just bumps version references in the README
A tiny followup to https://github.com/hseeberger/scala-sbt/pull/179

Might be better to switch to jdk17 for the docs? (where available)


Make managed installs list sortable

The managed installs list table on the managed software tab is now
sortable using dataTables. Enhancement Request #178. Thanks for bearing with me on the pull requests and sorry I am such a gitiot.

Thanks!


Lightbulb or other visual cue for refactorings

We have the squiggles now to show some potential analyser fixes, but we don't have any indicator that a potential refactoring is possible.

Landed as 1d742aacea0 / #370


event webhook doc update

*sg_event_id can't be used as a differentiator where its not present. Made an update in event.md *

Description of the change: Updated event.md doc
Reason for the change:  sg_event_id can't be used as a differentiator where its not present.
Link to original source: https://github.com/sendgrid/docs/issues/2862
Closes #2862
@ksigler7

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hello @sayak119,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


Fix PHP headers and unit tests

Fix getGapicVersion function
Fix unit test generation for files without return type

Codecov Report

Merging #1086 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1086   +/-   ##
=========================================
  Coverage     85.53%   85.53%
  Complexity     3495     3495
=========================================
  Files           365      365
  Lines         13844    13844
  Branches       1573     1573
=========================================
  Hits          11841    11841
  Misses         1554     1554
  Partials        449      449

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 641935a...c5ed4f8. Read the comment docs.

LGTM


[AutoPR servicefabric/data-plane] Remove newline characters at the end of the description property value.

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3524

(message created by the CI based on PR content)