Build dashboard

Build a dashboard view that shows:
New Post:
Simple new post button. opens modal
Settings:
Button that redirects to settings view
Search:
Should suggest users that are cached locally
Submitting the form should redirect to the search view
Pressing Ctrl + k (and whatever mac is) should focus the search input
People Lists:
Always show "Contacts" or "Main" first
The next three should be the most recent k30000 the user has used
Chats:
Show the most recent incoming messages
Only show message content if its already decrypted
Notifications:
Show 5-6 latest notifications
Tools:
Show the most recent tools used
Clicking card should redirect to /other-stuff
Figma: https://w3.do/MhlM_pOw

Added Feeds, Search, New Note, and Messages in alpha version


Improve the design of Switch Branches modal for Git

The sync button beside the switch branches text is confusing for the user as it looks like a CTA for switch branches where as it is a different context altogether.

This kind of icon should work I think !?

Thanks for the input, we're planning to redesign this, and will take this into consideration!

HI @Debsourabh can I try to solve this issue if nobody is working on it currently?
(This would be my first issue in this repo)

@Anonymous961  - We're planning to redesign this flow so, we don't have a design that can be implemented yet. Can you please search for other Good First Issues that you can contribute toward?


Biscuit Clicker

Biscuit clicker.
I want to ask for a new challenge in which we make a simple game using basic like Cookie clicker.
Libraries
HTML, CSS, JS
@DavidMatthewFraser @terrifricker

That sounds like a really fun project!
Again, it is not really related to teaching beginners Git/Github.
We are also not really looking for more projects right now given Terri and I's busy personal schedules. Thanks!

Why don't you give the responsibility to someone?


Reloading of data files doesn't work for dynamic pages in Middleman 5.0 (master)

Expected behavior and actual behavior
I'm running the preview server for a Middleman app that defines proxy pages from data files. When I change the data files, these pages aren't updated unless I restart the preview server.
Steps to reproduce the problem (from a clean middleman installation)
Suppose I have the following in data/people.yaml
- name: Tom
  bio: A jolly fellow

and the following in config.rb
data.people.each do |person|
  proxy "/#{person.name.parameterize}.html", "/person.html", locals: { person: person }
end

and the following in person.html.erb

<%= person.name %>

<%= person.bio %>

When I start the preview server, and visit http://localhost:4567/tom.html, I see the dynamic page. If I change the value of bio in data/people.yaml, and reload the page, there isn't any change; however, in Middleman 4, the newest value of bio would be shown.
This issue appears to be limited to proxy pages. If I have an template where I iterate through all data, for example the following, reloading works properly.
<% data.people.each do |person| %><%= person.name %><% end %>

Additional information

Ruby version: 2.7.1p83
Middleman version: 5.0.0 via master branch
OS version: macOS 10.15.4

Some of the VERY magical machinery that made this work in MM4 was removed. It was overkill. What should happen in this case is a full reboot of the dev server (rather than the old fancy bit). I believe this should just be tracking down the place where we handle restarting the server on certain file changes. I'll dig in

Thanks! Doing a full reboot when data changes would be highly appreciated, and probably solve some a related issue I'm having that's specific to some custom code in my app.

This is the code which controls the reload process: https://github.com/middleman/middleman/blob/master/middleman-core/lib/middleman-core/preview_server.rb#L151-L178
As you might expect, things are a bit busy right now. I will attempt to dig in, but that may give you a head start.

We could extend match_against to include the data_dir like the following:
match_against = [
  /^config\.rb$/,
  %r{^environments/[^\.](.*)\.rb$},
  %r{^lib/[^\.](.*)\.rb$},
  %r{^#{config[:helpers_dir]}/[^\.](.*)\.rb$},
  %r{^#{config[:data_dir]}/[^\.](.*)\.(yml|yaml|json)$}
]

However, this approach would create an implicit coupling between the preview server and the data extension. By defining it as an extension, it seems like that was something you were striving to avoid.
The other approach would be to have the data extension itself trigger the :reload event. This way, while they'd still be coupled, the extension would implicitly be dependent on the preview server, which is perhaps a nicer strategy.

I agree with the more evented approach. Sorry, I don't spend enough time deep in the codebase to have it all in my head right now.
As a minor aside, data dir can nest indefinitely. Doing the change in the data extension should allow that to "just work" as opposed to a regex


ONE_DIR Issues/Questions

Hi Everyone,
Many thanks for the great project!  I have read through everything I can find in the README, issues people have opened, wiki, etc. re ONE_DIR, but I'm still running into issues.  I have seen the posts tomav recommends temporarily switching to ONE_DIR=0 so it will generate all the necessary file & directories and then switch back to ONE_DIR=1.  However, when I change that setting in my docker-compose.yml it looks like rebuilds the container and now the previously created files and dirs are gone.  Am I missing something?
Thanks!

I did notice that _misc_save_states() in start-mailserver.sh runs I get this when ONE_DIR=1:
mail    | Starting Misc
mail    |   * Consolidating all state onto /var/mail-state
mail    |   *   Moving contents of /var/spool/postfix to /var/mail-state/spool-postfix:
mail    | mv: cannot remove '/var/spool/postfix/usr/lib': Invalid argument
mail    |   *   Destination /var/mail-state/lib-postfix exists, linking /var/lib/postfix to it
mail    |   *   Moving contents of /var/lib/amavis to /var/mail-state/lib-amavis:
mail    | mv: cannot remove '/var/lib/amavis/.pyzor': Invalid argument
mail    | mv: cannot remove '/var/lib/amavis/.razor': Invalid argument
mail    |   *   Moving contents of /var/lib/clamav to /var/mail-state/lib-clamav:
mail    | mv: cannot remove '/var/lib/clamav': Invalid argument
mail    |   *   Linking /var/lib/spamassasin to /var/mail-state/lib-spamassasin
mail    |   *   Moving contents of /var/lib/fail2ban to /var/mail-state/lib-fail2ban:
mail    |   *   Moving contents of /var/lib/postgrey to /var/mail-state/lib-postgrey:
mail    |   * Fixing /var/mail-state/* permissions
mail    | Starting mail server

And then it goes on to output errors like:
mail    | Oct  2 20:56:49 mail2 amavis[260]: (!!)TROUBLE in pre_loop_hook: No TEMPBASE directory: /var/lib/amavis/tmp at /usr/sbin/amavisd-new line 12742.
mail    | Oct  2 20:56:49 mail2 dovecot: master: Error: bind(/var/spool/postfix/private/auth) failed: No such file or directory
mail    | 2017-10-02 20:56:49,371 INFO exited: dovecot (exit status 89; not expected)
mail    | Oct  2 20:56:49 mail2 dovecot: master: Fatal: Failed to start listeners
mail    | 2017-10-02 20:56:49,373 INFO spawned: 'dovecot' with pid 282
mail    | 2017-10-02 20:56:49,377 INFO success: dovecot entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | 2017-10-02 20:56:49,377 INFO exited: amavis (exit status 255; not expected)
mail    | 2017-10-02 20:56:49,412 INFO spawned: 'amavis' with pid 285
mail    | 2017-10-02 20:56:49,413 INFO exited: dovecot (exit status 89; not expected)
mail    | Oct  2 20:56:49 mail2 dovecot: master: Error: bind(/var/spool/postfix/private/auth) failed: No such file or directory
mail    | Oct  2 20:56:49 mail2 dovecot: master: Fatal: Failed to start listeners
mail    | 2017-10-02 20:56:49,413 INFO success: amavis entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | 2017-10-02 20:56:49,415 INFO spawned: 'dovecot' with pid 286
mail    | 2017-10-02 20:56:49,451 INFO success: dovecot entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | Oct  2 20:56:49 mail2 dovecot: master: Error: bind(/var/spool/postfix/private/auth) failed: No such file or directory
mail    | Oct  2 20:56:49 mail2 dovecot: master: Fatal: Failed to start listeners
mail    | 2017-10-02 20:56:49,452 INFO exited: dovecot (exit status 89; not expected)

Hmm, seems to be working now after I wiped the whole server and did a fresh install.  I had done a docker system prune -a -f a bunch of times before I did the wipe and cleaning out where my maildata and mailstate dirs were located, so i think I had been trying it from a fresh start before, but it refused to work earlier.
In any event, sorry for the false alarm.


Fail when trying to run webui with ipfsd-ctrl

Describe the bug
I can't connect the webui with the spawned daemon, even with my API.HTTPHeaders options set up inside the ipfsOptions, this is the error I get:

If i reload the webui at the same time my app is starting it shows data and a succes message, just for a sec (if you change webui view it shows the error message again). I can't reproduce this right now.
Reproduction
const { createController } = require('ipfsd-ctl')
const ipfsHttpModule = require('ipfs-http-client');
const ipfsBin = require.resolve('ipfs/src/cli.js');

export const getDataNode = async (port) => {
  const ipfsd = await createController({
    ipfsHttpModule,
    ipfsBin,
    remote: false,
    type: 'js',
    ipfsOptions: {
      config: {
        API: {
          HTTPHeaders: {
            "Access-Control-Allow-Origin": [
              "*"
            ],
            "Access-Control-Allow-Methods": ["PUT", "POST", "GET", "DELETE"],
            "Access-Control-Allow-Credentials": true,
          }
        }
      }
    }
  })
  console.log(ipfsd);
  return ipfsd.api
};

Expected behavior
Connet webui with my daemon.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop:

OS: Win10
Browser: chrome
Version 2.11.4

@denyncrawford you need to enter either URL or Multiaddr:

(we added the above hint in https://github.com/ipfs/ipfs-webui/pull/1811 and will ship in next version)

@lidel This is what I have in that field:

The error is still the same:

And this is how I have my addresses:

Seems like it's not the solution, I have my gateway working, but the webui isn't :/ Thank you btw.

Ah, I just realized you are using js-ipfs (type: 'js').
The latest version of webui does not support js-ipfs.
I'm closing this as we are tracking fixing that  in https://github.com/ipfs/ipfs-webui/issues/1737
If you want to use webui  with js-ipfs, you need to use older version that is bundled with js-ipfs – it can be loaded via http://<IP_ADDRESS>:{api_port}/webui, in your case http://<IP_ADDRESS>:5001/webui

Nah, it is the same version:


Error while running the run_full.py for the gfs-reforecast dataset from hugging face

Describe the bug
While running and debugging the python file mentioned, I found that the data is sliced for only one time stamp whereas in the next lines it is mentioned that the data has a starting and ending time. After reading through the paper, my understanding is that one node has one timestamp and model is trained only be of one timestamp but that contradicts the start and end variables in the XrDataset dataloader.

I do have another question regarding the aux_dims in the encoder. If I run the example usage, it shows the issue that output and input dimensions do not match as input feature dimensions sum up to a total of 102 (input_dims(78) + aux_dim(24)) whereas the output dims are just 78.

To Reproduce
Steps to reproduce the behavior:

Go to hf_forecasts.json.
Change the first file name to data/forecasts/GFSv16/2021/04/2021040100.zarr.zip as other files are not found on the webpage
Go to train/run_full.py
Run the file.
See error

Steps to reproduce the behavior:

Go to train.
Create a new file for example usage.
Run the file.
See error

Expected behavior
These steps should give you the errors as shown in the images.
Additional context
Also, I could not find the files mentioned in the hf_forecasts.json on hugging face gfs-reforecast dataset.

Replacing the line 35, i.e., "data = self.data.isel(reftime=item, time=slice(start_idx, start_idx + 1))", in XrDataset definition with the following line maybe effective.
data = self.data.isel(reftime=item, time=slice(start_idx, start_idx + 2))

Thank you for the response. I have already implemented this line and have tested running the model and it works. I just wanted to make sure, if this indeed is an error, it might be better to correct this in the main repo as well.

Thanks @jjjj32481 and @SwordSaintLancelot would you be able to do a PR?
@jjjj32481 do you know why this is?

@peterdudfield I don't think I have write access to the repository. Should I still look into creating the PR?

Yea, I think you can fork the repo, and then make a PR back to this one?


Node.js v4 Preview typescript function file not created correctly

In a new/empty directory, I created a v4 ts app. The boilerplate looks correct except for the function file itself.
{
    "name": "Azure"
}

How did you create this project? What kind of trigger did you start with? When you create a new TS project with an httpTrigger, it looks like this:

I started with VSCode's Azure functions extension to create function app but selected the Node.js v4 model. The trigger was an HTTP trigger but I renamed it in the step to status.
Thanks for providing the code - I do know what the code looks like - just wondered if the Azure Functions vscode extension was supposed to work with the new programming model.

I can't repro this now.

Just repro'd: more details.

On windows - internal FTE laptop windows version.
In new/empty folder - nothing else in it - not even .git.
Created new app - all questions asked and answered - no problems.
After process, file is named correctly but only has

{
    "name": "Azure"
}

Another weird thing is that the directory structure is an additional layer of api.


fixed openwhyd issue #458

Tests

adds support for searching deezer.com/fr/track:id urls
by changing the regex.

Thank you for the fix!
The noisy diff is probably caused by the mass reformatting you committed on files, probably done automatically by your code editor. I know, the experience would have been nicer if I had added a formatting+linter configuration in the project... Sorry about that!
If I understand well, the gist of your fix is:

an updated regex in https://github.com/adrienjoly/playemjs/pull/43/files?diff=unified&w=1#diff-dc450709bf1d1e6d40ca75c7eda9c2a079558942938c76bfd5881c6c707dd966
an additional test case in https://github.com/adrienjoly/playemjs/pull/43/files?diff=unified&w=1#diff-0c532c9033ee0ac895543f4273bf1b2d7cff4122125806dd34c569dd9f154557

Unless you really want to do it yourself, I'm going to reapply your changes without the reformatting, to make the diff smaller.


bug: Classname 'divider' is not a Tailwind CSS class!

What version of daisyUI are you using?
4.6.2
Which browsers are you seeing the problem on?
Chrome
Reproduction URL
none
Describe your issue
Today I tried to open a project I worked on a year ago to continue development. The daisyui version at that time was v2. The project started normally and the styles also existed. However, in my eslint, it prompted that the classname related to daisyui did not exist.

This bothers me a lot. I tried upgrading the version of daisyui to the latest version, but the warning still exists.
The following is the configuration file of my tailwindcss：

I assume you're using eslint-plugin-tailwindcss with no-custom-classname rule. If so, it is expected to get warning.
Disabling that rule should fix the warning.
eslint-plugin-tailwindcss docs:
https://github.com/francoismassart/eslint-plugin-tailwindcss
Also make sure you're using the latest version:
https://github.com/francoismassart/eslint-plugin-tailwindcss/issues/129
And finally, this is warning from your linter plugin so probably asking about it in the related repo would be more helpful.


generate an empty folder ，“-p”

_shelljs2.default.exec('mkdir -p ' + _path2.default.dirname(outPath));,will generate an empty folder,-p,use _shelljs2.default.mkdir('-p', _path2.default.dirname(outPath)); will not genertate

I'm doing -p https://github.com/corysimmons/imagemin-cli-preserve-dir-structure/blob/master/lib/index.js#L32

oh, the index.js what i saw is compiled

shelljs.mkdir() will generate an empty directory.
shelljs.exec('mkdir -p') will not.

Is this correct?

shelljs.exec('mkdir -p') will generate an empty directory.
shelljs.mkdir() will not.

PR please.


sqlite replaced by hive

macos,windows,web platforms support added
updated packages and fixed problems

First time i try to pull request , i hope i did it right.
It look like i changed a lot of files but actually i just removed sqlite and changed inside StorageDisk file and a few fix problems. After added platform support its added a lot of files


Async CanFD via Generics

... Wish I had checked the pull requests and seen number #51 already, I wouldn't have implemented this 😬
This takes a slightly different approach in that I made the interfaces generic, not sure if you like it more or less,
so figure I should post it just in case.
I also did a stream impl and copy pasta'ed the tests and made minor tweaks.
the stream tests pass when run independently but are non-deterministic as part of cargo test, not sure if that's existing behavior.
Thanks for the library, feel free to close this or lift anything you want out of it.

Actually, I was thinking about reconsidering the implementation of the socket classes using generics all around. The amount of redundant code is starting to explode with the different runtimes and protocols being considered.
I just put out a release of the Netlink stuff, and don't have a whole lot of time to keep working on this crate right now, but perhaps you folks can consider how best to use one or the other of these two PRs, and/or combine them? Then, when I swing back around to this one, we can get it all merged?
@balattar do you have any comments on this?

...and, of course, there's still a matching async_io implementation that would need to be done :smiley:

Well I'd love to help out, and I don't have to take time off of work to do that :)

I knocked out one of the other open-source crates last night, and thought to give this a try before moving on to the next one...
But I'm getting intermittent failures of the unit tests. Like this:
running 16 tests
test dump::test::test_simple_example ... ok
test frame::tests::test_bit_flags ... ok
test errors::tests::test_errors ... ok
test dump::test::test_extended_example ... ok
test frame::tests::test_data_frame ... ok
test dump::test::test_fd ... ok
test frame::tests::test_defaults ... ok
test frame::tests::test_error_frame ... ok
test frame::tests::test_fd_frame ... ok
test frame::tests::test_frame_to_fd ... ok
test frame::tests::test_remote_frame ... ok
test nl::rt::tests::test_as_bytes ... ok
test tokio::tests::test_receive ... ok
test tokio::tests::test_receive_can_fd ... ok
test tokio::tests::test_sink_stream_fd ... FAILED
test tokio::tests::test_sink_stream ... FAILED

failures:

---- tokio::tests::test_sink_stream_fd stdout ----
Sent 3 frames
thread 'tokio::tests::test_sink_stream_fd' panicked at src/tokio.rs:442:9:
assertion `left == right` failed
  left: 0
 right: 2
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

---- tokio::tests::test_sink_stream stdout ----
Sent 3 frames
thread 'tokio::tests::test_sink_stream' panicked at src/tokio.rs:403:9:
assertion `left == right` failed
  left: 4
 right: 2

failures:
    tokio::tests::test_sink_stream
    tokio::tests::test_sink_stream_fd

test result: FAILED. 14 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

error: test failed, to rerun pass `--lib`

The existing test failed once. The new FD test fails like 50% of the runs I tried.
I'll look at the tests, since the original one seems flawed. But do you have any ideas? Do the tests work for you consistently?

Oh, wait... Nevermind. I see it.
The new FD tests are running in parallel (at the same time) with the old ones and they're all reading and writing to vcan0 and interfering with each other at random.
There are a couple ways to solve this, but one way we're already using is the serial_test crate, which allows you to mark a test as #[serial]. All tests marked as such run one at a time so they don't clash.
When I did that with the tokio tests, they all started passing consistently.
Looking good.

Hey thanks!


HBASE-27829 Introduce build for kuttl image, basis for dev/test environment

This supersedes apache/hbase-operator-tools/#118

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
3m 16s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ main Compile Tests _

_ Patch Compile Tests _

+1 :green_heart:
codespell
0m  0s

No new issues.

+1 :green_heart:
detsecrets
0m  2s

No new issues.

-1 :x:
blanks
0m  0s
/blanks-eol.txt
The patch has 2 line(s) that end in blanks. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

-1 :x:
hadolint
0m  0s
/results-hadolint.txt
The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

-1 :x:
markdownlint
0m  1s
/results-markdownlint.txt
The patch generated 7 new + 0 unchanged - 0 fixed = 7 total (was 0)

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
shelldocs
0m  0s

No new issues.

_ Other Tests _

+1 :green_heart:
asflicense
0m  0s

The patch does not generate ASF License warnings.

3m 24s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43

GITHUB PR
https://github.com/apache/hbase-kustomize/pull/3

Optional Tests
dupname asflicense codespell detsecrets hadolint shellcheck shelldocs markdownlint

uname
Linux 25b80aab0522 5.4.0-1101-aws #109~18.04.1-Ubuntu SMP Mon Apr 24 20:40:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
nobuild

Personality
/home/jenkins/jenkins-home/workspace/hbase-kustomize-github-pr_PR-3/yetus-precommit-check/src/.yetus/personality.sh

git revision
main / 177cc9248d234702b6282f3d70f180621a7f84ef

Max. process+thread count
8 (vs. ulimit of 5000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/hbase-kustomize-github-pr/job/PR-3/3/console

versions
git=2.25.1 hadolint=2.10.0 codespell=2.2.1 detsecrets=1.2.0 markdownlint=0.31.1 shellcheck=0.8.0

Powered by
Apache Yetus 0.14.1 https://yetus.apache.org

This message was automatically generated.

The hadolint complaint is invalid, seems it was fixed in 2.11.0,
% docker container run --rm -i hadolint/hadolint:v2.11.0 < dockerfiles/kuttl/Dockerfile
%

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 24s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ main Compile Tests _

_ Patch Compile Tests _

+1 :green_heart:
codespell
0m  0s

No new issues.

+1 :green_heart:
detsecrets
0m  2s

No new issues.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-1 :x:
hadolint
0m  0s
/results-hadolint.txt
The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
markdownlint
0m  0s

No new issues.

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
shelldocs
0m  1s

The patch generated 0 new + 0 unchanged - 2 fixed = 0 total (was 2)

+1 :green_heart:
yamllint
0m  0s

The patch generated 0 new + 0 unchanged - 10 fixed = 0 total (was 10)

_ Other Tests _

+1 :green_heart:
asflicense
0m  0s

The patch does not generate ASF License warnings.

0m 33s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43

GITHUB PR
https://github.com/apache/hbase-kustomize/pull/3

Optional Tests
dupname asflicense codespell detsecrets yamllint shellcheck shelldocs hadolint markdownlint

uname
Linux cae6b6c17c7b 5.4.0-1101-aws #109~18.04.1-Ubuntu SMP Mon Apr 24 20:40:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
nobuild

Personality
/home/jenkins/jenkins-home/workspace/hbase-kustomize-github-pr_PR-3/yetus-precommit-check/src/.yetus/personality.sh

git revision
main / 223620d230bc6df5b62ce58c885257c1ce1b3cef

Max. process+thread count
9 (vs. ulimit of 5000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/hbase-kustomize-github-pr/job/PR-3/4/console

versions
git=2.25.1 hadolint=2.10.0 codespell=2.2.1 detsecrets=1.2.0 markdownlint=0.31.1 shellcheck=0.8.0 yamllint=1.26.3

Powered by
Apache Yetus 0.14.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 24s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ main Compile Tests _

_ Patch Compile Tests _

+1 :green_heart:
codespell
0m  0s

No new issues.

+1 :green_heart:
detsecrets
0m  2s

No new issues.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-1 :x:
hadolint
0m  0s
/results-hadolint.txt
The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
markdownlint
0m  0s

No new issues.

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
shelldocs
0m  0s

The patch generated 0 new + 0 unchanged - 2 fixed = 0 total (was 2)

+1 :green_heart:
yamllint
0m  1s

The patch generated 0 new + 0 unchanged - 10 fixed = 0 total (was 10)

_ Other Tests _

+1 :green_heart:
asflicense
0m  0s

The patch does not generate ASF License warnings.

0m 34s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43

GITHUB PR
https://github.com/apache/hbase-kustomize/pull/3

Optional Tests
dupname asflicense codespell detsecrets yamllint shellcheck shelldocs hadolint markdownlint

uname
Linux 0294a1c10a00 5.4.0-1101-aws #109~18.04.1-Ubuntu SMP Mon Apr 24 20:40:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
nobuild

Personality
/home/jenkins/jenkins-home/workspace/hbase-kustomize-github-pr_PR-3/yetus-precommit-check/src/.yetus/personality.sh

git revision
main / d896acd7e3f7decd65356939a3ed541980d9844f

Max. process+thread count
9 (vs. ulimit of 5000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/hbase-kustomize-github-pr/job/PR-3/5/console

versions
git=2.25.1 hadolint=2.10.0 codespell=2.2.1 detsecrets=1.2.0 markdownlint=0.31.1 shellcheck=0.8.0 yamllint=1.26.3

Powered by
Apache Yetus 0.14.1 https://yetus.apache.org

This message was automatically generated.


Update to Shopware <IP_ADDRESS>

Update to Shopware <IP_ADDRESS>.
Tested and already in productive use.

Thanks :blue_heart:


Unmaximizing the Babylon Native Playground on Win32 causes an interesting crash

For questions, please use the forum.
Describe the bug
It looks like this interrupts the render loop somehow. Maximizing and then unmaximizing the Playground appears to cause us to call StartRenderingCurrentFrame when m_rendering is already true.
To Reproduce
Steps to reproduce the behavior:

Run the Playground.
Maximize.
Unmaximize.

Expected behavior
Doesn't crash.
Screenshots
N/A
Other

Platform: Win32

PR https://github.com/BabylonJS/BabylonNative/pull/823


Add comment to go.mod to specify which branch of osmosis-labs/cosmos-sdk we are using

Right now, it just looks something like:
github.com/osmosis-labs/cosmos-sdk v0.43.0-rc3.0.20211209072213-711e78b4f6b4
and this is hard to tell.
Is there some other way to know, that I'm not aware of?

no, not really (to my knowledge)
I find that best result comes from schlepping on a tag, but the tags aren't branches and end up doing undesired stuff over time.


mishandles nested masgn nodes in block args

a.k.a. parenthesized block arguments.
this might be a bug in ruby_parser or ruby2ruby.
example:
test("ok") { foo { |(bar, (baz, qux)), ugh| agh } }

output
it("ok") { foo { |(bar, masgn, baz, qux), ugh| agh } }

this might be a bug in ruby_parser or ruby2ruby.

Those projects are very well tested so it's more likely a bug in minitest_to_rspec :)

doesn't seem so - https://github.com/seattlerb/ruby2ruby/issues/50

Thanks Janosch, Given https://github.com/seattlerb/ruby2ruby/issues/50, should we close this, or is there more to do here?

@jaredbeck that depends on whether you want to leave this open as a warning / heads-up or not.
the bug is still there because the fix wasn't merged into ruby2ruby.
in the minitest codebase where i encountered a lot of these, i ended up working around it by using my branch of ruby2ruby.
on the other hand it is probably a rare issue.

I think we can close this? According to https://github.com/seattlerb/ruby2ruby/issues/50#issuecomment-478908839 it's fixed?


On Board Screen Logic

Added onboarding screen logic to the code
Now it open only once when the app Is run 1st time
after that, the main screen is shown every time it app runs after it.
https://user-images.githubusercontent.com/66347715/123741953-8b79b480-d8c8-11eb-83c2-1c37c5beb26e.mp4

Thank you


port_compiler: consistently format default_env/0

Would be great if we can merge this trivial fix before the attempt to sync port_compiler with the rebar3 plugin.


Fix: Fixed an issue where the file list would scroll up when refocusing the window

Resolved / Related Issues

[x] Were these changes approved in an issue or discussion with the project maintainers? In order to prevent extra work, feature requests and changes to the codebase must be approved before the pull request will be reviewed. This prevents extra work for the contributors and maintainers.
Closes #13220

Validation
How did you test these changes?

[x] Did you build the app and test your changes?
[ ] Did you check for accessibility? You can use Accessibility Insights for this.
[ ] Did you remove any strings from the en-us resource file?

[ ] Did you search the solution to see if the string is still being used?

[ ] Did you implement any design changes to an existing feature?

[ ] Was this change approved?

[ ] Are there any other steps that were used to validate these changes?

Open app ...
Click settings button ...

Screenshots (optional)
Add screenshots here.

The following step will cause the file list to scroll up:

Select the item at the top of the list
Deselect the item
Unfocus the app window
Refocus the app window

@MyoMinHein1246

@yaira2 Sorry for late response. I have got a lot on my plate recently. But I will work on this real soon. 😊

I looked further into it, and apparently, the file list scrolls to the last selected (or currently if there's one) item every time it get focused. Unfortunately, I still cannot find any fixes. 😭 The only thing I could find was to not let the user focus the file list, which obviously worsen the user experience. I need help.😔👀


[Outlook] (testing) document special flag when mocking Outlook

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

File
Status
Preview URL
Details

docs/testing/unit-testing.md
:white_check_mark:Succeeded
View

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


Rabbit mq fails start after enabling admin plugin

All, Installing sensu on a somewhat distributed environment, just rabbitmq on separate host. it installs fine and it starts, then installs the admin plugin and fails to restart. This is RHEL 7.1 with 2.12.0 version of the cookbook.
* service[rabbitmq-server] action start                                                                [393/4993]
    - start service service[rabbitmq-server]
Recipe: rabbitmq::mgmt_console
  * rabbitmq_plugin[rabbitmq_management] action enable
    * execute[rabbitmq-plugins enable rabbitmq_management] action run
      - execute rabbitmq-plugins enable rabbitmq_management

Recipe: rabbitmq::default
  * service[rabbitmq-server] action restart

    ================================================================================
    Error executing action `restart` on resource 'service[rabbitmq-server]'
    ================================================================================

    Mixlib::ShellOut::ShellCommandFailed
    ------------------------------------
    Expected process to exit with [0], but received '1'
    ---- Begin output of /sbin/service rabbitmq-server restart ----
    STDOUT: Restarting rabbitmq-server (via systemctl):  [FAILED]
    STDERR: Job for rabbitmq-server.service failed because the control process exited with error code. See "systemc
tl status rabbitmq-server.service" and "journalctl -xe" for details.
    ---- End output of /sbin/service rabbitmq-server restart ----
    Ran /sbin/service rabbitmq-server restart returned 1

    Cookbook Trace:
    ---------------
    /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:41:in `run_action'
    /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:49:in `block in ru
n_action'
    /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:47:in `each'
    /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:47:in `run_action'

    Resource Declaration:
    ---------------------
    # In /var/chef/cache/cookbooks/rabbitmq/recipes/default.rb

    225:   service node['rabbitmq']['service_name'] do
    226:     action [:enable, :start]
    227:     supports :status => true, :restart => true
    228:     provider Chef::Provider::Service::Upstart if node['rabbitmq']['job_control'] == 'upstart'
    229:     provider Chef::Provider::Service::Init if node['rabbitmq']['job_control'] == 'init'
    230:   end
    231: else

    Compiled Resource:
    ------------------
    # Declared in /var/chef/cache/cookbooks/rabbitmq/recipes/default.rb:225:in `from_file'

    service("rabbitmq-server") do
      action [:enable, :start]
      updated true
      supports {:status=>true, :restart=>true}
      retries 0
      retry_delay 2
      default_guard_interpreter :default
      service_name "rabbitmq-server"
      enabled true
      running true
      pattern "rabbitmq-server"
      declared_type :service
      cookbook_name "rabbitmq"
      recipe_name "default"
    end

Here is the out put from startup
Jun 30 13:48:59 LXXXXX01 rabbitmq-server[19847]: Stopping rabbitmq-server: RabbitMQ is not running
Jun 30 13:48:59 LXXXXX01 rabbitmq-server[19847]: rabbitmq-server.
Jun 30 13:48:59 LXXXXX01 systemd[1]: Stopped LSB: Enable AMQP service provided by RabbitMQ broker.
-- Subject: Unit rabbitmq-server.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rabbitmq-server.service has finished shutting down.
Jun 30 13:48:59 LXXXXX01 polkitd[743]: Unregistered Authentication Agent for unix-process:19842:180970377 (s
Jun 30 13:48:59 LXXXXX01 polkitd[743]: Registered Authentication Agent for unix-process:20074:180970433 (sys
Jun 30 13:48:59 LXXXXX01 systemd[1]: Starting LSB: Enable AMQP service provided by RabbitMQ broker...
-- Subject: Unit rabbitmq-server.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rabbitmq-server.service has begun starting up.
Jun 30 13:48:59 LXXXXX01 su[20169]: (to rabbitmq) root on none
Jun 30 13:48:59 LXXXXX01 su[20169]: pam_unix(su:session): session opened for user rabbitmq by (uid=0)
Jun 30 13:48:59 LXXXXX01 su[20169]: pam_unix(su:session): session closed for user rabbitmq
Jun 30 13:48:59 LXXXXX01 su[20319]: (to rabbitmq) root on none
Jun 30 13:48:59 LXXXXX01 su[20319]: pam_unix(su:session): session opened for user rabbitmq by (uid=0)
Jun 30 13:48:59 LXXXXX01 su[20321]: (to rabbitmq) root on none
Jun 30 13:48:59 LXXXXX01 su[20321]: pam_unix(su:session): session opened for user rabbitmq by (uid=0)
Jun 30 13:49:03 LXXXXX01 auditd[572]: Audit daemon rotating log files
Jun 30 13:49:05 LXXXXX01 su[20321]: pam_unix(su:session): session closed for user rabbitmq
Jun 30 13:49:05 LXXXXX01 rabbitmq-server[20079]: Starting rabbitmq-server: SUCCESS
Jun 30 13:49:05 LXXXXX01 rabbitmq-server[20079]: rabbitmq-server.
Jun 30 13:49:05 LXXXXX01 systemd[1]: Started LSB: Enable AMQP service provided by RabbitMQ broker.
-- Subject: Unit rabbitmq-server.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rabbitmq-server.service has finished starting up.
--
-- The start-up result is done.

@devilldog thanks for opening this issue but I believe the error you are encountering is occurring outside the scope of this cookbook. For now I'm going to close this issue, but feel free to open another if you find there's behavior in this cookbook which is at the root of the issue.


[skip ci] Allow ModelCheckpoint in Trainer callbacks list

Allows passing ModelCheckpoint directly to the callbacks list:
Trainer(callbacks=[ModelCheckpoint(...)])

This was not possible before because save_function was not set. We now set it in the callback directly.
The following cases need to be considered:

Trainer(checkpoint_callback=True, callbacks=[ModelCheckpoint()])
Trainer(checkpoint_callback=False, callbacks=[ModelCheckpoint()])
Trainer(checkpoint_callback=ModelCheckpoint(), callbacks=[ModelCheckpoint()])

This PR ignores the checkpoint_callback setting if one is passed to callbacks. Does this make sense @PyTorchLightning/core-contributors ?
TODO:

[x] needs a test
[x] need to define trainer.checkpoint_callback, we probably need to limit it to 1 checkpoint callback for now?

Seems good. Should we add a warning too if both are provided since this happens during initialization? One can change it if required.

The tests currently fail as they reveal another bug, which I will fix here: #4027


setRippleColor()

I want to set a color that its not from res
please fix It

This work
ripple:rv_color="@color/primary"
or
ripple:rv_color="#ffffff"
remember to put
xmlns:ripple="http://schemas.android.com/apk/res-auto"

I want to programmatically set a color that its not from res.
is it fixed?


Error in SAMPLEFOLDER

Hi,
I have been trying to run velocyto run10x, but I keep getting this error for my sample folder:
Error: Invalid value for 'SAMPLEFOLDER': Directory '~rds/.../filtered_feature_bc_matrix' does not exist.
Could you please tell me the files this command requires in the 10x output folder? barcodes.tsv, matrix.tsv and features.tsv ?
Thanks

velocyto run10x requires the Cell Ranger outputs like below

use codes like below
velocyto run10x -@ 16 -m /mnt/d/KP/hg38_rmsk.gtf /home/hyjforesight/SMC05T/ /mnt/d/KP/refdata-gex-GRCh38-2020-A-modified/genes/genes.gtf

Hi hyjforesight,
I have been getting this error as well. I got it only when I run on cellranger output of cell ranger multi.
I assume this is because the outs folder structure is different where the sample_alignment.bam and bam.bai will be found in a subfolder in the following path instead of being directly in outs 'sample1/outs/per_sample_outs/sample1/ '
Is that correct?. Could you please advise?. I tried to even put the file path as 'sample1/outs/per_sample_outs/sample1/' instead of sample1 only but it also didn't work.
Thanks

hello @Sa753
we also did multiplexed scRNA-seq. As I remember, velocyto run10x didn't work for cell ranger multi. you should use velocyto (on any technique) for individual bam

Hi  hyjforesight,
Thanks so much for prompt reply. I will have to run cell ranger on individual samples then do Velocyto. is correct?.
Thanks

hello @Sa753
if your samples were prepared by 10X cell plex kit, you will get 2 libraries after sequencing. One is oligo, the other is sequencing data (Sorry, I don't remember exactly the names). Then you should run Cell Ranger Multi for demultiplexing these sequencing data. The Cell Ranger Multi output includes folders for individual samples, where bam file is there. Use these bam files and run velocyto (on any technique) one by one. velocyto run10x is only for samples prepared by 10X v2 or v3 kit.

Hi hyjforesight,
Yes, cell ranger multi produces bam files for each of the components of cell ranger multi and there are separate bam file for each but it is still not accepting this bam file.
There is another thing, are you sure that Velocyto run10x is only for v2 or v3 kits?. Velocyto is established long before v2 or v3 kits were made and I run it on samples prepared by v1?.
Thanks

hello @Sa753
try this
# sort individual bam first
samtools sort /home/hyjforesight/sorting/Apc_Tumor.bam -o /home/hyjforesight/sorting/possorted_Apc_Tumor.bam -@ 16
# use the 10X barcodes.tsv and 10X reference genome file
velocyto run -@ 16 -b /home/hyjforesight/barcodes.tsv -o /home/hyjforesight/loom/ -m /home/hyjforesight/mm10_rmsk.gtf /home/hyjforesight/possorted_Apc_Tumor.bam /home/hyjforesight/refdata-gex-mm10-2020-A/genes/genes.gtf

Velocyto run10x is also suitable for v1.

Hi hyjforesight,
You pointed the right thing in the error which is that it always can't find the barcodes.tsv. I will try and run this code and update you. however, I just want to point that in the cellranger multi, the bam file is not called 'possorted.bam' it is called is made into assigned.bam in the per_sample_outs/counts folder which has the filtered reads assigned to cells and unassigned.bam in the multi folder/counts that contain the raw reads.
so I think I will use the path to the bam in the filtered counts not the raw.
Thanks

Hello @Sa753
Please use the assigned.bam. As I remember, I renamed this bam into the format of possorted_XXX.bam, so that velocyto doesn't resort it again.
And unzip the barcodes file generated by Cell Ranger Multi. Velocyto needs it to match the real cell numbers.

Hi hyjforesight,
Can I just clarify if the possorted_genome.bam that is produced from cellranger (not cell ranger multi) needs sorting or not?. Velocyto 10x run always sort it and the run takes around 10h and large amount of RAM?. Am I missing something here?.
Also, why should I unzip the barcode file from cellranger multi when Velcyto runs on the zipped barcode files from cell ranger without the need to unzip it?
Thanks

Hi hyjforesight,
I tried the above code and it is not working.. It can't find the barcodes.tsv file and when I added
-b  path to barcodes.tsv file . the error log was that it didn't understand the argument -b
again just to say, cell ranger multi doesn't produced possorted_XXX.bam.
Thanks

@Sa753
Could you please show me your folder contents in per_sample_outs folder?
This is the example of our Cell Ranger outputs, but I don't remember the contents in subfolder of CKP.


Update needed to CLI output for transactions to fix 2 issues

Describe the bug
Currently we have 2 issues the TXID is missing the first 2 characters
The link to explorer is not pointing to the current version of the explorer
This is what we get
{
txid: 'a5659553e404089f861efba24394268a1bfefbe2d44a1301d45e2505a8ce6c79',
transaction: 'https://testnet-explorer.now.sh/txid/0xa5659553e404089f861efba24394268a1bfefbe2d44a1301d45e2505a8ce6c79'
}
This is what we should get
{
txid: '0xa5659553e404089f861efba24394268a1bfefbe2d44a1301d45e2505a8ce6c79',
transaction: 'https://testnet-explorer.blockstack.org/txid/0xa5659553e404089f861efba24394268a1bfefbe2d44a1301d45e2505a8ce6c79'
}
To Reproduce
Steps to reproduce the behavior:

Go to the CLI
Send a a token send transaction
look at the output and you will see the 2 issues above

Expected behavior
{
txid: '0xa5659553e404089f861efba24394268a1bfefbe2d44a1301d45e2505a8ce6c79',
transaction: 'https://testnet-explorer.blockstack.org/txid/0xa5659553e404089f861efba24394268a1bfefbe2d44a1301d45e2505a8ce6c79'
}
Screenshots
If applicable, add screenshots to help explain your problem.
Terminal Log
If applicable, add console log to help explain your problem.

The 0x prefix in the TXID is just to indicate that the string is hexadecimal. I don't think we have agreement to make the prefix format standard. For example, Bitcoin does not prefix TXIDs with 0x. The prefix is added to the explorer URL though because that's what it expects.
Regarding explorer URL, we can update that. My understanding was that https://testnet-explorer.now.sh is the most up-to-date build. If that's not the case please provide the correct URL.

@yknl feels like having a consistent txid format would be beneficial. what do you think about that? should we spend some time agree on the format in all of our projects (part of eng best practices)?
The Explorer URL for production is https://testnet-explorer.blockstack.org/

Yes we should be consistent. My vote is for not including the 0x though. @zone117x @aulneau @hstove should chime in if they feel otherwise.

My preference is towards an explicit 0x for all hex strings. If you come across something displaying 447814 in the context of a block or transaction, what does it signify?
An integer block height? A truncated hash string?
If we always indicate hex with the prefix then we don't need special rules like "if the string is 64 chars or contains a-fA-F then omit 0x..."


fix: panel_button_control for ST 4

In ST 4, panel_button_control no longer works, use sidebar_button_control instead.
Having both for compatibility reason for ST 3.
Just copy panel_button_control classes and modify them into sidebar_button_control.
Related discussion: https://github.com/sublimehq/sublime_text/issues/3304#issuecomment-621230229

Thanks for helping. sidebar_button_control doesn't work with ST3. I added sidebar_button_control below panel_button_control expecting it works with ST4.

close because of https://github.com/poucotm/Guna/commit/874c7178474b77db2b3b52dcf38f9d5f7e50df0b


Typescript should be able to derive the type of the array created by Object.keys from the key signature of the object

TypeScript Version:  3.2.0-dev.201xxxxx

Search Terms:
object.keys
Code
type keys = 'one' | 'two'

const obj:{[key in keys]: string} = {
  one: 'value for one',
  two: 'value for two',
}

Object.keys(obj).forEach(key =>
  console.log(obj[key])
)

Expected behavior:
No error.
Actual behavior:
$ tsc --noImplicitAny test.ts
test.ts:9:15 - error TS7017: Element implicitly has an 'any' type because type '{ one: string; two: string; }' has no index signature.

9   console.log(obj[key])
                ~~~~~~~~

Playground Link:
Related Issues:

Duplicate of #26901 (any many others).

@ahejlsberg thanks for the additional context. If this isn't possible, could someone at least explain or link to what is the most idiomatic typescript in these situations?

@quinn If you are certain obj has no other enumerable properties you can assert that using a type assertion. Either of the following:
type Keys = 'one' | 'two';

const obj:{[key in Keys]: string} = {
  one: 'value for one',
  two: 'value for two',
};

Object.keys(obj).forEach(key => console.log(obj[key as Keys]));

(Object.keys(obj) as Keys[]).forEach(key => console.log(obj[key]));

@ahejlsberg using as fixed it, thank you! My assumption would be that if I somehow mutated the object to have a key other than 'one' or 'two' the fact that i have a defined type for the key [key in Keys] typescript would catch that.

and I definitely feel like i'm not doing something right if i ever need to use as. I really hate to rely on being certain myself rather than letting typescript to its thing.

So let's say you write
const obj = { x: 1, y: 2 };

keyof typeof obj has type "x" | "y"
It would be bad if TypeScript allowed a value "z" to appear in an expression typed as "x" | "y". But that's exactly what's at stake here:
type Point = { x: number, y: number };

function fn(x: Point) {
  // Proposal: make this *not* an error
  for (let k in x) printXorY(k);
}

function printXorY(key: keyof Point) {
  switch(key) {
    case "x":
      console.log("is x");
      break;
    case "x":
      console.log("is x");
      break;
    default:
      throw new Error("HOW IS THIS HAPPENING");
  }
}

const p3 = { x: 1, y: 2, z: 3 };
fn(p3); // oops


[Feature] Ability to block individual channels/tags from showing up anywhere

This would be like instagram/twitters block or mute features. One place that blocks them everywhere. I think this would probably go on the settings page? Not sure.
Also, what happens when I manually go to a claim that is by one of these channels? Add a warning message somewhere?
Just creating this to track discussion for now.

This would also include tags - I can see them being implemented together.

remaining changes:

change icon to slash (possibly slash plus circle)
change text to be word "manage" from settings
blur images from channels that are blocked

filter claim search


create an MQTT command to redefine the toe safety box parameters on the fly

Sometimes there's a need to extend the default toe safety box parameters due to the nature of the leg movement in the script. Rather than have to edit parameters and recompile to code, it would be better if there was a command that could be embedded in a script to supply new values for one or more of the default parameters, or to return to the default values set at compile time.
Proposed syntax:
SAFETY_BOX, XP, XM, YP, YM, ZP, ZM
where: the 6 numeric parameters are values for X, Y and Z local coordinate limitations in the positive ("P") and negative directions, and

if a value is 0, leave the previous setting untouched
if a value is -ve, return it to the default value set at compile time

example:
SAFETY_BOX, 0, 0, 8, 0, 0, 0
// let the leg go higher away from floor - up to 8 cm above the home position

It might have been nice to have this command be a short form FLOW command like the ones for cycle control. Unfortunately, there aren't enough numbers in that command, so we need a new one anyway.

Latest approach, first documented in issue 143:
numerical ordering of F_operation codes. The ordering facilitates selective treatment of short vs long flow commands and their arguments, and commands that affect a flow in real time, but don't completely prepare for next leg movements:
basic move commands, absolute vs relative to home / global or local
---- end of commands that prepare for next line, start of overhead commands (cycles, newhome, toesafety)
newHome with specified (global/local) coordinates in 18 numbers
---- end of commands with 18 numbers, start of short commands
newHome using current location
newHome using original home positions
toeSafety-X
toeSafety-Y
toeSafety-Z
toeSafetyReset
the 4 toeSafety related operation codes are all short form flow commands:
flow, 0, , new-X-plus-limit, new-X-minus-limit, 0, 0
flow ,0, , new-Y-plus-limit, new-Y-minus-limit, 0, 0
flow ,0, , new-Z-plus-limit, new-Z-minus-limit, 0, 0
flow ,0, , 0, 0, 0, 0
flow operation codes are defined in .../include/flows.h following the declaration of the f_operation flow array that holds their values.


Add a gradle subproject for scripts.

Add a gradle subproject for scripts. This migrates the shellcheck and black operations from GitHub actions to gradle tasks, which makes it easier to run these operations locally.
With this change, black and shellcheck are triggered via the check task, which is run by test. So running build at the root level will also run black and shellcheck on the scripts subproject, if that project is out of date.
To use this, you must have shellcheck installed at /usr/local/bin/shellcheck (which is where brew install shellcheck puts it), and black must be installed and on your PATH (using pip install black should do this).
Another nice thing about having a subproject for scripts is it makes it easier to configure IntelliJ to support python editing features for the .py files.
This change also adds python settings to .editorconfig.

Example build with shellcheck failure: https://github.com/DataBiosphere/terra-data-catalog/runs/6212722425?check_suite_focus=true

Should there be a ticket number for the PR?

I didn't think it was necessary since it's a change to how our checks are run (preserving current behavior, not adding new checks) and it was done "off the clock". But the reviewing has taken up more time than I thought it would, so maybe it should've had one.

I noticed a bunch of changes to python code here, I assume that's from Black? Otherwise I would probably say we should spin that out into separate PRs relating to the code cleanup, just to keep the diffs small and well contained.

I agree, I've reverted the file with the most python changes. I was thinking we'd want to follow PEP8 too but that's something to discuss as a team before making any changes.

Just out of curiosity, based on the conversations before, are there ways to set custom error messages with gradle? I was particularly wondering if, when we were using Pip to install Black, we could have it spit out a clean error message with the instructions for installing black if the error was that it wasn't found. Fully just for my own understanding though.

There's nothing built into gradle for this, as far as I can tell. It can be done by creating a custom task (which calls System.exec, or searches all locations in $PATH) and then making the downstream task depend on it. I think it would be hard to make it cache properly since the build environment isn't declared as a task input


Training

How can I can train on my own dataset?
You reference to skimage, but I don;t see anywhere in the code that you data augmentation with superpixel, did I miss something?

The superpixels are not enrolled in the training, instead, they are pre-computed before the second stage. I don't  write the code here, you can add it easily in the second stage as in DDFlow.

Thank you for the clarification.
On Wed, Apr 8, 2020, 15:25 Pengpeng Liu<EMAIL_ADDRESS>wrote:

The superpixels are not enrolled in the training, instead, they are
pre-computed before the second stage. I don't write the code here, you can
add it easily in the second stage as in DDFlow.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ppliuboy/SelFlow/issues/14#issuecomment-610928129,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACDB7A5KZ6BIQ5D7QYTBOITRLRUNFANCNFSM4LD2OIHA
.


Loading Axion Biosystems AXIS data

Hi!
Does spikeinterface support loading .raw or .spk formats of AXIS data? I don't see it in the docs, so I guess this format is not implemented.
Thanks!

Hi @alexmascension Neo does not support this format as far as I can see. Feel free to open a PR to add a corresponding IO to Neo, see the instructions for adding a new format.
As far as I know spikeinterface does not use Neo to load spiking data, so for the .spk files you will need to check with that project directly.

Hi @JuliaSprenger I'll open the PR then. Thanks!

@alexmascension do you know if there is a Python API to open Axion data?

I can't find it. They currently work with MATLAB files to load the data. I will try to contact them to see if they have some Python code for that (although I guess they won't).

In my lab someone have also this system.
Apparently the raw is a standard binary file, so you must specify manually the number of channel the sampling rate et the dtype.
In my case it was dtype=int16 8*64=512channels and sampling_rate = 12.5kHz.
I did not find any header in txt, json or xml format along sie the raw file.
I need to check with my colleague.

I ended up creating some scripts that do the job (you can find them here), although I guess that a better implementation can be done.


Update storage-quickstart-blobs-dotnet-legacy.md

Updating to point to the latest version as a note.

@Petermarcu : Thanks for your contribution! The author(s) have been notified to review your proposed change.

:LGTM:

I dont think I have permissions to merge so if this is signed off, can one of the admins merge?

#sign-off

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Petermarcu, can you please move the note down to after the first paragraph?

@Petermarcu @mhopkins-msft Hi, there's a new automated validation for Docs content that checks for the H1 as the first content after the metadata. We're manually applying this in the public repo. I've moved the note to below the H1. (There's another rule that says the H1 must be followed by an introduction.)
https://review.docs.microsoft.com/en-us/help/contribute/validation-ref/h1-not-first?branch=master
https://review.docs.microsoft.com/help/contribute/contribute-how-to-write-pull-request-quality-criteria?branch=master

@mhopkins-msft I'll wait to merge until you sign off again. Thanks.

@ktoliver, thank you for moving the note


No response object

Getting No response object error when trying to implement a flow something like,
Http In -> Twilio Contrib SMS node -> Http out.
The response object provided by the HTTP In node isn’t getting to the HTTP Response node.
Any suggestions? or Alternatives?

My guess is that the http in/http out nodes are not properly configured
Try testing the sms node with this sample flow first:
[
{
"id": "6648f34.726260c",
"type": "inject",
"z": "45dff058.1536",
"name": "",
"topic": "",
"payload": "",
"payloadType": "date",
"repeat": "",
"crontab": "",
"once": false,
"x": 231,
"y": 402,
"wires": [
[
"c539a5b2.3416d8"
]
]
},
{
"id": "c539a5b2.3416d8",
"type": "sms",
"z": "45dff058.1536",
"name": "sms",
"throttle": 1000,
"x": 392,
"y": 404,
"wires": [
[
"ebb326a5.367fc8"
]
]
},
{
"id": "ebb326a5.367fc8",
"type": "debug",
"z": "45dff058.1536",
"name": "",
"active": true,
"console": "false",
"complete": "false",
"x": 572,
"y": 402,
"wires": []
}
]

Inject/Debug are working fine. Could you provide me an example with http in/out nodes?


sf 2.8 testing

;)

https://i.imgflip.com/tr10a.jpg :D

Yep, and it worked :D
Had je er nochtans over gemailed @tvlooy


DDP expects same model across all ranks, but Rank 0 has 10 params, while rank 1 has inconsistent 16 params.

실험 6번 진행 중 오류 발생
실행 명령어
accelerate launch run_textbox.py --model=PTG --dataset=dd --model_path=facebook/bart-large --gpu_id=0,1 --find_unused_parameters=true

에러 로그
17 Jul 15:35    INFO ====== Finished training, best validation result at train epoch 2 ======
17 Jul 15:35    INFO Best valid result: score: 63.65, <bleu-1: 32.48>, <bleu-2: 31.17>, bleu-3: 33.93, bleu-4: 33.51, distinct-1: 2.82, distinct-2: 10.89, distinct-3: 18.18, distinct-4: 23.90
17 Jul 15:35    INFO Loading model structure and parameters from saved/PTG-dd-2023-Jul-17_12-19-22/checkpoint_best ...
[E ProcessGroupNCCL.cpp:821] [Rank 0] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=12163, OpType=ALLGATHER, Timeout(ms)=1800000) ran for 1802592 milliseconds before timing out.
17 Jul 16:05    ERROR Traceback (most recent call last):
  File "/workspace/TextBox/textbox/utils/dashboard.py", line 321, in new_experiment
    yield True
  File "/workspace/TextBox/textbox/quick_start/experiment.py", line 129, in run
    self._do_test()
  File "/workspace/TextBox/textbox/quick_start/experiment.py", line 110, in _do_test
    self.test_result = self.trainer.evaluate(self.test_data, load_best_model=self.do_train)
  File "/opt/conda/lib/python3.9/site-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
    return func(*args, **kwargs)
  File "/workspace/TextBox/textbox/trainer/trainer.py", line 478, in evaluate
    self.model = self.accelerator.prepare(self.model)
  File "/opt/conda/lib/python3.9/site-packages/accelerate/accelerator.py", line 1199, in prepare
    result = tuple(
  File "/opt/conda/lib/python3.9/site-packages/accelerate/accelerator.py", line 1200, in <genexpr>
    self._prepare_one(obj, first_pass=True, device_placement=d) for obj, d in zip(args, device_placement)
  File "/opt/conda/lib/python3.9/site-packages/accelerate/accelerator.py", line 1027, in _prepare_one
    return self.prepare_model(obj, device_placement=device_placement)
  File "/opt/conda/lib/python3.9/site-packages/accelerate/accelerator.py", line 1295, in prepare_model
    model = torch.nn.parallel.DistributedDataParallel(
  File "/opt/conda/lib/python3.9/site-packages/torch/nn/parallel/distributed.py", line 655, in __init__
    _verify_param_shape_across_processes(self.process_group, parameters)
  File "/opt/conda/lib/python3.9/site-packages/torch/distributed/utils.py", line 112, in _verify_param_shape_across_processes
    return dist._verify_params_across_processes(process_group, tensors, logger)
RuntimeError: DDP expects same model across all ranks, but Rank 0 has 10 params, while rank 1 has inconsistent 16 params.

[E ProcessGroupNCCL.cpp:456] Some NCCL operations have failed or timed out. Due to the asynchronous nature of CUDA kernels, subsequent GPU operations might run on corrupted/incomplete data.
[E ProcessGroupNCCL.cpp:461] To avoid data inconsistency, we are taking the entire process down.
terminate called after throwing an instance of 'std::runtime_error'
  what():  [Rank 0] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=12163, OpType=ALLGATHER, Timeout(ms)=1800000) ran for 1802592 milliseconds before timing out.
ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: -6) local_rank: 0 (pid: 932) of binary: /opt/conda/bin/python
Traceback (most recent call last):
  File "/opt/conda/bin/accelerate", line 8, in <module>
    sys.exit(main())
  File "/opt/conda/lib/python3.9/site-packages/accelerate/commands/accelerate_cli.py", line 45, in main
    args.func(args)
  File "/opt/conda/lib/python3.9/site-packages/accelerate/commands/launch.py", line 950, in launch_command
    multi_gpu_launcher(args)
  File "/opt/conda/lib/python3.9/site-packages/accelerate/commands/launch.py", line 642, in multi_gpu_launcher
    distrib_run.run(args)
  File "/opt/conda/lib/python3.9/site-packages/torch/distributed/run.py", line 753, in run
    elastic_launch(
  File "/opt/conda/lib/python3.9/site-packages/torch/distributed/launcher/api.py", line 132, in __call__
    return launch_agent(self._config, self._entrypoint, list(args))
  File "/opt/conda/lib/python3.9/site-packages/torch/distributed/launcher/api.py", line 246, in launch_agent
    raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
====================================================
run_textbox.py FAILED
----------------------------------------------------
Failures:
  <NO_OTHER_FAILURES>
----------------------------------------------------
Root Cause (first observed failure):
[0]:
  time      : 2023-07-17_16:05:27
  host      : 2c2e0baec811
  rank      : 0 (local_rank: 0)
  exitcode  : -6 (pid: 932)
  error_file: <N/A>
  traceback : Signal 6 (SIGABRT) received by PID 932
====================================================

다시 실행시키면 해결됨


[Documentation] Update "README.rst" to reflect beartype's hard-earned support for pyright 😄

https://github.com/beartype/beartype#under-vscode currently tells users to disable pylance in order to use beartype, which is no longer necessary: beartype now valiantly supports mypy and pyright! ❤

Gah! Thanks a heap for the gentle reminder that demonstrable badness is still afoot in our README.rst. I'd meant to excise away that entire subsection. It's unnecessarily combative, which is a bad look for @beartype in 2022. It's also embarrassingly wrong to push VSCode's mypy extension, when doing so pathetically slows VSCode to a crawl and when mypy is arguably less accurate than pyright in common use cases and painfully broken in others (e.g., recursive type hints).
Sadly, this got pushed under the rotten rug in our feverish push to release beartype 0.11.0. Thankfully, we have a brief reprieve before the madness resumes. I still need to actually document everything everyone did for beartype 0.11.0. So, this is now the first action item on that list!
Thanks again for helping us out of the pit of bad documentation that we have dug. :grin:

Resolved by 430065b. Our existing FAQ entry on VSCode has been fundamentally rewritten from the ground up to be considerably more charitable to pyright, whose stupefying speed justifies its default usage in Pylance.
Thanks so much for the gentle reminder, @rsokl. You make AI happen. Hopefully, not scary AI.


Inconsistency in Uint128 api for overflow/underflow behaviour

Add use default + operator under the hood, while Sub use checked_sub.
I think it would be better to keep is consistent with rust std's behaviour:

default operator +/-, panic when wrapping.
add methods for explicit checked_*/wrapping_*/saturating_* operations.

Thank you for bringing this up. Good point. I'll check with Ethan, who originally created the Underflow error case to find a way tht is consistent.
Panics in smart contracts are a bit problematic because they are very hard to debug. Your code is terminated but there is no error message or stack trace available.

I think it might already cause overflow issues in the example contracts like: https://github.com/CosmWasm/cosmwasm-plus/blob/master/contracts/cw20-base/src/contract.rs#L132
I guess adding the explicit methods like checked_*/wrapping_*/saturating_* is less controversial.
then we need to decide on the default behavior of the operators.


 Use a spec "
                    f"for the mock if {name!r} is meant to be an attribute.")
E               AttributeError: 'called_once_with' is not a valid assertion. Use a spec for the mock if 'called_once_with' is meant to be an attribute..  Use a spec "
                    f"for the mock if {name!r} is meant to be an attribute.")
E               AttributeError: 'called_once_with' is not a valid assertion. Use a spec for the mock if 'called_once_with' is meant to be an attribute..  Use a spec "
                    f"for the mock if {name!r} is meant to be an attribute.")
E               AttributeError: 'called_once_with' is not a valid assertion. Use a spec for the mock if 'called_once_with' is meant to be an attribute.. Did you mean: 'assert_called_once_with'?

/nix/store/l014xp1qxdl6gim3zc0jv3mpxhbp346s-python3-3.12.4/lib/python3.12/unittest/mock.py:663: AttributeError
=========================== short test summary info ============================
FAILED tests/unit/test_bootloader.py::test_get_uid_for_known_family_reads_at_correct_address[F1] - AttributeError: 'called_once_with' is not a valid assertion. Use a spec for...
FAILED tests/unit/test_bootloader.py::test_get_uid_for_known_family_reads_at_correct_address[F3] - AttributeError: 'called_once_with' is not a valid assertion. Use a spec for...
FAILED tests/unit/test_bootloader.py::test_get_uid_for_known_family_reads_at_correct_address[F7] - AttributeError: 'called_once_with' is not a valid assertion. Use a spec for...
========================= 3 failed, 46 passed in 0.88s =========================
/nix/store/1r32fki5z5ivgaikgh8pq0r6vz3b0jpj-stdenv-linux/setup: line 1655: pop_var_context: head of shell_variables not a function context

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] 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

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.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

[x] Fits CONTRIBUTING.md.

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

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

4 packages built:

python311Packages.stm32loader
python311Packages.stm32loader.dist
stm32loader (python312Packages.stm32loader)
stm32loader.dist (python312Packages.stm32loader.dist)


Review overview/process

The document I believe is outdated, refers to using XML files and deploying with Device Configuration profiles rather than the new Endpoint Security profiles. Also, multiple settings now available in settings catalog profile types vs existing "Templates" based Device Configuration profiles. Overview table contains links to other articles that are then not mentioned in the steps below, causing confusion on best practice for deploying Defender to macOS.

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

ID: cd66a255-36e5-29dc-7610-d50ef8bca3f3
Version Independent ID: 17375473-bc07-f8e5-a85f-d732bbba3d71
Content: Intune-based deployment for Microsoft Defender for Endpoint on Mac
Content Source: microsoft-365/security/defender-endpoint/mac-install-with-intune.md
Service: microsoft-365-security
Sub-service: mde
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@Dansimp Please help us in resolving this issue. Thanks

Agreed. I personally think this document is a little confusing in current form. The summary table and the more detailed steps below the table deviate in at least three ways that I spotted....

The summary table includes the "Configure Microsoft AutoUpdate" which then isn't in the steps below the table.
(Resolution would presumably be to add this to the steps below table too.)

The table also has the XML type of "Microsoft Defender for Endpoint Configuration Settings", but in the steps below, they talk about the Configuration Profiles instead (which I think is the correct method maybe?).
(Resolution would presumably be to change Defender Configuration Settings line in the summary table to mention Configuration Profiles instead of XML method).

Finally, you have added the new Background Services step to the steps below the table, but this doesn't have a summary entry in the table.
(Resolution would presumbaly be to add this as a line on the summary table too).

I am only just trying to decipher how this is all meant to work, so I am far from being an expert in this... so there is a reasonable chance my suggested resolutions above are not correct, but hopefully they at least help clarify what I believe needs looking at, even if the correct solution is actually different to my suggestion. Someone more knowledgable than me should be able to rectify it correctly.
Also, I'm glad to see that someone has fixed the wording a names for the Background Services section recently. Just before Christmas I was scratching my head, as that section had clearly been copy-pasted from the Notifications section, but hadn't been edited fully. (Maybe I just happened to be studying the page mid-edit, but glad to see that has been fixed already as that added to the confusion a few weeks ago!).
Hope this helps you to imprive the page.

Image link in step Assign devices on the Assignment tab. Click Next. is wrong
Current:
source="images/mdatp-6-systemconfigurationprofiles-2.png"
Expected:
source="images/mdatp-6-systemconfigurationprofiles-3.png"
Similar for the next step Open Devices > Configuration profiles, you can see your created profile there.
Current:
source="images/mdatp-6-systemconfigurationprofiles-3.png"
Expected:
source="images/mdatp-6-systemconfigurationprofiles-4.png"

Full disk access section might contain a wrong word as well. In the last sentence it should be:
"and downloaded fulldisk.mobileconfig as Configuration profile name file."

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


Unused cases in a switch do not trigger warnings

Consider those two elaboratables:
class Impl1(Elaboratable):
    def __init__(self):
        self.sel = Signal()
        self.A = Signal()
        self.B = Signal()

    def elaborate(self, platform):
        m = Module()

        with m.Switch(self.sel):
            with m.Case():
                m.d.comb += [
                    self.A.eq(1),
                    self.B.eq(1),
                ]
            with m.Case(0):
                m.d.comb += [
                    self.A.eq(1),
                    self.B.eq(0),
                ]
            with m.Case(1):
                m.d.comb += [
                    self.A.eq(0),
                    self.B.eq(0)
                ]

        return m

class Impl2(Elaboratable):
    def __init__(self):
        self.sel = Signal()
        self.A = Signal()
        self.B = Signal()

    def elaborate(self, platform):
        m = Module()

        with m.Switch(self.sel):
            with m.Case(0):
                m.d.comb += [
                    self.A.eq(1),
                    self.B.eq(0),
                ]
            with m.Case(1):
                m.d.comb += [
                    self.A.eq(0),
                    self.B.eq(0)
                ]
            with m.Case():
                m.d.comb += [
                    self.A.eq(1),
                    self.B.eq(1),
                ]

        return m

Because the default/wildcard case was declared first in Impl1, it prevents Case(0) and Case(1) from being matched. This is a bit misleading for newbies who would expect cases to be position agnostic (and therefore Impl1 having equivalent behaviour as Impl2).
As discussed on IRC, a sensible way of dealing with that issue would be to trigger warnings whenever some cases are unreachable. We still have to figure out how we can silence those warnings when they are undesired (think code generation).

I've submitted a PR. To enabling filtering out the warning I propose declaring a new warning type, which could then be ignored.

I've submitted a PR.

Sorry but any attempt to fix this issue (or any other issue that touches language features) is premature until we actually agree on the design. I prefer to have no fix at all to a careless fix that negatively impacts downstream.

To enabling filtering out the warning I propose declaring a new warning type, which could then be ignored.

I don't like the solution of explicitly disabling lints by name. Sometimes it's unavoidable, sure, like in case of UnusedElaboratable, but for syntactic lints my preference is to allow silencing the lint through the use of an idiomatic but more verbose pattern. Take a look at _check_signed_cond to see what I mean here.

We had a discussion about this issue on IRC: https://freenode.irclog.whitequark.org/nmigen/2020-06-16#1592311000-1592313032;
Long story short, the issue goes much further than just checking the position of the default case. We should actually check for unreachable cases in a switch (which covers the default cases being in first position, but also other scenarios), but we shouldn't forget that in some applications (eg. generated code) those checks are unneeded and for those situations we should let the user disable those warnings.

Sorry but any attempt to fix this issue (or any other issue that touches language features) is premature until we actually agree on the design. I prefer to have no fix at all to a careless fix that negatively impacts downstream.

The purpose was mainly to get something started.

I don't like the solution of explicitly disabling lints by name. Sometimes it's unavoidable, sure, like in case of UnusedElaboratable, but for syntactic lints my preference is to allow silencing the lint through the use of an idiomatic but more verbose pattern. Take a look at _check_signed_cond to see what I mean here.

I am not sure if I parse this correctly. Warnings are very easy to suppress, actually more than anything you could ever do programmatically. But you can build something directly, or on top of the warnings module, it does not make much difference here. The benefits of using the warnings module is that we would not have to care about the warning suppression in the code that is issuing them. Anyway, there is no need for me to try being a perfectionist and force you to spend some of your time arguing about the technicalities of the implementation, so I will not pick this battle.
Can you describe the mechanism you had in mind? Or do you prefer to implement it yourself?

The purpose was mainly to get something started.

The life of a language feature does not start with code.

Can you describe the mechanism you had in mind?

The specific mechanism for disabling the warnings for unreachable cases, or the general approach? The general approach can be seen in _check_signed_cond. The specific mechanism for unreachable cases is something I don't know yet, and which we can work out in this issue.

Or do you prefer to implement it yourself?

There can be no implementation until there is a design! Which is what this issue is about.

The specific mechanism for disabling the warnings for unreachable cases, or the general approach?

The mechanism to disable the warnings.

The specific mechanism for unreachable cases is something I don't know yet, and which we can work out in this issue.

I was thinking we could just do it when exiting the context manager. This is what makes the most sense to me.

Ah sorry, I was unclear earlier. I meant that I don't know yet what kind of user-visible mechanism there should be to disable the warnings for unreachable cases, and that we should discuss that. It doesn't really matter at this point how the logic of emitting the warnings should be implemented—in general until the design is done I don't care at all about the implementation in cases where it's clear that some reasonable implementation is possible.

Okay, what do you want to do?
I proposed declaring a new warning type which could then be filtered. We can declare a warning type for these cases and then subclass the specific warnings from there. Warnings are easily filterable, but we can even provide a helper function to do just that if you want. This is what I was proposing above, I am not sure if it was clear enough. You didn't seem to be a fan of my approach.

Just a note. I am not knowledgable enough in the code structure to propose a direct way to do this in the code, so you'll have to be the one providing an option.

I'm not expecting you to propose any way to do this in the code! Implementation is secondary to the interface; until we decided on the interface it doesn't even make sense to talk about the implementation for the most part.
Anyway, let's see which options we have for the interface used to suppres the warning:

Using Python's warnings module. This has the advantage that it's semi-standard. The drawbacks are that it increases rightward drift of code (due to the with warnings.catch_warnings statement) and that Python's catch_warnings function is broken in multithreaded applications, as the documentation admits. Because of the last point I think it should never be used outside of tests.
Using an explicit keyword argument for with m.Case():. Since it's just our own code it doesn't suffer from problems of (1). This has the drawback that it's not composable: the m.Case interface gains a new argument whose meaning doesn't directly affect the semantics of the code. If we end up with a lot more lints, we'll have a lot more of such arguments, and that sounds like it would make the language harder to learn. But maybe that's okay.
Adding a context manager that configures nMigen's existing linter, and extend this linter (which currently just exists to suppress the UnusedElaboratable warning) to make it possible to suppress other warnings too. In effect this would create something similar to Rust's #[allow]/#[deny]/#[warn] mechanism.

Both (2) and (3) seem generally alright, with a weak preference for (3). If we go with (2) this issue is easy to fix; (3) will need further design work to figure out how linter options should be configured.

Of course there can be other possible strategies that I'm missing, so anyone reading these comments is welcome to suggest alternatives.

I have a preference towards 3). Can you point me to the linker code?

Sure, search for _linter in nmigen._utils and nmigen._unused. The current implementation is extremely bare-bones (it basically exists to make it bearable to write tests that create and then don't simulate elaboratables), so first we'd need to design an interface that would accommodate this issue (at the very least it should be possible to disable lints per lexical scope, and we should probably do something about the rightward drift too).

I've filed an RFC https://github.com/nmigen/nmigen/issues/436 to discuss this.

Looking over this again, there is basically no reason to ever have cases after with m.Case(); if you programmatically generate cases it's trivial to break from the loop, and if you don't then this could potentially find bugs in the code generator.
Sorry @FFY00, I think I wasn't feeling very well when first looking at the issue and didn't approach it in the most constructive way. I'll add this functionality taking your PR as a base.

Discussed on the 2023-02-06 weekly meeting, with no conclusion reached beyond no one objecting to catching common cases of this issue without a full exhaustiveness check.
In my view, there are three intersecting issues at play here:

Exhaustiveness checking, undoubtedly useful (and already tracked at #451) but difficult to implement in the general case. Even a limited implementation of exhaustiveness checking requires a linter override, which we currently don't have an interface for (#360, #436); if you end up with lints that are false positives and that you can't turn off, people learn to ignore them, which is very bad.
It's easy to make a typo and end up with with m.Case(): unintentionally, which looks like with m.Case(0) and is easy to overlook. This is why we have with m.Default():. However it's tricky to warn on a literal m.Case() since it's only distinct at the call site from something like m.Case(*[]), and the latter should be allowed in metaprogrammed code.
Novice Amaranth designers not recognizing that with m.Switch(): is a priority-case statement. An exhaustiveness check (1) would quickly clarify that when used on code like the one in this issue, but it seems like a tall order to require a full exhaustiveness check to catch something that isn't even about exhaustiveness.

Even if we implement (1) we still should do something about (2) since an exhaustiveness check will say nothing about an m.Case(): at the end of a switch.
The key difficulty here is the lack of a linter interface, which I don't think will get better any time soon. So I'm focusing on solutions that avoid it. One such solution is always emitting a warning for a literal m.Case(), and then emitting a warning if there are any cases past m.Default() specifically (but not m.Case(*[]), as would be in metaprogrammed code). These checks will have no false positives and therefore we don't need to turn them off.

Now that m.Default(): and m.Case(): mean two separate (opposite, in fact) things, we can solve this by warning on any case that comes after m.Default():, without any of the complex proposed mechanisms.


[macOS - Web] Hot restart resets URL.

Code: https://github.com/flutter/uxr/blob/master/nav2-usability/scenario_code/lib/deeplink-pathparam/router.dart
Steps:

run
click to change the page
press 'r' in terminal or the hot refresh button in the IDE

The page will change to '/'. This has been happening in macOS since always. I talked with some people and this works in Windows and Ubuntu. Only mac is affected.
FAIL - macOS (Channel beta, 2.2.0-10.3.pre, on macOS 11.3 20E232
darwin-x64)
https://user-images.githubusercontent.com/351125/118549624-1eec9100-b732-11eb-84c4-7e2e1653dc53.mov
WORKS - ubuntu (Channel stable, 2.0.6)

Thanks for the detailed report. Verified this using latest master and see the same behavior on Mac.

 flutter doctor -v
[✓] Flutter (Channel master, 2.3.0-2.0.pre.253, on Mac OS X 10.15.4 19E2269
    darwin-x64, locale en-GB)
    • Flutter version 2.3.0-2.0.pre.253 at
      /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision bac5a0db3b (5 hours ago), 2021-05-18 10:19:03 +0800
    • Engine revision 3cda7f5807
    • Dart version 2.14.0 (build 2.14.0-119.0.dev)

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.55.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • Mac OS X 10.15.4 19E2269
      darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 90.0.4430.212

! Doctor found issues in 1 category.

This is present on all OSs with either Router API or "Navigator 1.0" and it was not present in stable 2.0.6. I'm not sure when exactly did it break, but is still present on master.
I would say this is a duplicate of #79241

Deduplicating with https://github.com/flutter/flutter/issues/79241


Failed to Set up, Check the logs - But still works

From the integrations page I get a message saying that Music Assistant Failed to setup and to check the logs. I then tried to play media through Music Assistant and everything worked as expected.  I am running 2022.6.1 The logs showed this error message:
Logger: homeassistant.config_entries
Source: custom_components/mass/init.py:167
Integration: Music Assistant (documentation, issues)
First occurred: 4:28:07 PM (1 occurrences)
Last logged: 4:28:07 PM
Error setting up entry Music Assistant for mass
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 339, in async_setup
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/mass/init.py", line 167, in async_setup_entry
if player_id not in entry.options[CONF_PLAYER_ENTITIES]:
KeyError: 'player_entities'

I think you ran into a so called "race condition" and you will not see this error again but that you reported it so I can fix it. Thanks!

fixed in 2022.6.2


Sprint2/sm130

Added HTTP GET for rotations
Fixed SQL Database Code
Updated Naming conventions

Codecov Report
Patch coverage: 8.33% and project coverage change: -4.41 :warning:

Comparison is base (b92bf42) 43.75% compared to head (e188a06) 39.34%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #19      +/-   ##
==========================================
- Coverage   43.75%   39.34%   -4.41%
==========================================
  Files           8       10       +2
  Lines         160      183      +23
==========================================
+ Hits           70       72       +2
- Misses         90      111      +21

Impacted Files
Coverage Δ

src/endpoints.rs
100.00% <ø> (ø)

src/endpoints/events/event_file.rs
0.00% <0.00%> (ø)

src/endpoints/notes.rs
41.81% <ø> (ø)

src/endpoints/rotations/rotation_files.rs
0.00% <0.00%> (ø)

src/endpoints/rotations.rs
18.18% <18.18%> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add support for Materialized Views

The documentation does mention that Views are not supported. It looks like Materialized Views are also not supported, though they are more like tables than views. We can create indexes, they contain data etc.

It's unfortunately not the straight forward (think webs of dependencies), but I do intend to add support for them and have a mental model in my head as to how I will achieve it. I first would like to refactor the SQL generation a bit before I implement (materialized) views.


HADOOP-18039. Upgrade hbase2 version and fix TestTimelineWriterHBaseDown

Description of PR
As mentioned on HADOOP-17668, we can't upgrade hbase2 profile version beyond 2.2.4 until we either have hbase 2 artifacts available that are built with hadoop 3 profile by default or hbase 3 is rolled out (hbase 3 is compatible with hadoop 3 versions only).
This PR is to upgrade hbase2 profile version to 2.2.4 and also fix TestTimelineWriterHBaseDown to create connection only after mini cluster is up.
How was this patch tested?
Local testing.
For unit testing, here is the test result with hbase2 profile:
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.apache.hadoop.yarn.server.timelineservice.reader.TestTimelineReaderWebServicesHBaseStorage
[INFO] Tests run: 33, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 29.996 s - in org.apache.hadoop.yarn.server.timelineservice.reader.TestTimelineReaderWebServicesHBaseStorage
[INFO] Running org.apache.hadoop.yarn.server.timelineservice.storage.TestTimelineWriterHBaseDown
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 33.288 s - in org.apache.hadoop.yarn.server.timelineservice.storage.TestTimelineWriterHBaseDown
[INFO] Running org.apache.hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageApps
[INFO] Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 33.485 s - in org.apache.hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageApps
[INFO] Running org.apache.hadoop.yarn.server.timelineservice.storage.TestTimelineReaderHBaseDown
[INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 201.434 s - in org.apache.hadoop.yarn.server.timelineservice.storage.TestTimelineReaderHBaseDown
[INFO] Running org.apache.hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageSchema
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 59.86 s - in org.apache.hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageSchema
[INFO] Running org.apache.hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageDomain
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 27.672 s - in org.apache.hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageDomain
[INFO] Running org.apache.hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageEntities
[INFO] Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 30.734 s - in org.apache.hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageEntities
[INFO] Running org.apache.hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowActivity
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 34.285 s - in org.apache.hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowActivity
[INFO] Running org.apache.hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowRunCompaction
[INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 38.799 s - in org.apache.hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowRunCompaction
[INFO] Running org.apache.hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowRun
[INFO] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 68.664 s - in org.apache.hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowRun
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 103, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  09:33 min
[INFO] Finished at: 2021-12-08T19:32:42+05:30
[INFO] ------------------------------------------------------------------------

For code changes:

[X] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 39s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
12m 49s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
21m 39s

trunk passed

+1 :green_heart:
compile
21m 50s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
19m  9s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
3m 37s

trunk passed

+1 :green_heart:
mvnsite
1m 26s

trunk passed

+1 :green_heart:
javadoc
1m 21s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 17s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+0 :ok:
spotbugs
0m 43s

branch/hadoop-project no spotbugs output file (spotbugsXml.xml)

+1 :green_heart:
shadedclient
20m 36s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 29s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m 34s

the patch passed

+1 :green_heart:
compile
21m 14s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
21m 14s

the patch passed

+1 :green_heart:
compile
19m  9s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
19m  9s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
3m 35s

the patch passed

+1 :green_heart:
mvnsite
1m 25s

the patch passed

+1 :green_heart:
xml
0m  3s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
1m 16s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 16s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+0 :ok:
spotbugs
0m 38s

hadoop-project has no data from spotbugs

+1 :green_heart:
shadedclient
20m 52s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
0m 37s

hadoop-project in the patch passed.

+1 :green_heart:
unit
14m 29s

hadoop-yarn-server-timelineservice-hbase-tests in the patch passed.

+1 :green_heart:
asflicense
0m 59s

The patch does not generate ASF License warnings.

198m  2s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3768/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3768

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell xml spotbugs checkstyle

uname
Linux 6b089725be82 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 38fbe6959c6453d0d08b58a58ea29c1d862cb8db

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3768/1/testReport/

Max. process+thread count
820 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase-tests U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3768/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

@aajisaka @ayushtkn Could you please take a look?

Merged. Thank you @virajjasani and @ayushtkn.


added selection sort in java

check if its okay and let me know!

okk thanks for review!

may you have a look now


improvement: add specific tags for service utils release

tagging 0.0.184-service-utils will just release service-utils
tagging 0.0.184-cli will just release the cli and publish packages
tagging 0.0.184-fern-typescript will just release the fern-typescript generator

https://www.notion.so/usebirch/Assembly-Line-Decomp-ae1c6297feee4e89b83e25a1997c22f8 eventually we can have a UI to manage this

@dsinghvi this is OBE with the new fern-ts repo right?


Facial Emotion Detection

Description
Added facial emotion detection
Fixes #624
Type of change

[ ] Added a new machine learning frameworks, libraries or software.
[yes ] Documentation update

Checklist:

[y ] My code follows the style guidelines of this project
[y ] I have performed a self-review of my own code
[y ] I have commented my code, particularly in hard-to-understand areas
[y] I have made corresponding changes to the documentation
[ y] My changes generate no new warnings

@sanjay-kv sir can you please merge it i want to update my branch for another issue