nest expects param data to be in the form of a plain object or an array of plain objects (forming a table)

So, I'm in trouble on the return knex.raw, what am I doing wrong?, always returns the error below...
My knex is ok, and return the data...Thanks, this software help me a lot!!!!
const CursoType = new GraphQLObjectType({
  name: 'Curso',
  sqlTable: 'curso',
  uniqueKey: 'id',
  description: 'Isto representa um curso',
  fields: () => ({
    id: {
      type: GraphQLInt
    },
    name: {
      type: GraphQLString
    }
  })
})

RootQuery ...
cursos: {
      description: 'Isto representa um curso',
      type: new GraphQLList(CursoType),
      resolve: (parent, args, context, ast) => {
        return joinMonster(ast, context, sql => {
          return knex.raw(sql)
        })
      }
    }

{
  "data": {
    "academic": {
      "cursos": null
    }
  },
  "errors": [
    {
      "message": "nest expects param data to be in the form of a plain object or an array of plain objects (forming a table)",
      "locations": [
        {
          "line": 3,
          "column": 5
        }
      ]
    }
  ]
}

Which dialect are you using with knex? Also, which version of knex? I believe knex.raw returns a slightly different shape of object depending on the dialect. This will work with SQLite, but not, for example with postgres. With postgres you need to grab the rows property on that object, like so:
resolve: (parent, args, context, ast) => {
    return joinMonster(ast, context, sql => {
        return knex.raw(sql).then(data => data.rows)
    })
}

If that doesn't work, can you console.log whatever data is so we can see what that object looks like?

@joserochadocarmo
Which dialect are you using with knex? Also, which version of knex? I believe knex.raw returns a slightly different shape of object depending on the dialect. This will work with SQLite, but not, for example with postgres. With postgres you need to grab the rows property on that object, like so:
resolve: (parent, args, context, ast) => {
    return joinMonster(ast, context, sql => {
        return knex.raw(sql).then(data => data.rows)
    })
}

If that doesn't work, can you console.log whatever data is so we can see what that object looks like?

Thanks @acarl005, It worked!!! I'm work with postgres and you were right about grab rows.

Yeah this wasn't super clear in the docs. I made an update that gives a clearer error message.


Add launch file checks and URDF checks

We need to write these tests and add them to travis
@ipa-fmw @ipa-mdl
Do you have a good idea how to deal with the problem about using $(find ) and $(arg ) and such mixed together?

@ipa-mdl:
rosinstall template https://github.com/ipa320/setup/blob/master/repositories/cob_indigo_bringup.rosinstall

Sweet!
Let's bring this new travis concept to the other repos as well - after the merge session on Tuesday!

We might need to update/recheck the robotlist entries in e.g. cob_bringup, cob_controller_configuration_gazebo, cob_gazebo,...

It would be even better to keep a consolidated list at one single place. It could be a symlinked cmake files that is included or we could keep the list in a  dedicated package (e.g. cob_robot_list) and expose it to dependent packages (CFG_EXTRAS).


there is not show Telugu language in text extractor

Description of the new feature / enhancement
there is not show Telugu language in text extractor
Scenario when this would be used?
there is not show Telugu language in text extractor
Supporting information
No response
### Tasks

We leverage the internal OCR engine.
https://learn.microsoft.com/en-us/windows/powertoys/text-extractor#supported-languages
/feedbackhub


Clarify required GitHub product in single sign-on documentation

Hi 👋 I'm part of GitHub's Enterprise Support team, and I'd like to make a suggestion regarding the Tutorial: Azure Active Directory integration with GitHub guide. It starts with a useful Prerequisites section that shows requirements for configuring Azure AD as a SAML IdP and includes this bullet:

...
GitHub single sign-on enabled subscription

I think it'd be useful here to either explicitly use the actual "GitHub Enterprise Cloud" product name (1, 2, 3) or to link to GitHub's About authentication with SAML single sign-on article that specifies the required product in the first green callout. I believe this would help folks to better understand the requirements for configuring single sign-on, and that it would ensure that they're using the right product before they start working through the instructions.
Thank you! 🙇

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

ID: 156e3923-74d6-432f-c5a0-b905520d4e7d
Version Independent ID: aeca7d10-15e2-9e42-74bc-5309a5108c05
Content: Tutorial: Azure Active Directory integration with GitHub
Content Source: articles/active-directory/saas-apps/github-tutorial.md
Service: azure-active-directory
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@mattpollard Thank you for your feedback !! As far as I understand it seems a valid clarification . I have requested the article author to review the suggestion and update as needed.
Thank you.

@mattpollard can you please make these changes directly by clicking on the Edit button in the top right corner and then we can review the article once you submit the PR?

Sure thing, @jeevansd! I overlooked the Edit button 😅 Opened https://github.com/MicrosoftDocs/azure-docs/pull/24792 🙇


pop-os-shell: init at 1.1.0

Motivation for this change
pop-os-shell version 1.0.0 was released 20 days ago. Now it's time to be a package :)
This is my first pr, so please tell me, if something is wrong :)
Things done

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

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

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

Should be good now :+1:

cc https://github.com/NixOS/nixpkgs/issues/92769 (@mogorman @Technical27 @operator-name)

This looks like it might be a duplicate of https://github.com/NixOS/nixpkgs/pull/102150

Oh, right. I was certain that we already had a PR open but could not find it with GitHub search :woman_shrugging:

Oh, neat to see someone get around to packaging this! I've had a commit sitting around waiting for a 1.0 release that might help a bit - I see this doesn't install the glib schema or set the uuid like other gnome extensions.
Also, it might be nice to also package pop-shell-shortcuts (https://github.com/pop-os/shell-shortcuts) to go with it, I believe otherwise the extension will try to open a website with the shortcuts.
Here's my commit for pop-shell: https://github.com/maxeaubrey/nixpkgs/commit/e46df8ddff5facaf57b86e5e7d5be189000e15a1
And here's pop-shell-shortcuts: https://github.com/maxeaubrey/nixpkgs/commit/5c14f15e6a2bfc9b6a11457ccb048a3668f10259

Looking at the source code, it should install schemas:
https://github.com/pop-os/shell/blob/1.0.0/Makefile#L74
https://github.com/pop-os/shell/blob/1.0.0/Makefile#L43

@maxeaubrey I had uuid set first, but i was advised to remove it if it is unnecessary.
Regarding pop-shell-shortcuts: I haven't had the problem with the website opening up and currently am using the package without shell-shortcuts. But maybe it's a good thing. Maybe putting it up as a second package is a good idea.

@remunds Oh, I guess uuid is obsolete now? 🤷♀ Fair enough.
@jtojnar I had problems with the schema being missing and the extension not working correctly otherwise, but I cannot reproduce right now. Soz, what I said can be ignored on that.

As i did not get an answer on my issue (https://github.com/pop-os/shell/issues/738), i just changed the license to gpl3Only. Hopefully that is fine. I also realized that there is a version 1.1.0 now, so i also updated the derivation. Lastly, i rebased to the current master branch.
Is there anything else missing?

As long as someone verifies that it works, looks good to me.

I tried it and everything works except for the button "floating window exceptions" and "Active Hint Color". This is the error message:
JS ERROR: GLib.SpawnError: Failed to execute child process “gjs” (No such file or directory)
                                                  color_selector/<@/run/current-system/sw/share/gnome-shell/extensions/pop-shell@system76.com/panel_settings.js:236:25

and
JS ERROR: GLib.SpawnError: Failed to execute child process “gjs” (No such file or directory)
                                                  async_process@/run/current-system/sw/share/gnome-shell/extensions/pop-shell@system76.com/utils.js:76:10
                                                  exception_dialog@/run/current-system/sw/share/gnome-shell/extensions/pop-shell@system76.com/extension.js:313:15
                                                  floating_window_exceptions/<@/run/current-system/sw/share/gnome-shell/extensions/pop-shell@system76.com/panel_settings.js:80:13
                                                  activate@resource:///org/gnome/shell/ui/popupMenu.js:191:14
                                                  vfunc_button_release_event@resource:///org/gnome/shell/ui/popupMenu.js:138:14

That means we need to patch those files with gjs paths, see https://github.com/NixOS/nixpkgs/blob/2a058487cb7a50e7650f1657ee0151a19c59ec3b/pkgs/desktops/gnome-3/extensions/drop-down-terminal/default.nix#L16-L21 for an example.

As I am not using those features, I did not find the bugs. Unfortunately, I have never applied a patch before and do not really know how to patch gjs files (and also which files need to be patched). Does anyone have an Idea on how to do that or can help me with it?

You would clone the pop-os repo, find the gjs references (see the files in https://github.com/NixOS/nixpkgs/pull/104160#issuecomment-749005632), replace them with @gjs@/bin/gjs and then create a patch using git diff > fix-paths.patch. You can then apply it as shown in https://github.com/NixOS/nixpkgs/pull/104160#issuecomment-749008197.

I would recommend submitting patches upstream for locating the system path if the default GLib subprocess launcher can't find the binaries in your system path. You may add additional search paths with a subprocess launcher. There are a couple areas in Pop Shell that call out gjs, including some of the default plugins which are gjs scripts.

@mmstick The point of Nix is that there is not system path – every package is self-contained and hardcodes paths to everything it needs (in theory anyway). For some things like script shebangs, we have tooling that hardcodes the correct path but for exec calls in code, a more manual approach is required.

The code that manually calls upon gjs can be changed to make use of the shebang line.

Right, that would be better for us too, we did the same with GSConnect. @remunds are you able to submit such patch upstream?

I've found another issue, although I'm not sure if it's maybe only on my end:
Deactivating "Show window titles" doesn't hide title bars.

This one is probably due to using Wayland where this is not supported upstream.

@jtojnar I will have a look at that later that day, but I am not sure whether I am capable enough. I'll let you know. Do I understand it right that the current approach is to create a patch that puts the shebang #!/usr/bin/env gjs in every file that needs it and then somehow modify the way those files are called?
@ymarkus that works for me.

@remunds Yes, that is correct. The files need to be invoked as scripts. Also, for that to work, you will need to make them executable if they are not already.

I'll give that a try, thanks :)

I was able to get the "floating window exception"-window with the other approach though.

Now its just the active hint color that doesn't work. Does anyone have an idea?

I've been using this for a few weeks now (updated to 1.2.0 though) on NixOS 20.09 under GNOME 3.36.5 Wayland and apart from the known upstream Wayland wonkiness, this actually works quite nicely.

Tangentially related in case anyone is interested: https://blog.system76.com/post/648371526931038208/cosmic-to-arrive-in-june-release-of-popos-2104
https://github.com/pop-os/cosmic
It has pop-shell as a dependency.

Solved in  #147542 - i believe we could close this PR now.
Maybe you add yourself to maintainers ;)


[android] Avoid linking twice with C++

The Android targetted libraries already link (manually) with the Android
NDK C++ libraries. When using Clang and lld, an extra link to libc++ is
requested, which will fail because Android names it libc++_shared.so
instead. To avoid looking for the wrong name, and since the library is
referenced manually either way, request no linking with the standard C++
libraries (but add the math library in, which is implicitly linked when
C++ is linked, and it is needed for Glibc at least).

@swift-ci please test and merge


Announce Installer availability

Messaging: Blueprint product to showcase Theia platform capabilities

Blog Post
Twitter: @ECDTools, @theia_ide
Press release

Announce in stages:

Alpha
Beta
Release

We (EclipseSource) intend to contribute to this on behalf of ST Microelectronics.

I will create a first draft for this

I will create a first draft for this

The release is now planned for April 10th. So the announcement should be released on Monday April 12th ideally.

@brianking Is this feasible for you?

Yes, feasible. I will make sure the post is complete by the end of the week, and publish on Monday.

Alpha release is online and web page is updated.

Blog post will be up shortly today.

The post is now live:
https://blogs.eclipse.org/post/brian-king/eclipse-theia-blueprint-now-available-download


Is vsm4r.vs still a valid instruction in vector crypto spec?

If so, the description of vsm4r.vs is missing in Section 3.21. If not, should remove vsm4r.[vv,vs] in Section 2.5.
(based on document 20221125)

Open https://github.com/riscv/riscv-crypto/pull/248 to add it back

Thanks for catching this omission, David. We had assigned an encoding for this but mistakenly left it out of the specification. It has now included in the specification.


Serve assets using new domain

This domain has changed.
To do before merging

[ ] Verify that this directory exists on the mirror machine

alexmuller@production-mirrorer-1:/mnt/crawler_worker$ find assets.digital.cabinet-office.gov.uk/ -type f | wc -l
15342
alexmuller@production-mirrorer-1:/mnt/crawler_worker$ find assets.publishing.service.gov.uk/ -type f | wc -l
116

alexmuller@production-mirrorer-1:/mnt/crawler_worker$ find assets.digital.cabinet-office.gov.uk/ -type f | wc -l
15346
alexmuller@production-mirrorer-1:/mnt/crawler_worker$ find assets.publishing.service.gov.uk/ -type f | wc -l
190

I suppose we could move/copy the old files to the new directory.

Agree, copy the files to the new directory if there's space?

alexmuller@production-mirrorer-1:/mnt/crawler_worker$ find assets.digital.cabinet-office.gov.uk/ -type f | wc -l
15346
alexmuller@production-mirrorer-1:/mnt/crawler_worker$ find assets.publishing.service.gov.uk/ -type f | wc -l
15350

:+1: MERGE AND FLY


autogenerated subtopics are confusingly labelled

If the user sees
Subtopics:
URL Sharing: reddit [138]

it doesn't mean much and in fact can create confusion. I think we should add an "System Generated" label or similar to any auto-generated.  Also, what is the significance of '138'?

yes, I just couldn't figure out a sane way to do this and basically gave up.
easy alternative is just to use the platform by itself ('reddit'), which
will work perfect in 95% of cases but be bad if there are more than one
topic_seed_query for a given platform.
next best alternative is to require the user to given each seed query a
name, but that seems like a lot of extra work for the user for a marginal
use.
we could in theory just put the query alongside the platform, but that
would look bad pretty quick as the query gets long.
ideas?
-hal
On Mon, Apr 6, 2020 at 12:35 PM rahulbot<EMAIL_ADDRESS>wrote:

Yeah - it's not great. The number is the topics_seed_query_id I think. he
is probably tacking it on there or convenience of debugging and
development. This requires explanation to the researchers, but they can
live with it for now I think.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_mitmedialab_MediaCloud-2DWeb-2DTools_issues_1786-23issuecomment-2D609934725&d=DwMCaQ&c=WO-RGvefibhHBZq3fL85hQ&r=0c5FW2CrwCh84ocLICzUHjcwKK-QMUDy4RRw_n18mMo&m=Dhqwh96Z0kLFR-fy6N8Qq6-fGKVxmu9i-CO5c2Wxg0s&s=JFb57f40y3JwUyO62vZLMzwk8mIha6ROnnQIl5TBS9o&e=,
or unsubscribe
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AAN66T2TEZZHWLEIUQ5Q5UTRLIHG3ANCNFSM4MCKFMDQ&d=DwMCaQ&c=WO-RGvefibhHBZq3fL85hQ&r=0c5FW2CrwCh84ocLICzUHjcwKK-QMUDy4RRw_n18mMo&m=Dhqwh96Z0kLFR-fy6N8Qq6-fGKVxmu9i-CO5c2Wxg0s&s=UsDTqri1Bax0JdxplFYGIXbQX_sNwvrou_Xbye0F4sA&e=
.


Expose IdP attribute names in SAML2 toolkit settings

I've added a new attribute, idp_attribute_names, to the IdP section of the settings class. I've encountered a few scenarios where the ability to extract attribute names from the IdP metadata would be useful and figured others might be interested in such functionality as well.

Can you add tests?


Ltd 1645 names

SS Before:

SS After:

Workflow

[x] Ticket exists in Jira https://uktrade.atlassian.net/browse/LTD-1645
[x] Jira ticket has the correct status.

Reviewing help

[ ] Explains how to test locally, including how to set up appropriate data
[x] Includes screenshot(s) - ideally before and after, but at least after

Housekeeping

[ ] Added all new environment variables to Vault.
[ ] Cleaned up old feature flags
[ ] Upgraded any vulnerable dependencies.
[ ] Ran the make manage download_geolocation_data command
[ ] I have updated security dependencies
[ ] Python requirements have been re-compiled.
[ ] Frontend assets have been re-compiled.

Merging

[x] This PR can be merged by reviewers. (If unticked, please leave for the author to merge)

For the new field, it may be worth checking with Colin on the wording, as I would imagine "Is this team an OGD?" would make more sense than "Is this team part of OGD?" (OGD stands for "Other Government Department").


Non-owned example

Extension of #1, but essentially should do an example that uses builtin without the use of GeneticSim for an easier form of managing fitness in complex simulations.

Well actually, this might be considered bad practice. Not sure if this is a good idea to include in an example.


Next PyPI Release Timeline

We're using django-auth-adfs in our project, and it looks like the latest version on github doesn't match the latest version on PyPI (1.2). The SETTINGS_CLASS configuration option in master would be very useful to us, so we were wondering if there was any plan to push the latest code to PyPI?

You may know this already, but you can pip install directly from github in these cases when the official packages aren't yet ready.
https://pip.pypa.io/en/latest/reference/pip_install/#git
https://stackoverflow.com/questions/13685920/install-specific-git-commit-with-pip

Don't panic, the project isn't dead yet :)
I'm just not very active during summer time. There are also some changes in my personal life because of which I temporarily have less time to work on this.
I'll see what I can do to release a new version in the next couple of weeks/month.

@arelcedar the next release is almost there.
Would you mind removing your forked package from pypi after the next release?
https://pypi.org/project/cedar-adfs-forked/
My name is all over the place in that package and it links back to this repo, but I've got nothing to do with that package. When I first noticed it, I thought it was a potentially malware package.

Released 1.3.0

@arelcedar
A little reminder to remove your cedar-adfs-forked project from PyPI.

Seems like it's still there @arelcedar .
Also @jobec , any plans to release a new version now? There is a few bugfixes in it.


Following/dashboard flow

A user should be able to see their dashboard content. TBD on what exactly this will include, but minimally it should display updates from observations/updates similar to the current iOS app (#281)

[ ] Display observation updates

Not including in the MVP.


Collect different approaches to provisioning workers (permanent and transient)

Here's how transient workers are currently implemented in GNOME OS.
There are no permanent worker machines set up.
Tests are started from Gitlab CI pipelines. See the .gitlab-ci.yml for openqa-tests.git for how this is implemented. Each Gitlab CI job for QA does the following:

Download the registry.opensuse.org/devel/openqa/containers15.6/openqa_worker:latest image and create a container.
Clone the repo which has the tests (in this case, openqa-tests.git which holds the GNOME OS tests)
3. Fetch test media. This uses utils/fetch_test_media.sh (a small wrapper around Curl) to download ISO and/or disk image from the S3 bucket where they are stored.
4. Create /etc/openqa/client.conf with an openqa.gnome.org API key (which is passed in as Gitlab CI variables.
5. Create a /etc/openqa/worker.conf with a unique worker class. The worker class contains the Gitlab CI pipeline number.
6. Call /run_openqa_worker.sh (the container entrypoint script) to start the worker daemon, which will connect to the web UI and register itself as a new worker.
7. Start the jobs. See utils/start_all_jobs.sh helper script, which uses openqa-cli to call the POST isos endpoint. We pass in  config/scenario_definitions.yaml, and openQA creates a job for each job_template defined in that file. Finally it parses the JSON response to get a list of job IDs.
8. Poll the job status of each job. See script utils/wait_for_job.sh. When all jobs have finished or cancelled, exits with 0 (all succeeded) or 1 (something failed or was cancelled).
9. In all cases, upload some logs as Gitlab CI artifacts, and generate JUnit test report.

Future improvements:

Avoid using helper scripts. As we roll out openQA to more components we want to avoid duplicating glue code in multiple places. See https://gitlab.gnome.org/GNOME/citemplates/-/issues/16. Some functionality could move into openQA upstream, perhaps as extensions to openqa-cli.
Clean up the worker after it stops - currently openqa.gnome.org has a list of all workers that ever existed.

In Fedora openQA, everything is deployed via ansible - https://pagure.io/fedora-infra/ansible . worker hosts are defined in the inventory in a few groups - https://pagure.io/fedora-infra/ansible/blob/main/f/inventory/inventory#_348 . There are some significant definitions in the group vars, including firewall config required for tap stuff in https://pagure.io/fedora-infra/ansible/blob/main/f/inventory/group_vars/openqa_tap_workers . The playbook is https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/groups/openqa-workers.yml and the plays are in https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openqa/worker . Worker hosts are physical machines running plain Fedora (currently 40) and install the relevant packages from Fedora's main repositories, where I maintain them.
We still use a very old-style deployment on Fedora, where the tests live on the server and are shared to the worker hosts via NFS, so checking out tests and so on happens on the server. The ansible plays take care of installing the packages, setting up networking, ensuring the NFS share is configured, enabling the worker instance services and so on.


find: '/var/lib/cexplorer': No such file or directory when resoring from docker

OS
Your OS: UBUNTU-Docker
Versions
The db-sync version (eg cardano-db-sync --version): 13.0.0
PostgreSQL version: 11.5-alpine
Build/Install Method
The method you use to build or install cardano-db-sync: docker image
Run method
The method you used to run cardano-db-sync (eg Nix/Docker/systemd/none): docker-compose
Additional context
TESTNET

RESTORE_SNAPSHOT=https://updates-cardano-testnet.s3.amazonaws.com/cardano-db-sync/13/db-sync-snapshot-schema-13-block-3680594-x86_64.tgz

Problem Report
cardano-tools-testnet-cardano-db-sync-1  | Connecting to network: testnet
cardano-tools-testnet-cardano-db-sync-1  | Downloading snapshot https://updates-cardano-testnet.s3.amazonaws.com/cardano-db-sync/13/db-sync-snapshot-schema-13-block-3680594-x86_64.tgz ...
cardano-tools-testnet-cardano-db-sync-1  | ** Resuming transfer from byte position<PHONE_NUMBER>
cardano-tools-testnet-cardano-db-sync-1  |   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
cardano-tools-testnet-cardano-db-sync-1  |                                  Dload  Upload   Total   Spent    Left  Speed
100   365    0   365    0     0    533      0 --:--:-- --:--:-- --:--:--   533
cardano-tools-testnet-cardano-db-sync-1  |   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
cardano-tools-testnet-cardano-db-sync-1  |                                  Dload  Upload   Total   Spent    Left  Speed
100   118  100   118    0     0    169      0 --:--:-- --:--:-- --:--:--   169
cardano-tools-testnet-cardano-db-sync-1  | db-sync-snapshot-schema-13-block-3680594-x86_64.tgz: OK
cardano-tools-testnet-cardano-db-sync-1  | find: '/var/lib/cexplorer': No such file or directory

That is strange, this issue should be already fixed: https://github.com/input-output-hk/cardano-db-sync/issues/1150
Maybe you need to remove your old v12 volumes ?
I used the same snapshot:
docker-compose logs cardano-db-sync
Attaching to cardano-db-sync_cardano-db-sync_1
cardano-db-sync_1  | /run/secrets
cardano-db-sync_1  | Generating PGPASS file
cardano-db-sync_1  | Connecting to network: testnet
cardano-db-sync_1  | Downloading snapshot https://updates-cardano-testnet.s3.amazonaws.com/cardano-db-sync/13/db-sync-snapshot-schema-13-block-3680594-x86_64.tgz ...
cardano-db-sync_1  |   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
cardano-db-sync_1  |                                  Dload  Upload   Total   Spent    Left  Speed
100 2729M  100 2729M    0     0   823k      0  0:56:36  0:56:36 --:--:--  725k
cardano-db-sync_1  |   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
cardano-db-sync_1  |                                  Dload  Upload   Total   Spent    Left  Speed
100   118  100   118    0     0     61      0  0:00:01  0:00:01 --:--:--    61
cardano-db-sync_1  | db-sync-snapshot-schema-13-block-3680594-x86_64.tgz: OK
cardano-db-sync_1  | db-sync-snapshot-schema-13-block-3680594-x86_64.sql
cardano-db-sync_1  | 62510369-d931221f9b-214.lstate
cardano-db-sync_1  | SET
cardano-db-sync_1  | SET
cardano-db-sync_1  | SET
cardano-db-sync_1  | SET
cardano-db-sync_1  | SET
cardano-db-sync_1  |  set_config
cardano-db-sync_1  | ------------
cardano-db-sync_1  |
cardano-db-sync_1  | (1 row)

...
...

cardano-db-sync_1  | ALTER TABLE
cardano-db-sync_1  | ALTER TABLE
cardano-db-sync_1  | ALTER TABLE
cardano-db-sync_1  | All good!
cardano-db-sync_1  | [db-sync-node:Warning:6] [2022-07-06 09:04:05.18 UTC] Version number: 13.0.0
cardano-db-sync_1  | [db-sync-node:Warning:6] [2022-07-06 09:04:05.18 UTC] Git hash: 67367b5ae317b2915de94dc3be43c29d796d876e
cardano-db-sync_1  | [db-sync-node:Warning:6] [2022-07-06 09:04:05.18 UTC] Option disable-ledger: False
cardano-db-sync_1  | [db-sync-node:Warning:6] [2022-07-06 09:04:05.18 UTC] Option disable-cache: False
cardano-db-sync_1  | [db-sync-node:Warning:6] [2022-07-06 09:04:05.18 UTC] Option disable-epoch: False
cardano-db-sync_1  | [db-sync-node:Warning:6] [2022-07-06 09:04:05.18 UTC] Enviroment variable DbSyncAbortOnPanic: False
cardano-db-sync_1  | [db-sync-node:Info:6] [2022-07-06 09:04:05.19 UTC] Schema migration files validated
cardano-db-sync_1  | [db-sync-node:Info:6] [2022-07-06 09:04:05.19 UTC] Running database migrations
cardano-db-sync_1  | [db-sync-node:Info:6] [2022-07-06 09:04:05.61 UTC] Using byron genesis file from: "/nix/store/kax0css4lx3ywihvsgrqjym0jpi20f99-byron-genesis.json"
cardano-db-sync_1  | [db-sync-node:Info:6] [2022-07-06 09:04:05.61 UTC] Using shelley genesis file from: "/nix/store/2xhy92909anynqsvx1b1x153cxwnfmzx-shelley-genesis.json"
cardano-db-sync_1  | [db-sync-node:Info:6] [2022-07-06 09:04:05.61 UTC] Using alonzo genesis file from: "/nix/store/8qnphq6yvcjspiy3z0aijfd6cv64l3hl-alonzo-genesis.json"
cardano-db-sync_1  | [db-sync-node:Info:6] [2022-07-06 09:04:05.72 UTC] NetworkMagic:<PHONE_NUMBER>
cardano-db-sync_1  | [db-sync-node:Info:6] [2022-07-06 09:04:05.73 UTC] Initial genesis distribution present and correct
cardano-db-sync_1  | [db-sync-node:Info:6] [2022-07-06 09:04:05.73 UTC] Total genesis supply of Ada:<PHONE_NUMBER>9.999903
cardano-db-sync_1  | [db-sync-node:Info:6] [2022-07-06 09:04:05.73 UTC] Inserting Shelley Genesis distribution
cardano-db-sync_1  | [db-sync-node:Info:6] [2022-07-06 09:04:05.73 UTC] epochStartup: Checking
cardano-db-sync_1  | [db-sync-node:Info:6] [2022-07-06 09:04:05.73 UTC] localInitiatorNetworkApplication: connecting to node via "/node-ipc/node.socket"
cardano-db-sync_1  | [db-sync-node.Subscription:Notice:55] [2022-07-06 09:04:05.73 UTC] Identity Starting Subscription Worker, valency 1
cardano-db-sync_1  | [db-sync-node.Subscription:Notice:56] [2022-07-06 09:04:05.73 UTC] Identity Connection Attempt Start, destination LocalAddress "/node-ipc/node.socket"
cardano-db-sync_1  | [db-sync-node.Subscription:Notice:56] [2022-07-06 09:04:05.73 UTC] Identity Connection Attempt End, destination LocalAddress "/node-ipc/node.socket" outcome: ConnectSuccessLast
cardano-db-sync_1  | [db-sync-node.Handshake:Info:56] [2022-07-06 09:04:05.73 UTC] WithMuxBearer (ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/ipc/node.socket"}) Send (ClientAgency TokPropose,MsgProposeVersions (fromList [(NodeToClientV_9,TInt<PHONE_NUMBER>),(NodeToClientV_10,TInt<PHONE_NUMBER>),(NodeToClientV_11,TInt<PHONE_NUMBER>),(NodeToClientV_12,TInt<PHONE_NUMBER>),(NodeToClientV_13,TInt<PHONE_NUMBER>)]))
cardano-db-sync_1  | [db-sync-node.Handshake:Info:56] [2022-07-06 09:04:05.73 UTC] WithMuxBearer (ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/ipc/node.socket"}) Recv (ServerAgency TokConfirm,MsgAcceptVersion NodeToClientV_13 (TInt<PHONE_NUMBER>))
cardano-db-sync_1  | [db-sync-node.Mux:Info:56] [2022-07-06 09:04:05.73 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/ipc/node.socket"} event: Handshake Client end, duration 0.000299198s
cardano-db-sync_1  | [db-sync-node.Mux:Info:57] [2022-07-06 09:04:05.73 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/ipc/node.socket"} event: State: Mature
cardano-db-sync_1  | [db-sync-node.Mux:Info:57] [2022-07-06 09:04:05.73 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/ipc/node.socket"} event: Eagerly started (MiniProtocolNum 5) in InitiatorDir
cardano-db-sync_1  | [db-sync-node.Mux:Info:57] [2022-07-06 09:04:05.73 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/ipc/node.socket"} event: Eagerly started (MiniProtocolNum 6) in InitiatorDir
cardano-db-sync_1  | [db-sync-node.Mux:Info:57] [2022-07-06 09:04:05.73 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/ipc/node.socket"} event: Eagerly started (MiniProtocolNum 7) in InitiatorDir
cardano-db-sync_1  | [db-sync-node.Mux:Info:57] [2022-07-06 09:04:05.73 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/ipc/node.socket"} event: Eagerly started (MiniProtocolNum 9) in InitiatorDir
cardano-db-sync_1  | [db-sync-node:Info:60] [2022-07-06 09:04:05.73 UTC] Starting chainSyncClient

@wutzebaer Were you able to restore state from snapshot, can this be closed ?

@ArturWieczorek  yes the problem was the changed mount point:
db-sync-data:/var/lib/cdbsync
must be changed to
db-sync-data:/var/lib/cexplorer


i18n(pt-BR): Update fonts.mdx translation

Update fonts.mdx translation
Updates the pt-br translation of the fonts.mdx guide.

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

pt-br
guides/fonts.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


ci: enable yarn install cache

Motivation
https://github.com/actions/cache/blob/main/examples.md#node---yarn
https://github.com/actions/cache/blob/main/examples.md#node---yarn-2
ci build time is now reduced per job by 30s~1min
Have you read the Contributing Guidelines on pull requests?
yes

Hey, that's a cool idea
Was just wondering if there isn't a way to remove all that verbosity?
I've used this action recently and it worked great, can it be used instead?
https://github.com/bahmutov/npm-install

it can be used, and its your call if you think that's a good idea

yes I think - uses: bahmutov/npm-install@v1 would be better.
Do you want to edit this PR or we close and I do another one?

i'm going to update this pr, do you think that we should apply this for windows machines to?

thanks, that looks fine

I think we can enable this on Windows too, do you see any reason not to?

generally caching on windows gh actions seem to be slow, i will try it out

didn't know that, is it documented or your personal experience? slower than no caching at all?

let's merge this for now and see if we can improve windows in another PR


response status override using self.status

Resource.status is currently being set but not used:
https://github.com/toastdriven/restless/blob/2.1.1/restless/resources.py#L82
An idea is to use it for overriding a successful response status, no matter the endpoint/method.
Example:
def update(self, pk):
    try:
        Post = Post.objects.get(id=pk)
        self.status = 200
    except Post.DoesNotExist:
        self.status = 201
        post = Post()

    post.title = self.data['title']
    post.user = User.objects.get(username=self.data['author'])
    post.content = self.data['body']
    post.save()
    return post

Fixes #118
If this gets accepted, please add it to documentation.

Nevermind this, closing.


week 8: service currently running as http fix to https?

https://dev.to/omergulen/step-by-step-node-express-ssl-certificate-run-https-server-from-scratch-in-5-steps-5b87

had 2 meetings with Andy, explored the different options available, decided that the best option would be to leave the application as is and to set up edge secure router using openshift commands and self signed cert from openssl

used commands to create the edge route, self signed certificate obviously shows up as unverified, but we do not care in the proof of concept project. in docs we will mention that a proper certificate will have to be used for prod


#10 Make button spin around on resize

https://github.com/Saif8599/ui-events/commit/57aeab7180346736f152f377670806ecbd03ff14


Update ipcsocket to 1.4.1-aa-4

Updates com.github.alexarchambault.tmp.ipcsocket:ipcsocket from 1.4.1-aa-2 to 1.4.1-aa-4.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.alexarchambault.tmp.ipcsocket", artifactId = "ipcsocket" } ]

labels: library-update, early-semver-pre-release, semver-spec-pre-release, commit-count:1

This includes the latest upstream ipcsocket changes, plus closes client sockets like how Bloop does (shutting down input / output streams, which interrupts ongoing reads and writes), which looks safer.


[DOCKER] Fix missing apt https transport support

These two patches are unrelated so should not be squashed on merge.  I can submit them as separate pull request if that is preferred.

Thanks @mshawcroft for the contribution. Given both of them fixed the same installation file, i will just merge it as it is.


Blank "ok" boxes

how to fix these blank boxes, haven't downloaded any other mods or changed any mod orders

Not the right place for issues; the readme tells you where to report such things.

if you mean the discord ive already done that and noone could help sadly

the probability you'll get helped here is infinitely lower.


free chatgpt is here https://gpt0123.github.io/

https://gpt0123.github.io/ https://gpt0123.github.io/

This website is really great. How was it built? Did you use the model in llava to write your own HTML?


Push Notifications reported as sent and without error but not received in case of ~ 20 notifications

In case we send a certain amount of push notifications, they don’t seem to be delivered correctly. Everything works correctly for a lower amount of push notifications. We do not use persistent connections.
Here’s some very rough logging code that we had in place:
    client.push(*notifications)
    Rails.logger.info "PNS Job (1/2): Send #{notifications.length} notifications. Notification Sample: #{notifications.first.inspect}. Errors: #{notifications.collect(&:error).compact}. Sent: #{notifications.collect(&:sent?)}"
    Rails.logger.info "PNS Job (2/2): #{client.devices}, Push Infos: #{push_options.inspect}"

All following examples were created with the production build of the app, using the production certificate and Houston production client with houston 2.2.1.
Here’s the log output of a working example. As you can see, the errors are empty and both notifications are reported as being sent, and they are correctly received on both clients.
PNS Job (1/2): Send 2 notifications. Notification Sample: #<Houston::Notification:0x000000070bb240 @token="<REPLACED>", @alert="Some Text", @badge=1, @sound=nil, @category=nil, @expiry=nil, @id=0, @priority=nil, @content_available=true, @custom_data={:custom_data=>{:rscs=>[{REPLACED}]}}, @sent_at=2014-09-26 10:15:13 +0200>.
Errors: []. Sent: [true, true]
PNS Job (2/2): [], Push Infos: {:alert=>"Some Text", :badge=>1, :content_available=>true, :custom_data=>{:rscs=>[{REPLACED}]}}

Here’s the log output of an example that does not work. Again, the errors are empty and all notifications are reported as being sent, but they are not in fact received on the target devices. The target devices include the two devices from the previous working example:
PNS Job (1/2): Send 23 notifications. Notification Sample: #<Houston::Notification:0x0000000c8dc488 @token="<REPLACED>", @alert="Some Alert", @badge=1, @sound=nil, @category=nil, @expiry=nil, @id=0, @priority=nil, @content_available=true, @custom_data={:custom_data=>{:rscs=>[{REPLACED}]}}, @sent_at=2014-09-29 15:33:36 +0200>.
Errors: []. Sent: [true, true, true, true, true, true, true, true, true, true, true, true, true, true, true, true, true, true, true, true, true, true, true]
PNS Job (2/2): [], Push Infos: {:alert=>"Some Alert", :badge=>1, :content_available=>true, :custom_data=>{:rscs=>[{REPLACED}]}}

What could be the source of the error or what else could we look into to narrow down the problem?

Hello, this issue was solved? If no, how are you handling this?

@LuizEdgar, not to the best of my knowledge, instead I send each notification separately to users instead of en masse.

Thanks @kaneda.
Well... but Apple says that it can be considered as an DoS Attack.
"Keep your connections with APNs open across multiple notifications; don’t repeatedly open and close connections. APNs treats rapid connection and disconnection as a denial-of-service attack. You should leave a connection open unless you know it will be idle for an extended period of time—for example, if you only send notifications to your users once a day it is ok to use a new connection each day."
How bad can it be? How many notifications are you sending per day?

@LuizEdgar it could be considered a DoS attack. I'm not sending many, in the hundreds.


IS there any specific information about 'needsChannelSelector' property in manifest file

Type of issue
Missing information
Feedback
n/a
Page URL
https://learn.microsoft.com/en-us/microsoftteams/platform/resources/schema/manifest-schema
Content source URL
https://github.com/MicrosoftDocs/msteams-docs/blob/main/msteams-platform/resources/schema/manifest-schema.md
Author
@surbhigupta
Document Id
7b3413f4-9ade-accf-5cb2-83fead11a32a

@dtiwarATS - It is explained here in the manifest schema - https://learn.microsoft.com/en-us/microsoftteams/platform/resources/schema/manifest-schema#:~:text=Describes whether or not the bot uses a user hint to add the bot to a specific channel.
Default value%3A false
Could you please let us know if you are looking for more information on this?


add support for arbitrary conda-build arguments

Needed for things like extra channels.

@jezdez I can't ask for a review but here you are :)


Submission of Group 30_2352288_2352910_2352761_2353114_2252048

This is the submisson code of group 30 for the MM241 Assignment. In this submission we implement 2 policy based on Albano-Sapuppo Algorithm and Genetic Algorithm, all are heuristics approach.

Do not modify anythings outside your folder


Alpha3 regex rule broken when MTLS is enabled

This seems to be the only alpha3 test failing right now - and only in MTLS.
A bit hard to figure out from logs - to repro I suggest running only that test (commenting out all other route tests), and check the sidecar output.
Traced it down to:
 Offending document key: #/ssl_context/verify_subject_alt_name
[2018-03-16 00:52:08.052][17][warning][upstream] external/envoy/source/server/lds_subscription.cc:68] lds: fetch failure: tcp proxy: unknown cluster 'out.orig-dst-cluster-tcp' in TCP route
[2018-03-16 00:52:09.015][17][warning][upstream] external/envoy/source/common/upstream/cds_subscription.cc:67] cds: fetch failure: JSON at lines 494-507 does not conform to schema.
 Invalid schema: #/definitions/ssl_context/properties/verify_subject_alt_name
 Schema violation: type
 Offending document key: #/ssl_context/verify_subject_alt_name

Which in turn corresponds to:
  {
    "name": "out.v2.pilot-auth-test.svc.cluster.local|grpc",
    "service_name": "v2.pilot-auth-test.svc.cluster.local|grpc",
    "connect_timeout_ms": 5000,
    "type": "sds",
    "lb_type": "round_robin",
    "ssl_context": {
     "cert_chain_file": "/etc/certs/cert-chain.pem",
     "private_key_file": "/etc/certs/key.pem",
     "ca_cert_file": "/etc/certs/root-cert.pem",
     "verify_subject_alt_name": null
    },
    "features": "http2"
   },

For reference the rule is:
v1alpha3/rule-regex-route.yaml.tmpl
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: default-route
spec:
  hosts:
    - c
  http:
    - match:
      - headers:
          foo:
            regex: "b.*"
        source_labels:
          version: v1
      route:
      - destination:
          name: c
          subset: v2
        weight: 100
    - route:
      - destination:
          name: v2
        weight: 100

+Louis - I think the rule itself is invalid - "destination: name: v2" should be name: "c" and subset.
But I think this but raises a much bigger issue - if we send any invalid config to Envoy the entire cluster will fail, in this case the invalid cluster prevents loading the entire CDS.
We need to add more 'invalid config' tests - and maybe for 0.8 add some pilot-side validation (at least it will be better with the proto-based v2 - but even there we should do additional checks).

@costinm, could you provide more steps to reproduce or error link? So I can investigate more? The first impression is verify_subject_alt_name = null seems not right, and it's generated by pilot.

I wonder if this is related: ci/circleci e2e-pilot-auth fails on an empty PR https://github.com/istio/istio/pull/4321 on v1alpha3 route rules test.

Thanks for diagnosing this @costinm. I created a fix for the badly defined config: https://github.com/istio/istio/pull/4327
@vadimeisenbergibm: yes, it should be causing failures in circleci as well.

@ijsnellf, thanks for the fix, can we mark this as closed now?

@ijsnellf  Thanks for the fix - but that's just hiding 2 much bigger problems.
Can you add back the (broken) rule first, so we can repro the 2 problems:

In some cases we seem to generate spiffee = null - not clear what and how, but we need to find the correct value.
Null should never be generated - it makes the entire CDS invalid and nothing will work in the mesh until the rule is removed.

To reproduce: just apply the (broken) rule, and watch for CDS, in an auth-enabled cluster.

@mandarjog

This seems to be a v1 issue, and is this still happening? @ZackButcher


Add into methods for Value

Specifically into_object into_array and into_string. These methods would significantly improve ergonomics in certain cases by reducing large match expressions into simple method calls.
match json {
    Value::Object(x) => x,
    _ => return Err(Error::None),
}

vs
json.into_object()?

Seems reasonable. Would these return Option and just destroy your value if it is the wrong type?

Alternatively they could return Result and return the Value inside the Err variant.

I think I would slightly prefer the Result way.
There are at least 3 reasonable error types:

Result<_, Value>—just give them back the value. I would prefer not to do this because it does not play well with ? and c-good-err.
Result<_, SomeConcreteError>—with an accessor for the original value. This could work but requires a map_err(de::Error::custom) if you want to call it from a deserialize impl.
<E> Result<_, E> where E: some trait—the way that Visitor methods are structured. We could make this easily usable in a deserialize impl without map_err but may require a type annotation elsewhere.

I would like to see an example of a deserialize impl using these into methods and see what we can do to make that ergonomic.

I think I prefer the Option way, for several reasons

It seems intuitive and semantically correct

The absence of a specific data type does not necessarily indicate an "error"

It is consistent with the existing as_* methods, which all return Option
I've encountered the need for into_* methods on Value a few times before, and every time an Option-like implementation would have been more useful than a Result-like implementation
If the need arises to get back the value on type mismatch, the user can easily write a match statement
It avoids the bikeshedding about the Result::Err type from the previous comment


1.3.0 segmentation fault with neat

I keep getting segmentation faults when running gulp-sass#1.3.0 with a project using neat. If I comment out the neat import in my scss file, the fault doesn't occur.
Reverting to 1.2.4 fixes things.

@saadfarooq This is probable a libsass / node-sass thing. Have you made sure to completely reinstall gulp-sas?

Yup... remove my npm cache, reinstalled all packages, even upgraded the system packages to make sure. Still crashes, even with 1.3.1.
Maybe it's something in neat who don't claim compatibility with the latest libsass but there should still be an error. With so many wrappers it's hard to tell where in the chain it's going wrong for me.

So this definitely seems like a<EMAIL_ADDRESS>issues. Closing here.


[e2e]: nodejs push main custom_publish slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8843839300
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Fri Apr 26 06:09:13 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8857800730
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Sat Apr 27 06:09:10 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8865519759
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Sun Apr 28 06:08:24 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8874015259
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Mon Apr 29 06:07:47 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8890030778
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Tue Apr 30 06:06:19 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8906040937
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Wed May  1 06:08:20 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8919349024
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Thu May  2 06:07:20 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8934790296
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Fri May  3 06:07:17 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8948478606
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Sat May  4 06:07:07 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8956151370
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Sun May  5 06:06:13 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8964721383
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Mon May  6 06:08:43 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8980461290
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Tue May  7 06:09:25 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8997060983
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Wed May  8 06:08:11 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/9013116313
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Thu May  9 06:06:57 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/9028022897
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Fri May 10 06:07:41 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/9041607505
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Sat May 11 06:08:33 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/9049305995
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Sun May 12 06:08:10 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/9058013113
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Mon May 13 06:08:19 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/9074541875
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Tue May 14 06:08:28 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/9090759487
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.custom_publish.slsa3.yml
Trigger: push
Branch: main
Date: Wed May 15 06:06:39 UTC 2024
Tests are passing now. Closing this issue.


The 3 body problem

Steps:
Create a script to calculate the propogation of 2 bodies in time
Find and use tools to animate results
Test that it remains stable
Add one body
AC
A configurable simulation script exists to generate, propogate, and visualize the 3-body problem

Consider:
http://arborjs.org/docs/barnes-hut


[querier] filter support in

Phenomenon and reproduction steps
Root cause and solution
filter support in
Impactions
Test method
Affected branch(es)

main

Checklist

[ ] Dependencies update required
[ ] Common bug (similar problem in other repo)

 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.Liu Chao 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.


Fix: add label to checkbox component

What I did
Adding a label to the Checkbox component for greater accessibility. I wrapped the Checkbox component with our InputLabel component. If a label is specified as a prop when instantiating a Checkbox, it will be visually displayed to the right of the component.

Victor approved visuals, merging!

Victor approved visuals! Merging and will update docs


Bug: API rate limit for GitHub contributors

Describe the bug
{
  "message": "API rate limit exceeded for {MY IP}. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
  "documentation_url": "https://developer.github.com/v3/#rate-limiting"
}

To Reproduce
Steps to reproduce the behavior:

Go to https://apprenticeships.me/ a crap ton
Contributors from GitHub don't show up

Expected behavior
Auth for API so there's never any rate limit reached
Screenshots

Additional Context
https://developer.github.com/v3/#rate-limiting

@benjaminmodayil Apologies for the delay here, I'm not entirely sure but some sleuthing into Hugo's docs would probably be better. Gatsby is much newer than Hugo and has a smaller community so I'd reckon Hugo can do this as well.

@fvcproductions I'll look into this. I always thought Hugo had a smaller community than Gatsby, haha. But I guess that's just because I use Gatsby a lot...


Add Cobo Vault hardware wallet support

Hi, this PR adds support for Cobo Vault
This PR integrate with cobo vault eth-keyring witch supports the common ETH related functionality and usage with Cobo Vault hardware.

Hi @aaronbarnardsound , thanks for your review, I have resolved code issues mentioned above, would you like to do a review again when you have time? 😄


404 on the webpage of liblb

At webpage: http://liblb.com/r2.html
I ran into a 404 when clicking: isup.me
It linked to: http://liblb.com/isup.me
Possible fix link to: http://isup.me/
Context on the webpage:

Use Cases
Three Tier Applications, most websites basically.
Stateless Applications, for example an uptime service that checks if a certain server up or not by sending a request to (isup.me)
liblb R2 Balancer API docs

good catch!
thanks.


Make "Add / Hide Tokens screen" table resize when keyboard is shown/hidden for searching #1990

Closes #1990

@hboon this PR depends on #1993

@vladyslav-iosdev is this good for review?

@vladyslav-iosdev is this good for review?

yes

@James-Sangalli you want to take a look?

@James-Sangalli bump


proj-includes not found when building sumo from source on macOS

Choose an option
This is a:

[ ] Question
[ ] Feature request
[x] Bug report

Describe the issue
Following the instructions to build sumo from source on macOS leads to the following error:
$ ./configure CXX=clang++ CXXFLAGS="-stdlib=libc++ -std=gnu++11" --with-xerces=/usr/local --with-proj-gdal=/usr/local
.
.
.
configure: error: proj-includes not found in "/usr/local/include".

To Reproduce
(flow) ➜  sumo git:(master) ✗ g co 2147d155b1
Checking out files: 100% (19725/19725), done.
M	tests/complex/tutorial/quickstart/data/quickstart.net.xml
Note: checking out '2147d155b1'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 2147d155b1 version info for cmake, refs #563
(flow) ➜  sumo git:(2147d155b1) ✗ make -f Makefile.cvs
autoreconf -i
glibtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
glibtoolize: and rerunning glibtoolize and aclocal.
glibtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
glibtoolize: 'AC_PROG_RANLIB' is rendered obsolete by 'LT_INIT'
(flow) ➜  sumo git:(2147d155b1) ✗ brew update
brew install Caskroom/cask/xquartz
brew install autoconf
brew install automake
brew install pkg-config
brew install libtool
brew install gdal
brew install proj
brew install xerces-c
brew install fox
export CPPFLAGS=-I/opt/X11/include
export LDFLAGS=-L/opt/X11/lib
Updated 4 taps (homebrew/cask-versions, homebrew/core, homebrew/cask and caskroom/cask).
==> Updated Formulae
angular-cli                      cocoapods                        lxc                              presto
==> brew cask install Caskroom/cask/xquartz
Warning: Cask 'xquartz' is already installed.

 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld
checking if the linker (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld) is GNU ld... no
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking the maximum length of command line arguments... 196608
checking how to convert x86_64-apple-darwin18.6.0 file names to x86_64-apple-darwin18.6.0 format... func_convert_file_noop
checking how to convert x86_64-apple-darwin18.6.0 file names to toolchain format... func_convert_file_noop
checking for /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... no
checking for strip... strip
checking for ranlib... (cached) ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking for dsymutil... dsymutil
checking for nmedit... nmedit
checking for lipo... lipo
checking for otool... otool
checking for otool64... no
checking for -single_module linker flag... yes
checking for -exported_symbols_list linker flag... yes
checking for -force_load linker flag... yes
checking for ANSI C header files... no
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking for gcc option to produce PIC... -fno-common -DPIC
checking if gcc PIC flag -fno-common -DPIC works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin18.6.0 dyld
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking how to run the C++ preprocessor... clang++ -E
checking for ld used by clang++... /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld
checking if the linker (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld) is GNU ld... no
checking whether the clang++ linker (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld) supports shared libraries... yes
checking for clang++ option to produce PIC... -fno-common -DPIC
checking if clang++ PIC flag -fno-common -DPIC works... yes
checking if clang++ static flag -static works... no
checking if clang++ supports -c -o file.o... yes
checking if clang++ supports -c -o file.o... (cached) yes
checking whether the clang++ linker (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin18.6.0 dyld
checking how to hardcode library paths into programs... immediate
checking for pkg-config... /usr/local/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for xerces-c >= 3.0... yes
checking for main in -lxerces-c... yes
checking xercesc/util/XercesVersion.hpp usability... yes
checking xercesc/util/XercesVersion.hpp presence... yes
checking for xercesc/util/XercesVersion.hpp... yes
checking for main in -lproj... yes
checking proj_api.h usability... no
checking proj_api.h presence... no
checking for proj_api.h... no
configure: error: proj-includes not found in "/usr/local/include".

Note that proj is definitely installed:
(flow) ➜  sumo git:(2147d155b1) ✗ ll /usr/local/include | ag proj
lrwxr-xr-x    1 brandon  staff    48B May  5 20:33 epsg_proj.inc -> ../Cellar/libgeotiff/1.5.1/include/epsg_proj.inc
lrwxr-xr-x    1 brandon  staff    39B May 20 09:58 geodesic.h -> ../Cellar/proj/6.1.0/include/geodesic.h
lrwxr-xr-x    1 brandon  staff    43B May 20 09:58 org_proj4_PJ.h -> ../Cellar/proj/6.1.0/include/org_proj4_PJ.h
lrwxr-xr-x    1 brandon  staff    33B May 20 09:58 proj -> ../Cellar/proj/6.1.0/include/proj
lrwxr-xr-x    1 brandon  staff    35B May 20 09:58 proj.h -> ../Cellar/proj/6.1.0/include/proj.h
lrwxr-xr-x    1 brandon  staff    39B May 20 09:58 proj_api.h -> ../Cellar/proj/6.1.0/include/proj_api.h
lrwxr-xr-x    1 brandon  staff    45B May 20 09:58 proj_constants.h -> ../Cellar/proj/6.1.0/include/proj_constants.h
lrwxr-xr-x    1 brandon  staff    48B May 20 09:58 proj_experimental.h -> ../Cellar/proj/6.1.0/include/proj_experimental.h
lrwxr-xr-x    1 brandon  staff    49B May 20 09:58 proj_symbol_rename.h -> ../Cellar/proj/6.1.0/include/proj_symbol_rename.h
(flow) ➜  sumo git:(2147d155b1) ✗ brew info proj
proj: stable 6.1.0 (bottled), HEAD
Cartographic Projections Library
https://proj4.org/
Conflicts with:
  blast (because both install a `libproj.a` library)
/usr/local/Cellar/proj/6.1.0 (58 files, 11.9MB) *
  Poured from bottle on 2019-05-20 at 09:58:16
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/proj.rb
==> Dependencies
Build: pkg-config ✔
==> Options
--HEAD
	Install HEAD version
==> Analytics
install: 12,180 (30 days), 32,910 (90 days), 95,434 (365 days)
install_on_request: 1,650 (30 days), 4,373 (90 days), 11,226 (365 days)
build_error: 0 (30 days)

Expected behavior
sumo to build successfully
Screenshots
Desktop (please complete the following information):

OS: macOS 10.14.5
Commit number of flow: f5a8d1cc9dd2323ace66c6b6ae98c28b6b9a1d6c
Version [run python -c "import flow; print(flow.version)"]: 0.4.0.dev

Additional context

hi @bmwilly from these lines:
checking for main in -lproj... yes
checking proj_api.h usability... no
checking proj_api.h presence... no
checking for proj_api.h... no

it looks like the problem might be proj_api.h. Can you check if this in in /usr/local/include? Maybe if you link this file to this folder the problem could be resolved.

@AboudyKreidieh you can see that it exists in my previous comment

hi @bmwilly from these lines:
checking for main in -lproj... yes
checking proj_api.h usability... no
checking proj_api.h presence... no
checking for proj_api.h... no

it looks like the problem might be proj_api.h. Can you check if this in in /usr/local/include? Maybe if you link this file to this folder the problem could be resolved.

How to link that file to this folder?
I really face many problems when install procedure.
Please help.

Hi,
I faced the same issue and this is how I fixed it. Instead of the recommended command:
$ ./configure CXX=clang++ CXXFLAGS="-stdlib=libc++ -std=gnu++11" --with-xerces=/usr/local --with-proj-gdal=/usr/local
Just use:
$ ./configure
and then follow along with the instructions and if that doesn't help use this:
$ brew tap dlr-ts/sumo
$ brew install sumo
Make sure your environment variables are pointing to the right directories though.
Refer to:
https://sumo.dlr.de/docs/Installing/MacOS_Build.html

closing since I no longer use flow


Please upload old version linux 32bits

Hello i want to install piskel on old small laptop .
It run with ubuntu 16.04 with lxde.
I must use midori for web and piskel don't work very well on it.
Thanks for your job.

Try building the desktop app using #1049.


[Event Request] Codeunit 5879 Phys. Invt. Order-Finish (Y/N) - OnBeforeConfirmOnRun

Hi Team,
In codeunit 5879 we need possibility to replace and avoid using standard code. Having event with handling in procedure OnRun, would be a perfect solution :

[IntegrationEvent(false, false)]
local procedure OnBeforeConfirmOnRun(var PhysInvtOrderHeader: Record "Phys. Invt. Order Header"; var IsHandled: Boolean)

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


[Cache] Caching should respect bigints

When reindexing from SQL cache, bigint types get fetched with scientific notation resulting in incorrect token IDs.
Update the fork and create a PR that resolves the issue so that the correct tokenIDs from event.params are returned

In #2


Check box for looping prompts, ability to repeat checkpoint use, embedded iterators with various lambda functions.

These features are working pretty well, and I've been enjoying the ability to use these together to iterate through batches of lora checkpoints and weights for testing.
CheckPoint Names: [checkpointIterations=20],realisticVisionV30_v30VAE
Prompts: lyco:lycoName-:1**[000001,lycoCount,++]**p1p3r
*the string for the initial value of the iterator is also used for the formatting of the output, so the numbers will increment like so: 000001, 000002, ...000011, ...
A prompt set up like this would produce 20 pictures, slowly increasing the one attribute weight:
CheckPoint Names: [checkpointIterations=20],realisticVisionV30_v30VAE
Prompts:  prompt text, (low key:[0,lowKeyIncrementer,+=,0.05])
In BatchParam.py there's an Operators dictionary with lamda functions. functions can be added here easily with as many variables as desired (just add defaults). simply pass in more variables in the iterator prompt [x,varName,lambda_name,n,a,b,c,d,...]
Important info and examples are currently in the Advanced Tab:
[CHECK BOX] Loop Through Prompts
Prompt list will be cycled through if shorter than model list.
A single prompt will repeat.
A longer prompt list will have the extra prompts ignored.
Add this to your Checkpoint Names input(comma separated like the checkpoints) to cause each checkpoint to be used n times before moving to the next checkpoint.
[checkpointRepetitions=n]
Example Checkpoint Names: [checkpointIterations=5], checkpointName1, checkpointName2, checkpointName3
*note: this is different than setting the batch with {{count:n}} in that it will support multiple prompts and embedded prompt iterators.
[CHECK BOX] Enable Embedded Prompt Iterators
Embedded Prompt Iterators allow you to have a number changed based on a function from generation to generation.
Each embedded iterator has a unique name, the first time that embedding is found, the initial value is used.
The next time that embedding is found, the operator is applied to the previous value.

Process Iterators: use the pattern [initVal,iteratorLabel,operator,operand,operand,operand…]. The brackets and contents will be replaced by the result of the operator. The initial value will be used first, and any subsequent call to the same iterator label will apply the operator using it’s optional operands.

Functions available:
++,–,sqrt:
[startInt,myIteratorName,++]
[1,myIncrementor,++] (put after a lora/lyco training checkpoint…)
+=,-=,=,/=,%=,^=:
[startInt,myAdderName,+=,operandFloat(default=1)]
[0.3,myMultiplier,=,1.1] (this will increase slowly but faster as it goes)
log,log10,log2:
[startInt,myIteratorName,sqrt,amplitudeFloat(default=1),FrequencyFloat(default=1)]
[0.5,mySinIterator,sin,0.1(default=1),FrequencyFloat(default=1)]
approach_limit:
[startInt,myIteratorName,approach_limit,limitFloat(default=1),RateFloat(default=1)]

i'm at the beginning of the exam phase, i don't have a lot of time. i understood and was able to use the iteration over the checkpoints. i think i understood what the prompt itterators should do, but i didn't get it working that way. Can you show me a concrete example?

I like your idea, but i think it's to much for this. checkout the fork_mention branch. I've mentioned your fork there if you want to.

Thanks! I might just use my fork for my specific testing purposes. Maybe I'll throw some documentation up so other ppl can use it if they want. I might even adapt it a little more to the purpose.

have fun with this script as base :)


Allow projects to use their own version names

I have currently worked on a project which required Node.js and some NPM packages. I had installed Node.js at the very beginning with brew install node. In my project, I use a package (NativeScript) which requires the LTS version of Node and is not particularly working with the latest version. So I tried installing a previous version of Node with brew install node@x but this failed because it does not install NPM correctly. So I tried to get some help from the Node.js team (see: https://github.com/nodejs/help/issues/1599).
So what I actually aiming to is that it would help packages like Node to create there own version names like in this case node@lts and node@latest to point to exactly this version they describe on their website. This would help users and would reduce error when working with latest features that are not completely saved to use in some projects.

They can create their own packages if they wish in their own tap. The current packages are the supported path.

with brew install node@x but this failed because it does not install NPM correctly.

This isn't enough information to help you with this. Please fill out the issue template and create a more detailed for this in Homebrew/homebrew-core.


This really needs a loud annoying notification sound.

I think that this project would be much more complete with a sound to notify me when I receive a new message.

I'll get to work on this later today.


go/build: Context.WorkingDir should just be Dir

CL 203820 introduced Context.WorkingDir but I don't see the API review anywhere.
It seems like it should just be "Dir".
We don't use the terminology "working dir" anywhere.

See also #36167.

/cc @bcmills @jayconrod

I chose WorkingDir because Dir seemed a bit ambiguous, particularly given the ImportDir method. That said, I don't have a strong preference either way.
(@griesemer and @jayconrod reviewed the original CL.)
I'll send some changes to switch it to Dir.

(FWIW, I think I had picked up the name WorkingDir from x/tools/internal/imports, introduced in CL 158437.)


Config: add missing documentation for networking-related settings

Config.workers especially deserves to be documented. The other config
settings don't entirely need to be documented, but for the sake of
transparency Config.ssl and Config.bindaddress have been added as
well.

Replaced the Config.ssl documentation with a blunt TODO

Removed the Config.ssl line


Compose/XML switch - Use a dropdown menu to change the framework used

@afrahB  & @mccart77 this can be tested in the "Buttons: Icons" component


azure-xplat-cli should be removed in favor of azure-cli (the python package)

azure-cli is the 2.0 of Azure's CLI.
There is a significant amount of functionality only available through it, and it's generally just always preferrable. We should package it. I hope to be able to do this, but any pointed appreciated.
(It's generally installable with pip install --user azure-cli but it has FFI and C dependencies in some places.)

PRs welcome! We should probably setup an alias for azure-xplat-cli though.

@matthewbauer Tracking issue for packaging azure-cli: https://github.com/NixOS/nixpkgs/issues/40073
I'm a bit stuck on it, but whenever it's available, I'll loop back around here and figure out how to clean up the old CLI.

we don't have that package anymore


Explanatory first-time launch popup for Scan

On mobile it redirects to sequence.app, which is confusing. Let's explain that in a good way. More details to follow.

@gglucass any more details? :)


Fix/refactor

:books:  Summery

Fixed issue when we open chrome extension in the window to detect the active tab
Code refactoring and splitting

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

Chrome Web Store
GitHub release

Your semantic-release bot :package::rocket:


Cor 442 add yes no field type

I've left the record rendering as the string "true" or "false". There should be a better visual indicator of this, but I think this is fine for the purposes of the pwa.

I cannot save a form with a checkbox in it, there's no corresponding network request the save callback from the formerContainer gets undefined as formdefinition and the boolean field is not stored in the state with the rest of the form

Weird, I'd already fixed this but it hadn't been committed. I've pushed up a fix now.

if not clicking the checkbox is automatically translated to false, why do we need to mark the field as required?

Good point.. There is also 3 statuses for checkboxes. "Checked" "Not Checked" and "Indeterminate". The "indeterminate" one is the one with the horizontal bar in it.
https://css-tricks.com/indeterminate-checkboxes/

if not clicking the checkbox is automatically translated to false, why do we need to mark the field as required?

If we didn't force it to be required this could lead to inconsistent states between the frontend and the api. If I hit the api directly I could create a checkbox with a null value, but the frontend doesn't know how to interpret it and it doesn't make much sense conceptually. By making it required we ensure that it can only ever be true or false.

Yeah it's quite ambiguous "false" or "null", but the html checkbox has support for displaying nulls differently than false. Though, very little users will know about that ! Manses sense to force required for now

Good point.. There is also 3 statuses for checkboxes. "Checked" "Not Checked" and "Indeterminate". The "indeterminate" one is the one with the horizontal bar in it.
https://css-tricks.com/indeterminate-checkboxes/
Probably that we "could" (should?) allow "nulls"/"undefined" for non-required yes/no fields by allowing the "indeterminate" status? I'm thinking that in the future, when we start implementing "relevance rules" for fields, we'll need to have non-required checkboxes!

I think the use case of intermediate checkboxes isn't clear. I think they become useful if we were to implement checkbox groups, with children (think of selecting emails in gmail). So I think they fall out of the scope of this pr.
If we were to implement them I probably wouldn't use null as that is not what null means. I'd probably change the value to 0,1,2 or an enum of some sort.

Looks good to me, @internetti have you resolved the issues on your side ?

/lgtm


Add timeout for downloading tiles

I find it can block for hours because of some network problems. Although it's not a common situation , I think it's a good idea to add a timeout for downloading each tile. If you don't set a timeout , it may affect the next execution of the script , depending on the scheduler you are using.

I think adding timeout is a good idea, though I think we can calculate the timeout automatically:

Instead of a times and timeout, we can add another variable deadline to indicate in how many himawaripy should be done.

Because using your defaults (times = 3 and timeout = 120) in the worst case himawaripy can run for 4 days. :) (((4 ** 2) * 3 * 120 / 60) / 24)

So the timeout will be DEADLINE * 60 / (LEVEL ** 2) seconds for each tile to be downloaded.

@Jekus Thank you!


MAIN: Templates for AWS implementation

@jordanrburger AWS implementation into Production. Approve it please, but don't merge please. I'll test templates in BETA after you merge the PR and then if successful, I'll merge this PR on my own. Thank you. :-)


incorrect error message when BASEFS does not exist

I ran poudriere jail -c and got the following error:
[00:00:00] Error: Please provide a BASEFS variable in your poudriere.conf
however I did have a BASEFS variable in poudriere.conf (the default /usr/local/poudriere), but the directory didn't exist

This error is only shown (in 2 places) if BASEFS is empty.
[ -z ${BASEFS} ] && err 1 "Please provide a BASEFS variable in your poudriere.conf"
I don't see how it could fire if not empty.

From common.sh `BASEFS=$(realpath "${BASEFS}")

Your second comment about realpath is something I hit at work this week as well. There's a regression here because an earlier version apparently did mkdir -p $BASEFS but now assumes it exists, doesn't hide the error, and doesn't give a clear error about it.
At work we had this that caused some very obscure failures with jail -c:
poudriere.conf:
BASEFS=/p

% poudriere jail -c ...
realpath: /p: No such file or directory

Sorry I wasn't trying to be cryptic, I just found the way BASEFS was being sent after your comment and should have provided additional information.
realpath gives a warning on stderr if the path does not exist:
% realpath /does/not/exist
realpath: /does/not/exist: No such file or directory

but I guess stderr is redirected here along the lines of
% cat foo.sh
#!/bin/sh
exec 2>/dev/null
P=$(realpath /does/not/exist)
echo $P
% sh foo.sh

%

Related issue https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240118

I find this is fixed if I revert these 2 changes (so I assume they caused this regression):
https://github.com/freebsd/poudriere/commit/681c63f075ab411018a19f3139b25f155f46eeaf
https://github.com/freebsd/poudriere/commit/f065e9450add8bf33e8c792c52429bb789423c96

My experience with this issue is that it blocks first time setup of a new poudriere machine. My "poudriere  jail -c" command was failing entirely due to this issue.
Reverting the above 2 changes does not entirely fix the issue - the jail creation will proceed, but 2 of the zfs datasets get mounted in the wrong location under /zroot/poudriere/ whilst the rest all get correctly mounted under /usr/local/poudriere/:

zroot/poudriere
zroot/poudriere/jails

/usr/local/etc/poudriere.conf (relevant settings):
ZPOOL=zroot
ZROOTFS=/poudriere
BASEFS=/usr/local/poudriere

The command output:
# poudriere  jail -c -j 12amd64 -v 12.1-RELEASE
realpath: /usr/local/poudriere: No such file or directory
[00:00:00] Error: Please provide a BASEFS variable in your poudriere.conf

# zfs list
NAME                            USED  AVAIL  REFER  MOUNTPOINT
zroot                          2.02G   150G    88K  /zroot
zroot/ROOT                      721M   150G    88K  none
zroot/ROOT/default              720M   150G   720M  /
zroot/poudriere                 712K   150G    88K  /zroot/poudriere
zroot/poudriere/data            624K   150G    96K  /data
zroot/poudriere/data/.m          88K   150G    88K  /data/.m
zroot/poudriere/data/cache       88K   150G    88K  /data/cache
zroot/poudriere/data/images      88K   150G    88K  /data/images
zroot/poudriere/data/logs        88K   150G    88K  /data/logs
zroot/poudriere/data/packages    88K   150G    88K  /data/packages
zroot/poudriere/data/wrkdirs     88K   150G    88K  /data/wrkdirs

I can manually work around this issue if I run these commands before the first time I try to setup poudriere:
# zfs create -o compression=lz4 -o atime=off -o mountpoint=/usr/local/poudriere zroot/poudriere
# zfs create zroot/poudriere/jails
# zfs create zroot/poudriere/ports

My experience with this issue is that it blocks first time setup of a new poudriere machine.

Yes, this is how I encountered it.

I find this is fixed if I revert these 2 changes (so I assume they caused this regression):
681c63f
f065e94

That helped, thank you.


Using Dreamhouse

This write up says
"For details on using sfdx-dreamhouse, please review the Salesforce DX Developer Guide."
but I don't see info on dreamhouse in the guide. Did you mean "For details on using DX to manage the sfdx-dreamhouse project, please review the Salesforce DX Developer Guide."
or
"For details on using sfdx-dreamhouse, please review http://www.dreamhouseapp.io/."
or something else?

Thanks @SamGarforth for pointing this out. You're correct, the Dev Guide doesn't provide any substantial additional, so we updated the text to indicate that you should go to the Dev Guide to learn more about Salesforce DX.


[WIP] fix(mock): Remove mock service and related code

This PR removes mock service and related code
Fixes https://openshift.io/openshiftio/openshiftio/plan/detail/2276

[test]

@jarifibrahim Your image is available in the registry. Run docker pull registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2667 && docker run -it -p 5000:8080 registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2667 and visit http://localhost:5000 to access it.

[test]

@jarifibrahim Your image is available in the registry. Run docker pull registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2667 && docker run -it -p 5000:8080 registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2667 and visit http://localhost:5000 to access it.


fuse-box eslint-loader

I started with fuse-box today and i got to say this is one of the best bundle-loaders i have ever worked with. It will be really nice to have a eslint-loader for sloppy developers like me.

Thanks for you kind words! We will keep you posted!

Please, check this doc!
https://github.com/fuse-box/fuse-box/blob/master/docs/third-party-plugins.md
It has been implemented.


WireGuard remote mechanism support for vppagent forwarder

WireGuard remote mechanism support for vppagent forwarder is required.
Docs
https://docs.google.com/document/d/1Cgmr5hDJJNI4YLXXarMbqZRvq1Zoe7HCY8a8hwl6JKo //case Memif full userspace datapath

The question to vpp related to problem connect AF_PACKET and tun: https://lists.fd.io/g/vpp-dev/message/15678

With this issue, I also tried to do the next thing:
Patch AF_PACKET interface on vpp side to make it works as l3 interface.
I'd found that AF_PACKET interface was designed as L2 and to patch it we will need to do many changes (Looks like better create a separate interface type instead of Patch AF_PACKET)

Doc with a decomposition of most popular ways to fix this problem: https://docs.google.com/document/d/1ICYb2kV48l-T1qounqkUBetUAmme0znD9gl405HJ2VQ/edit?usp=sharing
@edwarnicke , @fkautz , @haiodo please take a look and share your thoughts.

finally blocked by https://github.com/networkservicemesh/networkservicemesh/issues/2137


Send MANIM_NOT_STARTED event during force quit

Fixes #83 where the Starting Manim... notification hangs when force-quitting right after starting the scene at a cursor position.
I could only reproduce this issue after several attempts, so I'm not sure if this is even the correct fix for it. Just tell me if this works on your end reliably @VladimirFokow.

Thank you! I'll check in the evening today


Migrate to github packages

Migrate CI and start using ghcr.io intead of quay.
https://docs.github.com/en/packages/learn-github-packages/introduction-to-github-packages
https://docs.github.com/en/actions/guides/publishing-docker-images

This hasn't solve my problem of being able to generate images per PR, closing it for now.


Different Robot Radius

Hi,
I want to use this benchmark with another bigger robot because I trained my planner for it.
But I think these worlds are not suitable for it. Did you consider this problem or do you have any suggestions about it?

Hi,
We are sorry that we designed the scenarios with reference to the size of the indoor mobile robot pioneer 3-DX, so these scenarios such as the narrow maze may not be suitable for large-sized outdoor mobile robots, e.g., husky.
In the future, we will build simulation scenarios for field robots, such as underground caves and mines. Currently, please consider using our robot model to train your planner.
Best,
Jian Wen
2021/9/6


CLOUD-304 cancellable polling

@keyki

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/852/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/859/

Jenkins build failed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/860/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/861/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/868/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/871/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/874/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/875/


Update OML mappings

This PR updates the OML mappings to use the new catchall mappings.
Test Steps:

OML Related tests should pass:

./gradlew :prime-router:testIntegration --tests "gov.cdc.prime.router.datatests.mappinginventory.omlo21.OMLO21Full" -Pforcetest
./gradlew :prime-router:testIntegration --tests "gov.cdc.prime.router.datatests.TranslationTests" -Pforcetest

All other tests should pass as well.

Changes

OML FHIR -> HL7 mappings are no longer dependent upon deprecated mapping files (hl7_mapping/common; hl7_mapping/v251; etc.)
Unused FHIR -> HL7 mappings have been removed
Created end-to-end tests for OML HL7 -> FHIR -> HL7 mappings.

OML HL7 -> FHIR catchall mappings were updated to better support a maximally configured OML message.

ServiceRequest.specimen and ServiceRequest.supportingInfo were added to support this. Specimen.collection and Patient.relationship were updated as well.

The vast majority of test updates on this PR are related to these catchall updates.

OML support for the CE to CWE casting was added.

Updated the OML data test files from translation-test-config.csv to reflect updates in the mappings

The .fhir file in the FHIR -> HL7 scenario will need to be verified and communicated with ETOR to ensure no breaking changes have been made. The significant differences here reflect the new and different fields being mapped in the OML HL7 -> FHIR conversion. #TODO

Checklist
Testing

[ ] Tested locally?
[ ] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[ ] (For Changes to /frontend-react/...) Ran npm run lint:write?
[ ] Added tests?

Process

[ ] Are there licensing issues with any new dependencies introduced?
[ ] Includes a summary of what a code reviewer should test/verify?
[ ] Updated the release notes?
[ ] Database changes are submitted as a separate PR?
[ ] DevOps team has been notified if PR requires ops support?

To Be Done
Follow up issues still need to be logged:

Ticket for Phase 2 of the OML mappings update. This will focus on adding any necessary new fields with a special focus on addressing fields that ETOR has documented as missing with the catchall uplift earlier this year.
A ticket to address a defect in the fhirdata cli tool which causes an exception when attempting to generate fhir data from a hl7 file. Unit tests should also be created for this command.
Possible ticket to add yml validation for conditional keywords. (ie NOT_NULL vs NOT NULL).

For some reason after pushing the last commit to fix the build, GitHub decided the backend didn't need to be built :/


LXD 3.15 : Package requirements (raft) were not met

LXD 3.15 seems to be still affected with this problem:
checking for RAFT... no
configure: error: Package requirements (raft) were not met:

Package 'raft', required by 'virtual:world', not found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables RAFT_CFLAGS
and RAFT_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

And I've patched the Makefile as follows:
diff --git a/Makefile b/Makefile
index 45d6749..17b4113 100644
--- a/Makefile
+++ b/Makefile
@@ -77,6 +77,7 @@ deps:
 	fi

 	cd "$(GOPATH)/deps/dqlite" && \
+		git checkout v0.3.0 && \
 		autoreconf -i && \
 		PKG_CONFIG_PATH="$(GOPATH)/deps/sqlite/:$(GOPATH)/deps/libco/:$(GOPATH)/deps/raft/" ./configure && \
 		make CFLAGS="-I$(GOPATH)/deps/sqlite/ -I$(GOPATH)/deps/libco/ -I$(GOPATH)/deps/raft/include/" LDFLAGS="-L$(GOPATH)/deps/sqlite/.libs/ -L$(GOPATH)/deps/libco/ -L$(GOPATH)/deps/raft/.libs/"

This happens on Alpine Linux as well as Arch Linux.
With and without this patch, LXD does not build.
Originally posted by @fcolista in https://github.com/lxc/lxd/issues/5875#issuecomment-511702064

The patch is only needed for version 3.14.
You don't need any patch for version 3.15, just build and install the dependencies included in the dist/ folder of the release tarball, or alternatively run make deps.


Feat: new features, performance improvements and bug fixes.

@xKeCo please remember to check Sonar suggestions. @JuanGuzman-io could you please help us here?

@xKeCo I will proceed to do the Pull merge without the requirements, but the errors reported by sonar must be addressed!


Azure Sentinel Workbook Displays Old Data Maybe Due To Caching

I have created a KQL and using that plotted a Tile view in the workbook. The data in the Tile is supposed to change based on the Timerange filter I have added. This is working fine unless new events are received. So let's say I have selected "Last 24 hours" at 12 PM and the count in tile is "2". Now I keep the session idle for a few minutes and at 12:10 PM, a new event arrives. Thereafter when I change the Timerange filter to "Last 5 minutes", I see the new event, but when I again change the Timerange filter to "Last 24 hours", the count still will be "2" instead of "3".
However, when I refresh the entire web page, the count will be updated. Is there any way to overcome this? I think the results are being cached by Azure and reused, but is there a way to disable this?

@utsavpatel51 - Thanks for letting us know and the detailed explanation of what is occurring.  Let me bring it back to some of the PM's on the team and we will see what we can track down.  Thanks, Shain

Thanks to John Gardner to help answer this query on MSDN.
@utsavpatel51 please review it and circle back for any further queries.
@shainw FYI

Thanks, I have to refresh the page manually or re-run the query but it seems when I use the tabs refresh button is not working for me.

Hi, thank you for your feedback.
I see that you have also asked this question via MSDN: https://social.msdn.microsoft.com/Forums/en-US/e1bb873b-089d-4da8-b322-6a4599b88a3e/azure-sentinel-workbook-displays-old-data-due-to-caching?forum=opinsights
please let us know if you have any further questions.