[syn] This adds a simple testsynthesis flow for DC

This adds a similar makefile-based testsynthesis flow for DC, analogous to the AscentLint flow. It allows to run a simple wire-load-model-based synthesis of individual IPs or the top-level.
Two example targets are provided within this PR, and they can be called by stepping into hw/syn and running:
make ip-aes_syn

or
make systems-top_earlgrey_syn

Area, timing, power and link reports will be written to hw/syn/reports once synthesis has completed.
Note that this is only a starting point and will soon be extended.
Also, this requires a technology setup scripts and the corresponding technology wrapper primitives to be present under hw/foundry/syn/dc and hw/foundry/ip/prim_<tech id>/
The integration into the dvsim dashboard (analogous to AscentLint) is in the making and will follow in a subsequent PR (together with more documentation).
Finally, it should be noted that this depends on PR #1679, hence the first two commits from @imphil should be ignored as they will disappear once that other PR has made it into the code-base.
Signed-off-by: Michael Schaffner<EMAIL_ADDRESS>

I should add that the SDC file is overly simple at the moment and will be soon updated to reflect the top-level better.

thank you for setting this up Michael!
On Thu, Mar 12, 2020 at 5:23 PM Michael Schaffner<EMAIL_ADDRESS>wrote:

I should add that the SDC file is overly simple at the moment and will be
soon updated to reflect the top-level better.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/pull/1739#issuecomment-598488917,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2RSUCULJB6M6OZLWJXCLRHF4JVANCNFSM4LGXNYFA
.

Added a couple of more top-level specific constraints, but this is still just meant to be a starting point (e.g. CDCs need to be refined, etc).

Thanks for all the comments, @cdgori! Appreciated.

Ok, I updated this with the suggestions from @cdgori and rebased it on top of master. @eunchan or @vogelpi could you maybe take a look as well? Note that there is a successor PR which will integrate this into dvsim, which gives us a nice dashboarding functionality: #1749
Also, once this is integrated into dvsim, I plan to split out the sdc constraints into individual constraint files on a per comportable IP basis.


Determine level of detail

@dgarijo  What level of detail do we want to go into in this repository?
Right now we have an initial  software-types.jsonld with a JSON-LD context and software-types.ttl that goes a bit deeper. I think ideally the jsonld file should have the same expressivity as the turtle file, right? (e.g. just two serializations of the same thing). Or do we want to keep the jsonld file only for the context? I don't really know what is customary and if json-ld files that contain more than context (i.e. a @graph) can also be referenced without issue from the `@context' of another.

I think both files should have equivalent information, i.e., the json-ld file should be self sufficient. In fact, we should probably maintain one and create the other one automatically. Thoughts?

Agreed!

Hmm, now I think they are not in sync


Maint: use async/await for services readiness

Please describe your feature request:
Replace the following hardly readable asyncronous pattern:
dnsTcpAlive := make(chan bool, 1)
go dnsTcpServer.ListenAndServe(dnsTcpAlive)
okTcpAlive <-dnsTcpAlive

with async/await functional programming which adds proper error propagation (depends on Use https://github.com/projectdiscovery/utils/pull/195):
checkTcp  := async.Exec(func() (bool, error) {
    return dnsTcpServer.ListenAndServe()
})
ok, err := checkTcp.Await()

Makes sense, the await should be wrapped itself into another go routine. The current implementation of async/await doesn't fit the runtime logic.


Support built-in functions on exposeFunctionByName, exposeFunctionByPrefix and exposeAsset

What is your feature request?
Built-in functions should work when passed as a string to exposeFunctionByPrefix and other related functions. E.g. exposeFunctionByPrefix("draw_").
Please describe in detail how you expect this new feature to behave.
Reduce sharp edge.

I could PR this directly, I just didn't because it has to be handled in a more jankier way. But the solution for it is just.
for(var i = 0; i < 10000; i += 1;) {
	if (!string_starts_with(script_get_name(i), "<unknown>")) {
	    // Native function exists, check additional for X
	}
}


New Button

Your component seems nice but there are too many unnecessary formatting changes like changing from single quotes to double quotes or adding semi colon. Please pull from our main branch and use only prettier for formatting. I'm closing this PR, you can open another one once you format using prettier.


add ignore to hco-bundle-registry-container

@tal-hason Would removing the relevant lines in https://github.com/openshift/check-payload/blob/main/config.toml to avoid redundancy ?

@tal-hason Would removing the relevant lines in https://github.com/openshift/check-payload/blob/main/config.toml to avoid redundancy ?

Not sure, i think it's only catching the versions, I can verify it with CVP slack

Is there a conversation in slack about these binaries? I'm curious why these are being disabled?

For example, there are *.test binaries that are not shipped to the customers, only to QE, and thus no FIPS checks needed. As for others, we just want to ignore this error (I'm pretty sure there is a reason for it in upstream).

@tal-hason Hi Tal, thanks! Just to make sure, it's only needed in 4.13, 4.18 and 4.19? I'd suggest to update PR's description to mention it.

@tal-hason Hi Tal, thanks! Just to make sure, it's only needed in 4.13, 4.18 and 4.19? I'd suggest to update PR's description to mention it.

From what I understood the 4.18 will effect the 4.17 4.16 4.15 and 4.14
and 4.13 will effect 4.12
am I correct?

Hello, can this be merged, is there anything blocking? We want to make sure we fully pass FIPS checks before the warnings become failures.

@ksimon1 can you assist with this PR to move to being merged

@tal-hason Hi Tal, thanks! Just to make sure, it's only needed in 4.13, 4.18 and 4.19? I'd suggest to update PR's description to mention it.

From what I understood the 4.18 will effect the 4.17 4.16 4.15 and 4.14 and 4.13 will effect 4.12
am I correct?

I'm not sure about this. I'd ask the maintainers of this repository.

@tal-hason Hi Tal, thanks! Just to make sure, it's only needed in 4.13, 4.18 and 4.19? I'd suggest to update PR's description to mention it.

From what I understood the 4.18 will effect the 4.17 4.16 4.15 and 4.14 and 4.13 will effect 4.12
am I correct?

I'm not sure about this. I'd ask the maintainers of this repository.

This is what was told here:
https://redhat-internal.slack.com/archives/C07TC0L7ATB/p1731420233351089?thread_ts=1731412943.825689&cid=C07TC0L7ATB

/lgtm
/approve


Create a HighLightCard component

[ ] Create a HighLightCard in atoms folder
[ ] It should receive img , title, description, and link props
[ ] It should match to UIX design

I've already done this one.


Publish to package registries

xref: https://github.com/chipsalliance/UHDM/issues/1000

[x] nixOS (@hzeller)
[x] homebrew / Mac (@timkpaine WIP: https://github.com/Homebrew/homebrew-core/pull/141533)
[x] conda (@timkpaine  conda-forge needs PR: https://github.com/conda-forge/staged-recipes/pull/23614)

[ ] debian (See note on UHDM issue)
[ ] rpm (See note on UHDM issue)

going to close this as its quite difficult to get in to Debian, but we've just onboarded to conda-forge


onboarding: Modify content on onboarding messages.

Tighten up the content.
Use pretty quotes.
Reorder "experiments" topic to appear after "start a conversation in Inbox.
Drop reference to messages being starred (not implemented yet). [bug fix]

Screenshots: messages in streams

Screenshot: Recent conversations

Screenshot: Inbox

@prakhar1144 While working on this PR, I noticed a possible bug, where I believe this line won't work when messages are translated:

    .filter(id__in=message_ids, content__icontains="a great place to say “hi”")

Would be great to figure out a fix if that's indeed a bug.

Closing in favor of https://github.com/zulip/zulip/pull/30063, which complets this.


Verify the payload field of a transaction matches the header

Signed-off-by: feihujiang<EMAIL_ADDRESS>Verify the payload field of a transaction matches the payload_sha512 field of the header.

I updated this PR according to your advice, and added a unit test. Please review again, thanks.


[SYSTEMML-445] [MINOR] Disable right indexing and refactor asserts to exceptions

@nakul02 can you please review this PR ?

Refer to this link for build results (access rights to CI server needed):
https://sparktc.ibmcloud.com/jenkins/job/SystemML-PullRequestBuilder/2088/

Refer to this link for build results (access rights to CI server needed):
https://sparktc.ibmcloud.com/jenkins/job/SystemML-PullRequestBuilder/2089/

@niketanpansare - if its not too much trouble, could you please split just disabling rightIndexing into a different PR than refactoring asserts and other minor optimizations? That way, we could test the impact of the optimizations separately from just disabling rightIndexing.

LGTM 👍
Please merge. This fixes the performance problems I've been seeing with GPU right indexing.

Refer to this link for build results (access rights to CI server needed):
https://sparktc.ibmcloud.com/jenkins/job/SystemML-PullRequestBuilder/2094/


After reboot server,Lxc is not working

hi,
After reboot server master node of lxc ,Lxc is not working. it is showing below error
Error: Get "http://unix.socket/1.0": dial unix /var/snap/lxd/common/lxd/unix.socket: connect: connection refused
while executing zfs  list command , it is giving result.
none of the lxc commands are not working,Every command giving above error only.
ps002,ps003(slave nodes) giving below details
lxc cluster list
+-------+----------------------------+----------+---------+--------------------------------------+--------------+----------------+
| NAME  |            URL    | DATABASE |  STATE  |               MESSAGE                | ARCHITECTURE | FAILURE DOMAIN |
+-------+----------------------------+----------+---------+--------------------------------------+--------------+----------------+
| ps001 | https://ip-1:8443 | YES      | OFFLINE | no heartbeat for 21h48m46.532442827s | x86_64       | default        |
+-------+----------------------------+----------+---------+--------------------------------------+--------------+----------------+
| ps002 | https://ip-2:8443 | YES      | ONLINE  | fully operational                    | x86_64       | default        |
+-------+----------------------------+----------+---------+--------------------------------------+--------------+----------------+
| ps003 | https://ip-3:8443 | YES      | ONLINE  | fully operational                    | x86_64       | default        |
+-------+----------------------------+----------+---------+--------------------------------------+--------------+----------------+
ps001 is master node of lxc every container is created in maser.ps001 has no heartbeat.
ps002,ps003(slave nodes) giving below details
sudo lxc list
+-------------------------+-------+------+------+-----------+-----------+----------+
|          NAME           | STATE | IPV4 | IPV6 |   TYPE    | SNAPSHOTS | LOCATION |
+-------------------------+-------+------+------+-----------+-----------+----------+
| Test-Storage            | ERROR |      |      | CONTAINER | 0         | ps001    |

Systemctl services was failed to restart but it is failling.
sudo systemctl status  snap.lxd.daemon
● snap.lxd.daemon.service - Service for snap application lxd.daemon
Loaded: loaded (/etc/systemd/system/snap.lxd.daemon.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2021-03-24 11:20:44 IST; 11min ago
TriggeredBy: ● snap.lxd.daemon.unix.socket
Process: 6916 ExecStart=/usr/bin/snap run lxd.daemon (code=exited, status=1/FAILURE)
Main PID: 6916 (code=exited, status=1/FAILURE)
Mar 24 11:20:44 ps001 systemd[1]: snap.lxd.daemon.service: Scheduled restart job, restart counter is at 5.
Mar 24 11:20:44 ps001 systemd[1]: Stopped Service for snap application lxd.daemon.
Mar 24 11:20:44 ps001 systemd[1]: snap.lxd.daemon.service: Start request repeated too quickly.
Mar 24 11:20:44 ps001 systemd[1]: snap.lxd.daemon.service: Failed with result 'exit-code'.
Mar 24 11:20:44 ps001 systemd[1]: Failed to start Service for snap application lxd.daemon.

Could you run snap set lxd daemon.debug=true, and provide us with the logs from snap logs lxd? That will likely display the error.

ok , i wil do it

after executing debug lxd command, it is working,Thank you

after executing debug lxd command, it is working,Thank you

That's great. The daemon.debug=true setting was only to get more information in the logs. You can safely turn it off again using snap unset lxd daemon.debug.


Remote "mirror" may already exist for self-hosted Actions runners

Brought up initially in PR #17 by @duythinht
Currently, the mirroring script works on an assumption that the remote mirror does not exist when the action executes. This should be true when using GitHub-hosted runners and using . However, if a user is using a self-hosted GitHub Action runner, this assumption may not necessarily be true.
In such a case where the remote exists git remote add fails.

@duythinht when you encounter this problem, are you using actions/checkout@v1 in your workflow to checkout the repository initially?

@duythinht when you encounter this problem, are you using actions/checkout@v1 in your workflow to checkout the repository initially?

Yeah, I have encounter this situation when I using a self-hosted GitHub Action runner on my server (via NAT) and try to mirror in to our gitlab server (self-hosted and have no access form outside internet), and I have used checkout@v2.
You also can look at the workflow (I already fixed it by some change, and I think those commit should merge to your upstream, because someone might be need it.
# This is a basic workflow to help you get started with Actions

name: CI

# Controls when the action will run.
on:
  # Triggers the workflow on push or pull request events but only for the master branch
  push:
    branches: [ master ]

# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
  # This workflow contains a single job called "build"
  build:
    # The type of runner that the job will run on
    runs-on: self-hosted

    # Steps represent a sequence of tasks that will be executed as part of the job
    steps:
      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
      - uses: actions/checkout@v2
        with:
          fetch-depth: '0'
      - uses: duythinht/mirror-action@master
        with:
          REMOTE: 'https://gitlab.internal'
          GIT_USERNAME: mirror-bot
          GIT_PASSWORD: ${{ secrets.GITLAB_PASSWORD }}

Also, the problem is addressing for self-hosted action runner, there is only once runner that can be action running, so everytime when the action run, there are no need to init a repo, which is already stored on the runner server. And the runner just use to checkout the branch, tag, etc... to run the workflow.
There are total difference with the cloud runner, each time the runner is triggered, the gh cloud runner will "borrow" a server, that may be available in the server pool, and I think after run the workflow the runner should be clean up before return to pool.

I believe this is resolved by #22 released in v0.5.0


Trying to migrate at runtime, "module is not an Ecto.Migration"

I'm trying to run selected migrations for tests - there are many tables created, and I need only 2 or 3 per test. I thought I would you use Ecto.Migrator to this end.
Environment

Elixir version (elixir -v): 13
Database and version (PostgreSQL 9.4, MongoDB 3.2, etc.): PostgreSQL v14
Ecto version (mix deps): 3.7
Database adapter and version (mix deps):{:ecto_sql, "~> 3.7"},
{:postgrex, ">= 0.0.0"},

Operating system: MacOS Monterey

Current behavior
Modules:
# dao/test/support/test_repo.ex
defmodule Dao.TestRepo do
  use Ecto.Repo, otp_app: :dao, adapter: Ecto.Adapters.Postgres
end

# dao/mix.exs
  defp elixirc_paths(:test), do: ["lib", "test/support", "priv/repo/migrations"]
  defp elixirc_paths(_), do: ["lib"]

# dao/priv/repo/migrations/20210402151318_create_accounts.exs
defmodule Pos.Migrations.CreateAccounts do
  use Ecto.Migration

  def change do
    create table(:accounts) do
      add(:some_id, :integer)
      add(:some_other_id, :integer)
      ...
    end
  end

Config:
config :dao,
	ecto_repos: [Dao.TestRepo]

config :dao, Dao.TestRepo,
	username: "postgres",
	password: "postgres",
	database: "test_db",
	hostname: "localhost"

MIX_ENV=test mix ecto.create correctly creates the db.
Usage:
Ecto.Migrator.up(TestRepo,<PHONE_NUMBER>1318, CreateAccounts)
# -> ** (UndefinedFunctionError) function Dao.Repo.Migrations.CreateAccounts.__migration__/0 is undefined (module Dao.Repo.Migrations.CreateAccounts is not available)

Ecto.Migrator.run(TestRepo, [{20210402151318, CreateAccounts}], :up, all: true)
# -> ** (Ecto.MigrationError) module Dao.Repo.Migrations.CreateAccounts is not an Ecto.Migration

Expected behavior
It should run the migration at runtime correctly.

You need to move the module into your lib directory then or use Code.require_file to load the file before running the migration.

Why is this:

defp elixirc_paths(:test), do: ["lib", "test/support", "priv/repo/migrations"]

not enough?

yes, cause I'm running tests

I'm guessing here, but maybe its because these are exs files?

Yup, .exs files would explain it.

If I copy the migration under lib/version_name.ex (not exs), it still doesn't get loaded.
It works only with Code.require_file. @josevalim is there a way to do this from mix.exs?


Can't scroll page when action menu is open

Sometimes the action menu extends beyond the page bounds, but when the action menu is open, the page cannot be scrolled.
The page should still be scrollable when the action menu is open.

I have plans to add option to switch this behaviour

Fixed in v4.0.0
Check in demos:

https://yoopta-editor.vercel.app/examples/withBaseFullSetup


add predictions to openapi

This change adds in the /predictions endpoint and the associated
definitions that go with it.

@ruivieira @sophwats ptal

@elmiko lgtm :)

@elmiko lgtm2
On 3 October 2017 at 15:25, Rui Vieira<EMAIL_ADDRESS>wrote:

@elmiko https://github.com/elmiko lgtm :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/radanalyticsio/jiminy-recommender/pull/1#issuecomment-333951241,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFELOUZrS4wbP2JyuMGODoztsS0cUTKeks5sooougaJpZM4PsjOw
.


it didn't work

*Hello, I don't really understand this, but I followed the instructions to manually set up a task.
I placed the ps file in mydocuments and added the appropriate path.

I tried running it manually and I tried restarting steam. each time, I press the guide button and SBP opens.
The only thing I can imagine might be an issue is that I have 2 steam profiles signed in... I can't think of anything else. does it make a difference that my gamepad is a dualsense?

Hey @triadne, sorry for the delay in coming back to you - it won't work if you run it just as a scheduled task in this way...
You'll need to set the scheduled task to watch for and to execute as Steam launches, because the button is remapped as Steam launches, and also when Steam closes; Valve's way of making sure it remains mapped... Groan.
Follow the guide for creating a scheduled task that watches for a Steam launch event trigger (either use the XML template I provided, or do so manually). This will work every time you launch Steam! 😊

Hi, thanks for your response.
Yes, I used the XML as instructed.

Awesome. Did you first enable 'Audit Process Tracking'? without that, the Steam process event ID (4688, as is per the screenshot, top-right) won't register...

hmm... I thought that was part of the automatic process.
okay. let's do that then!
but I have a concern. what is computer configuration? I don't have that. I have msconfig and computer management. is it one of those?

It will be, in time! I have to keep plugging away at the Powershell to get that part worked out! I logged it as issue#6, I think!
What version of Windows are you using? Do a START>RUN and type 'winver'

it's 22h2.
so where do I find this computer configuration? do I download it?

No, it's built in. Run gpedit.msc

Run gpedit.msc

Yeah... It didn't work...
I looked into my config.vdf, and none of the controller configs contain "guide:b1" or similar strings... There's no "guide" reference there, but it still opens the BPM...
I have Logitech F310... (To be honest, I didn't even think that was a real button until today)

Yeah... It didn't work... I looked into my config.vdf, and none of the controller configs contain "guide:b1" or similar strings... There's no "guide" reference there, but it still opens the BPM... I have Logitech F310... (To be honest, I didn't even think that was a real button until today)
UPD: I think I figured it out... It only works if you assign buttons manually at least once - through the "Test Device Inputs" menu... As some people have recommended, I skipped assigning the Guide button, and it now doesn't launch the BPM... However, nothing has changed in the config.vdf... If I do assign the Guide button, then it indeed appears in config.vdf... Now the fun part - If you press Reset device inputs, the Guide button starts to open BPM again, but in the config.vdf there are still no mentions of the "guide", unlike the case when you assign it manually... Something seems to be hardcoded in Steam...

You sir, appear to be unconditionally right (at least in my case, too). If one assigns the buttons, it works.
The script itself is nothing more that an automated process that looks for and opens the config.vfd file, iterates through, and removes and mention of 'guide:xx' [stopping at the next comma], so yeah, if it's not in there, it just won't work. Groan.


Do you have a version that runs on Mac OS 10.14.6 (18G9028) ?

If there is a way to download it, please advise. Thank you.

Unfortunately not. This app started out targeting macOS 11.

Thanks very much.
On Monday, May 31, 2021, Sindre Sorhus @.***> wrote:

Unfortunately not. This app started out targeting macOS 11.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sindresorhus/System-Color-Picker/issues/14#issuecomment-851434347,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA7N5CU3OHNR7MBDKZ2RQTTQNZM3ANCNFSM452XIIQQ
.

--
[via phone]


Remove asct-b/ref-organ docs

Katy said these are not actually needed, and the DOIs will reference github instead?

Hi Chuck,
Yes, yesterday it was determined that we create our own GitHub repo for the purpose of managing files associated with the DOI process. Sorry for all the unnecessary effort on your end. The DOIs will reference this new repo.
Thanks again for the help.

From: Chuck McCallum @.>
Sent: Friday, March 26, 2021 8:13 AM
To: hubmapconsortium/portal-docs @.>
Cc: Cross, Leonard Edward @.>; Review requested @.>
Subject: [hubmapconsortium/portal-docs] Remove asct-b/ref-organ docs (#60)
Katy said these are not actually needed, and the DOIs will reference github instead?

You can view, comment on, or merge this pull request online at:
https://github.com/hubmapconsortium/portal-docs/pull/60
Commit Summary

Katy said these are not actually needed, and the DOIs will reference github instead?

File Changes

D asct-b/bone-marrow-and-blood.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-4e314a3de08de130605da55e875f0a4e758448b2017dc8f0d25d42714158ecca (20)
D asct-b/brain.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-2283d777f301a40ad9b34113e7c6b56a94cb3dc47cfbc07b0454ccb753f59b85 (20)
D asct-b/heart.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-063b7060b2d233f1623abc19609f81f1a43c4d80558ce7ccdb69f7217fe29f5d (20)
D asct-b/intestine-large.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-083885a35bb69c0bbaa3fa5602194eb8fa71e92658eead2cc4977c804361dc69 (20)
D asct-b/kidney.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-16f4d0d120d47381546acf5ba479dddee1cf56c84e8ed64d2ca74f107fc251af (20)
D asct-b/lung.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-7905ee5cdc41b239e7953af180cfabe9b396b7e639a67c852d0648ec13fd03a5 (20)
D asct-b/lymph-node.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-d5572affaed07057ee2942be10ad00d199d0a2f691b65d73fa5c74b9667135cb (20)
D asct-b/readme.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-7c3807d36c92da99bfa4e3de69c438f7f1b812fa519beba9d6063ca3e99476fd (1)
D asct-b/skin.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-641db8bde120752153f5f5f8d5f2b2baa404ae4ac0b98d8f39d9c0e68ae63a2b (20)
D asct-b/spleen.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-9a508b64bf8ea97fb3fa3e739d775428f74d7bb657f4a5a22ffbdd6339760a9b (20)
D asct-b/thymus.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-6ffbf3bb63b83f2f964dff714fde26c4e4a4d343bd7c598cc939ac6ef48a8076 (20)
D asct-b/vasculature.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-bbe621b6b99f8f5d2602969c38a26704acf2eaf4acf573edacc2ed4cb0c1f919 (20)
D ref-organs/brain-female.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-6330ec941779c0542dc17edfbc49651eb2ec04eacdbcb935b21607cafb1e6dd5 (20)
D ref-organs/brain-male.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-191ec4b9f071b2fe74d32002a4b3672b86955d95c025e76d53950d29dda9b8b7 (20)
D ref-organs/heart-female.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-238ba45d1262375f176fab6aa555f956f76250ce36a55276069c8b91ce520b43 (20)
D ref-organs/heart-male.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-6f955594b5b39b54f8ecd9096d07095ea401b006304d353db54e634591f2eba6 (20)
D ref-organs/intestine-large-female.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-d89cbc2bb9458be90ebf65ca4b786db3e61c6d7af4e7832101cf410369e58a29 (20)
D ref-organs/intestine-large-male.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-af4e442636caaada698cc361e6b794e68c4c47b0323b56a03e11cc52f2f94ac2 (20)
D ref-organs/kidney-female-left.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-8c2c71de181a6ae6fa1c039e4d1337753097de3da185f485ec0e3bebe218ded3 (20)
D ref-organs/kidney-female-right.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-b2abfd2dc5da2846cf7b878edaca10d0a7cef884d1c602f0f1482b102eb1e4f1 (20)
D ref-organs/kidney-male-left.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-5a4a2bc42aabe7a7bd3be6ba60b8df3ad73c6f5aa789c0520c5960a038184088 (20)
D ref-organs/kidney-male-right.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-17c951000e11cd072ae82bdbc9c309e5882fc2010d6690676278bf563a65d4d6 (20)
D ref-organs/lung-female.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-5919506be3e567ffd94f494ca10bb4c3219c369c9ec3e53ca3c3d0ca6c65b9d2 (20)
D ref-organs/lung-male.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-de7f4154503c5859fffb245c4040723922b3ecf4022ae1defebb7ba59ea8699a (20)
D ref-organs/lymph-node-female-left.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-bdc4a83da525a5a9125e1fd9e9297423f4a76a54e0f45fde2fe212926d7357af (20)
D ref-organs/lymph-node-female-right.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-e6f2cc9a24aa2d49056c9c9fa59fc668529f1d4425dba811a38196f5e8503998 (20)
D ref-organs/lymph-node-male-left.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-9de2e48a574324a9f39806c2b93956db2055e90106b57e0194ef8c2a3e8c237d (20)
D ref-organs/lymph-node-male-right.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-ff1a4ff196d0fcf60479affa5ff8f0efd66f5b54cf0edaba1e2e7ba45f80deb0 (20)
D ref-organs/pelvis-female.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-62a593ad3b32b8bfb880aff8271e501416e33264f85cd04e0524b334e6ebe2d1 (20)
D ref-organs/pelvis-male.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-644a8514e0c67a9633ffdf6ace26282ede4626579f4cf68f6aabc3283f073959 (20)
D ref-organs/skin-female.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-1b32c3a84de5db0240ee9f2d78109727a94042094e57d908f411f721ee8d5721 (20)
D ref-organs/skin-male.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-aeb3841187dbbfb684710301222034aef5998a8204a456c61c06ea65adab5dcc (20)
D ref-organs/spleen-female.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-7425fd2b386b3544861a9d3e1fc48b897cb80e3ca2210f047abd768e85786681 (20)
D ref-organs/spleen-male.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-53dfa8dc626e59fd55be19fd652fbea4fd7024532c7a00a00e752f0d902f2bbe (20)
D ref-organs/thymus-female.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-98a731182afbb034f41b781a2ace215b2e8c4d54f5729e5037be6094a1496f70 (20)
D ref-organs/thymus-male.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-c947f388c2cd317491692f5deb639562e5a2e21c4641246fe8ed2a9eef365f63 (20)
D ref-organs/vasculature-female.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-686f8578c4cf5c1e5c28ed6be5a0dc53b14e28dbad286987cea8df558b9ef331 (20)
D ref-organs/vasculature-male.mdhttps://github.com/hubmapconsortium/portal-docs/pull/60/files#diff-81d00754a263ed6ffba9fe2a68fe5c29c0c63b26321c1546aa1bae3ffbfd7582 (20)

Patch Links:

https://github.com/hubmapconsortium/portal-docs/pull/60.patch
https://github.com/hubmapconsortium/portal-docs/pull/60.diff

—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHubhttps://github.com/hubmapconsortium/portal-docs/pull/60, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJIWOIH2ZCN7BG6P3WVWR43TFSQBDANCNFSM4Z3SKISQ.

@lecross : Can you explicitly approve this PR, if it's ok?

Chuck, not sure what you need me to do. If you need me to simply state it is good to go, then yes. If you need me to do something in GitHub, then let me know. You can cancel the pull entirely. As far as I know, the files can be deleted from the server.

From: Chuck McCallum @.>
Sent: Friday, March 26, 2021 9:29 AM
To: hubmapconsortium/portal-docs @.>
Cc: Cross, Leonard Edward @.>; Mention @.>
Subject: Re: [hubmapconsortium/portal-docs] Remove asct-b/ref-organ docs (#60)
@lecrosshttps://github.com/lecross : Can you explicitly approve this PR, if it's ok?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/hubmapconsortium/portal-docs/pull/60#issuecomment-808354870, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJIWOIHAZMXYEZT36UZBYFDTFSZALANCNFSM4Z3SKISQ.

In the future, please use the PR review process in github to indicate approval: https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews#about-pull-request-reviews
I have a lot of PRs out, and it makes my life easier if I can just look at the status icon to know whether a PR can be merged.


Add receipt printer driver

Adds a simple receipt printer driver. On my system I have these claims in my setup.folk
Claim tm-l90 is the default printer
Claim tm-l90 is a receipt printer
Claim tm-l90 is at <IP_ADDRESS>
Claim tm-l90 has tag geometry {tagSize 30mm top 24mm right 28.5mm left 14mm bottom 75.5mm}

I tried to use a nested When initially, but I wasn't able to do an early return and it was behaving weird if the printer claims were retracted/reclaimed e.g. if they were on a printed program that went missing and came back.

@osnr How do we want to handle previously printed programs? We currently have code that throws an error when you try to reprint an existing program.

@osnr How do we want to handle previously printed programs? We currently have code that throws an error when you try to reprint an existing program.

Empirically, I think that safeguard is pretty important (it's easy to end up in terrible situations where you accidentally stomp your old programs and your printed programs are inaccurate). I guess the useful application of this is if you want to fully replace an old program, both source and layout? But then you should just delete the files by hand, maybe.

I think the previously printed program safeguard is the last thing I want to resolve before merging this.

it's easy to end up in terrible situations where you accidentally stomp your old programs and your printed programs are inaccurate

I'm not sure I follow. If you have an existing program open in web-editor, there's nothing that prevents stomping old programs (code). In which case, I feel like someone would actually want the updated code printed.
Maybe the distinction is that we want to see if the code requested to print is different than what exists on disk?

New program
just save and print
Code is the same as $id.folk
Allow to reprint
Code is different from $id.folk
??? maybe throw an error and require a save before printing?


pull request for e2e test at 02/04/2017 07:15:06

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


Update Ubuntu version to 18.04

The images that do not rely on an old glibc being available are updated to the new LTS version.

HI Thanks for the PR.
We had a similar PR that changed from 12.04 to 14.04 but wasn't merged yet (#164). The comment explains it. I wonder if this PR is affected by the same issue.

It is not affected as it only touches the targets that do not build binaries that use glibc symbols.

Closing as this is starving and now partially applied in another PR. I will not put any work in this anymore.


stm32g4: adc3: set resolutions & sampling-times

bring back adc3 with latest "st,stm32-adc" required properties: resolutions & sampling-times

@gautierg-st sure :)


Add script to automate production deployment

This is in reference to issue #248 -- it foregoes the env_prod.list file since docker-compose seems to have issues with parsing in the environment variables and instead uses a BASH script that takes input to replace the variables in a templated docker-prod.yml file. This is more of a proof-of-concept than something I expect to be production ready.

Taking a better look at this I really like the idea. My only problem with is the lack of use of the env file. IMO I think we need to find a way to use the file as it's much easier to maintain and would make deploying simpler.

Hi Ryan,
Sorry for the delayed response. I just ran a test to grab the environment variable from within the container using the env file and it appears to be set correctly there:
# python
Python 2.7.13 (default, Jul 24 2017, 20:13:18)
[GCC 4.9.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import os
>>> print(os.environ.get('ALLOWED_HOST'))
'food.neverlocate.me'
>>>

but the settings.py file still does not contain the host in the allowed hosts list. I can modify the script to work with an ENV file since I agree that it would be the best way to go about this.

Using a quick test Python script I do see that the quotes may be an issue, but it still doesn't explain why settings.py isn't getting the correct variable:
 python test.py
ALLOWED_HOSTS before append: ['localhost', '<IP_ADDRESS>', 'node']
env_allowed_host: 'food.neverlocate.me'
ALLOWED_HOSTS after append: ['localhost', '<IP_ADDRESS>', 'node', "'food.neverlocate.me'"]
env_allowed_host: 'food.neverlocate.me'

test.py
import os

ALLOWED_HOSTS = ['localhost', '<IP_ADDRESS>', 'node']

env_allowed_host = os.environ.get('ALLOWED_HOST', None)
if env_allowed_host is not None:
    print 'ALLOWED_HOSTS before append: %s' % (ALLOWED_HOSTS)
    print 'env_allowed_host: %s' % (env_allowed_host)
    ALLOWED_HOSTS.append(env_allowed_host)
    print 'ALLOWED_HOSTS after append: %s'  % (ALLOWED_HOSTS)
    print 'env_allowed_host: %s' % (env_allowed_host)

The settings file shouldn't have anything to do with the image being built vs using a pre-built image. When the container first starts up and tries to either run gunicorn or the django dev server, it will load the settings files and read the environment vars.
If you try and change the environment vars after the container has started then the settings files (and the django app) won't have those changes. You need to restart the containers if you do make a change to the environment file.
You can add something like this to the settings file to see what it's getting when it's booting the app.
ALLOWED_HOSTS = ['localhost', '<IP_ADDRESS>', 'node']

print("allowed Host list:")
print(ALLOWED_HOSTS)

print("allowed Host ENV:")
print(os.environ.get('ALLOWED_HOST', None))

env_allowed_host = os.environ.get('ALLOWED_HOST', None)
if env_allowed_host is not None:
    ALLOWED_HOSTS.append(env_allowed_host)

print("allowed Host list after append:")
print(ALLOWED_HOSTS)

Then restart you docker-compose with:
Note: we are printing the all logging to stdout here.
docker-compose stop
docker-compose up

You should see something like this:
api_1   | allowed Host list:
api_1   | ['localhost', '<IP_ADDRESS>', 'node']
api_1   | allowed Host ENV:
api_1   | ryannoelk.ocm
api_1   | allowed Host list after append:
api_1   | ['localhost', '<IP_ADDRESS>', 'node', 'ryannoelk.ocm']

Closing this PR for now. I have added a script to start the containers and the containers will now automatically create static content and apply DB migrations.


feat: response interceptor

implements #515

Coverage decreased (-2.9%) to 84.444% when pulling 26064a155057e664a7cd6933eb1496c20cda9cf0 on response-interceptor into 0381fdfbc5976ad8a3632fd92b7406047f1c6748 on master.


Editing task configuration - knowledge bases forgotten

As revealed on Friday, knowledge bases are not always properly selected when editing task configuration. So sometimes it happens that after opening the conf, you have to re-select knowledge bases again

I am not sure whether the bug persists, but I doubt it - the error was caused by a race condition (2 calls for reentering digest cycle), which has been removed. If the selected bases are not loaded, it may be you have not waited enough (< 5 secs should be enough, however).
BTW, correction of the bug tested in Firefox, Chrome.

@istvan-satmari @tomas-knap It works for me now. Closing.


cc-wrapper: omit adding -D_FORTIFY_SOURCE if it would cause redefinition

Description of changes
See discussion in #224822 regarding annoying redefinition warnings it caused. This is the simplest of my proposed options.
This shouldn't actually change behaviour as the way hardeningCFlags are currently prepended to supplied params, the caller-supplied value will win anyway, but in omitting our definition, we'll avoid annoying (and potentially fatal) warnings.
Tested against #217390 successfully, nixos x86_64.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

I'm not too excited about this.  Trying to parse the flags that upstream's build process passes to the wrapper, and then change our behavior based on that...
It's a long established principle that conflicting C compiler flags are okay, and later flags supersede earlier flags.  Nixpkgs has always exploited and depended upon this, extensively.
It sounds like all this extra complexity is simply because:

annoying redefinition warnings it caused

Frankly I think the complexity this adds to cc-wrapper is infinitely more annoying.
Better solutions would be:

If a package unilaterally sets the hardening flags, get it to not do that (possibly by upstreaming a patch creating an option that says "don't set these flags for me").
Turn off the warning.

I think 2 is a good idea in any case.  We use and rely upon the ability to pass flags that override other flags.  It's not a defect; we don't need to be warned when this happens.

FWIW we already inspect params in add-hardening.sh for the -pie option, and in cc-wrapper.sh we quite extensively parse the params and change our behaviour based on it.
As for it "being annoying" it's a bit of an understatement - there are some packages where it doubles the size of the build log.
But failing that, a more comprehensive solution may be to move -D_FORTIFY_SOURCE additions to a suffixed hardeningCFlags-alike, though at that point we're overriding the build system's choice. Perhaps that's fine, but there's bound to be at least a few packages that causes problems with.
Anyway, let's keep more general discussion of other possible solutions on #224822

I think I would generally support overriding upstream for hardening, especially since I expect most of these in practice are opting in to hardening rather than out and we can hardeningDisable for the rest.

I think one of my concerns is how few things cc-wrapper currently adds to the end of the command line. The general pattern is to let the command-line "win".

#246244 was merged instead


Lowercase me

Lowercase me pleez. 👾

@guardrex,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


CB-10985 Android sets type to -1 for ims

Added a corresponding test
Jira issue

Well that might fix the -1 issue. But the android version of this plugin behaves very differently from the ios Version.
The iOS Version returns the custom label (if there is one set) for the type. Android simply returns "Custom".
I don't think that's intended.

I've openend an Issue on that: https://issues.apache.org/jira/browse/CB-11028


improper encoding

Metro2 Version: moov/metro2:latest
What were you trying to do?
Convert Json to Metro2 using API call
What did you expect to see?
Converted response text in metro 2 format
What did you see?
Got the converted response but the encoding seems to be wrong. please find the attached screenshot for reference.
How can we reproduce the problem?
Run docker container using docker for windows.
Execute /convert API passing sample data.
Read the response and save in a file.
check file encoding.

how do you know this encoding is broken? isn't the resulting file in binary format so it won't even render properly in many text editors?

This sounds similar to https://github.com/moov-io/imagecashletter/issues/227. Can we get more information about your environment / request / response?

Metro2 segments have 2 types character and packed
character segment is readable. but packed is not readable, looks like invalid encoding
Global function NewFile(string) is to specify segment type
convert function is using segment type of input file
New params added into convert command to avoid this problem
metro convert --help
Usage:
convert [output] [flags]
Flags:
--format string   format of metro file(required) (default "json")
-g, --generate        generate trailer record
-h, --help            help for convert
-n, --newline         has new line (will use new line between records)
--type string     file type (character or packed)
Global Flags:
--input string   input file (default is $PWD/metro.json)


Missing urlSync documentation

No mention of the urlSync in the documentation :/

Oups. Fixing that!

You can submit the fix to the master branch directly @bobylito with "hotfix" in the body. So it will be updated, automatically :)


what's time for react native android support load remote-js instead of devPcHelper, v0.12? thks

@yipengmu Thanks for the interest.
I'll let @mkonicek comment on future plans, however we are more than happy to accept pull requests :)

What is devPcHelper?
There's a possibly related PR, see https://github.com/facebook/react-native/pull/3189


[BACKPORT/24.1.x] Multiple backports for 24.1.1

Backports the following:

#5785
#5804
#5813

Why not just releasing unbreaking release 24.2

Sure, we could do that as well. I would actually like 24.2 more. Let's do it that way.


How to display the UML source code?

How to display the UML source code?

What do you mean? Using Xcode extension will show UML diagram in browser with respective PlantUML script
https://user-images.githubusercontent.com/4176826/224826293-2b9e7747-ebe3-46d5-a33c-f9e88452a702.mov

Generate the source file to the local or selected directory

Some relationships are very complex, such as complex class inheritance relationships, resulting in large data or large drawing. If this optimization option can be provided, it may reduce the drawing of beams or drawing area or drawing size, and the description may not be very appropriate.

So the problem is that the diagram is too large to be rendered in the browser?
Try to limit the information, e.g. show elements/members only for certain access level

or merge extensions instead of showing them separately in the diagram

If this is not helpful or not desired then please use the command-line tool SwiftPlantUML and read this

In other words, there are a large number of class data structures (such as hundreds, thousands, tens of thousands, and even more) in the current actual scenario. Through Http requests, one request may have large data, and the other may return large results.
Don't know whether you can directly add the option of generating local UML source files and directly convert them locally?

In other words, there are a large number of class data structures (such as hundreds, thousands, tens of thousands, and even more) in the current actual scenario.

You are talking about evaluating many files. Then please use the command-line tool SwiftPlantUML

Don't know whether you can directly add the option of generating local UML source files and directly convert them locally?

This is possible with command-line tool SwiftPlantUML and using PlantUML to generate image locally. See #large-diagrams for more info.


refactoring extract_geo_features

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 16.12903% with 26 lines in your changes missing coverage. Please review.

Project coverage is 52.74%. Comparing base (400af13) to head (6817221).
Report is 98 commits behind head on dev.

Files with missing lines
Patch %
Lines

anyway/parsers/location_extraction.py
17.24%
24 Missing :warning:

anyway/parsers/news_flash.py
0.00%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##              dev    #2704      +/-   ##
==========================================
- Coverage   53.22%   52.74%   -0.49%
==========================================
  Files         119      122       +3
  Lines        9924    10079     +155
==========================================
+ Hits         5282     5316      +34
- Misses       4642     4763     +121

Flag
Coverage Δ

unittests
52.74% <16.12%> (-0.49%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


I won't be able to return a value.

I have a problem.
I won't be able to return a value.
Why... How do I solve?
func getQuests(category: NSString, count: Int) -> NSArray {
        var quests = NSArray()

        Alamofire.request(.GET, apiUrlString, parameters: ["category": category, "count": count])
            .responseJSON { (request, response, json, error) in
                dispatch_async(dispatch_get_main_queue(), {
                    quests = json as NSArray
                })
        }

        println(quests)  #=> ()

        return quests
    }

I want you to help me.

Please post this question on StackOverflow. I will answer it there.

@tkrajacic
http://stackoverflow.com/questions/28564801/i-wont-be-able-to-return-a-value-with-alamofire-in-swift
Thank you.

Thanks, @tkrajacic.


Update RxSwift dependency to 4.0.0-beta.0

Resolves #1303

Is there any reason that Moya doesn't have .swift-version file?

Also, should we change the target of this PR to 10.0.0-dev as RxSwift 4 is not stable yet?

@pedrovereza, not sure. Please change the base branch before being merged if needed :)

@pedrovereza Updated Package.swift :)

On the branch: we should, so I changed it to the dev branch 👍

@BasThomas, thanks! I just rebased 10.0.0-dev branch and force-pushed.

Build Error:
Resolving dependencies of Podfile
[!] Due to the previous naïve CocoaPods resolver, you were using a pre-release version of RxSwift, without explicitly asking for a pre-release version, which now leads to a conflict.
Please decide to either use that pre-release version by adding the version requirement to your Podfile (e.g. pod 'RxSwift', '= 4.0.0-alpha.1') or revert to a stable version by running pod update RxSwift.

Seems like the Podfile.lock on the Demo project needs to be updated

Codecov Report

Merging #1306 into 10.0.0-dev will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           10.0.0-dev   #1306   +/-   ##
==========================================
  Coverage          83%     83%
==========================================
  Files              24      24
  Lines             753     753
==========================================
  Hits              625     625
  Misses            128     128

Continue to review full report at Codecov.

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

@pedrovereza Can be it approved now?

Because I had to rebase 10.0.0-dev, I resolved conflicts here as well. But then I figured that we probably don't want this merge and rebase would be more preferable. Would you be able to remove my merge commit and rebase this one, @devxoul? Sorry for the trouble.

SwiftLint found issues
Warnings

File
Line
Reason

Package.swift
9
Collection literals should not have trailing commas.

Package.swift
15
Collection literals should not have trailing commas.

  Generated by :no_entry_sign: Danger

Thanks again, @devxoul! 🎉


Provide Windows Batch task

Same handling as for the Powershell task provide a Batch task running .cmd or .bat files.

Done.


Random bfs tree

This PR adds a function (and testing) for constructing a Breadth First Search tree for a graph but in a random manner.
The tree stems from a source vertex s. The edges from s to its neighbors are guaranteed to be in the tree but remaining edges in the tree will be random.
This will be useful for ITensorNetworks.jl as it adds the ability to orthogonalise a network along different trees.

Codecov Report

Merging #32 (69da830) into main (1d125b3) will increase coverage by 0.49%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main      #32      +/-   ##
==========================================
+ Coverage   78.89%   79.38%   +0.49%
==========================================
  Files          19       19
  Lines         796      815      +19
==========================================
+ Hits          628      647      +19
  Misses        168      168

Impacted Files
Coverage Δ

src/Graphs/abstractgraph.jl
64.39% <100.00%> (+3.93%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Thanks!


ls with Pattern

Is there a simple way to run ls with a glob pattern, e.g. analogous to shell version of
ls *.txt

or do you have to use grep, ls, and convert from FilePath to Text and back?

Well...in a hurry you can always do inshell "ls *.txt" empty".

@reckbo This is very similar to find, except just searching only the current directory.  You can just take the implementation of find:
-- | Search a directory recursively for all files matching the given `Pattern`
find :: Pattern a -> FilePath -> Shell FilePath
find pattern dir = do
    path <- lstree dir
    Right txt <- return (Filesystem.toText path)
    _:_       <- return (match pattern txt)
    return path

... and modify it to use ls instead of lstree, so the final solution is something like this:
files :: Shell FilePath
files = do
    here <- pwd
    path <- ls here
    Right txt <- return (Filesystem.toText path)
    _:_       <- return (match (suffix ".txt") txt)
    return path

This would be simplified further when I'm done reviewing #180 because then the solution would just be:
files = do
    here <- pwd
    onFiles (grep (suffix ".txt")) (ls here)

Thanks!
Looking forward to onFiles, that's the type of function I was originally looking for.

I want to do the same thing, except paths would be read from an external file. I could do the following:
pth <- select ["{,**/}*.hs", ...]
stdout $ inshell ("echo " + pth) Turtle.empty

...but this brings up shell injection dangers. I'm not worried about malicious users, but another person may.

@joelmccracken: If paths are read from an external file, you could do:
example = do
    line <- input yourFile
    let file = fromText (lineToText line)
    ...

It's not clear how this relates to globbing, though

Say I had a config file with a list of directories. This file is user created, so the user probably doesn't want to type their home directory over and over again.
The file  would look something like this:
git ~/Projects/*
inbox ~/Inbox
inbox ~/Desktop
inbox ~/Downloads

I want to expand ~ to the user's home directory, and expand * to be everything below ~/Projects. I could parse and expand myself, but it seems like there might be a better way.

Probably the simplest approach is to use shell, which runs the text command line through a shell interpreter, including glob expansion.  It would look something like this:
--  I haven't type-checked or ran this code

example :: Shell FilePath
example = do
    line <- input "yourFile.txt"
    case Data.Text.words (lineToText line) of
        [_, glob] -> do
            line' <- inshell ("ls -1d " <> glob) empty
            return (fromText (lineToText line'))
        _ -> die "Malformed line"

Another approach is to use the Haskell Glob library for doing glob expansion natively within Haskell without going through a shell interpreter

I wish the solution posted above stood out more. It also requires an update changing grep for grepText. So, for posterity:
-- files ~= ls *.txt
--
files = do
    here <- pwd
    onFiles (grepText (suffix ".txt")) (ls here)


Unload render engine when the sensors system exists

🦟 Bug fix
Fixes https://github.com/gazebosim/gz-sim/issues/1410
Depends on:

https://github.com/gazebosim/gz-sensors/pull/340
https://github.com/gazebosim/gz-rendering/pull/840

Summary
The render engine is never destroyed / unloaded when the server shuts down. This leads to issues such as memory leak and not being able to relaunch the server with the sensors system, e.g. as seen in #1410, rendering tests n gz-sim can not be run one after another in the same process.
This PR adds a function in RenderUtil to destroy the scene and unload the engine.
To test:
Run the PERFORMANCE_sensors_system test that repeatedly launches the server with the sensors system.
Note that to run the tests, you'll need the above PRs in gz-rendering and gz-sensors otherwise gz will crash.
Checklist

[x] Signed all commits for DCO
[x] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

I think this is still failing PERFORMANCE_sensors_system on the buildfarm, so it may need another look.

I think this is still failing PERFORMANCE_sensors_system on the buildfarm, so it may need another look.

removed bad ifdef logic in e26e577, which should hopefully fix it.

ubuntu build fixed


[Feat] ability to run linter in pre-commit / pre-push hook

in the absence of a build step that can fail if there are type errors, it would be useful to be able to run the linter in a pre-commit / pre-push hook that can block the commit / push when errors are found.
(this is not a super important feature tho, definitely a nice to have / low priority)

hmmm, i actually wonder if it isn't worth focusing efforts on the linter side of things because it has been brought to my attention that i could use stylelint for highlighting unknown variables instead, and it integrates well with CI.

To my knowledge, users usually use a library to add git hooks or integration some flows in CI pipelines.
This project is purely an extension and there's no node package for the same.
Not sure how you wanted to use this extension as a git hook or in the CI pipeline.
Do enlighten me if I am missing something here, where extensions can be used in CI pipelines?

Do enlighten me if I am missing something here, where extensions can be used in CI pipelines?

ah sorry, i wasn't proposing the extension is used in CI pipelines because as you say, that's not possible, but also didn't want to propose a solution here in case you had good ideas for handling this that i hadn't considered.
my thinking was that the extension could read a configuration file that can also be read by a cli based linter (to avoid configuration in two separate places) but given our recent conversations and change of direction, i am going to close this :)


new mers figure

Someone complained to me about Figure S5 in our paper from last year. I have tried to make a new design of the figure which will display better in various different programs or when it is printed. The new figure function is also in a pull request at the following location: https://github.com/SABS-R3-Epidemiology/branchpro/pull/234
If one of you @I-Bouros or @FarmHJ has the chance to approve these that would be really helpful. Thank you.


Adding an improved documentation base and (eventually) readthedocs support.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 84.75%. Comparing base (07140c1) to head (0f1944c).
Report is 3 commits behind head on dev.

Additional details and impacted files
@@            Coverage Diff             @@
##              dev      #42      +/-   ##
==========================================
- Coverage   84.85%   84.75%   -0.10%
==========================================
  Files          17       18       +1
  Lines        1096     1102       +6
==========================================
+ Hits          930      934       +4
- Misses        166      168       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[cli] Make validating checksums easier

There is a flag in the drone-github-release plugin to flatten the paths in the checksum file that would enable users to just do a
$ sha256sum --check sha256sum.txt --ignore-missing
rancher-linux-amd64-v2.4.11.tar.xz: OK

(This was after editing the file to remove the dist/... paths)

Available to test on v2.6.3-rc1

I just tested this and it seems that the following fails with the 2.6.3 RC2 release on Github.
sha256sum --check sha256sum.txt --ignore-missing rancher-images.txt
sha256sum: sha256sum.txt: no file was verified
sha256sum: rancher-images.txt: no properly formatted checksum lines found

This file doesn't appear to be flattened and still includes the bin prefix.
@brendarearden

@phillipsj, this change is for the rancher/cli repo, not the main rancher/rancher. The issue is in this project on purpose, but the PR above is in the CLI repo. Also, looks like there has already been an v2.6.0 RC-2 release of the CLI, and the paths are properly modified in the checksum file.
https://github.com/rancher/cli/releases/tag/v2.6.0-rc2

@genexpr okay, I will test that then.

This has passed dev validation.
sha256sum sha256sum.txt --check --ignore-missing rancher-windows-386-v2.6.0-rc2.zip
rancher-windows-386-v2.6.0-rc2.zip: OK


Opensource : 6.2 Compare npm vs yarn

Opensource : 6.2 Compare npm vs yarn
Fixes #2965

Compare npm vs yarn📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Open Source 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] Java#Script
[ ] ME#RN
[ ] Machine #Learning
[x] Open Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[ ] I follow Contributing Guidelines & Code of conduct of this project.
[ ] I have performed a self-review of my own code or work.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] My changes generates no new warnings.
[ ] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@Aryamanz29 when will my pull request merged?


Add missing splice() to FieldArray's fields prop

The FieldArray's fields prop was missing the splice() function. This was once discussed in #2870.

Me too. For bonus points: #3244 :).


Fix blue_30 RGB values

There's a slightly different variant of the color that slipped into some mockups. This is the correct value confirmed w/ Cecile.
:eyeglasses: @keybase/react-hackers

:mag_right: No visual changes found as a result of these commits.

👍


Is NVIDIA Jetson SoCs in nvjpeg-python Roadmap

Hello,
I've had a great experience with nvjpeg-python and have been wondering if there are plans to port it to the NVIDIA Jetson SoC platforms that are based on aarch64 and tegra kernel.

Nvjpeg in cuda is not similar with nvjpeg in L4T Multimedia API.
I will try to implement it with L4T Multimedia API.

Hello,
I've had a great experience with nvjpeg-python and have been wondering if there are plans to port it to the NVIDIA Jetson SoC platforms that are based on aarch64 and tegra kernel.

The last version 0.0.12 has been release.
I have tested in NVIDIA Jetson AGX Xavier.


added transaction generation for orphan network spans

#137

This PR also fixes stale active spans remaining in the shared context for View Controller instrumentation.


Slice data updates from QP study

QP feedback:

Slice and show expanded slice controls by default
Move refresh button from editor title menu to be next to breadcrumb
Fix dropdown styles
Show a placeholder slice in the input box to guide users

[ ] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[ ] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).

Can we see a screenshot of what this looks like now.

Current screenshot (Jill and Jeffrey have signed off):

New placement:


Fix: Update torch.load to use weights_only=True to prevent security w…

Fix: Update torch.load to use weights_only=True to prevent security warning
Changes Made:
In this pull request, I updated the torch.load function call to use weights_only=True in order to prevent a security warning related to the unpickling process.
Code Change:
- checkpoint = torch.load(fp, map_location=device)
+ checkpoint = torch.load(fp, map_location=device, weights_only=True)

For anyone else with this issue, I've been doing this for now:
import functools
whisper.torch.load = functools.partial(whisper.torch.load, weights_only=True)


no return value

Hello
Excuse me！i made a demo according to the code of example/example1.php，bug why is there no return value for running the loop whit the `parallel-forhttps://github.com/hironobu-s/parallel-for/blob/master/example/example1.php

i found the cause of the Issues，
Because i userd the old version code。


update swift-markdown from 5.6 to 5.9

Chumber!! 👋 Thanks!! 😜

No probs! I also just added you as a collaborator so you can tweak things as needed.


Using multiple FsiEvaluationSessions in the same process causes thread-safety issues

While I understand that an FsiEvaluationSession is by itself not thread-safe, there doesn't seem to be any documentation that suggests that running multiple sessions within the same process space should conflict.
However, when I run multiple sessions in parallel, under high stress, some evaluations fail with the following exception:
Message: System.Exception : Error creating evaluation session: System.InvalidOperationException: Operations that change non-concurrent collections must have exclusive access. A concurrent update was performed on this collection and corrupted its state. The collection's state is no longer correct.
   at System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
   at System.Collections.Generic.Dictionary`2.TryGetValue(TKey key, TValue& value)
   at FSharp.Compiler.AbstractIL.Internal.Library.Tables.memoize@1051.Invoke(a x)
   at FSharp.Compiler.AbstractIL.ILBinaryReader.typeDefReader@1784.Invoke(Int32 idx)
   at System.Threading.LazyInitializer.EnsureInitializedCore[T](T& target, Func`1 valueFactory)
   at FSharp.Compiler.Import.entities@482-2.Invoke(Tuple`2 tupledArg)
   at FSharp.Compiler.Import.multisetDiscriminateAndMap@425.GenerateNext(IEnumerable`1& next)
   at Microsoft.FSharp.Core.CompilerServices.GeneratedSequenceBase`1.MoveNextImpl()
   at Microsoft.FSharp.Collections.SeqModule.ToList[T](IEnumerable`1 source)
   at FSharp.Compiler.Import.multisetDiscriminateAndMap[Key,Value,a](FSharpFunc`2 nodef, FSharpFunc`2 tipf, FSharpList`1 items)
   at FSharp.Compiler.Import.ImportILTypeDefList[a](FSharpFunc`2 amap, range m, CompilationPath cpath, FSharpList`1 enc, FSharpList`1 items)
   at FSharp.Compiler.Import.modty@480.Invoke(Unit unitVar)
   at System.Lazy`1.ViaFactory(LazyThreadSafetyMode mode)
   at System.Lazy`1.ExecutionAndPublication(LazyHelper executionAndPublication, Boolean useDefaultConstructor)
   at System.Lazy`1.CreateValue()
   at FSharp.Compiler.CompileOps.TcImports.ccuHasType(CcuThunk ccu, FSharpList`1 nsname, String tname)
   at Microsoft.FSharp.Collections.ArrayModule.loop@739-41[T](FSharpFunc`2 predicate, T[] array, Int32 i)
   at FSharp.Compiler.TcGlobals.TcGlobals.findSysTypeCcu(FSharpList`1 path, String typeName)
   at FSharp.Compiler.TcGlobals.TcGlobals.findSysTyconRef(FSharpList`1 path, String nm)
   at FSharp.Compiler.TcGlobals.TcGlobals..ctor(Boolean compilingFslib, ILGlobals ilg, CcuThunk fslibCcu, String directoryToResolveRelativePaths, Boolean mlCompatibility, Boolean isInteractive, FSharpFunc`2 tryFindSysTypeCcu, Boolean emitDebugInfoInQuotations, Boolean noDebugData)
   at FSharp.Compiler.CompileOps.BuildFrameworkTcImports@4752-2.Invoke(Tuple`2 _arg7)
   at FSharp.Compiler.AbstractIL.Internal.Library.CancellableModule.bind@709.Invoke(CancellationToken ct)
   at FSharp.Compiler.AbstractIL.Internal.Library.CancellableModule.bind@709.Invoke(CancellationToken ct)
   at FSharp.Compiler.AbstractIL.Internal.Library.CancellableModule.bind@709.Invoke(CancellationToken ct)
   at FSharp.Compiler.AbstractIL.Internal.Library.CancellableModule.runWithoutCancellation[a](Cancellable`1 comp)
   at FSharp.Compiler.Interactive.Shell.FsiEvaluationSession..ctor(FsiEvaluationSessionHostConfig fsi, String[] argv, TextReader inReader, TextWriter outWriter, TextWriter errorWriter, Boolean fsiCollectible, FSharpOption`1 legacyReferenceResolver)

Repro steps

Create  5 threads, that each create an FsiEvaluationSession:

let fsiConfig = FsiEvaluationSession.GetDefaultConfiguration()
let sbOut = new StringBuilder()
let sbErr = new StringBuilder()
let inStream = new StringReader("")
let outStream = new StringWriter(sbOut)
let errStream = new StringWriter(sbErr)
let fsiSession = FsiEvaluationSession.Create(fsiConfig, allArgs, inStream, outStream, errStream, collectible = true)

Evaluate any expression that deals with types (e.g. {A = 5; B = "Foo"}) a few dozen times on each thread
Dispose off the session, and go to #1, and re-create the session, and keep repeating

Expected behavior
The evaluation should work without issues.
Actual behavior
You might encounter an arbitrary crash, with the above stack trace, usually within the first few hundred evaluations.
Known workarounds
A global lock is needed around all FSI API calls, both creation and evaluation. One thing to note is even thought the stack trace seems to originate from the constructor of an FsiEvaluationSession, due to a lazy being part of the stack trace, the exception could get thrown as part of regular evaluation.
Related information
Provide any related information

Operating system - Windows
Branch - master, FSharp.Compiler.Services 27.0.1, FSharp.Core 4.5.4
.NET Runtime, CoreCLR or Mono Version - .NET Core 2.1
Editing Tools (e.g. Visual Studio Version) - VS 2017 15.9.4

I had a similar question.
https://github.com/fsharp/FSharp.Compiler.Service/issues/798
I think its not recommended

Ah, thanks @goswinr, I clearly need to improve my searching skills :)
I'll close this as a duplicate in this case.


subnet that uses a /27 or /28 vs subnet of /27 or larger

Some configurations require more IP addresses than others. We recommend that you create a gateway subnet that uses a /27 or /28.
contradicts
https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpn-gateway-settings
While you can create a gateway subnet as small as /29, we recommend that you create a gateway subnet of /27 or larger (/27, /26 etc.)

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

ID: 59e72010-dab4-54d9-1409-c95b0ce60824
Version Independent ID: 0da5450c-6181-1c27-93c0-b0c698d2d598
Content: Configure P2S server configuration - certificate authentication: Azure portal - Azure VPN Gateway
Content Source: articles/vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal.md
Service: vpn-gateway
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

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

@inknochen Thanks again for bringing this to our attention.
@cherylmc Please update the document to mention that the minimum subnet size required is /27 or more for Zonal and Zone-Redundant gateways except for a Basic SKU, where it can be /29.

Fixing. Thanks! #please-close


Fix metric rule pattern regex

Description
The . requires escaping throughout the pattern string if it is intended to represent a . literal. The only reason its working right now is because its surrounded by specific patterns, so the match all . regex is only matching actual . character.
More discussion around this issue (with an example where it breaks) here.
This PR tries to fix this by escaping all . literals.
It also replaces *? with * for custom metric rules as the surrounding pattern matching is well defined.
labels
bugfix refactor

It also replaces *? with * for custom metric rules as the surrounding pattern matching is well defined.

Can you please elaborate more on this? Maybe you can use an example to explain why it is needed?

It also replaces *? with * for custom metric rules as the surrounding pattern matching is well defined.

Can you please elaborate more on this? Maybe you can use an example to explain why it is needed?

@zhtaoxiang
As @Jackie-Jiang pointed out in point 3 here,
Let's say a metric is of the format somePrefix.tableName.someMetric
Case 1 using *? :
pattern = somePrefix\\.([^.]*?)\\.someMetric
The parser will do conservative iterations of
1 . somePrefix.t -> fails as . is not encountered after it
2 . somePrefix.ta -> fails as . is not encountered after it
.
.
n . somePrefix.tableName -> success as . is encountered after it
Case 1 using * :
pattern = somePrefix\\.([^.]*)\\.someMetric
The parser will match somePrefix.tableName in the first iteration itself as its greedy and only breaks at the . in .someMetric

It also replaces *? with * for custom metric rules as the surrounding pattern matching is well defined.

Can you please elaborate more on this? Maybe you can use an example to explain why it is needed?

@zhtaoxiang As @Jackie-Jiang pointed out in point 3 here, Let's say a metric is of the format somePrefix.tableName.someMetric Case 1 using *? : pattern = somePrefix\\.([^.]*?)\\.someMetric The parser will do conservative iterations of
1 . somePrefix.t -> fails as . is not encountered after it 2 . somePrefix.ta -> fails as . is not encountered after it . . n . somePrefix.tableName -> success as . is encountered after it
Case 1 using * : pattern = somePrefix\\.([^.]*)\\.someMetric The parser will match somePrefix.tableName in the first iteration itself as its greedy and only breaks at the . in .someMetric

I get the log for *?. For Case 1 using *, if it's greedy, I feel * should match tableName.someMetric first, then tableName.someMetri, then tableName.someMetr.
If my understanding is correct, isn't greedy matching slower? Because in most cases, the suffix will be much longer than the prefix, so greedy is slower. For example, if the pattern is somePrefix\\.([^.]*?)\\.someMetric\\.suffix1\\.suffix2\\.suffix3, and the metric is somePrefix.sometable.someMetric.suffix1.suffix2.suffix3, we need to try 11 times; if the pattern is somePrefix\\.([^.]*)\\.someMetric\\.suffix1\\.suffix2\\.suffix3, we need to try 25 times.


bottomItem

If there are 5 tags, the title can only display up to 3 words.

Yeah the titles in bottom navigation bar according to google design guideline should be small.
I will have a look at that, Can you share the titles you are setting ?

Soory @kangshaopeng , Long Titles can't be displayed by the BottomNavigationBar.


TypeError: Cannot create property 'enabled' on boolean 'false'

Describe the bug
I can't run vitest after upgrading from 0.29.2 -> 0.33.0
it shows following error
TypeError: Cannot create property 'enabled' on boolean 'false'  ELIFECYCLE  Command failed with exit code 1.

"@vitest/ui": "0.33.0"
"vite": "4.4.7"
"vitest": "0.33.0"
"jsdom": "21.1.0"
Reproduction
upgrade from 0.29.2 to 0.33.0
System Info
MacOS Catalina 10.15.4, Chrome
pnpm 7.29.0
npm 6.14.15
node v14.18.3

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

i resolved
/spa/public


Support arbitrary painting in scene

Capturing ongoing discussion. Similar to tilt brush, study how to integrate arbitrary painting in an ARENA scene.

Does each brush stroke map to an individual object?
Do we need additional support for VR controllers?
https://aframe.io/examples/showcase/a-painter/
Run discrete polygon test program to see where we start to hit performance issues.

https://openbrush.itch.io/openbrush


unexpected response 'RSP.T_BD'

Hello,
I try to send data (normal .H) with send_file, binary_mode=False on a "iTNC530 60642002 SP10" (the same code works on a TNC640)
could not send data, received unexpected response 'RSP.T_BD
The Heidenhan Doc says "Blockübertragungsfehler" (sorry German)
Die Fehlernummern 100 - 199 sind Blockübertragungsabbruchfehler (T_BD)
con.last_error() repeats also an Error :(
Traceback (most recent call last):
  File "h:\python\pyLSV2\pyLSV2 test Datei.py", line 28, in <module>
    con.last_error()
TypeError: 'LSV2Error' object is not callable

Sorry for the stupid question, but how can I easily get the logs that are relevant to you 🙈
last error:
ic| con.last_error.e_code: <LSV2StatusCode.T_ER_NON: -1>
ic| con.last_error.e_type: -1
ic| con.last_error.__doc__: 'data class for LSV2 errors'
ic| con.last_error.__module__: 'pyLSV2.dat_cls'

I was able to reproduce the exact same error that you are seeing. I actually found a general problem in reporting of error messages but it is not the source of what we are seeing here.
Going by the log messages it seems like two different situations:

Testing non binary file transfer with a programing station for iTNC530 340494 08 SP2 shows similar results as your test with iTNC530 606420 02 SP10. After finding the problem mentioned above I get a more detailed error message "error in program block". If I strip everything from the nc program besides the comment lines the transfer works as expected. It seems like the control doesn't like something about the syntax in the NC program which is why it is rejected.

The log from your test with iTNC530 340422 13 is a bit strange. The time out error indicates some hang up while waiting for a response from the control. I don't have access to a machine with such an old software version to do some testing. The oldest programming station I am able to find is iTNC 530 340494 02 but I haven't been able to get it working on Windows 10. I will set up a VM with an old version of Windows but this might take some time. Maybe the source of the problem in this case is the same as in the other case but the control does not report the error and just stops responding altogether.

Can you please check if the file transfer again this either a minimal NC program with only line blocks? Or you could first download a program from the control and upload it with a different name.

Thank you,
for iTNC530 606420:
Then I made a minimal program with only linear blocks and was able to narrow down the error. I think it has to do with the length of the program
this works:
0  BEGIN PGM test MM
1  L  X+1  Y+2  Z+3
2  L  X+1  Y+2  Z+3
3  L  X+1  Y+2  Z+3
4  L  X+1  Y+2  Z+3
5  L  X+1  Y+2  Z+3
6  L  X+1  Y+2  Z+3
7  L  X+1  Y+2  Z+3
8  L  X+1  Y+2  Z+3
9  L  X+1  Y+2  Z+3
10 L  X+1  Y+2  Z+3
11 L  X+1  Y+2  Z+3
12 L  X+1  Y+2  Z+3
13 L  X+1  Y+2  Z+3
14 L  X+1  Y+2  Z+3
15 L  X+1  Y+2  Z+3
16 L  X+1  Y+2  Z+3
17 L  X+1  Y+2  Z+3
18 L  X+1  Y+2  Z+3
19 L  X+1  Y+2  Z+3
20 L  X+1  Y+2  Z+3
21 L  X+1  Y+2  Z+3
22 L  X+1  Y+2  Z+3
23 END PGM test MM

and this not (only 1 line more):
0  BEGIN PGM test MM
1  L  X+1  Y+2  Z+3
2  L  X+1  Y+2  Z+3
3  L  X+1  Y+2  Z+3
4  L  X+1  Y+2  Z+3
5  L  X+1  Y+2  Z+3
6  L  X+1  Y+2  Z+3
7  L  X+1  Y+2  Z+3
8  L  X+1  Y+2  Z+3
9  L  X+1  Y+2  Z+3
10 L  X+1  Y+2  Z+3
11 L  X+1  Y+2  Z+3
12 L  X+1  Y+2  Z+3
13 L  X+1  Y+2  Z+3
14 L  X+1  Y+2  Z+3
15 L  X+1  Y+2  Z+3
16 L  X+1  Y+2  Z+3
17 L  X+1  Y+2  Z+3
18 L  X+1  Y+2  Z+3
19 L  X+1  Y+2  Z+3
20 L  X+1  Y+2  Z+3
21 L  X+1  Y+2  Z+3
22 L  X+1  Y+2  Z+3
23 L  X+1  Y+2  Z+3
24 END PGM test MM

log:
DEBUG:LSV2 TCP:Socket successfully created, host <IP_ADDRESS> was resolved to IP <IP_ADDRESS>
INFO:LSV2 Client:enabling safe mode. restricting functionality
DEBUG:LSV2 TCP:Connected to host <IP_ADDRESS> at port 19000
DEBUG:LSV2 TCP:telegram to transmit: command CMD.A_LG payload length 8 bytes data: bytearray(b'\x00\x00\x00\x08A_LGINSPECT\x00')
DEBUG:LSV2 TCP:received block of data with length 8
DEBUG:LSV2 Client:expected response received: RSP.T_OK
DEBUG:LSV2 Client:login executed successfully for login INSPECT
DEBUG:LSV2 TCP:telegram to transmit: command CMD.R_VR payload length 1 bytes data: bytearray(b'\x00\x00\x00\x01R_VR\x01')
DEBUG:LSV2 TCP:received block of data with length 16
DEBUG:LSV2 Client:expected response received: RSP.S_VR
DEBUG:LSV2 TCP:telegram to transmit: command CMD.R_VR payload length 1 bytes data: bytearray(b'\x00\x00\x00\x01R_VR\x02')
DEBUG:LSV2 TCP:received block of data with length 23
DEBUG:LSV2 Client:expected response received: RSP.S_VR
DEBUG:LSV2 TCP:telegram to transmit: command CMD.R_VR payload length 1 bytes data: bytearray(b'\x00\x00\x00\x01R_VR\x03')
DEBUG:LSV2 TCP:received block of data with length 25
DEBUG:LSV2 Client:expected response received: RSP.S_VR
DEBUG:LSV2 TCP:telegram to transmit: command CMD.R_VR payload length 1 bytes data: bytearray(b'\x00\x00\x00\x01R_VR\x04')
DEBUG:LSV2 TCP:received block of data with length 186
DEBUG:LSV2 Client:expected response received: RSP.S_VR
DEBUG:LSV2 TCP:telegram to transmit: command CMD.R_VR payload length 1 bytes data: bytearray(b'\x00\x00\x00\x01R_VR\x05')
DEBUG:LSV2 TCP:received block of data with length 21
DEBUG:LSV2 Client:expected response received: RSP.S_VR
DEBUG:LSV2 TCP:telegram to transmit: command CMD.R_VR payload length 1 bytes data: bytearray(b'\x00\x00\x00\x01R_VR\x07')
DEBUG:LSV2 TCP:received block of data with length 10
INFO:LSV2 Client:an error was received after the last transmission, Error Type: 1, Error Code: 24 'LSV2_ERROR_T_ER_WRONG_PARA'
DEBUG:LSV2 Client:got version info: iTNC530 / 606420 02 SP10
DEBUG:LSV2 TCP:telegram to transmit: command CMD.R_PR payload length 0 bytes data: bytearray(b'\x00\x00\x00\x00R_PR')
DEBUG:LSV2 TCP:received block of data with length 132
DEBUG:LSV2 Client:expected response received: RSP.S_PR
DEBUG:LSV2 Client:got system parameters: <pyLSV2.dat_cls.SystemParameters object at 0x000001D8B04DFB00>
DEBUG:LSV2 TCP:telegram to transmit: command CMD.R_CI payload length 4 bytes data: bytearray(b'\x00\x00\x00\x04R_CI\x00\x00\x00\x01')
DEBUG:LSV2 TCP:received block of data with length 16
DEBUG:LSV2 Client:expected response received: RSP.S_CI
DEBUG:LSV2 TCP:telegram to transmit: command CMD.R_CI payload length 4 bytes data: bytearray(b'\x00\x00\x00\x04R_CI\x00\x00\x00\x02')
DEBUG:LSV2 TCP:received block of data with length 16
DEBUG:LSV2 Client:expected response received: RSP.S_CI
DEBUG:LSV2 TCP:telegram to transmit: command CMD.R_CI payload length 4 bytes data: bytearray(b'\x00\x00\x00\x04R_CI\x00\x00\x00\x03')
DEBUG:LSV2 TCP:received block of data with length 16
DEBUG:LSV2 Client:expected response received: RSP.S_CI
DEBUG:LSV2 Client:setting connection settings for ControlType.MILL_OLD and block length 4096
DEBUG:LSV2 Client:use buffer size of 4096
DEBUG:LSV2 TCP:telegram to transmit: command CMD.C_CC payload length 2 bytes data: bytearray(b'\x00\x00\x00\x02C_CC\x00\x07')
DEBUG:LSV2 TCP:received block of data with length 8
DEBUG:LSV2 Client:expected response received: RSP.T_OK
DEBUG:LSV2 TCP:telegram to transmit: command CMD.C_CC payload length 2 bytes data: bytearray(b'\x00\x00\x00\x02C_CC\x00\x13')
DEBUG:LSV2 TCP:received block of data with length 8
DEBUG:LSV2 Client:expected response received: RSP.T_OK
DEBUG:LSV2 Client:secure file send is enabled
DEBUG:LSV2 TCP:telegram to transmit: command CMD.A_LG payload length 5 bytes data: bytearray(b'\x00\x00\x00\x05A_LGFILE\x00')
DEBUG:LSV2 TCP:received block of data with length 8
DEBUG:LSV2 Client:expected response received: RSP.T_OK
DEBUG:LSV2 Client:login executed successfully for login FILE
INFO:LSV2 Client:successfully configured connection parameters and basic logins
iTNC530
606420 02 SP10
DEBUG:LSV2 Client:login already active
DEBUG:LSV2 Client:login already active
DEBUG:LSV2 TCP:telegram to transmit: command CMD.C_DC payload length 6 bytes data: bytearray(b'\x00\x00\x00\x06C_DCTNC:\\\x00')
DEBUG:LSV2 TCP:received block of data with length 8
DEBUG:LSV2 Client:expected response received: RSP.T_OK
DEBUG:LSV2 Client:changed working directory to TNC:\
DEBUG:LSV2 Client:login already active
DEBUG:LSV2 Client:login already active
DEBUG:LSV2 TCP:telegram to transmit: command CMD.C_DC payload length 5 bytes data: bytearray(b'\x00\x00\x00\x05C_DCTNC:\x00')
DEBUG:LSV2 TCP:received block of data with length 8
DEBUG:LSV2 Client:expected response received: RSP.T_OK
DEBUG:LSV2 Client:changed working directory to TNC:
DEBUG:LSV2 TCP:telegram to transmit: command CMD.R_DI payload length 0 bytes data: bytearray(b'\x00\x00\x00\x00R_DI')
DEBUG:LSV2 TCP:received block of data with length 178
DEBUG:LSV2 Client:expected response received: RSP.S_DI
DEBUG:LSV2 Client:successfully received directory information for TNC:\
DEBUG:LSV2 Client:login already active
DEBUG:LSV2 TCP:telegram to transmit: command CMD.R_FI payload length 12 bytes data: bytearray(b'\x00\x00\x00\x0cR_FITNC:\\test.H\x00')
DEBUG:LSV2 TCP:received block of data with length 10
INFO:LSV2 Client:an error was received after the last transmission, Error Type: 1, Error Code: 32 'LSV2_ERROR_T_ER_NO_FILE'
DEBUG:LSV2 Client:file does not exist
DEBUG:LSV2 Client:ready to send file from H:\python\pyTNC\pyLSV2\test.H to TNC:\test.H
DEBUG:LSV2 Client:selecting non binary transfer mode
DEBUG:LSV2 TCP:telegram to transmit: command CMD.C_FL payload length 13 bytes data: bytearray(b'\x00\x00\x00\rC_FLTNC:\\test.H\x00\x00')
DEBUG:LSV2 TCP:received block of data with length 8
DEBUG:LSV2 TCP:telegram to transmit: command RSP.S_FL payload length 525 bytes data: bytearray(b'\x00\x00\x02\rS_FL0  BEGIN PGM test MM \r\n1  L  X+1  Y+2  Z+3\r\n2  L  X+1  Y+2  Z+3\r\n3  L  X+1  Y+2  Z+3\r\n4  L  X+1  Y+2  Z+3\r\n5  L  X+1  Y+2  Z+3\r\n6  L  X+1  Y+2  Z
+3\r\n7  L  X+1  Y+2  Z+3\r\n8  L  X+1  Y+2  Z+3\r\n9  L  X+1  Y+2  Z+3\r\n10 L  X+1  Y+2  Z+3\r\n11 L  X+1  Y+2  Z+3\r\n12 L  X+1  Y+2  Z+3\r\n13 L  X+1  Y+2  Z+3\r\n14 L  X+1  Y+2  Z+3\r\n15 L  X+1  Y+2  Z+3\r\n16 L  X+1  Y+2  Z+3\r\n17 L  X+1  Y+2  Z+3\r\n18 L  X+1  Y+
2  Z+3\r\n19 L  X+1  Y+2  Z+3\r\n20 L  X+1  Y+2  Z+3\r\n21 L  X+1  Y+2  Z+3\r\n22 L  X+1  Y+2  Z+3\r\n23 L  X+1  Y+2  Z+3\r\n24 END PGM test MM ')
DEBUG:LSV2 TCP:received block of data with length 10
WARNING:LSV2 Client:could not send data, received unexpected response 'RSP.T_BD'
DEBUG:LSV2 TCP:telegram to transmit: command CMD.A_LO payload length 0 bytes data: bytearray(b'\x00\x00\x00\x00A_LO')
DEBUG:LSV2 TCP:received block of data with length 8
DEBUG:LSV2 Client:expected response received: RSP.T_OK
INFO:LSV2 Client:logout executed successfully for login None
DEBUG:LSV2 TCP:Connection to <IP_ADDRESS> closed
DEBUG:LSV2 Client:connection to host closed

The possible lines shift by longer or shorter blocks
on the iTNC530 340494 08 i testet the same, but i cant transver one single line (file recive works perfectly)

iTNC530 606420 02:
Ok, since it related to the length, there probably is an error identifying the buffer size for the connection. Going by the log messages pyLSV2 uses a buffer size of 4096 bytes. This decision is made based on the system parameters that are set during there initialization phase. The longer file results in a transfer of 525 bytes.
Can you please try the following to force pyLSV2 to use a buffer size for 256 before sending the file? Going by what little documentation is available, this is the smallest possible buffer size and should therefor be supported by any version. To do this, add following line before sending the file:
con._llcom.buffer_size = 256

If the transfer works after adding this line, the init code is wrong.
iTNC530 340494 08:
I haven't had time to get a old version of windows running but I hope to find some time soon.

This works for me too, thank you very much
The iTNC530 340494 08 is not very important to me, I personally don't necessarily need a fix and don't want to burden you unnecessarily

can you please retest with the current master branch? I think #67 might also fix the last remaining issue

Hello drunsinn,
thank you very mutch, the transver work :)


[Question] :  Update

Describe the new feature or enhancement
When will there be an update for the unity version 2021.3.10f1? Now coroutines don`t work there, and there is nothing to replace them with

tracked in #327


fr: add support for include-only pragmas

Per #45, implement include only configurations such that if specified, no additional files are compiled unless included in the respective option.
Linked Issues:

[ ] Testing - #46

How difficult would this be to implement?

How difficult would this be to implement?

Not too difficult tbh, just need to set some time aside this week & will implement in an eve

Nice job!


Char single-quote and double-quote escape

Debug.print(debug_show('\"')); => " - good?
Debug.print(debug_show('"')); => syntax error [M0002], malformed operator, should be allowed?
Debug.print(debug_show(''')); => ' - should be syntax error?
Debug.print(debug_show('\'')); => ' - good

Yes, this looks like it needs reconsidering. Thanks for reporting!

Actually, on second thought. I think this behaviour is actually fine since we know that a Char literal must contain exactly one Character.


Qubino flush dimmer 0-10V (ZMNHVD) included but do not want to use repeaters

Hi,
I have an issue with one ZMNHVD flush dimmer. Although alive and connected (included and seems to be working well), it is not willing to use any repeaters although should be available and better connection. On the map is shown as grey (named wallbox)... Healing does not help neither....
Any advice how to solve this?
Thanks a lot.
Regards,
Kratax

@Kratax try to heal device

@Kratax try to heal device

I did it twice.... Still the same...

cc @AlCalzone


Support command-line decoding

It would be useful if classyshark supported command-line decoding similar to apktool d. (To make it easier to view the result in other editors.)

Added expert button to export ClassyShark results, here is the commit https://github.com/google/android-classyshark/commit/c1303f68a51a46aebf9e8b98c3efcccb365d8860


Back to the drawing board

I don't think I like current design:

I don't like actor<T>, functions are not actors, actors are bigger than a single function
I don't like how heavyweight current context switching is, coroutines should have very little state
I don't like to co_await context() at the start of every function, even tests look ugly as a result
Tests with use coroutine local values show how weird this "one set of locals before co_await, different locals after co_await"

After getting more inspiration from both Swift and Python, here's what I'd like instead:

I'd like coroutines to just be lazy start coroutines, very lightweight, without any need for a separate task<T>
I'd like these coroutines to be marked async<T>, similar to async def in Python and async functions in Swift
I'd like these coroutines to have an associated "task", which doesn't change as long as it's a single logical thread of execution
I'd like this task to be extremely liteweight, i.e. there shouldn't be any extra allocations when async<T> is a pure coroutine, without any actor context, etc.

This task could be inline in the awaiter from non-async to async coroutines, so it doesn't live "on the heap", and it's lifetime is bound to the first async<T> lifetime
The ability to detach async calls may throw a wrench into this, but solvable by using something like task::detached(async<T>) static method, which would create a new detached coroutine, then await on the async<T>, which would create its own task

I'd like async<T> to have a single entrance via co_await and exit via its awaiter, and I'd like it to be as simple as possible, i.e. just return to a continuation that awaited us (optionally restoring context first)
I'd like current task and context to just inherit naturally, i.e. one async to another should be a direct symmetric transfer, no change in current task or anything
Current stop token, current context, current task local values, will all be properties of the task
Task group will naturally create a task for each added awaitable, and this new task will naturally inherit parent's task locals, etc.
Task will need to unmount from thread-locals when awaiting non-task-aware awaitables, and remount when awaiter wrapper resumes (along with a switch to current task's actor context)
We wouldn't need async promise to inherit from any intrusive data structures, because those can move to "stack locals", e.g. as part of an awaiter

This way I hope to simlify the design, and make actors and async coroutines more orthogonal to each other.

Implemented in 144423c96a444acd8b3ac1ddaa03867dc6f8b865


Added the news page

Description
Designed the news page properly.
Related Issues

Closes #555

Type of PR

[ x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes]

Checklist

[ x] I have gone through the contributing guide
[x ] I have updated my branch and synced it with project main branch before making this PR
[x ] I have performed a self-review of my code
[ x] I have tested the changes thoroughly before submitting this pull request.
[ x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x ] I have commented my code, particularly in hard-to-understand areas.

@shruti110503 Resolve conflicts

@shruti110503 LGTM after resolving conflicts

There are some misalignment see in the deploy

I can;t see the changes in news page of attached screenshot and see home page in the deploy it got misaligned

No! Activity