feat(theme): added new styles for component Skeleton

Styles for component Skeleton
Introduction
In this PR add new feature for component Skeleton, it is about styles:
Details
Added new variants like:

rounded

Api refernece
 const variants = {
   rounded: {
      none: 'rounded-none',
      sm: 'rounded-sm',
      md: 'rounded-md',
      lg: 'rounded-lg',
      full: 'rounded-full',
   }
}

new animation
const animations = {
  animation: {
    'pulse-infinite': 'pulse-infinite 2s cubic-bezier(0.4, 0, 0.6, 1) infinite',
  },
  keyframes: {
    'pulse-infinite': {
      '0%': {
        opacity: 1,
      },
      '50%': {
        opacity: 0.5,
      },
      '100%': {
        opacity: 1,
      },
    },
  },
}

Related problems
Resolves #250
Preview
By default, for rounded the variant is full and icons is none
mode light
https://github.com/OpenLab-dev/openui/assets/128724547/1b09d59e-5157-4a64-bf20-348b5954fac3
mode dark
https://github.com/OpenLab-dev/openui/assets/128724547/e8e068a8-227a-40af-a92e-c12507616b78
How to use
import { Skeleton} from '@openui-org/react'

function CheckboxExample() {
return <Skeleton/>
}

LGTM


package name should be validated before publishing

Package names with underscores (instead of dashes) can confuse PyPI indexers.
The packaging step (or an earlier build validation step) should check the package name against validating regular expressions before publishing.
A failure in validation should fail the build with a helpful message about how to fix it.

Fixed by changes in 7974048d2c26bf8b6d95205739410ff7bc626393
https://github.com/KairosAerospace/dkr-circleci/blob/7974048d2c26bf8b6d95205739410ff7bc626393/build_bin/kairos_python_deploy#L9-L16


remove node engine from package.json

I cannot use this in my current project because I am using node version 12, but this library forces node version to 8.

💜 Thanks @ssowonny
Are you planning a release any time toon?


Critical: 'Path cannot be empty'

Fresh install with:

Grav: v1.7.7
Admin: v1.10.6

Going to Tools > Logs and selecting 'Email Log' on the first dropdown menu throws a 500 error.
In the 'Grav System Log' a 'critical' error shows up as 'Path cannot be empty' with the following verbose output:
 /var/www/html/system/src/Grav/Common/Helpers/LogViewer.php(57): fopen('', 'rb')
 /var/www/html/system/src/Grav/Common/Helpers/LogViewer.php(36): Grav\Common\Helpers\LogViewer->tail(false, 20)
 /var/www/html/vendor/twig/twig/src/Template.php(702): Grav\Common\Helpers\LogViewer->objectTail(false, 20, false)
 /var/www/html/cache/twig/94/94b142c62db7e41d8b6f634ef8f90cce3bce97689e798c31d9c84cb6d9d6118b.php(54): Twig\Template->getAttribute(Object(Grav\Common\Helpers\LogViewer), 'objectTail', Array, 'method')
 /var/www/html/vendor/twig/twig/src/Template.php(453): __TwigTemplate_aaf73f8a8f4bbad5ac0b80447e6a6dd88bce94b156e2ce84bd99ff37f32f35e5->doDisplay(Array, Array)
 /var/www/html/vendor/twig/twig/src/Template.php(420): Twig\Template->displayWithErrorHandling(Array, Array)
 /var/www/html/cache/twig/89/8908abb9fd86e218bef96a07a2085efb6f058b4bd3b7ab75f44133d3c3057942.php(166): Twig\Template->display(Array)
 /var/www/html/vendor/twig/twig/src/Template.php(214): __TwigTemplate_9911a9be75d869c7c91dcb31c59b331e1be18d826531fd932963706b5a5d1116->block_content(Array, Array)
 /var/www/html/cache/twig/e2/e2d8c56b2cabf6174f67c5b934befacc91956b0682a9a6625766d45b4ed68d77.php(317): Twig\Template->displayBlock('content', Array, Array)
 /var/www/html/vendor/twig/twig/src/Template.php(214): __TwigTemplate_8da8783a11985568a56090ec88cc253b1c6df47687c434d66458f7838f80ab1d->block_content_wrapper(Array, Array)

I can see that the HTTP request performed when using that option is '/admin/tools/logs?verbose=true&log=email.log'. I don't have an 'email.log' file on any path of my Grav installation so I guess that can be the problem.
There is a similar issue described on #3265, but what you have to do to reproduce it is way different, so I don't know if this have the same origin.

This doesn't look like the same issue as in #3265 which was a bug in uploaded file handling.
Might be related to the missing log file, there's likely a missing check for file existance.

Great, thanks!

released


ffmpeg-normalize: 1.19.0 -> 1.22.1

Motivation for this change

version update ffmpeg-normalize: 1.19.0 -> 1.22.1
move from ffmpeg_3 to ffmpeg (part of https://github.com/NixOS/nixpkgs/issues/120705)
introduce ffmpeg-progress-yield dependency

Things done

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

[ ] 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)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 120848 at ecf9ff2b run on aarch64-linux 1

3 packages built successfully:

ffmpeg-normalize
python38Packages.ffmpeg-progress-yield
python39Packages.ffmpeg-progress-yield

Result of nixpkgs-review pr 120848 run on x86_64-linux 1

3 packages built:

ffmpeg-normalize
python38Packages.ffmpeg-progress-yield
python39Packages.ffmpeg-progress-yield


Upgrade to docusaurus 2

Motivation:

docusaurus-build on 1.x is very slow. I spent some time trying to monkeypatch it to be faster, but ultimately failed at this.
docusaurus build on 2.x seems much faster. It looks better, and there are some nice features

Take a look yourself:
https://5f49290d80ad146dc21cec9e--nitro-protocol.netlify.app/docs/
To note:

Docusaurus 2 stores the entire snapshot of the docs when you cut a new version. when of versions are saved. So the problem of having lots of .md files is exacerbated. In the end I just nuked all versioned_docs on this branch as this was annoying me. Sadly I don't think git LFS would be much help if we wanted to keep using versioning.
I spent some time fixing mermaid diagrams, which got broken as a part of the migration.
The build job needs more memory on circle
the combination of upgrade and nuking old docs (but mostly nuking old jobs) means it builds a lot faster. About 1 minute to build, and 1 minute to deploy to netlify.

TODO

[ ] Take a careful look through the site to see if anything isn't as good as it was
[x] Decide on what to do about versioning
[ ] fix all the broken links that are highlighted in the output of docusaurus build
[ ] fix solidity syntax highlighting

https://v2.docusaurus.io/docs/versioning
It seems that docusaurus themselves would not recommend using versioning for our site, and certainly not to cut versions as often as we do. So I think versioning is out.

:racehorse: :scissors: this looks like an awesome change set. It's unfortunate about the versioned docs, but perhaps we can revisit that later with a different approach.


FDW unit test fixes

Context
This PR fixes the tests that were broken by the FDW implementation. Coders extracted the new_importer method and the tests in table_spec.rb where stubbed an weak (they made assumptions on the implementation of new_importer).
The fix is to fix the bad stub. It's not worth it to remove it, since merge code handles importers differently anyway.
There is also one minor mod: the common data user fetch doesn't assume that common data is present in app_config.yml.

@mbektas here's the fix for FDW, please review when you can


Handling error messages for validations

Hey Valery,
Here is the changeset to resolve #33.
Thanks for consider to merge the code!

Coverage decreased (-0.2%) to 71.287% when pulling db4ae6fdb2f6bc270eb485dc40a7352d15a855ac on puentesarrin:error_messages into a08f132c8cbe94586e381ab37a13d8cbcb725d7d on bodbdigr:master.


[🐛] build fails with module not found when building the project

:bug: Bug report
Description
Looks like there is a react dependency on useShallow that is coming from zustand. I was getting the error below when running a npm install on nodejs version 20. It worked once I added react as a dependency in the package.json. Also looks like the folks that maintain zustand are aware.
https://github.com/pmndrs/zustand/discussions/2095
:microscope: Minimal Reproduction
run npm install
:fire: Exception or Error

./node_modules/zustand/esm/shallow.mjs:1:0-31 - Error: Module not found: Error: Can't resolve 'react' in '/home/andrew/juice-shop/frontend/node_modules/zustand/esm'

:deciduous_tree: Your Environment

v20.8.0
10.1.0

Additional Information

This is solved on develop branch already by adding+pinning zustand to the previous version. Should also be in the snapshot Docker image already.

Release v15.2.1 is currently building and addresses this issue.


huestecan purple screen

i currently have huestecan on my W10 PC, while i start syncing, it only detects the color purple. i have no clue why and i cant change it in the settings. whats the matter? im using V2.6


Support custom winbar filename

It's convenient to custom winbar filename with custom file formatter.
When set file_formatter to %:., it will expand to:

should be document.

Done


I18n Country Select

Please support also localized_country_select so a full I18n support is available.
Also this module is quite more up to date an fetches the offcial ISO Codes.
( https://github.com/karmi/localized_country_select )
Thank You !

I'm closing this issue - it's been dormant for 4 months now, the reference to a maintained version of country_select has been updated a few days ago.
If there's the need for a country_select plugins that translated the country names there are maintained gems like carmen that are compatible to the original country_select implementation and can be used with formtastic.


Todoist Plugin Not Rendering in Live Preview Mode in Obsidian v0.13.4

Describe the bug
Obsidian introduced a Live Preview feature that renders elements and plugin code blocks in line. This does not work for this plugin.
To Reproduce
Steps to reproduce the behavior:

Write a todoist plugin code block
Click outside of it
It isn't rendered.

Expected behavior
Rendered live into a functioning todoist task list.
Screenshots
Live Preview Mode:

Preview Mode

Desktop:

Plugin Version 1.8.1
Obsidian Version 0.13.4

Have you tried again in 13.14? It works for me.

@aventuraviper It doesn't for me. Does it depend on the theme, or do you have a custom css for that?

Have you tried again in 13.14? It works for me.

Just installed and checked the latest version—no dice. I'd echo what @ChrArendt said: do you have some sort of custom css that may be making it work when it otherwise wouldn't?

Does not work for me either, v0.13.19

Not working for me either, v0.13.19.

Also not working for me, v.0.13.19

Apologies, I can confirm it is isn't working for me on v.0.13.19.
I usually use Todoist blocks by referencing them into another note using ![[note with todoist code block]]. These work fine in Live preview (are always rendered). I also had a pluigin swapping between edit and read that was taking me out of live preview and into reading mode when I tried to reproduce.
Again, apologies.
Is this due to the Todoist block syntax perhaps? Other plugins that use blocks like this, such as tasks or Toggl, don't need curly braces or quote marks, so perhaps these trip the live preview mode into treating it as a regular block of code text?

Hey all, will take a look at this one over the weekend and try to get a fix out then!

Little update on this one: I've got it rendering in Live preview and the functionality seems to work, but the styling is all out of wack.  Weirdly it doesn't seem like anything to do with CSS, there's just extra spacing added between some of the divs.

That's good to hear! I've seen issues like this(spacing) happen with other plugins. I even reported the issue for Admonition. Not sure if it'll help, but maybe the way they fixed it will provide some manner of insight.

@lukthony that's perfect, seems to resolve most, if not all the issues, will do some further testing and then cut a release!

Glad to help. Thanks for everything.

Hey all, this should be fixed in v1.9.0, let me know if you notice regressions. You may need to adjust any custom CSS accordingly!


Type error with subject example code

Documentation Related To Component: Subject

Please check those that apply

[ ] typo
[ ] documentation doesn't exist
[ ] documentation needs clarification
[x] error(s) in example
[ ] needs example

Description Of The Issue
import { Subject, from } from "rxjs";

const subject = new Subject<number>();

subject.subscribe({
  next: (v) => console.log(`observerA: ${v}`),
});
subject.subscribe({
  next: (v) => console.log(`observerB: ${v}`),
});

const observable = from([1, 2, 3]);

observable.subscribe(subject); // You can subscribe providing a Subject

// Logs:
// observerA: 1
// observerB: 1
// observerA: 2
// observerB: 2
// observerA: 3
// observerB: 3

there is a type error which is about overload at observable.subscribe(subject)

I don't see any type errors in RxJS 6.6.3 and you haven't filled out the issue template, so IDK what version you are using.

I use RxJS 6.6.3, typescript 4.0.2, ts-node 9.0.0
When I used ts-node, there was below error.

and tsc compile had this error.

So, I add es2020 and dom in lib option of tsconfig. then ts-node error is solved. but there are same error with tsc compile

From the docs:

When input files are specified on the command line, tsconfig.json files are ignored.


[Bug] RoutineLoad重复消费

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
1.2.7
What's Wrong?
routine load 配置了如下参数，在stop重新创建后，会从头开始消费数据
property.kafka_default_offsets="OFFSET_BEGINING",
property.auto.offset.reset="earliest"
What You Expected?
希望的是，如果该消费者组没有offset，则从最早消息开始消费；如果offset存在，则从offset开始消费。
但是property.auto.offset.reset="earliest"并不生效，不知道正确的配置是什么，还是就是有bug
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

When a job is created, it is a new job and does not have any relation with stopped jobs. So it works as expected.

I know  it is a new job,but the kafka consumer group are the same,so why it consume from the begin,not from the last offset;

You can set offsets when creating a new job, it consums from the specified offsets.
thks  for  your  answer;
my topic has  many partitions(≥50),so set  the  offsets  will be  very  difficult;  what  i  hope  is can  routine  load work like  other  normal  kafka  client，when  auto.offset.reset=earliest，it  consume  from the  last  offset，if  the  last offset  not  exist, it  consume  from  the  beginning.

@dataroaring In many commonly used components, the existing consumer group offset is prioritized, and the default offset is only used when the consumer group offset doesn't exist. This is the case with Kafka clients, ClickHouse's Kafka engine, Flink, and others. Why does Doris handle this differently?

When a job is created, it is a new job and does not have any relation with stopped jobs. So it works as expected.

auto.offset.reset: Action to take when there is no initial offset in offset store or the desired offset is out of range: 'smallest','earliest' - automatically reset the offset to the smallest offset, 'largest','latest' - automatically reset the offset to the largest offset, 'error' - trigger an error (ERR__AUTO_OFFSET_RESET) which is retrieved by consuming messages and checking 'message->err'.
Refer to：https://github.com/confluentinc/librdkafka/blob/master/CONFIGURATION.md

Perhaps you need to upgrade your version. Doris 2.0 and above already support this feature，when you pause your routine task, the offset already consumed will be recorded, and when you restart it, it will be consumed from offsert


Attempt to cache bundler

This flag does not appear to work correctly based on our current configuration (perhaps related to appraisal + multiple versions of Ruby/Rails)?


launch

Ran Plan for dir: . workspace: default
Show Output
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+ create

Terraform will perform the following actions:

  # google_compute_instance.default will be created
+ resource "google_compute_instance" "default" {
      + can_ip_forward       = false
      + cpu_platform         = (known after apply)
      + current_status       = (known after apply)
      + deletion_protection  = false
      + guest_accelerator    = (known after apply)
      + id                   = (known after apply)
      + instance_id          = (known after apply)
      + label_fingerprint    = (known after apply)
      + machine_type         = "e2-micro"
      + metadata_fingerprint = (known after apply)
      + min_cpu_platform     = (known after apply)
      + name                 = "atlantis-vm-dev"
      + project              = (known after apply)
      + self_link            = (known after apply)
      + tags                 = [
          + "dev",
          + "engineering",
        ]
      + tags_fingerprint     = (known after apply)
      + zone                 = "us-central1-a"

      + boot_disk {
          + auto_delete                = true
          + device_name                = (known after apply)
          + disk_encryption_key_sha256 = (known after apply)
          + kms_key_self_link          = (known after apply)
          + mode                       = "READ_WRITE"
          + source                     = (known after apply)

          + initialize_params {
              + image  = "projects/ubuntu-os-cloud/global/images/ubuntu-2204-jammy-v20221014"
              + labels = {
                  + "env" = "dev"
                }
              + size   = (known after apply)
              + type   = (known after apply)
            }
        }

      + network_interface {
          + ipv6_access_type   = (known after apply)
          + name               = (known after apply)
          + network            = "default"
          + network_ip         = (known after apply)
          + stack_type         = (known after apply)
          + subnetwork         = (known after apply)
          + subnetwork_project = (known after apply)

          + access_config {
              + nat_ip       = (known after apply)
              + network_tier = (known after apply)
            }
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

:arrow_forward: To apply this plan, comment:

atlantis apply -d .

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -d .

Plan: 1 to add, 0 to change, 0 to destroy.

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

atlantis apply

Ran Plan for dir: . workspace: default
Show Output
google_compute_instance.default: Refreshing state... [id=projects/terraformprojects-365816/zones/us-central1-a/instances/atlantis-vm-dev]

Changes to Outputs:
+ hostname          = ""
+ instance_id       = "2979553188716095310"
+ network_interface = [
      + {
          + access_config      = [
              + {
                  + nat_ip                 = "<IP_ADDRESS>"
                  + network_tier           = "PREMIUM"
                  + public_ptr_domain_name = ""
                },
            ]
          + alias_ip_range     = []
          + ipv6_access_config = []
          + ipv6_access_type   = ""
          + name               = "nic0"
          + network            = "https://www.googleapis.com/compute/v1/projects/terraformprojects-365816/global/networks/default"
          + network_ip         = "<IP_ADDRESS>"
          + nic_type           = ""
          + queue_count        = 0
          + stack_type         = "IPV4_ONLY"
          + subnetwork         = "https://www.googleapis.com/compute/v1/projects/terraformprojects-365816/regions/us-central1/subnetworks/default"
          + subnetwork_project = "terraformprojects-365816"
        },
    ]

You can apply this plan to save these new output values to the Terraform
state, without changing any real infrastructure.

:arrow_forward: To apply this plan, comment:

atlantis apply -d .

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -d .

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

Locks and plans deleted for the projects and workspaces modified in this pull request:

dir: . workspace: default


Is there any information loss during the conversion process

Thanks for your sharing firstly.  I have noticed that the original MIDI file and the MIDI file obtained after conversion using midi2note are not consistent.
there is my note2midi convert:
midi = pretty_midi.PrettyMIDI(resolution=960)
instrument = pretty_midi.instrument.Instrument(program=0, is_drum=False, name='piano')

for note_data in note_list:
    pitch = note_data['pitch']
    onset = note_data['onset']
    offset = note_data['offset']
    velocity = note_data['velocity']

    # 创建Note对象并添加到MIDI对象中
    note = pretty_midi.Note(
        velocity=velocity,
        pitch=pitch,
        start=onset,
        end=offset
    )
    instrument.notes.append(note)

# 将乐器添加到PrettyMIDI对象中
midi.instruments.append(instrument)

midi.write('tmp_note.mid')

And the ori midi like this:

Then convert to note and convert the note to midi:

this case is '2018/MIDI-Unprocessed_Chamber2_MID--AUDIO_09_R3_2018_wav--1.midi' in MAESTRO-V3 dataset.

Hello @Chunyuan-Li
Thank you very much for the comment.
I apologize for the delay in responding, as I have just realized this issue.
Our hFT-Transformer does not transcribe pedal information (control change #64), so we convert the MIDI information as played without a pedal. This conversion makes longer duration if the pedal is used.
We implement this process in https://github.com/sony/hFT-Transformer/blob/master/corpus/conv_midi2note.py.
If you listen to both MIDI files, you can notice that both are identical in the audio domain.

If represented as sheet music, on one hand, the presence of the pedal causes the durations of the notes we derive from audio to be longer than standard. On the other hand, the poor separation of piano hands in the score (mainly due to the fact that the maestro dataset consists of single-track MIDI while in Musescore it is dual-track) leads to an appearance that is consistent audibly but looks quite distorted. I'm wondering if you have researched these two issues.

If represented as sheet music, on one hand, the presence of the pedal causes the durations of the notes we derive from audio to be longer than standard. On the other hand, the poor separation of piano hands in the score (mainly due to the fact that the maestro dataset consists of single-track MIDI while in Musescore it is dual-track) leads to an appearance that is consistent audibly but looks quite distorted. I'm wondering if you have researched these two issues.


Error in documentation for Pagination

Looking at the documentation on pagination.
props({ data: { loading, feed, currentUser, fetchMore } }) {
    return {
      loading,
      feed,
      currentUser,
      loadMoreEntries() {
        return fetchMore({
          // query: ... (you can specify a different query. FEED_QUERY is used by default)
          variables: {
            // We are able to figure out which offset to use because it matches
            // the feed length, but we could also use state, or the previous
            // variables to calculate this (see the cursor example below)
            offset: feed.length,
          },
          updateQuery: (previousResult, { fetchMoreResult }) => {
            if (!fetchMoreResult.data) { return previousResult; }
            return Object.assign({}, previousResult, {
              // Append the new feed results to the old one
              feed: [...previousResult.feed, ...fetchMoreResult.data.feed],
            });
          },
        });
      },
    };
  },
})(Feed);

Shouldn't the offset being set in loadMoreEntries be something like pageSize * pageNumber - 1.
For example if I am on page 1 with a page size of 10 and I click on page 3, based on the example, my offset will be 10, when it should be 20.

I think props gets called again with a new feed after your first loadMoreEntries? Have you tried it @ryannealmes?

@tmeasday, note I am not saying load entries is not being called. I am saying the example does not return the correct data when it is called. In pagination your offset is based on the number you click 1,2,3,4,5. If I click 3 my offset is not the feed.length.
Hence the example is invalid.
Maybe I missing something?
I know that if you have loaded entries sequentially then the offset would most likely be correct, but if you skip pages I think the offset is wrong.

Oh. Well this is example is intended as an "infinite scroll" type situation.
If you wanted to do a paged style approach, you'd need to pass an offset argument into the loadMoreEntries callback.

Ah ok. From the documentation it felt like it was talking about numbered pages and not infinite scrolling. It may be good to make this distinction.
Just for reference this is what is describing the functionality.
Offset-based pagination — also called numbered pages — is a very common pattern, found on many websites, because it is usually the easiest to implement on the backend. In SQL for example, numbered pages can easily be generated by using OFFSET and LIMIT.
Thanks for clearing that up though. Appreciate the time! Loving apollo!

Yeah, I can see where you are coming from. I think the wording is a bit awkward there. Perhaps you can suggest an improvement via a PR?


Error handling after future timeout

If an instance times out during startup (future timeout) we get a strange behavior. The instance has been added to the database successfully but timed out during connection to the docker host. But nonetheless the instance was not removed afterwards and was reported with state deploying to the management application

I'm currently not able to reproduce this, thus moving it to the next milestone.

Referring #131

Closed with #131


Allow to include files with underscore and numbers

Fixes #130

Hello! Thanks for the PR, good catch 😝
Going further I have checked the docs and it seems there would still be valid names not catched, they even suggest the regex [a-zA-Z_\x80-\xff][a-zA-Z0-9_\x80-\xff]* so I think that would be perfect. Do you mind to add this change?

Well, the class name can even consist of emojis themselves :facepalm: :joy:.

Today I'll be checking some errors I've seen while running in php 7.4, either I can fix them or not on time, I will release this tonight.
Thank you again!


[BUGFIX] -  Analytics Mixpanel board showing -null- and -not set- fields

📝 Description
Analytics Mixpanel board was showing -null- and -not set- fields

Before
After

LOG  selectedLanguage     default : fr
LOG  selectedLanguage fr     default : fr

if we look at the code block
 useEffect(() => {
    if (selectedLanguage) { // now this value is set with a default value so updateIdentify is triggered and then update value for Segment & Mixpanel
       ...

      dispatch(setLanguage(selectedLanguage));
      updateIdentify();
    }
  }, [dispatch, selectedLanguage, toggleModal]);

❓ Context

JIRA or GitHub link: LIVE-6672

✅ Checklist
Pull Requests must pass the CI and be code reviewed. Set as Draft if the PR is not ready.

[x] npx changeset was attached.
[ ] Covered by automatic tests.
[x] Impact of the changes: Analytics update

🧐 Checklist for the PR Reviewers

[x] The code aligns with the requirements described in the linked JIRA or GitHub issue.
[x] The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
[x] There are no undocumented trade-offs, technical debt, or maintainability issues.
[x] The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
[x] Any new dependencies have been justified and documented.
[x] Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

Doing that introduce a bug, so i'll put in draft during investigation :)


Killed characters are now resurrected after 3 seconds

Also, added helpful function for finding free space for adding new objects. Useful for creating powerups later too. @dekespo

There is some bug, when AI hits with so many projectiles at the same time (due to the different velocity of each projectile), it gives segmentation fault.

Yes, I've noticed it too, and am not sure where it occurs. Take a look if you want.


Update all Zewo modules to the new 07-25 snapshot

The plan:

All dependencies pointed at 0.10 (with the exception of Open-Swift/S4, which should be pointed at 0.11)
The version in the README updated to majorVersion: 0, minor: 10
The badge in the README updated to 0.10 (i.e. )
Once the branch satisfies the requirements, a pull request is to be created (merging into master, obviously)
Build and run the tests locally, and fix any warnings or errors
Create a new tag 0.10.0

List of relevant repositories:

[ ] Zewo/Zewo
[ ] Zewo/Router
[ ] Zewo/HTTP
[ ] Zewo/Mustache
[ ] Zewo/Sideburns
[ ] Zewo/JSON
[ ] Zewo/JSONMediaType
[ ] Zewo/MediaType
[ ] Zewo/HTTPSerializer
[ ] Zewo/URI
[ ] Zewo/CURIParser
[ ] Zewo/HTTPParser
[ ] Zewo/CHTTPParser
[ ] Zewo/OpenSSL
[ ] Zewo/COpenSSL
[ ] Zewo/SQL
[ ] Zewo/PostgreSQL
[ ] Zewo/CLibpq
[ ] Zewo/MySQL
[ ] Zewo/CMySQL
[ ] Zewo/WebSocket
[ ] Zewo/WebSocketClient
[ ] Zewo/WebSocketServer
[ ] Zewo/EngineIOServer
[ ] Zewo/BasicAuthMiddleware
[ ] Zewo/Base64
[ ] Zewo/POSIXRegex
[x] Zewo/POSIX
[x] Zewo/String
[ ] Zewo/TrieRouteMatcher
[ ] Zewo/StructuredData
[ ] Zewo/Log
[ ] Zewo/LogMiddleware
[ ] Zewo/URLEncodedForm
[ ] Zewo/ContentNegotiationMiddleware
[ ] Zewo/RegexRouteMatcher
[ ] Zewo/Redis
[ ] Zewo/Event
[x] Zewo/XML
[x] Zewo/CLibXML2
[ ] Zewo/PathParameterMiddleware
[ ] Zewo/Mapper
[ ] Zewo/RecoveryMiddleware
[ ] Zewo/BranchMiddleware
[ ] Zewo/Resource
[ ] Zewo/RedirectMiddleware
[ ] Zewo/URLEncodedFormMediaType
[ ] Zewo/UUID
[ ] Zewo/SessionMiddleware
[ ] Zewo/TodoBackend
[ ] Zewo/Reflection
[ ] Zewo/CUUID
[x] Zewo/zlib
[x] Zewo/gzip
[x] VeniceX/Venice
[x] VeniceX/CLibvenice
[ ] VeniceX/ChannelStream
[ ] VeniceX/IP
[ ] VeniceX/TCP
[ ] VeniceX/HTTPServer
[ ] VeniceX/HTTPClient
[x] VeniceX/File
[ ] VeniceX/HTTPFile
[ ] VeniceX/UDP
[ ] VeniceX/TCPSSL
[ ] VeniceX/HTTPSServer
[ ] VeniceX/HTTPSClient

Looking at that list, I'm sure we could script most of the work described above. Maybe automatically: 1. switch to master, 2. pull, 3. make sure clean git status, 4. create and switch to branch 3.0-preview-1, 5. switch .swift-version, 6. swift build --clean=dist, 7. swift build, 8. swift test, then human will check no warnings, errors, test failures and finish each repo up? There needs to be a better way going forward then doing all these manually one by one :)

Great idea! Once we resolve the swiftenv issue we'll work on that :)

On July 5th, 2016 preview 2 was released, is that now the intended goal?

@Lidbetter There are a number of issues with the previews. We're probably going to adopt the next development snapshot that comes out (after 06/20), though right now we're busy with Quark :)

@czechboy0 could you check off the repositories which you updated? Thanks!

@Danappelxx Done, I also checked off the ones that didn't need any update to work with 07-25 (so no new release was made).

This is not the workflow we're going to use. Instead, we're going to work with a monolith at zewo/flux and update from there.


Enable wallet encryption

#179 was opened and then addressed some time later in #212 which was then closed because it would require refactoring. I cannot find any evidence that this is being worked on.
It's a matter of history that an unencrypted wallet is asking for trouble. Steps to using hot wallets:

Download wallet
Encrypt Wallet with high entropy
Don't forget to encrypt wallet

It would be my opinion, that having a wallet where one can store LBC tokens with some level of confidence is probably one of the most important aspects of any blockchain related project. Otherwise, we're forced to rely on centralized exchanges for our security.
We all know how that ends.

Thanks for your response on #212.

Is there presently a bounty reward for the person responsible?
Can we pool the bounty to incentivize this to get done sooner? (last progress update was ~6 months ago)
Is there anything the community can do to help push this up on the list?

Take a look at https://github.com/lbryio/lbry/pull/631 for most recent update.
Adding encryption adds a layer of inconvenience to the users, which needs to be dealt with carefully so as not to disrupt the UX.
We've recommended creating a separate wallet (generated, zipped and password protected) for storing large amounts of LBC.
We also were recently integrated to Coinomi, which should be coming to Ios and desktop soon. This is not the best solution as it doesn't allow the wallet to integrate the app, but it's a safe haven nonetheless.
We understand your concerns, thanks for your research and suggestions. I'm sure this will become a bigger priority once the app improves functionality wise.

As someone who has a day job that consists of standing between marketers who want to destroy UX and backend devs who do everything they can to make it difficult, I empathize
However, anything that deals with storing and/or transmitting cryptocurrency is essentially a bank. This argument is not much different from saying that password strength requirements are an encumbrance to conversion rates, and thus shouldn't be enforced because UX.
UX doesn't mean anything if the entire value metric that your technologies lies upon is compromised and subsequently sinks the community as well.
The solution seems obvious to me, as this is how it was done in the early days. Encryption is optional, users decide whether or not they want to encrypt their wallets. They either choose convenience or security, and are thus responsible for their decision. I for one don't mind entering my password

I'll share your concerns with the team, in the case they don't read this.
Coinomi with LBC is available for Android right now and from what we hear, ios and desktop projects are around the corner.

And it's being worked on aswell :)

I set up a description for password interface for anyone that wants to work on this https://github.com/lbryio/lbry/pull/712

closed by #783


Is there a one-page doc to tell which function now changes to which in OpenSSL3?

Actually, my question is quite general:
It looks a lot of functions in OpenSSL1.1.1 is NOW deprecated in OpenSSL3 .

Is there a doc to tell which function in  OpenSSL1.1.1 is NOW change to which function in OpenSSL3 ???
Or any documentaion that provides a very simple code snippet to compare the implementation based on OpenSSL1.1.1 and the implementation using OpenSSL3 .

error: ‘EVP_PKEY_get1_RSA’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations]
error: ‘SSL_CTX_use_RSAPrivateKey’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations]
error: ‘RSA_free’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations]
error: ‘ENGINE_init’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations]
error: ‘ENGINE_set_default’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations]
error: ‘ENGINE_load_private_key’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations]
error: ‘ENGINE_finish’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations]
error: ‘ENGINE_free’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations]
error: ‘ENGINE_by_id’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations]
error: ‘TLSv1_2_method’ is deprecated: Since OpenSSL 1.1.0 [-Werror=deprecated-declarations]
error: ‘TLSv1_1_method’ is deprecated: Since OpenSSL 1.1.0 [-Werror=deprecated-declarations]
error: ‘TLSv1_method’ is deprecated: Since OpenSSL 1.1.0 [-Werror=deprecated-declarations]
error: ‘ERR_load_BIO_strings’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations]
error: ‘ERR_remove_thread_state’ is deprecated: Since OpenSSL 1.1.0 [-Werror=deprecated-declarations]
error: ‘ENGINE_load_builtin_engines’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations]

Short answer: no
Long answer: no, the migration guide is the best we have.

@paulidale
Actually, I'm NOT going to rebuild openssl3...
It's just the default openssl3 from Ubuntu 22.04 repo is build with OPENSSL_NO_DEPRECATED.
Looks like Ubuntu 22.04 strictly sticks to the NEWER anc cleaner rule.
That's why I may have to modify accordingly to some third-party libraries...


ycmd: unstable-2020-02-22 -> unstable-2022-08-15

Resolves autocompletion error
'ValueError: The given version is not in the right format. Use something like "3.8" or "3".'
when YouCompleteMe vim plugin is used with current python3.
Signed-off-by: Sirio Balmelli<EMAIL_ADDRESS>

@ofborg eval

Result of nixpkgs-review pr 188140 run on x86_64-linux 1

2 packages built:

vimPlugins.YouCompleteMe
ycmd


Windows

Hello,
Try to test knife-block on windows under git-bash and I got the following errors:

ERROR: NotImplementedError: symlink() function is unimplemented on this machine - https://github.com/greenandsecure/knife-block/blob/master/lib/chef/knife/block.rb#L77
ERROR: NotImplementedError: readlink() function is unimplemented on this machine  - https://github.com/greenandsecure/knife-block/blob/master/lib/chef/knife/block.rb#L125
Same with unlink https://github.com/greenandsecure/knife-block/blob/master/lib/chef/knife/block.rb#L175
...

Thanks.

I can't say this'll be a high priority, as it wasn't built to support Windows originally, and I'm taxed with trying to get master in working order with Chef 12, ChefDK, and Ruby 2.2, but I setup https://ci.appveyor.com/project/solarce/knife-block and will try to play with it more this week and see about getting a Windows build going, which should help determine what needs to be fixed to make it support Windows in some fashion.

+1
I currently use this on mac, but have some windows fanatic coworkers who will want this once we get the second chef server running.

Symbolic links are not implemented that way with Windows and this tool fundamentally uses symbolic links. There is however a tool for Windows called mklink. It would be possible to factor the code to call the 3rd-party programme if Windows is detected: http://stackoverflow.com/questions/21511347/how-to-create-a-symlink-on-windows-via-ruby
The question is though, do we want to do this? Would it compromise the code-base? It is a shame to rule out an entire platform though.
Another option would be to not use symlinks and call knife with the -c argument, but that is potentially another discussion entirely.

That's a shame. Bit of advice though, it should be made it clear in the README that this gem doesn't support Windows.

@james-s-nduka There is a PR here https://github.com/knife-block/knife-block/pull/18  that addresses the issue. I have not got around to testing it though as I do not use Windows much. If you can try and test it I cam merge it and we will have windows support.

@james-s-nduka that's a fair point, if I get five minutes I'll update the README.
Originally, this was just a tool for helping me whilst contracting to switch between customers, then it started being used by a few Linux engineers at one of my customers, then it snowballed in to this!
:)


Implement CI/Release flow similar to base package

This Pull request replaces current CI flow and implements a similar like flow as the base package (Automapper repo).
This enables to push the tagged versions towards NuGet.
The NUGET_API_KEY secret needs to be set with the right API key for NuGet.
Solves: https://github.com/AutoMapper/AutoMapper.EF6/issues/30

@jbogard Help! :)

@lbargaoanu @jbogard any help needed from my side? the image posted in https://github.com/AutoMapper/AutoMapper.EF6/pull/29 would give me the impression that the API KEY is set but doesn't have the right permissions to update the AutoMapper.EF6 package.

Yes, we need @jbogard :)

@lbargaoanu @jbogard Do we have any update on this one already? 😄

https://www.nuget.org/packages/AutoMapper.EF6/

@lbargaoanu @jbogard awesome guys 🙌 🙌 🙌
Thanks a lot!


Improve TunnelingMetaStoreClientFactoryTest

Address the comments on TunnelingMetaStoreClientFactoryTest from PR #100

Done as part of https://github.com/HotelsDotCom/waggle-dance/pull/143.


az webapp hybrid-connection add no longer works.

az webapp hybrid-connection add no longer works.
From a cloud shell in the portal or from an Azure DevOps pipeline this used to work but now returns this error.
(InvalidApiVersionParameter) The api-version '2017-04-01' is invalid. The supported versions are '2023-07-01,2023-07-01-preview,2023-03-01-preview,2022-12-01,2022-11-01-preview,2022-09-01,2022-06-01,2022-05-01,2022-03-01-preview,2022-01-01,2021-04-01,2021-01-01,2020-10-01,2020-09-01,2020-08-01,2020-07-01,2020-06-01,2020-05-01,2020-01-01,2019-11-01,2019-10-01,2019-09-01,2019-08-01,2019-07-01,2019-06-01,2019-05-10,2019-05-01,2019-03-01,2018-11-01,2018-09-01,2018-08-01,2018-07-01,2018-06-01,2018-05-01,2018-02-01,2018-01-01,2017-12-01,2017-08-01,2017-06-01,2017-05-10,2017-05-01,2017-03-01,2016-09-01,2016-07-01,2016-06-01,2016-02-01,2015-11-01,2015-01-01,2014-04-01-preview,2014-04-01,2014-01-01,2013-03-01,2014-02-26,2014-04'. Code: InvalidApiVersionParameter Message: The api-version '2017-04-01' is invalid. The supported versions are '2023-07-01,2023-07-01-preview,2023-03-01-preview,2022-12-01,2022-11-01-preview,2022-09-01,2022-06-01,2022-05-01,2022-03-01-preview,2022-01-01,2021-04-01,2021-01-01,2020-10-01,2020-09-01,2020-08-01,2020-07-01,2020-06-01,2020-05-01,2020-01-01,2019-11-01,2019-10-01,2019-09-01,2019-08-01,2019-07-01,2019-06-01,2019-05-10,2019-05-01,2019-03-01,2018-11-01,2018-09-01,2018-08-01,2018-07-01,2018-06-01,2018-05-01,2018-02-01,2018-01-01,2017-12-01,2017-08-01,2017-06-01,2017-05-10,2017-05-01,2017-03-01,2016-09-01,2016-07-01,2016-06-01,2016-02-01,2015-11-01,2015-01-01,2014-04-01-preview,2014-04-01,2014-01-01,2013-03-01,2014-02-26,2014-04'.

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

ID: 645d01fc-eae4-67c0-ef63-77d34d854d5e
Version Independent ID: 516bc8a7-d927-d080-36a6-69ca95686feb
Content: Hybrid connections - Azure App Service
Content Source: articles/app-service/app-service-hybrid-connections.md
Service: app-service
GitHub Login: @madsd
Microsoft Alias: madsd

@MikeSCSU
Thanks for your feedback! We will investigate and update as appropriate.

Could it be a Linux vs. Window thing?
@.***
From: Venkateshdodda-MSFT @.>
Sent: Thursday, December 21, 2023 12:05 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Abrahamson, Mike @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] az webapp hybrid-connection add no longer works. (Issue #118200)
CAUTION: This e-mail originated from outside the Minnesota State System. Only click links or open attachments from trusted sources. Please report suspicious messages using the "Report Message Button".
@MikeSCSUhttps://github.com/MikeSCSU I have tested in one of our subscriptions by creating an app service running on standard app service plan and by using the cmdlet az webapp hybrid-connection add we are able to create hybrid connection to webapp as shown below.
image.png (view on web)https://github.com/MicrosoftDocs/azure-docs/assets/103091186/4779be66-7fc5-481a-bcf8-26301fa30ac6
I would suggest you try installing the latest version of az webapp extension and check whether are you passing the valid properties that are accepted by az webapp hybrid-connection addhttps://learn.microsoft.com/en-us/cli/azure/webapp/hybrid-connection?view=azure-cli-latest#az-webapp-hybrid-connection-add cmdlet as listed in the cmdlet documentation.
Feel free to reach back to me if you have any further questions on this.

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/118200#issuecomment-1865549387, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BDH6345YBDBWO2CC7RPLP6TYKPGQZAVCNFSM6AAAAABA5MKMCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRVGU2DSMZYG4.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Here's the screenshot I sent via email above.

@MikeSCSU I have tested running the same cmdlet in different environments. In one environment cloud shell cmdlet is working fine and in other it is failing with the above mentioned error. It looks like an issue with cloudshell not with the cmdlet.
I have raised a bug request related to this in cloud shell repo here is the link #370  for your reference.
We will close this out, but if you feel you need more information, please just let us know.

Not just cloud shell, this fails in Azure DevOps Release Pipelines as well.  It used to work in the Central Region but now fails there as well.


[Autocomplete] TextField with InputProps breaks the listbox from displaying

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

Customizing an Autocomplete's TextField with InputProps breaks the listbox from displaying. Version 4.6.0 did not exhibit this behavior.
Expected Behavior 🤔

The listbox should display.
Steps to Reproduce 🕹

https://codesandbox.io/s/material-demo-275b2?fontsize=14
Context 🔦

Your Environment 🌎

Tech
Version

Material-UI
v4.6.1

@sdornan The behavior has changed in #18289. It's important to deep merge the params:
    <Autocomplete
      id="combo-box-demo"
      options={top100Films}
      getOptionLabel={option => option.title}
      style={{ width: 300 }}
      renderInput={params => (
        <TextField
          {...params}
          InputProps={{ ...params.InputProps, style: { fontSize: 24 } }}
          label="Combo box"
          variant="outlined"
          fullWidth
        />
      )}
    />

This still doesn't work when trying to pass in more custom InputProps...
https://codesandbox.io/s/nifty-feather-nbtnf?file=/src/App.js


Clang-format check deleted

Clang-format check will be moved to CI repository

This looks good, I think it will work.


Problem with IR light

After hack my G2H, IR light turns on only for 5 seconds after connecting via RTSP

After hack my G2H, IR light turns on only for 5 seconds after connecting via RTSP

I haven't seen that issue on mine. Can you share what version of firmware you are running and the contents of /mnt/config/flash_config.ini ?

If you connect in the dark, the IR light goes out after five seconds.
But if you connect during daylight hours, and then darkness falls, the backlight will work correctly, but until the next connection
https://www.youtube.com/watch?v=scSjIGCFUeo
firmware 2.1.1_0002.0515
git_head = 23c88446c0c00834a739e2772fddb4b07e2b2851
build_time = 2020/12/01 14:11:48
firmware_version = 2.1.1

[misc]
cloud                          = 1
language                       = en

[network]
ip                             = <IP_ADDRESS>
netmask                        = <IP_ADDRESS>
gateway                        = <IP_ADDRESS>
dns1                           = <IP_ADDRESS>
dns2                           = <IP_ADDRESS>
dhcp                           = 1

[wifi]
auth                           = 2
enc                            = 3

[test]
var1                           =
var2                           =
var3                           = 0x0
var4                           = 0x0

[video]
video_on                       = 1
osd                            = 1
ldc                            = 1
wdr                            = 1
flip                           = 0
pwr_freq                       = 0
codec                          = 0
brightness                     = 50
contrast                       = 50
saturation                     = 50
hue                            = 50
fps0                           = 0
fps1                           = 0
bitrate0                       = 0
bitrate1                       = 0
motion_region                  =<PHONE_NUMBER>11111111111111
md_sensitivity                 = 1

[audio]
in_vol                         = 80
out_vol                        = 80
in_mute                        = 0
out_mute                       = 0
sd_sensivity                   = 1

[gpio]
led                            = 1
nightvision                    = 2

[gateway]

[record]
enable                         = 1
mode                           = 1
cover                          = 1
tlp_enable                     = 0
tlp_starttime                  = 00:00
tlp_endtime                    = 23:59
tlp_day                        = 1111111

[alarm]
peroid                         = 180
sound_enable                   = 0
motion_enable                  = 0
sound_push                     = 0
motion_push                    = 0
starttime                      = 00:00
endtime                        = 23:59
day                            = 1111111

[rtsp]
port                           = 554

[samba]
server                         =
path                           =
user                           =
passwd                         =
enable                         = 0
sync_interval                  = 60
video_save_time                = 86400

[miio]
reserve                        =

[tutk]
live_ch                        = 1
playback_ch                    = 0

[aiot]
ota                            = 0

[ppcs]
uid                            = AQARA-******-*****
apilicense                     = ******
initstring                     = ****************************************:aqara_p2p_key
crckey                         = aqaraCRC
live_ch                        = 0
playback_ch                    = 0

[homekit]
paird_status                   = 1
mfi_address                    = 0x10
camera_active                  = 1
iseverpaired                   = 1

checksum = be7bc4396547c0ff78d6bc702e10f21b

I just tested two of my cameras and can replicate your issue - IR goes off after a few seconds. I suspect this could be another simple patch to the camera binary hopefully, I will fire up Ghidra and do some debugging when I get some spare time.

Thanks, I will wait for the fix

Managed to find some time for this. From what it looks like the RTSP connection triggers this function - which turns on the IR LED, waits 6 seconds and then turns it off (??). If I patch the 'off / 0x00' to an 'on / 0x01' this problem goes away. From my limited testing it will switch off again when it senses brightness.

Using the hexdump + sed hack this works around the issue  's/20 46 01 21 bd e8 38 40/20 46 00 21 bd e8 38 40/' - I've tested this on two firmware versions and it seems ok. I'll update the script - Let me know if this works for you.

Hi!
I did it:
mv /tmp/out/camera /tmp/out/camera.1
hexdump -vC /tmp/out/camera.1 | sed -e 's/20 46 01 21 bd e8 38 40/20 46 00 21 bd e8 38 40/' | hexdump -R > /tmp/out/camera
chmod 755 /tmp/out/camera
reboot
I restarted the camera in the dark, connected to it
ffplay rtsp: //<IP_ADDRESS>/12
and after 6 seconds the backlight turned off. Did I do something wrong?

It works! Thanks!


HTML5 Canvas fix clear(), add drawCircle/fillCircle handle for Canvas…

… in GraphicsExtension
Sorry for the long message!

Looking good, thank you.


Access to UI methods

Hi, guys!
How I can access API UI methods, for example addExtraDropzone etc.
I see there are only API Core methods accessible via provider.methods.xxx

You can't. This is core only - you'll need to build your own UI, use React Fine Uploader, or Vue Fine Uploader

Thanks @rnicholus


Brew formula update for pulumi version v3.40.1

Generated from a new script in pulumi/pulumi#10796.

I think the CI failure is because https://github.com/pulumi/docs/blob/master/static/latest-version didn't get updated due to https://github.com/pulumi/pulumi/issues/10787. Currently looking at that one now.


ach-cli Parse IAT Batch/Entries/Addendas

ACH Version
1.21.2
What were you trying to do?
I am trying to view IAT Batch and Entries associated with them using ach-web-viewer. Since, it calls ach-cli to read the ach file, I want to add the ability to parse out IAT Batches, IATEntries and Addenda Records associated with them
What did you expect to see?
I am expecting to view IAT records using both cli and web-viewer

Yep, that should be supported. Let us know if some of the Addenda records for IAT aren't quite right.


Fix/108 do not mark current page as link in pagination

Pagination links should appear as before, but there will no longer be an <a> around the page number you're currently on, so it will no longer be in the tab order.

All good.


constitutional delay of growth and puberty

Preferred term label: constitutional delay of growth and puberty
Synonyms: constitutional growth delay
Definition: transient state of hypogonadotropic hypogonadism associated with prolongation of childhood phase of growth, delayed skeletal maturation, delayed and attenuated pubertal growth spurt, and relatively low insulin-like growth factor-1 secretion. (PMID: 23087852])
Parent term (use OLS, or your favorite ontology browser): disorder of development or morphogenesis
Children terms (if applicable) Should any existing terms that should be moved underneath this new proposed term?
Your nano-attribution (ORCID): 0000-0001-7151-1615

It looks like "constitutional delay of growth and puberty" could be in Mondo based on

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3475892/
https://www.researchgate.net/figure/Elements-for-the-differential-diagnosis-between-CDGP-and-CHH-in-males_tbl1_348893334
This term is in snomed as a disorder: https://www.ebi.ac.uk/ols/ontologies/snomed/terms?iri=http%3A%2F%2Fsnomed.info%2Fid%2F237813007


NEL: embedding-based & fuzzy lexical candidate selection

Goals
Implement a working draft picking entity candidates based on

similarities in the embedding space between entity description and text
fuzzy lexical similarity between entity name and text

This description is WIP and will be updated.
Description

Selects entity candidates based on similarities to the entity vectors in the embedding space, with some postprocessing.
Types of change

New feature.
Checklist

[x] I confirm that I have the right to submit this contribution under the project's MIT license.
[ ] I ran the tests, and all new and existing tests passed.
[ ] My changes don't require a change to the documentation, or if they do, I've added all required information.

Still running this, but ran into a few minor issues that need fixing.

Thanks for the feedback! I'm currently working on the Mewsli-9 dataset - will clean up when that's done (and aim to merge afterwards).

Couple of small things:

Sorry I didn't get back to you earlier! Didn't this last comment. Will clean up project.yml and the readme.

On a different note: running the entire project is obviously unfeasible since the addition of the Wiki dump download and parsing. Other steps could be limited in their runtime rather easily, but we'd still need the downloaded complete Wiki dump, unfortunately. Unsure as to how to proceed here. Any suggestions?

Can we directly provide the output of processing the dataset somehow? If hosting isn't difficult that would be easiest to set up.
A more principled thing would be to pick a subset, like "people born after 1900" or something. Picking a reasonable subset could be hard though.

Can we directly provide the output of processing the dataset somehow? If hosting isn't difficult that would be easiest to set up.
A more principled thing would be to pick a subset, like "people born after 1900" or something. Picking a reasonable subset could be hard though.

Yes, we could host the .sqlite file with the parsed data. In total it's around 14 GB. I'll look into figuring out a reasonable subset.

On second thought, this would bypass testing the parsing script. It'd be better if we started with small Wiki dumps and went from there. One option is to

locally run through both dumps,
pick a limited number of entries - either randomly or in a more principled fashion,
copy them into a new archive,
upload the archive so it's publicly available,
in the test suite: download the smaller test dumps and run all steps (I guess I'd have to adjust project.yml for the test case).

This seems like a bother, but is perhaps the only way to test the entire project. Except @svlandeg has a better idea?

I'm quite fond of having an alternative, much smaller dataset, even if it's perhaps unrealistically small, for testing purposes. Not just for the CI, but also to allow people to have a quick look & run through the project without first having to sit around for hours to wait for the download to finish.
We could think of a very narrow domain like Paul mentioned, and then your outline Raphael does sound sensible to me!

Suggestion:

Pick every Wiki entity mentioning at least one of a set of seed terms related to astronomy (moon, star, galaxy, ...) in their description.
Parse the Wiki dump again (:smiling_face_with_tear:) and move these entities + their articles into two separate entities/articles archives.
Upload the archives (where to?) and make them publicly available.
Comment the original Wiki dump download links and replace them (with an appropriate notice) with links to the smaller test sets.

We could do something similar for the Mewsli dataset, but IIRC the legal situation around redistributing the data was unclear. We could download it in full and then filter it afterwards though with similar terms, otherwise we'd have a large non-astronomy corpus and only astronomical entities to link.

I think filtering based on seed terms like that makes sense.

Upload the archives (where to?) and make them publicly available.

I think the default for this would usually be Github Releases, unless the data is too large or something.

I filtered by a list of European capitals now (testing the mentioned teams/city names idea). The filtered Wikidata and Wikipedia dumps are 74 and 58 MB respectively. Are we ok with that or do we want a smaller set?

Git LFS is another option, I guess? Feels kinda weird to me if the only "release" in the repo were the Wiki dump.

Sorry for the late reply.

I filtered by a list of European capitals now (testing the internally discussed sports teams/city names idea). The filtered Wikidata and Wikipedia dumps are 74 and 58 MB respectively. Are we ok with that or do we want a smaller set?

Those sizes sounds great, easy to work with.

Git LFS is another option, I guess? Feels kinda weird to me if the only "release" in the repo were the Wiki dump.

We've done this for things like sense2vec before. Git LFS would also work but I think using it is pretty awkward, especially for data a user is only likely to use once, especially if we aren't very concerned about diffs.
For files <100MB you can just put them in git, though Github will warn that you should use LFS. We wouldn't want to do that in the main branch here though. One other thing I've heard of people doing is having a "data" branch, so normal checkouts are fast but data is still in git, though I think releases are still preferable since this won't be updated often.

Closing and reopening to trigger CI.

 What were the results? How do the different candidate generators compare?

Not in the current version, but it's on my todo list.


Staging branch

Hey @TheOneWithTheBraid, is the master branch in stable state? I want to publish some latest changes to pub.dev but not sure about the state of the branch. Also maybe going forward we can move into 2 stage branching, so any work in progress or preview changes will be pushed into staging branch and when they become we would merge it into master, so we can keep master as stable as possible.

@themisir there is this build problem: #1040.

@themisir is there any possibility of publishing with the fixes of #1039?


Help Out with Translation

Currently, we are trying to allow this project to be used by more and more people. To do that we need translators!
If you would like to help translate Gobo.cf into other languages follow the bellow checklist:

Be fluent in English and at least one other language.
Have a Transifex account (create an account here)

Languages that have been translated into:

French (@locness3)
Swedish (@Andreto)
German (@M-S-72 & @Smilingouido)
Persian (@FarzanHosseini)
Spanish (@jsedano)
Portuguese (Brazil) (@brunopulis)
Russian (@yanicka)
Ukrainian (@yanicka)
Hindi (@imbdb)
Lithuanian (@mantasio)
Dutch (@pjgeutjens)

If you would like to help translate just leave a comment here with your Transifex username and what language you would like to translate it into.
If you know a language that has already been translated, please still review the project to ensure correctness.

@ScratchUtilities/translators Please go back to the Transifex project and make sure that all translations are correct and up to date.

Hey I would like to help with Spanish
Transifex user: jsedano

Updated Swedish(sv)

@jsedano Okay! I have added you to the Transifex project. I tried to translate the project myself with my very limited knowledge of the Spanish language. Make any changes that you need.

Hey I can help on Persian(Farsi) language
Transfix Username: Farzan

@FarzanHosseini Okay! I have added you to the Transifex project.

Hey @KennethSweezy I just finished with the Strings in Spanish, should I mark them as reviewed and open a PR or something ?

You can just mark them as reviewed in Transifex if they look correct.

Hey I would like to help with Brazilian Portuguese
Transifex user: brunopulis

@brunopulis Okay! I have added the ability to translate into Brazilian Portuguese and invited you to the project. Good luck with your translations!

I would like to translate it into Russian and/or Ukrainian. My username is yanicka

@yanicka Thank you for your willingness to contribute! I have invited you to the Transifex project so that you can translate the project into Russian and Ukrainian.

@all-contributors please add @locness3 for translation
@all-contributors please add @Andreto for translation
@all-contributors please add @M-S-72 for translation
@all-contributors please add @Smilingouido for translation
@all-contributors please add @FarzanHosseini for translation
@all-contributors please add @jsedano for translation
@all-contributors please add @brunopulis for translation

@all-contributors please add @locness3 for translation

@all-contributors please add @Andreto for translation

@all-contributors please add @M-S-72, @Smilingouido, @FarzanHosseini, @jsedano, @brunopulis for translation

@all-contributors please add @M-S-72 @Smilingouido @FarzanHosseini @jsedano @brunopulis for translation

@all-contributors please add @Smilingouido for translation

@all-contributors please add @FarzanHosseini for translation

@all-contributors please add @jsedano for translation

@all-contributors please add @brunopulis for translation

Language: Hindi
Transifex username: imbdb

@imbdb Okay! I have added you to the project for translation to Hindi. Thank you in advance.

@locness3 Could you update the translations for French?
@M-S-72 @Smilingouido Can you update the translations for German?

Hey, I can help with Lithuanian translations. Transifex username: mantasio

I would love to help to translate this to Traditional Chinese if you guys need it.

@mantasio Okay! You have been added to the project. Good luck.

Yes!

Please use my suggestion for "shorten URL ->"

@locness3 Thanks for the updates. I have now used your suggestions for all strings.

@KennethSweezy I'll do that in the next days.

@Smilingouido Ok, thank you.

No Problem...
Samuel Bittrich
Am 06.10.2019 um 18:28 schrieb Kenneth Blake Sweezy <notifications<EMAIL_ADDRESS>@Smilingouidohttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSmilingouido&data=02|01||86f62c46452e4b098f8d08d74a7a2acf|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637059760864400594&sdata=GrBzlFq7qdjBOJ%2BfE64bYeD6wimiBIAuq5%2BZMjKLSE4%3D&reserved=0 Ok, thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FScratchUtilities%2Fgobo.cf%2Fissues%2F71%3Femail_source%3Dnotifications%26email_token%3DAKILSFAUGHIVWY6FM2REJDDQNIGZJA5CNFSM4I4XPCF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAOOCKA%23issuecomment-538763560&data=02|01||86f62c46452e4b098f8d08d74a7a2acf|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637059760864410603&sdata=W5AjWVNPftuoQ5zK5VT5F1oV9Vsm%2Bq%2FRqWmLOULUxKI%3D&reserved=0, or mute the threadhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKILSFBMBWU2JJON3VR6UQ3QNIGZJANCNFSM4I4XPCFQ&data=02|01||86f62c46452e4b098f8d08d74a7a2acf|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637059760864410603&sdata=VfeCmxpHTYIjGTr8vFn3synXLGTXiGDdbndISLMAB6k%3D&reserved=0.

@KennethSweezy No problem.

I could help out with Dutch translation
transifex username: pjgeutjens

@pjgeutjens Okay! I have added you to the project! Good luck!

I cam help out with German, Hindi, and Marathi translation.
transifex username: AdiPat

username: Ph1lbert
lang : greek

Hi, I can help a bit with translating into Khmer (Cambodian)
Username: IsaiahSeihla

username: NotRealPaz
Thai Translation

@AdityaFRC @Ph1lbert @Seihla @NotRealPaz I have added all of you to the languages that you requested.
Good luck with your translations!

@KennethSweezy I want to preview my translation but can't due to this issue #84

Hi, I could help out with Japanese translation.
Transifex username: munex_com

Transifex username : cracknut
Language : Hindi

@munex-com @cracknutmeg I have added both of you to the languages that you have requested.

There is a typo on about page in russian. There is "Gobo.cf - это сократитесь". Should be "Gobo.cf - это сократитель".

hey, I want to help with Indonesian (bahasa)
Transifex username: haidarrifki

@haidarrifki I have added you to the Transifex project.
@Smollet777 I have made the correction.

Hello I think that I could help for the Italian (it-IT) translation.
My transifex id is: @mntmtt
Regards :)

Hi , I can work on Armenian translation
transifex id : teegrik

Hi, I can translate to Turkish.
Transifex user: yecicen

Hi , I can work on Marathi (India) translation
transifex id : rakeshlanjewar

I can translate to Bengali. I have a Transifex account and I am also a Scratch Translator.

Transifex id: R4356th

@KennethSweezy , is translating plan put down?

Since the project has been unable to be usable for a while. I am going to close this issue for now.
Thank You to all of the contributors and prospective contributors.


support for arrow function

Hi , can you add a feature to support arrow function ? I write really a lot of arrow functions instead of normal functions.
I think , parse-function is good enough for this feature.

I've added support for arrow functions

thank you


MLOps: GHWorkspace for Jupyter notebook

We can think of GitHub Workspace for Jupyter Notebook an environment for Notebooks where in a single click an environment will be spun up for the Data Scientist allowing them to run the notebook without them having to install any dependencies.
Targeted Customer Journey:
Customer opens a ML application in "GitHub workspace for Jupyter" which creates a fork
He can run the notebook without having to install any dependencies.
Makes changes to the notebook and data pipeline as needed and iterate
Executed the model and plot metrics.
Saves the updated model to forked branch.

This is a really important and fundamental feature that is missing.
@awmatheson we have been talking about this a couple of months ago.

@pulkitaggarwl

Should we wait for codespaces?
Large overlap with codespaces. Will it be supported in codespaces?


[stable/falco] add ability to set proxy server to the daemon set

What this PR does / why we need it:
Add ability to set a proxy server
Which issue this PR fixes: fixes https://github.com/helm/charts/issues/7656
Special notes for your reviewer:

/lgtm


encoding/pem: fix stack overflow in Decode - CVE-2022-24675

From Golang Security announcement:
encoding/pem: fix stack overflow in Decode
A large (more than 5 MB) PEM input can cause a stack overflow in Decode, leading the program to crash.
Thanks to Juho Nurminen of Mattermost who reported the error.
This is CVE-2022-24675 and https://go.dev/issue/51853.

Closed by:

https://github.com/aws/eks-distro-build-tooling/blob/main/projects/golang/go/1.16/patches/0002-go-1.16.15-eks-encoding-pem-fix-stack-overflo.patch


connect with google Problem in iPhone Browser

From<EMAIL_ADDRESS>on December 05, 2014 04:50:59
Hi,
i am using connect with google (g+ siginin) in my website it's working fine in desktop and android browsers. but
not wortking in ipad and iphone browsers.i used javascript api for google siginin.
here my Example is https://www.funmango.com/search/test and i also checked google developer example in iphone browser . but not working what you give in google developer website https://google-developers.appspot.com/+/demos/signin_demo_basic
Original issue: http://code.google.com/p/google-api-javascript-client/issues/detail?id=176

gapi.auth2 now supports iPhone and iPad. Closing this issue as obsolete.


About bio eval

Great job.
Regarding the bio data eval work, I didn't find the parameter you described in the FActScore repository - data_path YOUR_OUTPUT_FILE - am I missing something?
Looking forward to your reply!

I also spent a considerable amount of time on this section, as the README for selfrag did not provide detailed instructions on how to use factscore. It took me some time to figure out the correct configuration. You can refer to the library I developed: RAGLAB, where I have refactored the selfrag algorithm and evaluation process, offering clearer and more concise code. I recommend using the script I've configured to address this issue: https://github.com/fate-ubw/RAGLAB/blob/main/run/Factscore/2-eval_fact-raglab-selfrag-selfrag_8B-always_retrieval-GPT.sh


Consumer used without Provider

I am using preact (in parcel) and getting this warning whenever I compose an HOC. I apologize, in advance, if this issue belongs in another queue, but it's a bit hard to track down.
Consumer used without Provider

The HOC still works fine, and it's not app-breaking, just hoping I am using it right and (I am new to preact & proppy, coming from recompose and react.)
Here is my 1-file example:
import { h, render } from 'preact'
import { compose, withState, withHandlers } from 'proppy'
import { ProppyProvider, attach } from 'proppy-preact'

const P = compose(
  withState('counter', 'setCounter', 0),
  withHandlers({
    increment: ({ counter, setCounter }) => e => setCounter(counter + 1),
    decrement: ({ counter, setCounter }) => e => setCounter(counter - 1)
  })
)

const PageHome = attach(P)( ({ increment, decrement, counter }) => (
  <div>
    <button onClick={decrement}>-</button>
    {counter}
    <button onClick={increment}>+</button>
  </div>
))

// global app-state
const providers = {
  foo: false,
  bar: true
}

const Index = () => (
  <ProppyProvider providers={providers}>
    <PageHome />
  </ProppyProvider>
)

render(<Index />, document.getElementById('app'))

I'd be happy to put it a quick project git repo, if easier reproduction would help.

@konsumer: you are right. the issue (warning) is reproducible here in the playground too: https://codesandbox.io/s/github/fahad19/proppy/tree/master/examples/preact-playground


Replace deprecated "Meteor.addCollectionExtension" function

Meteor.addCollectionExtension is deprecated and should be replaced with CollectionExtensions.addExtension.

Hey thanks @pavchip we should probably also update the dependency to the latest version of collection-extensions.

Added commit that updates collection-extension dependency.


fix: Python below 3.8, shutil.copytree does not have argument 'dirs_exist_ok'

TypeError: python copytree() got an unexpected keyword argument 'dirs exist_ok'

 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.charlichen seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

published 0.12.1


node-sass not parse variables

NPM version (npm -v): 5.6.0
Node version (node -v): 9.8.0
Node Platform (node -p process.platform): darwin
Node architecture (node -p process.arch): x64
node-sass version (node -p "require('node-sass').info"): 4.8.3
npm node-sass versions (npm ls node-sass): 4.8.3
libsass: 3.5.2

└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>
Recently I update gulp-sass to 4.0.0 (and to<EMAIL_ADDRESS>and now not parse variables.
All works fine, mixins, functions, etc. but the Sass variables appear in the output css.
The console not show errors.
that could be happening?

Please provide a code example
On Tue., 10 Apr. 2018, 1:35 am Iván Barcia<EMAIL_ADDRESS>wrote:

NPM version (npm -v): 5.6.0
Node version (node -v): 9.8.0
Node Platform (node -p process.platform): darwin
Node architecture (node -p process.arch): x64
node-sass version (node -p "require('node-sass').info"): 4.8.3
npm node-sass versions (npm ls node-sass): 4.8.3
libsass: 3.5.2

└─┬<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>Recently I update gulp-sass to 4.0.0 (and to<EMAIL_ADDRESS>and now not
parse variables.
All works fine, mixins, functions, etc. but the Sass variables appear in
the output css.
The console not show errors.
that could be happening?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2326, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWFPDWhCgdXfwDXOc0QP6lK10NL0Sks5tm3_cgaJpZM4TMwbj
.


Feature/dockstore 328 streamline tool path

Same thing as Workflow in https://github.com/ga4gh/dockstore/pull/327
Related issue: https://github.com/ga4gh/dockstore/issues/328
Related pull request: https://github.com/ga4gh/dockstore-ui/pull/65
This pull request has the webservice added for tool. It will change the descriptor path on each tag when the default path is changed. To avoid merge conflict, it's better to add the test later after the workflow pull request is merged.

Changes Unknown when pulling bf5cbdd48068f3d622a33eebdd5bbf3a79f8c0a7 on feature/dockstore_328_streamline_tool_path into ** on develop**.

Coverage decreased (-0.02%) to 15.536% when pulling bf5cbdd48068f3d622a33eebdd5bbf3a79f8c0a7 on feature/dockstore_328_streamline_tool_path into fc30e41f7a3cb8163edf56185c32a8806c36ffe9 on develop.

Coverage increased (+0.04%) to 74.151% when pulling e1d4b4a37ad2c279ebc8dd7eaea05e9210c38783 on feature/dockstore_328_streamline_tool_path into fc30e41f7a3cb8163edf56185c32a8806c36ffe9 on develop.

Coverage increased (+0.04%) to 74.151% when pulling e1d4b4a37ad2c279ebc8dd7eaea05e9210c38783 on feature/dockstore_328_streamline_tool_path into fc30e41f7a3cb8163edf56185c32a8806c36ffe9 on develop.

Coverage increased (+0.04%) to 74.151% when pulling 6779ac618ea027395e0a7174be4f62b9039793c8 on feature/dockstore_328_streamline_tool_path into fc30e41f7a3cb8163edf56185c32a8806c36ffe9 on develop.


Post confirmation trigger lambda function getting 403 errors when calling API Gateway API

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
Amplify Console GitHub Issue Tracker

Describe the bug
In brief: post confirmation lambda is not allowed to access a REST API on API Gateway.
[ Use case: We need this because only the REST API gets credentials that contain identityID, which our post confirmation lambda needs to create a new user in DynamoDB... ]. Here's how it shows up:
Created a post-confirmation trigger lambda function via amplify auth update, after first having created a REST Api linked to a lambda function. The API is set up to require authentication for both guest and authenticated users and either is allowed only read access to the API.
After the cli sets up the post confirmation lambda, I run an amplify function update and give the post confirmation lambda read access to the API in the section where it asks if we want to enable other resources from the project.
The cli sets up an IAM role for the post confirmation lambda.  The Amplify cli also attaches the (seemingly) correct policy for the post confirmation lambda to access the REST API.
Now the test: sign-up a new user. This test fails. The post confirmation lambda gets an error returned from its request from the API. A 403 error
I tried two ways to have the post confirmation lambda call the API:

axios
using the AWS sdk's Service() call

both failed with a 403 error. The second method gave a bit more info, saying
          "Missing authentication token"

In the post confirmation lambda logs, I see an error code and message for this, both named "UserLambdaValidationException". There were no logs for the API call, even though that was set-up and tested to work via the console, which tells me the request was rejected before reaching the API.
I thought the Amplify CLI took care of setting up the authentication token for us automatically, even in the case of lambdas accessing cli-generated APIs (I may be wrong on this).
NOTE: when I test the same API from the test link in API-gateway console, it works: it returns a 200 response with the expected payload.
Amplify CLI Version
You can use amplify -v to check the amplify cli version on your system
4.42.0
To Reproduce
Steps to reproduce the behavior or terminal output if applicable

Add a lambda function that will be doing the work behind a RES API

dtal@thing5: amplify add function
? Select which capability you want to add: Lambda function (serverless function)
? Provide an AWS Lambda function name: getUser
? Choose the runtime that you want to use: NodeJS
? Choose the function template that you want to use: Serverless ExpressJS function (Integration with API Gateway)

Available advanced settings:
- Resource access permissions
- Scheduled recurring invocation
- Lambda layers configuration

? Do you want to configure advanced settings? No
? Do you want to edit the local lambda function now? Yes
Please edit the file in your editor: /home/dtal/repos/wg9r5td5e.dd.org/amplify/backend/function/getUser/src/app.js
? Press enter to continue

Here's the code of that lambda (note: this is a temporary lambda we're using to test this issue now):

var express = require('express')
var bodyParser = require('body-parser')
var awsServerlessExpressMiddleware = require('aws-serverless-express/middleware')

// declare a new express app
var app = express()
app.use(bodyParser.json())
app.use(awsServerlessExpressMiddleware.eventContext())

// Enable CORS for all methods
app.use(function (req, res, next) {
    res.header("Access-Control-Allow-Origin", "*");
    res.header(
        "Access-Control-Allow-Headers",
        "Origin, X-Requested-With, Content-Type, Accept"
    );
    next();
});

// Remember: these are available to you:
// req.apiGateway.event
// req.apiGateway.context
// req.body - not available on 'get' but avail on 'put', 'post'

app.get("/get-user", function (req, res) {
    if (req.query.postconf) {
        if (req.query.postconf === "15923220-9750-4075-a096-efeedc1dec82") {
            if (req.query.id) {
                console.log("/get-user got id: " + req.query.id);
                var resJson = {
                    statusCode: 200,
                    url: req.url,
                    test: JSON.stringify(req.apiGateway.event)
                };
                res.json(resJson);
            } else {
                res.json({
                    statusCode: 400,
                    url: req.url,
                    error: "err1"
                });
            }
        } else {
            res.json({
                statusCode: 400,
                url: req.url,
                error: "err2"
            });
        }
    } else {
        res.json({
            statusCode: 400,
            url: req.url,
            error: "err3"
        });
    }
});

app.listen(3000, function () {
    console.log("App started");
});

// Export the app object. When executing the application local this
// does nothing. However, to port it to AWS Lambda we will create a
// wrapper around that will load the app from this file
module.exports = app;

After editing the code, add a REST api for the function

Successfully added resource getUser locally.

Next steps:
Check out sample function code generated in <project-dir>/amplify/backend/function/getUser/src
"amplify function build" builds all of your functions currently in the project
"amplify mock function <functionName>" runs your function locally
"amplify push" builds all of your local backend resources and provisions them in the cloud
"amplify publish" builds all of your local backend and front-end resources (if you added hosting category) and provisions them in the cloud

dtal@thing5: amplify add api
? Please select from one of the below mentioned services: REST
? Provide a friendly name for your resource to be used as a label for this category in the project: getUser
? Provide a path (e.g., /book/{isbn}): /get-user
? Choose a Lambda source Use a Lambda function already added in the current Amplify project
? Choose the Lambda function to invoke by this path getUser
? Restrict API access Yes
? Who should have access? Authenticated and Guest users
? What kind of access do you want for Authenticated users? read
? What kind of access do you want for Guest users? read
Auth configuration is required to allow unauthenticated users, but it is not configured properly.
Successfully updated auth resource locally.
? Do you want to add another path? No
Successfully added resource getUser locally

Some next steps:
"amplify push" will build all your local backend resources and provision it in the cloud
"amplify publish" will build all your local backend and frontend resources (if you have hosting category added) and provision it in the cloud

dtal@thing5:

Create a post confirmation lambda

dtal@thing5: amplify auth update
Please note that certain attributes may not be overwritten if you choose to use defaults settings.

You have configured resources that might depend on this Cognito resource.  Updating this Cognito resource could have unintended side effects.

Using service: Cognito, provided by: awscloudformation
 What do you want to do? Walkthrough all the auth configurations
 Select the authentication/authorization services that you want to use: User Sign-Up, Sign-In, connected with AWS IAM controls (Enables per-user Storage features for images or other content, Analytics, and more)

 Allow unauthenticated logins? (Provides scoped down permissions that you can control via AWS IAM) Yes
 Do you want to enable 3rd party authentication providers in your identity pool? No
 Do you want to add User Pool Groups? No
 Do you want to add an admin queries API? No
 Multifactor authentication (MFA) user login options: OFF
 Email based user registration/forgot password: Enabled (Requires per-user email entry at registration)
 Please specify an email verification subject: Your verification code
 Please specify an email verification message: Your verification code is {####}
 Do you want to override the default password policy for this User Pool? No
 Specify the app's refresh token expiration period (in days): 30
 Do you want to specify the user attributes this app can read and write? No
 Do you want to enable any of the following capabilities?
 Do you want to use an OAuth flow? No
? Do you want to configure Lambda Triggers for Cognito? Yes
? Which triggers do you want to enable for Cognito Post Confirmation
? What functionality do you want to use for Post Confirmation Create your own module
Successfully added resource ddcff88827PostConfirmation locally.

Next steps:
Check out sample function code generated in <project-dir>/amplify/backend/function/ddcff88827PostConfirmation/src
"amplify function build" builds all of your functions currently in the project
"amplify mock function <functionName>" runs your function locally
"amplify push" builds all of your local backend resources and provisions them in the cloud
"amplify publish" builds all of your local backend and front-end resources (if you added hosting category) and provisions them in the cloud
Successfully added the Lambda function locally
? Do you want to edit your custom function now? Yes
Please edit the file in your editor: /home/dtal/repos/wg9r5td5e.dd.org/amplify/backend/function/ddcff88827PostConfirmation/src/custom.js
? Press enter to continue

Edit function to use this code

const aws = require('aws-sdk');
const axios = require('axios');

aws.config.update({region: process.env.REGION});

const getUserEndpointBaseUrl =
      'https://' + process.env.API_GETUSER_APIID + '.execute-api.' +
      process.env.REGION + '.amazonaws.com/' + process.env.ENV;
const postconf = '15923220-9750-4075-a096-efeedc1dec82';

exports.handler = (event, context, callback) => {
    // axios way of making the API call
    const url = getUserEndpointBaseUrl + '/get-user?id=' +
          event.request.userAttributes.sub + '&postconf=' + postconf;
    axios.get(url).then((response) => {
        const identityId = response.identityId;
        console.log('got identityId: ' + identityId);
        if (identityId) {
            callback(null, event);
        } else {
            callback('no identityId', null);
        }
    }).catch((error) => {
        callback(error, null)
    });
};

Update the post confirmation trigger lambda function to give it access to the API created above

dtal@thing5: amplify update function
? Select which capability you want to update: Lambda function (serverless function)
? Select the Lambda function you want to update ddcff88827PostConfirmation
General information
| Name: ddcff88827PostConfirmation
| Runtime: nodejs

Resource access permission
- Not configured

Scheduled recurring invocation
| Not configured

Lambda layers
- Not configured

? Which setting do you want to update? Resource access permissions
? Select the categories you want this function to have access to. api
? Api has 3 resources in this project. Select the one you would like your Lambda to access getUser
? Select the operations you want to permit on getUser read

You can access the following resource attributes as environment variables from your Lambda function
        API_GETUSER_APIID
        API_GETUSER_APINAME
? Do you want to edit the local lambda function now? No

dtal@thing5:

Final amplify push
In the browser, in the IAM console, I noticed that two policies were created and attached to the IAM role for the post confirmation lambda: one is named amplify-lambda-execution-policy - here's that policy:{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "apigateway:GET",
                "apigateway:HEAD",
                "apigateway:OPTIONS"
            ],
            "Resource": [
                "arn:aws:apigateway:us-east-1::/restapis/getUser/*"
            ],
            "Effect": "Allow"
        }
    ]
}

The second policy that gets attached by this deploy process to the post confirmation lambda role is named lambda-execution-policy - for the Cloudwatch logs access.
The test: just invoke this lambda right after you enter the confirmation code for your user at the end of the authentication flow. The post confirmation then returns with an error UserLambdaValidationException caused by it getting a 403 when it tried to make the API call.
When I changed the code of the API call to not use axios but use the aws-sdk Service() call instead, I also got a 403 error but in this case, got a bit more info about what caused the error, it said: "PostConfirmation failed with error Missing Authentication Token.".

Expected behavior
I expected the request from post confirmation lambda to the API to not get back a "missing authentication token" 403 error.
I expected the request's authentication token to have been there, with credentials of those of the user being post-confirmed.
I noticed that both the Auth and Unauth roles have policies to invoke the API. Had the correct authentication token been there, it would have worked.
Desktop (please complete the following information):

OS: recent Debian linux
Node Version. 12.0.0
Amplify cli version: 4.42.0

@dorontal Thanks for your detailed report. I was able to reproduce this with the given axios snippet, though I saw that this wasn't signed with aws creds.
A few questions here:

Is the aws versioned signed with the credentials provided to the lambda?
Could you provide the way you called api gateway with the AWS SDK?

@SwaySway thank you for quick response. Reagarding the first question, I believe you mean whether the aws version that I used in the code that used the aws.Service() command, right?  If so, the answer is that it was not signed at all. Neither axios version or the aws version of the code did any signging. Regarding the second question, sure, here is the exact code I used to have the post confirmation lambda access the API Gateway REST endpoint:
const aws = require('aws-sdk');
const axios = require('axios');

aws.config.update({region: process.env.REGION});

const getUserEndpointBaseUrl =
      'https://' + process.env.API_GETUSER_APIID + '.execute-api.' +
      process.env.REGION + '.amazonaws.com/' + process.env.ENV;
const postconf = '15923220-9750-4075-a096-efeedc1dec82';

//
// axios way of making the API call
//
exports.handler = (event, context, callback) => {
    const url = getUserEndpointBaseUrl + '/get-user?id=' +
          event.request.userAttributes.sub + '&postconf=' + postconf;
    axios.get(url).then((response) => {
        const identityId = response.identityId;
        console.log('got identityId: ' + identityId);
        if (identityId) {
            callback(null, event);
        } else {
            callback('no identityId', null);
        }
    }).catch((error) => {
        callback(error, null)
    });
};

I believe that this is what's going on and will propose a direction to fix it (though I may be wrong):

The post-confirmation lambda gets called and is authenticated at that time with Cognito User Pool
Here's what needs to happen
With the user token, get temporary IAM credentials from the Identity Pool
Use these IAM credentials to sign the API request with Signature Version 4
as desribed here, for example.

Hi @dorontal.  I stumbled across this issue because I'm trying to solve the same problem you are.  I believe the behavior you are experiencing is expected.
When you enable IAM authorization on your REST API, API Gateway requires that you authenticate every request you send by signing the request.  In your code snippets, it appears that you are not signing the request, so a 403 "Missing Authentication Token" makes sense.

NOTE: when I test the same API from the test link in API-gateway console, it works: it returns a 200 response with the expected payload.

This is also expected behavior.  When you make a test call via the API Gateway Console, API Gateway skips authorization and directly invokes your method.

@SethThomas - thank you for your reply - I think I understand it, but luckily we no longer need to have the post-confirmation trigger lambda function make an API call - the original reason for doing this was that we needed the identityId of the user, but in post-conf lambda that identityId doesn't exist, so it has to make an API Gateway call to an API Gateway API to ask for this identityId. But we have found a workaround for the original problem which caused this very special use case.

@dorontal Ah yes, the Cognito identityID problem.  It's a real struggle, I've been down that road myself.  It sounds like we've settled on similar solutions.  Glad you were able to solve your problem!

@dorontal But we have found a workaround for the original problem which caused us to first try the use case described in this issue.
This is really frustrating that getting identity Id still requires a workaround.

I understand the purpose of identity Id being it available only after authentication of the particular user, but maybe AWS should consider if this is really the ID needed as principal to be used on other AWS services (such as AWS IoT). It is very ugly to self-manage IoT policies to check on every user login (in my opinion).


Backporting master's .gitignore to openssl-3.1's .gitignore

updated openssl-3.1's .gitignore to match the master branches .gitignore (backporting)
Fixes #23574 - https://github.com/openssl/openssl/issues/23574
I am updating the openssl-3.1's .gitignore file to include the statements (backporting) in the master's .gitignore file.
Deleted in line 10:
/*.pc
Added after line 16:
/builddata.pm
/installdata.pm

# Exporters
/*.pc
/OpenSSLConfig*.cmake
/exporters/*.pc
/exporters/OpenSSLConfig*.cmake

Added after line 59:
/include/openssl/core_names.h
/include/internal/param_names.h

# Auto generated parameter name files
/crypto/params_idx.c

Added after line 143:
/util/quicserver
Added after line 248:
!.ctags.d
Added after line 257:
# LSP (Language Server Protocol) support
.cache/
compile_commands.json

@bbbrumley - faculty at RIT who would like to track my PR progress :)

Thank you. We already have PR #23847 which can be cherry-picked cleanly to the 3.1 branch and which is approved already.


Missing EMS data for Epidemiology in France (FR)

Hello,
Number of deaths in France is wrong, as France doesn't include deaths in specialized care units (for elder people), hence we can see this difference (for March 3rd 2021):
epidemiology.csv:

2021-03-03,FR,26788,322,261289,,3810125,62569,39964358,53548191

But on the French website: https://www.santepubliquefrance.fr/dossiers/coronavirus-covid-19/coronavirus-chiffres-cles-et-evolution-de-la-covid-19-en-france-et-dans-le-monde

87568 deaths, of which 62595 in the hospital

(Which is close to the 62569 number above, some data is changing along the way)
Data is available here: https://www.data.gouv.fr/fr/datasets/synthese-des-indicateurs-de-suivi-de-lepidemie-covid-19/ (second dataset)

'esms_dc'= Décès en EHPAD et ESMS

Perhaps adding this as a fake region would be a good idea (such as FR_IDF stands for «Île de France», it could be «FR_ESMS»).
Thanks for this project!

Thanks for reporting this and for the kind words @dugwood!

Data is available here: https://www.data.gouv.fr/fr/datasets/synthese-des-indicateurs-de-suivi-de-lepidemie-covid-19/ (second dataset)

We will update our data source to this which seems more accurate, thanks for the pointer.

Perhaps adding this as a fake region would be a good idea (such as FR_IDF stands for «Île de France», it could be «FR_ESMS»).

I like this idea, it's one of the reasons why we have a "special aggregation level" — so we can report data for non-standard "localities". Let me chat about this with the team, although it's definitely a lower priority than reporting the appropriate country-wide numbers.

We've now fixed the undercounting and France includes deaths from ESMS. I'm not happy about how subregions do not have this data, but I don't think there's anything we can do about it...
We have not added an ESMS region yet — we'll consider that for future work. But I'm closing this issue for now since the main problem has been resolved.


[stable/wordpress] Add update strategy

What this PR does / why we need it:
It make kubernetes update strategy configurable via values file. I think this will be useful when we use PVC with RWO so that we can use Recreate strategy instead of Rolling Update.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

Hi!!
@akhfa did you see my suggestions? It seems you didn't address them in your last commit.

Hi @juan131, of course I read your suggestions. I didn't push any changes yet. Will update my PR soon.

/ok-to-test
/lgtm


[ISSUE #1134]🔥Remove BrokerConfig duplicate codes🔥

Which Issue(s) This PR Fixes(Closes)

Fixes #1134
Brief Description

How Did You Test This Change?

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥


Fixed typo in python publishing readme.

Grammar fix as pointed out in googleapis/api-client-staging/pull/21

Current coverage is 91.23% (diff: 100%)

Merging #134 into master will not change coverage

@@             master       #134   diff @@
==========================================
  Files             3          3
  Lines           719        719
  Methods         150        150
  Messages          0          0
  Branches        116        116
==========================================
  Hits            656        656
  Misses           63         63
  Partials          0          0

Powered by Codecov. Last update 944f038...572383c

Can you add the period, too?

Done.

@bjwatson PTAL. Looks like some of the links were broken as well.

LGTM


Wrong duration showed for the image import

What happened:
$ pvsadm image import --workspace-id 63e2dd1d-85c8-4008-a546-226b361ae773 --bucket rhcos-powervs-images-us-south --bucket-region us-south --object rhcos-417-94-202408270355-0-ppc64le-powervs.ova.gz --pvs-image-name rhcos-417 --public-bucket -w --debug
....
....
I0919 18:18:22.444114   37087 import.go:311] Successfully imported the image: rhcos-417 with ID: 5c1e52cf-b669-4ccc-95c7-0559bf3cdd88 in 11.046950792s

here is shows 11.046950792s which is invalid
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

pvsadm version (use pvsadm version):
Environment - On-Prem or IBM PowerVS:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Others:

cc @kishen-v

/good-first-issue

/assign

Fixed through #673
/close