[NFC] [AutoDiff] Minor cleanup.

Set default true for -enable-experimental-differentiable-programming flag
on tensorflow branch. The default will be false on master.
Rename unit test to AutoDiffIndexSubset.cpp, since AutoDiffIndexSubset is
the tested data structure.

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow

Looks like you didn't change CMakeLists.

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow


BackgroundAudio Sample Fail to play audio

Can't play an audio file when running against Local Machine or Simulator.
Running against WP Emulator works though.
Failing in StartBackgroundAudioTask in Scenario1.xaml.cs on the following line:
bool result = backgroundAudioTaskStarted.WaitOne(10000);

The result is always false.
Running on Windows 10 Pro Insider Preview 10074 (Visual Studio 2015 RC)

Hi Christian, thanks for reporting this. I suspect it's due to an issue with the background task not starting up on x86 architectures in that Windows 10 build. Do you have an x64 machine you can target to confirm whether it works there?

Hi Aaron, yes it works when I change target to x64.
Thanks!

Hi again Aaron, can't get my own project to work.
Not even on WP emulator. There is'nt an issue with the background task not starting up on VB.NET projects?

Great! Thanks for confirming x64 worked in the sample. Support for x86 on x64 is on the way.
Language shouldn't make a difference. Can you tell me more about your VB project configuration? Did you convert it to a Windows Universal project? Check also that you updated your Package.appxmanifest file to include the required task extensions.
      <Extensions>
        <Extension Category="windows.backgroundTasks" EntryPoint="BackgroundAudioTask.MyBackgroundAudioTask">
          <BackgroundTasks>
            <Task Type="audio" />
          </BackgroundTasks>
        </Extension>
      </Extensions>

Created a Windows Universal Solution from scratch on 10.0.10030.0
I then installed Visual Studio 2015 RC and changed to 10.0.10069.0
When I debug the sample, I run it, put a breakpoint in CastsBackgroundAudioTask.Run method and suspend the app through Lifecycle Events which will put me in the Run method of the background task.
If I do the same in my project nothing happens when I suspend the App. The background task is never invoked.
Here are the Projects:
CASTS_BACKGROUNDAUDIO (Windows Runtime Component)
Assembly name: CASTS_BACKGROUNDAUDIO
Default namespace: CASTS_BACKGROUNDAUDIO
Background task class: CastsBackgroundAudioTask
CASTS_UAP (APP)
Has reference to CASTS_BACKGROUNDAUDIO project
Package.appxmanifest:
<Extensions>
  <Extension Category="windows.backgroundTasks" EntryPoint="CASTS_BACKGROUNDAUDIO.CastsBackgroundAudioTask">
    <BackgroundTasks>
      <Task Type="audio" />
    </BackgroundTasks>
  </Extension>
</Extensions>

Don't know what can be the problem, I hade a Silverlight App previously which I could make work.
Thanks for the help!

I created a new solution with only the basics, tried to suspend the app for it to break in the Run method but nothing. The solution is here: http://1drv.ms/1F8fGIV

Strange, when I suspend the sample now it will not break in the Run method.
What is triggering the Background task to Run?

Got it to work!
Had to create a new solution and projects.
Don't know why it didn't work with my previous solution, I used the same code.

Yay! There may have been some project template changes between 10030 and 10069 that just creating a new project resolved. Glad to hear that worked for you!


Update simpleio.tone to match 3.x audioio api

simpleio.tone is using a previous audioio API. We need to update it to check the version number, use the 3.x+ audioio API, and if it finds 2.x, to use the previous API. See https://github.com/adafruit/Adafruit_CircuitPython_CircuitPlayground/blob/master/adafruit_circuitplayground/express.py#L622 for an example of using version numbers to utilise multiple APIs in a single funciton.
The issue is here: https://github.com/adafruit/Adafruit_CircuitPython_SimpleIO/blob/master/simpleio.py#L57
This will need to be tested by using simpleio.tone to produce a tone using a non-PWM pin.

See #36

Fixed, thank you!


test.py is empty

The test.py file is empty. It should be removed from the repository to avoid confusion.

Thanks @quantumgizmos!


Fix data corrupted issue when loading from UFS

This fixes a bug in corrupted data files.
Previously,  https://github.com/Alluxio/alluxio/pull/17497 attempt to solve this issue but only covers the case when creating a UFS reader Notice we only handle block reader. So this may not fix paged Block Reader in 2.x
Please clarify why the changes are needed. For instance,

If you propose a new API, clarify the use case for a new API.
If you fix a bug, describe the bug.

Please list the user-facing changes introduced by your change, including

change in user-facing APIs

addition or removal of property keys

webui
   pr-link: Alluxio/alluxio#18525
   change-id: cid-bbba0feb29231e70750e5e79da5f405bb591d47a

What changes are proposed in this pull request?
Please outline the changes and how this PR fixes the issue.
Why are the changes needed?
Please clarify why the changes are needed. For instance,

If you propose a new API, clarify the use case for a new API.
If you fix a bug, describe the bug.

Does this PR introduce any user facing changes?
Please list the user-facing changes introduced by your change, including

change in user-facing APIs
addition or removal of property keys
webui

alluxio.master.journal.raft.SnapshotReplicationManagerTest not related to the changes

alluxio-bot, force-merge this please

alluxio-bot, force-merge this please


Fix of show accounts dropdown when transition is ended by backpressed issue #117

emove onTransitionEnd listener after it is called to avoid username.showDropDown() be called on end transition by backpressed

Thanks for the fix!


I Want Change Color of Line but error is coming

I make one horizontal line and want to change color of line. but error is coming
using IPresentation source = SCPresentation.Create();
var slide1 = source.Slides[0].Shapes;
    var horizontalLine1 = slide1.AddLine(startPointX: 60, startPointY: 100, endPointX: 5000, endPointY: 100);
    if (horizontalLine1 != null)
    {
        horizontalLine1.Width = 2300;
        horizontalLine1.Height = 0;
        horizontalLine1.Outline.Weight = 10;
        //horizontalLine1.Fill.SetColor("#f8de7e");
        var fill = horizontalLine1.Fill;
        fill.SetColor("#f8de7e");  // here System.NullRefrenceException is coming.
    }

error is coming

Another approach I tried But not able to set Color of horizontal line
    var slideMaster1= source.Slides[0];

var lineShape= (IAutoShape)slideMaster1.Shapes.Where(sp=>sp.Name == horizontalLine1.Name).FirstOrDefault();
var l1 = lineShape.Outline;
    l1.Weight = 10;
    l1.Color = "#f8de7e";
    lineShape.Fill.SetColor("#f8de7e");

horizontalLine1.Fill is null because of Shape Fill is not available for lines:

Here is how you can change line color:
...
horizontalLine1.Outline.Color = "f8de7e";

Don't forget to skip leading # of hex string.


Pandora module changes

These are Pandora's module changes we are testing.

Cool, thanks guys.
Changed functionality can be implemented system-wide, I'll update the Jinjta template.
The write module is in my blacklist of things to not generate and I wasn't bright enough to leave a note as to why I excluded it. I'll follow up on that.
I'll regen this evening and merge updated modules provided tests pass.
Thanks again.


NEON_FLT_SP and ALTIVEC float32x4 implementation of sqrt(0) returns NaN

the formula for these appears to use the 1/sqrt(a) estimate operation, which presumably results in Inf for a=0. Probably need to explicitly check for a==0 and mask result accordingly.

Agreed, thanks for the report.


Update why.mdx

Fix typo
Closes
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

Thanks for the PR, would you mind following these instructions https://react-spectrum.adobe.com/contribute.html#contributor-license-agreement then closing and reopening the PR?

Hi Robert, sorry I missed the agreement part. Now it seems to be OK.
HTH,
Artur


Autocomplete: ability to configure when to show the suggestions float

It would be a good improvement to be able to configure, when writing, the quantity of keystrokes needed to show the suggestion float. For example, after three keystrokes.

Resolved in #1329


Minikube as local development solution for Helm charts

Minikube as local development solution for Helm charts.
This is an epic issue, which will have several other issues associated with it.

related to #3067


Problems with custom MFM sync words [Amiga]

Original report by Matti Immonen on Facebook is failure to load Hybris (SPS IPF 1457) on a stock A500 with TEAC FD-235F-161-U after writing the IPF to disk using GW v0.15 and a Sony MPF920 drive. Many other IPFs (including the slightly tricky Xenon 2, SPS IPF 2234) loaded fine on the same test system. Additionally, an earlier conversion of the IPF to HFE (using HxC tools) loaded fine on the same test system using FlashFloppy/Gotek.
The cause is apparently the use of custom sync words with MFM-invalid sequences of zeroes. Matti wrote the IPF to several disks, some of which worked somewhat better than others (but none actually load 100%). He then dumped those disks to SCP using Greaseweazle on the offending Amiga TEAC drive (images: https://drive.google.com/open?id=1JDF0_ZVL4W9BbjqyK2F1Z6dhITRtIUef).
The offending SCP images do not load properly in emulation, and analysis with Disk-Utilities indicates bad tracks. The following tracks in file Teac_Hybris_bad_disk.scp are unloadable: 3.1 (5412), 4.1 (5241), 6.0 (a429), 14.1 (5412), 15.0 (5241), 16.0 (a429), 17.0 (2541), 19.1 (2541), 30.0 (2541), 44.1 (a425), 50.0 (5412), 62.1 (2541).
The bad syncs are: 5412 (3), 5241 (2), 2541 (4), a429 (2), a425 (1).
Take Track 3.1 with sync 5412 = 0101 0100 0001 0010, which has an MFM-illegal sequence of five zeroes. This is a flux interval of 12us. Cowlark Fluxengine author reports problems at around 10us (ref http://cowlark.com/fluxengine/doc/technical.html). Searching for the sync word manually in Disk-Utilities we find 5592 = 0101 0101 1001 0010: Two bits in the five-zero sequence have been flipped! Note that syncs 5241 and 2541 are similarly afflicted with a five-zero sequence in their 41 byte.
Take Track 6.0 with sync a429 = 1010 0100 0010 1001, which has an illegal sequence of four zeroes (flux interval 10us). Searching manually in Disk-Utilities we find sync a5a9 = 1010 0101 1010 1001: Again two-adjacent bits in the four-zero sequence have been flipped! Further, we can print the exact flux intervals in the bad sync word (ns): 3950, 6000, 3525, 2375, 3825, 3825, 6000. Note the expected interval 10000 has been split into 3525+2375+3825 by the drive.

Update: Dump from Sony MPF920 (the write drive) has same issue, albeit on other random tracks. For example, Track 26.0 should have sync 5241, but we see 5259 (same substitution as before: 41 -> 59). Similar bad flux for what should be ~11740ns region: 3275+2950+5450=11675ns

My own test, on a setup that appears to reliably boot Hybris. Write with NEC FD1231M, and immediately dump. Circa 10 bad tracks (bad syncs). The dumps do not boot in UAE. Dump with my Amiga modded TEAC 235-HF: One consistently bad track, bad sync (10+ revolutions read). This disk boots all the same (in emulation too) as that track is not used to get to Level 1.
Rewrote the bad track with the TEAC, and it then read in the TEAC okay.
Wrote entire disk with the TEAC, read back 100% okay. Read in the NEC, two tracks bad (17.0, 18.0) and could not improve the read result by rewriting them. Read them in the TEAC again: No problem!

Another experiment, Star Ray (IPF 1488) which has a small 16-MFM-bit weak area each track, written by GW as 16 zeroes.
Written by TEAC:

Read by TEAC: 25 tracks with non-changing weak area
Read by NEC: 6 tracks with non-changing weak area
Written by NEC:
Read by NEC: 10 tracks non-changing weak area
Read by TEAC: 29 tracks with non-changing areas

Interesting. May need a different short-weak pattern. Or maybe write-verify will help...

Tested Hybris with Kryoflux DTC and NEC drive: Same exact problem.
Also it seems that Kryoflux does not verify IPF writes either?

Note relevance to #19: inner-most Mac tracks have 12us bit times at 300RPM.


Jasmine html runner

Hi
I just moved to Angular-Cli Webpack from the Broccoli. This works a lot better in terms of compressing files, creating a bundle and reduces my loading time.
But I used to have jasmine-html-runner with a nice looking page for all my unit tests. Is there a way to set up this with webpack?
<!DOCTYPE html>
<html>

<head>
	<meta http-equiv="content-type" content="text/html;charset=utf-8">
	<title>Unit Tests</title>
	<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/jasmine/2.4.1/jasmine.min.css">
	<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css" integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7" crossorigin="anonymous">
	<script src="https://google.github.io/traceur-compiler/bin/traceur.js"></script>
	<script src="https://cdnjs.cloudflare.com/ajax/libs/jasmine/2.4.1/jasmine.min.js"></script>
	<script src="https://cdnjs.cloudflare.com/ajax/libs/jasmine/2.4.1/jasmine-html.min.js"></script>
	<script src="https://cdnjs.cloudflare.com/ajax/libs/jasmine/2.4.1/boot.min.js"></script>
	<script src="https://code.jquery.com/jquery-2.2.4.min.js" integrity="sha256-BbhdlvQf/xTY9gja0Dq3HiwQF8LaCRTXxZKRutelT44=" crossorigin="anonymous"></script>
	<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/js/bootstrap.min.js" integrity="sha384-0mSbJDEHialfmuBBQP6A4Qrprq5OVfW37PRR3j5ELqxss1yVqOtnepnHVP9aJ7xS" crossorigin="anonymous"></script>

</head>
<body>
	<script type="text/javascript">
		describe("A suite", function() {
			it("contains spec with an expectation", function() {
				expect(true).toBe(false);
			});
		});
	</script>
	<script type="text/javascript" src="./app/_pipes/nice-number.pipe.spec.ts"></script>
</body>
</html>

This is the basic setup, but how do I load all the spec files from the main.bundle.js?

Windows 10
angular-cli: 1.0.0-beta.11-webpack.2
node: 4.4.7
os: win32 x64

I have no idea to be honest. Karma is now compiling the spec files via webpack, and it's all in memory so no disk output.
Going over http://karma-runner.github.io/1.0/config/configuration-file.html, I see there's a customContextFile property. Haven't tested it myself, but it looks like it's what you need.
Leaving the question open in case someone else can weight in.

I have given up on this for now. Using mocha reporter gives a similar view in the command line and is significantly faster.

Alright, closing then.


fixed: asset url import not working

What version of Hono are you using?
4.3.3
What runtime/platform is your app running on?
CloudFlare Workers
What steps can reproduce the bug?
Thanks for this amazing project!
Was trying out the CloudFlare starter and wanted to import a logo.png
import { Hono } from 'hono'
import { renderer } from './renderer'

import logo from './logo.png'

const app = new Hono()

app.use(renderer)

app.get('/', async (c) => {
  return c.render(
    <>

Hello Hono

    </>)
})

export default app

When I run the dev server the logo path shows as  and I'm getting a 404
Not sure what I'm doing wrong?
What is the expected behavior?
I'd expect to see the logo
What do you see instead?
Getting a 404
Additional information
If I add ssrEmitAssets to the vite.config
  build: {
    assetsDir: "static",
    ssrEmitAssets: true
  }

It does get generated during the build
vite v5.2.11 building SSR bundle for production...
✓ 44 modules transformed.
dist/static/logo-BC-ZWNTt.png  13.50 kB
dist/_worker.js                27.50 kB

Figured it out!
Had to add .png to exclude in vite.config.ts
import devServer, { defaultOptions }  from '@hono/vite-dev-server'

devServer({
  adapter,
  entry: 'src/index.tsx',
  exclude: [/.*\.png/, ...defaultOptions.exclude]
}),

@yusukebe better documentation on what exactly dev server exclude does might be helpful.
It's not clear what this means

The paths that are not served by the dev-server.

Does that mean anything in exclude is served by vite instead of hono dev server?
An example of what you would want to be served by hono dev server (instead of vite) would be nice.

I'm loving Hono, thanks for such a great framework!
My use case is JSX SSR on the server and Hotwire on the client
Had it working on Fastify Vite
But switching to Hono for the multi-runtime/serverless support...

Hi @ajaishankar
Update the doc!: https://github.com/honojs/vite-plugins/pull/136

Thanks @yusukebe!


small code cleanup, simplify constructor and nested statements

remove console.logs
explicitly cast to string
define methods outside of constructor, I dont see why this was required other than perhaps calling view instead of this.view
use early returns for deeply nested if statements

Looks good on first sight. 👍 Will do some deeper testing and then merge it, if everything works.


Difference between bin/delayed_job and rake jobs:work?

The README says both "will start working off jobs".
The README seems to present delayed_job script as the preferred method since it's introduced first.
The Heroku DJ guide uses rake jobs:work.
Ryan Bates has a RailsCast where he says to use the delayed_job script instead of rake jobs:work in production.

So far we've been starting Delayed Job by running rake jobs:work but in production we should use the delayed_job script provided in the script folder.

Any tips for when to use which?

what about when running via supervisord which requires foreground processes?

rake jobs:work is no less production worthy than bin/delayed_job. Use what works for your use case.

I want to run delayed_job as a foreground process since I as using runsv to supervise the workers. But the --pid-dir option doesn't work while running it in foreground i.e pid-file is not created in approot/shared//tmp/pids which is preventing me to send kill signal to that process while deploying.

I have the same question. When I look into the source code of both two ways,  I found actually they are doing the similar things, except bin/delayed_job will start the worker in a daemon process(this is the reason why you need to install gem 'daemons')`.
You can refer to the source code below:
    #lib/delayed/command.rb
    def run_process(process_name, options = {})
      Delayed::Worker.before_fork
      Daemons.run_proc(process_name, :dir => options[:pid_dir], :dir_mode => :normal, :monitor => @monitor, :ARGV => @args) do |*_args|
        $0 = File.join(options[:prefix], process_name) if @options[:prefix]
        run process_name, options
      end
    end

def run(worker_name = nil, options = {})
      Dir.chdir(root)

      Delayed::Worker.after_fork
      Delayed::Worker.logger ||= Logger.new(File.join(@options[:log_dir], 'delayed_job.log'))

      worker = Delayed::Worker.new(options)
      worker.name_prefix = "#{worker_name} "
      worker.start
    rescue => e
      STDERR.puts e.message
      STDERR.puts e.backtrace
      ::Rails.logger.fatal(e) if rails_logger_defined?
      exit_with_error_status
    end

  #lib/delayed/tasks.rb
  desc 'Start a delayed_job worker.'
  task :work => :environment_options do
    Delayed::Worker.new(@worker_options).start
  end


Staging indio

Patch for UM-510AC-V3 and UM-550AC submitted.
JIRA - WIFI-7459, WIFI-7460

rebased and merged into next branch, including CI job


Dependabot seems to be unable to update python packages containing dots in their names

Package ecosystem
pip
Package manager version
poetry 1.1.8
Language version
python 3.9
Manifest location and content prior to update
/pyproject.toml, /poetry.lock, /requirements.txt

dependabot.yml content
https://github.com/Parnassius/test-dependabot-core-4209/blob/master/.github/dependabot.yml

Updated dependency
dj.choices 0.10.0

What you expected to see, versus what you actually saw
I expected a PR updating dj.choices to 0.11.0

Native package manager behavior
Running poetry add dj.choices=0.11.0 (as far as i know that's the only way to update a dependency pinned in pyproject.toml) correctly updates it

Images of the diff or a link to the PR, issue or logsDependabot logs
  proxy | time="2021-09-07T18:15:03Z" level=info msg="proxy starting" commit=93723d302417967a9c1e1c1ed73660a424c34f96
  proxy | 2021/09/07 18:15:03 Listening (:1080)
updater | 2021-09-07T18:15:03.560044186 [anonymous-instance:main:WARN:src/firecracker/src/main.rs:370] You are using a deprecated parameter: --seccomp-level 2, that will be removed in a future version.
updater | 2021-09-07T18:15:03.661297519 [199575147:main:WARN:src/devices/src/legacy/serial.rs:432] Detached the serial input due to peer close/error.
updater | time="2021-09-07T18:15:08Z" level=info msg="guest starting" commit=430a07b08c88e74905c1f154360398e015168fb4
updater | time="2021-09-07T18:15:08Z" level=info msg="starting job..." fetcher_timeout=5m0s job_id=199575147 updater_timeout=45m0s updater_version=0.161.0-96ef7692e1e608c55d699d2ef99d58a2e4bd6fc7
updater | I, [2021-09-07T18:15:13.581062 #7]  INFO -- sentry: ** [Raven] Raven 3.1.2 ready to catch errors
updater | warning: parser/current is loading parser/ruby27, which recognizes
updater | warning: 2.7.4-compliant syntax, but you are running 2.7.1.
updater | warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
updater | INFO <job_199575147> Starting job processing
  proxy | 2021/09/07 18:15:20 [002] GET https://api.github.com:443/repos/Parnassius/test
  proxy | 2021/09/07 18:15:20 [002] * authenticating github api request
  proxy | 2021/09/07 18:15:20 [002] 200 https://api.github.com:443/repos/Parnassius/test
  proxy | 2021/09/07 18:15:20 [004] GET https://api.github.com:443/repos/Parnassius/test/git/refs/heads/master
  proxy | 2021/09/07 18:15:20 [004] * authenticating github api request
  proxy | 2021/09/07 18:15:20 [004] 200 https://api.github.com:443/repos/Parnassius/test/git/refs/heads/master
  proxy | 2021/09/07 18:15:20 [006] GET https://api.github.com:443/repos/Parnassius/test/contents/?ref=47b40d523121b54091a22082668888308dafff6b
  proxy | 2021/09/07 18:15:20 [006] * authenticating github api request
  proxy | 2021/09/07 18:15:20 [006] 200 https://api.github.com:443/repos/Parnassius/test/contents/?ref=47b40d523121b54091a22082668888308dafff6b
  proxy | 2021/09/07 18:15:20 [008] GET https://api.github.com:443/repos/Parnassius/test/contents/pyproject.toml?ref=47b40d523121b54091a22082668888308dafff6b
  proxy | 2021/09/07 18:15:20 [008] * authenticating github api request
  proxy | 2021/09/07 18:15:20 [008] 200 https://api.github.com:443/repos/Parnassius/test/contents/pyproject.toml?ref=47b40d523121b54091a22082668888308dafff6b
  proxy | 2021/09/07 18:15:20 [010] GET https://api.github.com:443/repos/Parnassius/test/contents/poetry.lock?ref=47b40d523121b54091a22082668888308dafff6b
  proxy | 2021/09/07 18:15:20 [010] * authenticating github api request
  proxy | 2021/09/07 18:15:20 [010] 200 https://api.github.com:443/repos/Parnassius/test/contents/poetry.lock?ref=47b40d523121b54091a22082668888308dafff6b
  proxy | 2021/09/07 18:15:20 [012] GET https://api.github.com:443/repos/Parnassius/test/contents/requirements.txt?ref=47b40d523121b54091a22082668888308dafff6b
  proxy | 2021/09/07 18:15:20 [012] * authenticating github api request
  proxy | 2021/09/07 18:15:20 [012] 200 https://api.github.com:443/repos/Parnassius/test/contents/requirements.txt?ref=47b40d523121b54091a22082668888308dafff6b
  proxy | 2021/09/07 18:15:21 [014] GET https://api.github.com:443/repos/Parnassius/test/contents/.github?ref=47b40d523121b54091a22082668888308dafff6b
  proxy | 2021/09/07 18:15:21 [014] * authenticating github api request
  proxy | 2021/09/07 18:15:21 [014] 200 https://api.github.com:443/repos/Parnassius/test/contents/.github?ref=47b40d523121b54091a22082668888308dafff6b
updater | INFO <job_199575147> Finished job processing
updater | time="2021-09-07T18:15:21Z" level=info msg="task complete" container_id=job-199575147-file-fetcher exit_code=0 job_id=199575147 step=fetcher
updater | I, [2021-09-07T18:15:23.809082 #7]  INFO -- sentry: ** [Raven] Raven 3.1.2 ready to catch errors
updater | warning: parser/current is loading parser/ruby27, which recognizes
updater | warning: 2.7.4-compliant syntax, but you are running 2.7.1.
updater | warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
updater | INFO <job_199575147> Starting job processing
updater | INFO <job_199575147> Starting update job for Parnassius/test
updater | INFO <job_199575147> Checking if pytz 2021.1 needs updating
  proxy | 2021/09/07 18:15:36 [018] GET https://pypi.org:443/simple/pytz/
  proxy | 2021/09/07 18:15:36 [018] 200 https://pypi.org:443/simple/pytz/
updater | INFO <job_199575147> Latest version is 2021.1
updater | INFO <job_199575147> No update needed for pytz 2021.1
updater | INFO <job_199575147> Checking if asgiref 3.4.1 needs updating
  proxy | 2021/09/07 18:15:37 [020] GET https://pypi.org:443/simple/asgiref/
  proxy | 2021/09/07 18:15:37 [020] 200 https://pypi.org:443/simple/asgiref/
updater | INFO <job_199575147> Latest version is 3.4.1
updater | INFO <job_199575147> No update needed for asgiref 3.4.1
updater | INFO <job_199575147> Checking if django 3.2.7 needs updating
  proxy | 2021/09/07 18:15:37 [022] GET https://pypi.org:443/simple/django/
  proxy | 2021/09/07 18:15:37 [022] 200 https://pypi.org:443/simple/django/
updater | INFO <job_199575147> Latest version is 3.2.7
updater | INFO <job_199575147> No update needed for django 3.2.7
updater | INFO <job_199575147> Checking if sqlparse 0.4.1 needs updating
  proxy | 2021/09/07 18:15:37 [024] GET https://pypi.org:443/simple/sqlparse/
  proxy | 2021/09/07 18:15:37 [024] 200 https://pypi.org:443/simple/sqlparse/
updater | INFO <job_199575147> Latest version is 0.4.1
updater | INFO <job_199575147> No update needed for sqlparse 0.4.1
updater | INFO <job_199575147> Checking if dj-choices 0.10.0 needs updating
  proxy | 2021/09/07 18:15:38 [026] GET https://pypi.org:443/simple/dj-choices/
  proxy | 2021/09/07 18:15:38 [026] 200 https://pypi.org:443/simple/dj-choices/
updater | INFO <job_199575147> Latest version is 0.11.0
  proxy | 2021/09/07 18:15:43 [028] GET https://pypi.org:443/pypi/dj.choices/0.10.0/json
  proxy | 2021/09/07 18:15:43 [028] 200 https://pypi.org:443/pypi/dj.choices/0.10.0/json
  proxy | 2021/09/07 18:15:43 [030] GET https://files.pythonhosted.org:443/packages/d4/22/c89b3c5f7f71972b2f84c847aec51c1ed9e7516c8678ab4ead695b693384/dj.choices-0.10.0-py2.py3-none-any.whl
  proxy | 2021/09/07 18:15:43 [030] 200 https://files.pythonhosted.org:443/packages/d4/22/c89b3c5f7f71972b2f84c847aec51c1ed9e7516c8678ab4ead695b693384/dj.choices-0.10.0-py2.py3-none-any.whl
  proxy | 2021/09/07 18:15:43 [032] GET https://pypi.org:443/pypi/six/1.16.0/json
  proxy | 2021/09/07 18:15:43 [032] 200 https://pypi.org:443/pypi/six/1.16.0/json
  proxy | 2021/09/07 18:15:43 [034] GET https://files.pythonhosted.org:443/packages/d9/5a/e7c31adbe875f2abbb91bd84cf2dc52d792b5a01506781dbcf25c91daf11/six-1.16.0-py2.py3-none-any.whl
  proxy | 2021/09/07 18:15:43 [034] 200 https://files.pythonhosted.org:443/packages/d9/5a/e7c31adbe875f2abbb91bd84cf2dc52d792b5a01506781dbcf25c91daf11/six-1.16.0-py2.py3-none-any.whl
  proxy | 2021/09/07 18:15:43 [036] GET https://pypi.org:443/pypi/django/3.2.7/json
  proxy | 2021/09/07 18:15:43 [036] 301 https://pypi.org:443/pypi/django/3.2.7/json
  proxy | 2021/09/07 18:15:43 [038] GET https://pypi.org:443/pypi/Django/3.2.7/json
  proxy | 2021/09/07 18:15:43 [038] 200 https://pypi.org:443/pypi/Django/3.2.7/json
  proxy | 2021/09/07 18:15:43 [040] GET https://pypi.org:443/pypi/sqlparse/0.4.1/json
  proxy | 2021/09/07 18:15:43 [040] 200 https://pypi.org:443/pypi/sqlparse/0.4.1/json
  proxy | 2021/09/07 18:15:43 [042] GET https://files.pythonhosted.org:443/packages/14/05/6e8eb62ca685b10e34051a80d7ea94b7137369d8c0be5c3b9d9b6e3f5dae/sqlparse-0.4.1-py3-none-any.whl
  proxy | 2021/09/07 18:15:43 [042] 200 https://files.pythonhosted.org:443/packages/14/05/6e8eb62ca685b10e34051a80d7ea94b7137369d8c0be5c3b9d9b6e3f5dae/sqlparse-0.4.1-py3-none-any.whl
  proxy | 2021/09/07 18:15:44 [044] GET https://pypi.org:443/pypi/pytz/2021.1/json
  proxy | 2021/09/07 18:15:44 [044] 200 https://pypi.org:443/pypi/pytz/2021.1/json
  proxy | 2021/09/07 18:15:44 [046] GET https://files.pythonhosted.org:443/packages/70/94/784178ca5dd892a98f113cdd923372024dc04b8d40abe77ca76b5fb90ca6/pytz-2021.1-py2.py3-none-any.whl
  proxy | 2021/09/07 18:15:44 [046] 200 https://files.pythonhosted.org:443/packages/70/94/784178ca5dd892a98f113cdd923372024dc04b8d40abe77ca76b5fb90ca6/pytz-2021.1-py2.py3-none-any.whl
  proxy | 2021/09/07 18:15:44 [048] GET https://pypi.org:443/pypi/asgiref/3.4.1/json
  proxy | 2021/09/07 18:15:44 [048] 200 https://pypi.org:443/pypi/asgiref/3.4.1/json
updater | INFO <job_199575147> Requirements to unlock update_not_possible
  proxy | 2021/09/07 18:15:44 [050] GET https://pypi.org:443/pypi/test/json/
  proxy | 2021/09/07 18:15:44 [050] 404 https://pypi.org:443/pypi/test/json/
updater | INFO <job_199575147> Requirements update strategy bump_versions
updater | INFO <job_199575147> No update possible for dj-choices 0.10.0
updater | INFO <job_199575147> Checking if six 1.16.0 needs updating
  proxy | 2021/09/07 18:15:45 [052] GET https://pypi.org:443/simple/six/
  proxy | 2021/09/07 18:15:45 [052] 200 https://pypi.org:443/simple/six/
updater | INFO <job_199575147> Latest version is 1.16.0
updater | INFO <job_199575147> No update needed for six 1.16.0
updater | INFO <job_199575147> Finished job processing
updater | time="2021-09-07T18:15:45Z" level=info msg="task complete" container_id=job-199575147-updater exit_code=0 job_id=199575147 step=updater

Note these four lines in the middle:
updater | INFO <job_199575147> Checking if dj-choices 0.10.0 needs updating
  proxy | 2021/09/07 18:15:38 [026] GET https://pypi.org:443/simple/dj-choices/
  proxy | 2021/09/07 18:15:38 [026] 200 https://pypi.org:443/simple/dj-choices/
updater | INFO <job_199575147> Latest version is 0.11.0

and this one near the end:
updater | INFO <job_199575147> No update possible for dj-choices 0.10.0

🕹 Bonus points: Smallest manifest that reproduces the issue
I initially encountered this with discord.py, I created the test repo linked above to check if the problem was specific to that, or it affected other deps with dots in their names. I also created a requirements.txt to exclude this being a poetry-specific problem

Thanks for reporting this, from the logs, it seems like this is not related to the package containing a dot, but rather a resolution bug in poetry.
In this case, the requirements.txt is not picked up, because dependabot assumes a single package manager per ecosystem per folder, so it picks poetry for the update here.
When running this code in a REPL we can see that for Poetry it resolves to 0.10.0 but for requirements.txt it indeed shows 0.11.0 as the resolvable version:
(byebug) pip_version_resolver.latest_resolvable_version
#<Dependabot::Python::Version 0.11.0>
(byebug) poetry_version_resolver.latest_resolvable_version(requirement: unlocked_requirement_string)
#<Dependabot::Python::Version 0.10.0>

So digging into this a little, what we do is basically the following, we take the poetry files and update the manifest to a range that includes the new version: >= 0.10.0, <= 0.11.0, we then run poetry, and we figure out what ended up in the lockfile.
The pyproject file now looks like this:
[build-system]
build-backend = "poetry.core.masonry.api"
requires = ["poetry-core>=1.0.0"]
[tool.poetry]
authors = ["Parnassius<EMAIL_ADDRESS>description = ""
name = "test"
version = "0.1.0"
[tool.poetry.dependencies]
"dj.choices" = ">= 0.10.0, <= 0.11.0"
python = "^3.9"
[tool.poetry.dev-dependencies]

And the lockfile is:
[build-system]
build-backend = "poetry.core.masonry.api"
requires = ["poetry-core>=1.0.0"]
[tool.poetry]
authors = ["Parnassius<EMAIL_ADDRESS>description = ""
name = "test"
version = "0.1.0"
[tool.poetry.dependencies]
"dj.choices" = ">= 0.10.0, <= 0.11.0"
python = "^3.9"
[tool.poetry.dev-dependencies]
nil
(byebug) print `cat poetry.lock`
[[package]]
name = "asgiref"
version = "3.4.1"
description = "ASGI specs, helper code, and adapters"
category = "main"
optional = false
python-versions = ">=3.6"

[package.extras]
tests = ["pytest", "pytest-asyncio", "mypy (>=0.800)"]

[[package]]
name = "dj.choices"
version = "0.10.0"
description = "An enum implementation for Django forms and models."
category = "main"
optional = false
python-versions = "*"

[package.dependencies]
django = "*"
six = "*"

[[package]]
name = "django"
version = "3.2.7"
description = "A high-level Python Web framework that encourages rapid development and clean, pragmatic design."
category = "main"
optional = false
python-versions = ">=3.6"

[package.dependencies]
asgiref = ">=3.3.2,<4"
pytz = "*"
sqlparse = ">=0.2.2"

[package.extras]
argon2 = ["argon2-cffi (>=19.1.0)"]
bcrypt = ["bcrypt"]

[[package]]
name = "pytz"
version = "2021.1"
description = "World timezone definitions, modern and historical"
category = "main"
optional = false
python-versions = "*"

[[package]]
name = "six"
version = "1.16.0"
description = "Python 2 and 3 compatibility utilities"
category = "main"
optional = false
python-versions = ">=2.7, !=3.0.*, !=3.1.*, !=3.2.*"

[[package]]
name = "sqlparse"
version = "0.4.1"
description = "A non-validating SQL parser."
category = "main"
optional = false
python-versions = ">=3.5"

[metadata]
lock-version = "1.1"
python-versions = "^3.9"
content-hash = "efa5f77f5e8011761a57bdce019a404838f266d477c483b1e8ceb11688cb3bb4"

[metadata.files]
asgiref = [
    {file = "asgiref-3.4.1-py3-none-any.whl", hash = "sha256:ffc141aa908e6f175673e7b1b3b7af4fdb0ecb738fc5c8b88f69f055c2415214"},
    {file = "asgiref-3.4.1.tar.gz", hash = "sha256:4ef1ab46b484e3c706329cedeff284a5d40824200638503f5768edb6de7d58e9"},
]
"dj.choices" = [
    {file = "dj.choices-0.10.0-py2.py3-none-any.whl", hash = "sha256:96d295872bd070d46cfd99c6db6b446898dbdec655fb3d866740899f3eee026f"},
    {file = "dj.choices-0.10.0.tar.gz", hash = "sha256:ed5547a0f635c3074ee607998a378465d70a84ce7ac1f9358f9be707adc636e9"},
]
django = [
    {file = "Django-3.2.7-py3-none-any.whl", hash = "sha256:e93c93565005b37ddebf2396b4dc4b6913c1838baa82efdfb79acedd5816c240"},
    {file = "Django-3.2.7.tar.gz", hash = "sha256:95b318319d6997bac3595517101ad9cc83fe5672ac498ba48d1a410f47afecd2"},
]
pytz = [
    {file = "pytz-2021.1-py2.py3-none-any.whl", hash = "sha256:eb10ce3e7736052ed3623d49975ce333bcd712c7bb19a58b9e2089d4057d0798"},
    {file = "pytz-2021.1.tar.gz", hash = "sha256:83a4a90894bf38e243cf052c8b58f381bfe9a7a483f6a9cab140bc7f702ac4da"},
]
six = [
    {file = "six-1.16.0-py2.py3-none-any.whl", hash = "sha256:8abb2f1d86890a2dfb989f9a77cfcfd3e47c2a354b01111771326f8aa26e0254"},
    {file = "six-1.16.0.tar.gz", hash = "sha256:1e61c37477a1626458e36f7b1d82aa5c9b094fa4802892072e49de9c60c4c926"},
]
sqlparse = [
    {file = "sqlparse-0.4.1-py3-none-any.whl", hash = "sha256:017cde379adbd6a1f15a61873f43e8274179378e95ef3fede90b5aa64d304ed0"},
    {file = "sqlparse-0.4.1.tar.gz", hash = "sha256:0f91fd2e829c44362cbcfab3e9ae12e22badaa8a29ad5ff599f9ec109f0454e8"},
]

If we give it a different constraint, it does resolve to 0.11.0:
poetry_version_resolver.latest_resolvable_version(requirement: ">= 0.11.0")
#<Dependabot::Python::Version 0.11.0>

But for these requirements it doesn't:
(byebug) poetry_version_resolver.latest_resolvable_version(requirement: "<= 0.11.0")
#<Dependabot::Python::Version 0.10.0>
(byebug) poetry_version_resolver.latest_resolvable_version(requirement: ">= 0.10.0")
#<Dependabot::Python::Version 0.10.0>

Now, unless I misunderstand Poetry's version ranges I'd expect >= 0.10.0, <= 0.11.0 to mean: greater than or equal to 0.10.0 and lesser than or equal to 0.11.0, which should resolve to 0.11.0?

I brought up the dot in the dependency name because the log sometimes refers to it as dj.choices, and other times as dj-choices, so I fear dependency.name in this line refers to the latter.
I tried running poetry update dj-choices --lock --no-interaction after relaxing the version range, and the generated lockfile is indeed the same as the one you posted, while running poetry update dj.choices --lock --no-interaction the locked version is correctly updated to 0.11.0.

I brought up the dot in the dependency name because the log sometimes refers to it as dj.choices, and other times as dj-choices, so I fear dependency.name in this line refers to the latter.
I tried running poetry update dj-choices --lock --no-interaction after relaxing the version range, and the generated lockfile is indeed the same as the one you posted, while running poetry update dj.choices --lock --no-interaction the locked version is correctly updated to 0.11.0.

Oh, I see what you mean now, yeah us normalizing the name does seem to cause this!
What I am confused about though, is that according to pep-0503, periods do not seem to be allowed as names. Does poetry make an exception here, or is pep-0503 not widely accepted as a standard?
I'm worried that deviating from that naming standard will cause other issues

Thanks for that added context 👍
So it seems like we should not normalize the name when parsing the dependency-file, but rather only when making requests to the registries.

So it seems like we should not normalize the name when parsing the dependency-file, but rather only when making requests to the registries.

Yes, that sounds correct to me

@Parnassius any interest in submitting a PR tackling this? I haven't dug into the code, but based on the comments in this issue it seems like a relatively straightforward change.

I tried running poetry update dj-choices --lock --no-interaction after relaxing the version range, and the generated lockfile is indeed the same as the one you posted, while running poetry update dj.choices --lock --no-interaction the locked version is correctly updated to 0.11.0.

The behaviour I described here doesn't seem to happen anymore with the latest poetry version, now both poetry update dj-choices --lock --no-interaction and poetry update dj.choices --lock --no-interaction produce the same lockfile with the expected 0.11.0 version. It seems that poetry itself added some sort of normalization that indirectly solved this issue.
I didn't notice it before today, but at the beginning of september Dependabot actually created a PR on my test repo, so I think this can now be closed.

Oh that's great news thanks for circling back to let us know.


Anatomic Site Concept ID (Entire vs Structure)

In the MI-CDM paper (Fig3), the anatomic_site_concept_id for lung nodule use case was designated as '4118108 (entire thorax)'. If we obtain anatomic site information from DICOM, '4184181 (thoracic cavity structure)' might be more appropriate.
p.s. I am seeking input on this matter to avoid confusion for researchers who are following MI-CDM based on our paper.
Rationale:

(DICOM) DICOM generally uses anatomic concepts with "structure" rather than "entire". For instance, the BodyPartExamined Tag 'CHEST' is defined as SCT '43799004 (thoracic cavity structure)'.
(OMOP CDM) Both codes are included as Standard Concept IDs in the Specimen Table's Accepted Concepts, but 'Entire' lacks descendants compared to 'Structure'.

Concept Type
OMOP Concept ID
SCT Code
Description

Structure
4184181
43799004
Thoracic cavity structure (body structure)

Entire
4118108
302551006
Entire thorax

References:

DICOM PS3.16 > Correspondence of Anatomic Region Codes and Body Part Examined Defined Terms
OMOP CDM v5.4 > Specimen Table > ETL Conventions

Agreed. We should follow the DICOM-SNOMED Value Set, which is the Thoracic cavity structure.


invalid syntax error on running on Mac

$ sacredboard
Traceback (most recent call last):
File "/usr/local/bin/sacredboard", line 7, in
from sacredboard.bootstrap import run
File "/Library/Python/2.7/site-packages/sacredboard/init.py", line 3, in
from sacredboard import bootstrap
File "/Library/Python/2.7/site-packages/sacredboard/bootstrap.py", line 105
"for more information.", file=sys.stderr)
^
SyntaxError: invalid syntax

Hi,
which version please?

Python upgrade solved this. Sorry for the false alarm. And thanks for the quick response.


[Improve][TubeMQ] tubemq-client-go lacks log level configuration API

Description
现在 github.com/apache/inlong/inlong-tubemq/tubemq-client-twins/tubemq-client-go 的日志级别是固定的warn，系统可以设置日志级别来输出日志，排查问题。
======================================================================
Now the log level of github.com/apache/inlong/inlong-tubemq/tubemq-client-twins/tubemq-client-go is fixed to warn, which is inconvenient to check.
The system can be improved by increasing the log level configuration API, which can output different detailed logs according to needs, which is convenient for troubleshooting.
Use case
No response
Are you willing to submit PR?

[x] Yes, I am willing to submit a PR!

Code of Conduct

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

@smarteng, thanks for contribution!

@smarteng do you still work on this issue?

https://github.com/apache/inlong/pull/10040 will continue to solve this problem.


CI: support aarch64

The aarch64 should be added, like this:
jobs:
  build:
      matrix:
        target:
          - x86_64-unknown-linux-gnu
          - aarch64-unknown-linux-gnu

      - uses: actions-rs/cargo@v1
        with:
          command: check
          args: --all-features --target ${{ matrix.target }}

Other relevant information: https://github.com/taiki-e/cargo-llvm-cov/pull/167

Static checks have been added for aarch64, also need to add unit tests for it.
https://github.com/openanolis/dragonball-sandbox/pull/163

close this since after moving to Kata repo, we will test dragonball-sandbox UT in there


Change: Observe User Preferences for Linodes Landing View

Description
Uses User Preferences for Linodes View
Type of Change

Breaking change ('break', 'deprecate')

Applicable E2E Tests
N/A
Note to Reviewers
!!DEPRECATED FUNCTIONALITY!!
Before the priority for showing grid or list view was this

URL Query Param (show whatever is in the param)
Viewport width (show grid view on xs breakpoints)
Local storage (use whatever is in LS)
Linode Count (show grid view if user has < 3 Linodes, otherwise show list view)

But since we now have implemented responsive tables, it was more effort than necessary to still honor this hierarchy, so instead this PR implements the following logic.

URL Query Param (show whatever is in the param)
User Preference (show whatever is in user preference, and default to list view)

To Test
Toggle all existing user preferences (theme, spacing, linode view, and linode group by tag). Make sure they're not overwriting each other and PUT to the API with the correct payload.

@johnwcallahan addressed feedback


[DOC] Minor addition for skipping connectivity matrices step

Changes proposed in this pull request

Current documentation shows different options for atlases but does not explain how an user may skip this step (e.g. to save compute time) if they are not using the matrices.
Documentation that should be reviewed

This PR adds one line to the connectivity_matrices.rst and should not affect functionality of the code base.

Thanks Howard!

Happy to contribute!


[BUG] ModuleNotFoundError: No module named 'packaging' for the check_update hook

The slack_cli_hooks versions
slack_bolt==1.19.0rc1
slack_cli_hooks==0.0.0.dev2
slack_sdk==3.27.0

Python runtime version
Python 3.11.8

OS info
ProductName:            macOS
ProductVersion:         14.3
BuildVersion:           23D56
Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:44 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6000

Describe the bug
The packaging module is not installed with this package so a ModuleNotFoundError is raised when calling the check_update hook. It seems like packaging is the only package not included in the standard library!
Steps to reproduce
$ slack create pkgs -t slack-samples/bolt-python-custom-function-template
$ cd pkgs

# Include only the slack_* modules
$ head -n 2 requirements.txt > tmp.txt && mv tmp.txt requirements.txt

$ python3 -m venv .venv
$ source .venv/bin/activate
$ pip install -r requirements.txt

$ slack update

Expected result
Updates are checked without any error
Actual result
$ slack update
Traceback (most recent call last):
File "<frozen runpy>", line 198, in _run_module_as_main
File "<frozen runpy>", line 88, in _run_code
File "/Users/me/programming/sandbox/example/.venv/lib/python3.11/site-packages/slack_cli_hooks/hooks/check_update.py", line 10, in <module>
from packaging.version import Version
ModuleNotFoundError: No module named 'packaging'

Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

Hi @zimeg thanks for opening this 💯
I tried to reproduce this on my send but can't get the error, how are you installing python 3.11.8?

@WilliamBergamin Apologies for a delayed response! Just tried again with the Python 3.12.0 included in my virtual environment and I'm finding the same thing 🤔
This only seems to happen when my requirements.txt includes the following:
slack-cli-hooks
slack-bolt==1.19.0rc1

Including the other packages present in the sample seems to bring packaging into my environment:
pytest
flake8==7.0.0
black==24.3.0


Project requiring Studio 3.0 to open

Hello, this project's Gradle plugin requires Studio 3.0 as seen from the error it generated when I tried opening it now Error:This Gradle plugin requires Studio 3.0 minimum. Do I really have to upgrade my android studio version?

Yes


Snapshot test for react navigator failing

Current Behavior
Hi guys, I recently upgraded react-navigation from beta 9 to beta 15 but it looks like the jest snapshot that my local environment generates is different from what circle ci generates. Mine seems add an extra undefined to the top level style prop.

On circle, it doesn't have the extra param.

Expected Behavior

expecting circle and my environment to generate the same snapshot.

Your Environment

software
version

react-navigation
beta 15

react-native
49.5

node
8.6

npm or yarn
1.0.1

circle env:
node: 8.5
yarn: 1.0.2

Hi thanks for reporting.

Is it related to https://github.com/react-community/react-navigation/issues/2820 ?
can you try with newer versions of the lib? We have worked a lot on Jest & Flow implementation so it may be fixed. Moreover we are going to release a new version very soon, so maybe if beta.19 still has this issue for you maybe try pointing at master.

@kelset I don't think so but I'll look into it more. It seems like its just a matter of the container adding an extra undefined in the styles array in the local environment compared to circle which doesn't.  I've rewritten the test a bit to bypass this issue (since it really is a mount test anyways)


Add email or discord notifications on test failures

GitHub is mysterious about who gets notified on automated test failures.
We should consider adding capability to notify in discord when tests fail. It may be annoying if everybody inherits it.
However, ddev-redis-7 was failing all its HEAD tests all the way up to v1.23.0 and we maintainers had no idea. The fixes were easy.

I see a number of discord actions that might work, https://github.com/marketplace?category=&type=actions&verification=&query=sort%3Apopularity-desc+discord

Regarding a Discord notification, it seems that some action require a discord webhook url (like this one ) or a webhook token/id (like this one ).
I don't know how these webhooks work, but I'm guessing we don't want to hard-code these values, and I'm not sure we want to share them so the end user can save them in their repo secrets.
What do you think ?
For email notification, this action looks good to me.

You're right that it might not work because of the required secret (webhook).

I worked a couple hours with ChatGPT to create https://github.com/ddev/ddev-add-on-monitoring and https://github.com/ddev/ddev-add-on-monitoring/blob/main/check-addons.sh
Now we have check-addons.sh set up in our icinga monitoring instance, and will automatically know when tests are failing on official add-ons.
It can be run against everything when we want. I did that and opened issues on the several add-ons which didn't have working or running tests.


rdkit cannot load some mol2 files

Dear Dr. Shen, thank you for sharing the source code of RTMScore. I’m trying to process decoys_docking set of CASF-2016, but I found that there are some mol2 files that cannot be successfully read by RDkit (fail to be sanitized and return None when executing “ligand_mol2 = Chem.MolFromMol2File(ligand_mol2_path, removeHs=True)”). Are there any solutions to solve this problem, or you just skipped those mol2 files that cannot be successfully loaded?

Thank you for your reply. I have other following questions. First, I saw you uploaded the processed graphs at https://zenodo.org/record/6859325#.Y6KpS3ZBxD-. I found that each data point is stored in a heterogeneous graph object. I guess I should convert it into two separate protein and ligand graphs before feeding it to RTMScore. Alternatively, I can also modify the model to make it possible to process heterogeneous graphs. Am I right? Second, the heterogeneous graph contains three types of distance (cadist, cedist, and mindist). Is mindist equal to the result returned by the function “compute_euclidean_distances_matrix” at model2.py? Do these three types of distance lead to similar performance? Third, do the two auxiliary tasks matter? Do you test the model performance by removing the two auxiliary tasks? To my understanding, the model is just trained to recover the information already included in the input features for the auxiliary tasks. I am looking forward to your reply. Thank you.

Thank you for your reply. I might have the following question. To my understanding, RTMScore is trained to predict a Gaussian-like distribution where mu is supposed to be at a position close to the true distance (i.e., y in the source code). However, when I check the prediction of the trained RTMScore I found that the predicted mu is far away from the true distance y. Is that normal, or perhaps I misunderstood the algorithm?

sigma and mu are all a group of parameters to determine the distribution of the distance, and the final distribution of a specific residue-atom pair shall be the mixtures of multiple Gaussians. Hence there shall be no relation between a single mu and the correponding y. It should be noticed that mu and y have different dimentions.
Hence I think perhaps you misunderstand the algorithm. To better understand the algorthm, perhaps you can refer to the original paper of DeepDock.

Thank you very much for your reply. I tried to apply for a license for OpenEye, but I haven’t received any feedback yet. Could you please upload the processed graphs or converted sdf files for CASF2016 decoys_docking set?

Thank you very much for your reply. I tried to apply for a license for OpenEye, but I haven’t received any feedback yet. Could you please upload the processed graphs or converted sdf files for CASF2016 decoys_docking set?

The following are the scores of the poses in CASF-2016 docking set predicted by our models, and I think they are enough to show the performance of our methodology.
rtmscore1_casf2016_docking.tar.gz
rtmscore2_casf2016_docking.tar.gz
rtmscore3_casf2016_docking.tar.gz


Simplify TF armax/argmin

Codecov Report
Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 57.57%. Comparing base (3cc4d44) to head (46d04b4).

Files
Patch %
Lines

keras/src/backend/tensorflow/numpy.py
0.00%
2 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (3cc4d44) and HEAD (46d04b4). Click for more details.
HEAD has 6 uploads less than BASE

Flag
BASE (3cc4d44)
HEAD (46d04b4)

keras
4
1

keras-torch
1
0

keras-tensorflow
1
0

keras-jax
1
0

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #20171       +/-   ##
===========================================
- Coverage   79.34%   57.57%   -21.77%
===========================================
  Files         501      501
  Lines       47319    47319
  Branches     8692     8692
===========================================
- Hits        37544    27244    -10300
- Misses       8017    18396    +10379
+ Partials     1758     1679       -79

Flag
Coverage Δ

keras
57.57% <0.00%> (-21.62%)
:arrow_down:

keras-jax
?

keras-numpy
57.57% <0.00%> (-0.01%)
:arrow_down:

keras-tensorflow
?

keras-torch
?

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

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


[SPARK-9371][SQL] fix the support for special chars in column names for hive context

cc @rxin

Merged build triggered.

Merged build started.

LGTM.

Test build #38506 has started for   PR 7684 at commit da21ffe.

Test build #38506 has finished for   PR 7684 at commit da21ffe.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged - can you submit a fix for branch-1.4 as well?


Introduce batch/v1 Job with Indexed completion mode

/kind discussion
We often implement features similar to batch/v1 Job (e.g., https://github.com/kubeflow/common/pull/196) since the training operator creates blocks of Pod + Service for each rank, not batch/v1 Job + Service once the custom Job resource (e.g., TFJob) is created.
IIUC, training-operator designed like the above since training-operator core architecture is created before the Indexed Job feature and Pod failure policy feature are released.
So I would like to propose the architecture that the training-operator creates batch/v1 Job with Indexed completion mode + Service, not Pod + Service.
Introducing batch/v1 Job eliminates the need to implement and maintain features similar to batch/v1 Job and makes introducing new batch/v1 Job features easy.
/cc @kubeflow/wg-training-leads

Interesting.  This would need a major rewrite ?
/cc @gaocegege @zw0610 @terrytangyuan

This would need a major rewrite ?

Probably, yes. Replacing Pod with batch/v1 Indexed Job, we can use [Job with Pod-to-Pod Communication] (https://kubernetes.io/docs/tasks/job/job-with-pod-to-pod-communication/) logic.
Also, we maybe remove most of the kubeflow/common codes and use batch/v1 Job logic.
For example, we can replace ReplicaSpec.RestartPolicy with PodFailurePolicy:
https://github.com/kubeflow/common/blob/34276e9d2ffa39f5922479bff87dc5ed5ed94cfb/pkg/apis/common/v1/types.go#L79-L83
https://github.com/kubernetes/kubernetes/blob/c9ed04762f94a319d7b1fb718dc345491a32bea6/pkg/apis/batch/types.go#L220-L229
This means replacing that, we don't need to hold the logic to judge whether restart pods.

/cc @alculquicondor

IIUC, Indexed Job feature aims tf-operator, mpi-operator and more.
https://github.com/kubernetes/kubernetes/issues/99497#issuecomment-786776056

Introducing batch/v1 Job eliminates the need to implement and maintain features similar to batch/v1 Job and makes introducing new batch/v1 Job features easy.

Since it's the major benefits is to reduce the duplicated developing workload regarding some features, do we have such a feature list which are not implemented in training-operator but will be completed once the batch/v1 Job was adopted?

Introducing batch/v1 Job eliminates the need to implement and maintain features similar to batch/v1 Job and makes introducing new batch/v1 Job features easy.

Since it's the major benefits is to reduce the duplicated developing workload regarding some features, do we have such a feature list which are not implemented in training-operator but will be completed once the batch/v1 Job was adopted?

Good point. I don't create such a list yet. At present, I found the suspend Job and pod disruption conditions.
I'll create a list and share it with you in this issue.

+1
This has been discussed before #1303
If you could provide a list of any missing functionality in the Job API, we could add those to the roadmap.
We did a lot of progress with failure policies, but IIUC, there's also a need for some form of success policy?
Also @ahg-g is working on a proposal for a multi-pod-template API, that he's going to present in the Batch working group meeting on Feb 2nd https://docs.google.com/document/d/1XOeUN-K0aKmJJNq7H07r74n-mGgSFyiEDQ3ecwsGhec/edit#heading=h.ukbaidczvy3r

+1
The benefit is not just deduping code, but also helping to defragment the ecosystem. While I do understand the benefit of having dedicated APIs for MPI, TF training etc., it is important that they build on a common API that we can use for job-level schedulers and autoscaling.
As @alculquicondor mentioned, I am working on a proposal that I will make public next week and will be discussed in Kubernetes batch working group.  I am also happy to schedule a time and discuss it with the kubeflow community, can you please let me know how/where I can put this topic on the meeting agenda?

If you could provide a list of any missing functionality in the Job API, we could add those to the roadmap. We did a lot of progress with failure policies, but IIUC, there's also a need for some form of success policy?

@alculquicondor Thanks for sharing.
I think introducing the success policy would be useful for training-operator since we hold the logic by ourselves in tensorflow-controller.
https://github.com/kubeflow/training-operator/blob/ddf372c8fe0d179674f3dc5e61fbd71246c32924/pkg/controller.v1/tensorflow/tfjob_controller.go#L505-L534
Maybe, tensorflow-controller or training-controller can be one of the use cases to introduce the success policy to batch/v1 Job.

Also @ahg-g is working on a proposal for a multi-pod-template API, that he's going to present in the Batch working group meeting on Feb 2nd https://docs.google.com/document/d/1XOeUN-K0aKmJJNq7H07r74n-mGgSFyiEDQ3ecwsGhec/edit#heading=h.ukbaidczvy3r

Thanks for sharing. I'm interested a muti-pod-template API since we can consider using the API after we introduce batch/v1 Job to training-operator.
Are there KEPs for a multi-pod-template API in k/enhancement?

The benefit is not just deduping code, but also helping to defragment the ecosystem. While I do understand the benefit of having dedicated APIs for MPI, TF training etc., it is important that they build on a common API that we can use for job-level scheduling and autoscaling.

@ahg-g Yes, exactly. I think so too.

As @alculquicondor mentioned, I am working on a proposal that I will make public next week and will be discussed in Kubernetes batch working group. I am also happy to schedule a time and discuss it with the kubeflow community, can you please let me know how/where I can put this topic on the meeting agenda?

We have bi-weekly community meetings for WG Training, and there is a meeting note in https://docs.google.com/document/d/1MChKfzrKAeFRtYqypFbMXL6ZIc_OgijjkvbqmwRV-64/edit#.
I rarely participate in meetings, but you can share a multiple-pod-template API with WG Training leads.

Are there KEPs for a multi-pod-template API in k/enhancement?

Not yet, as I mentioned above, I will share a google doc next week, it is easier to discuss such a significant proposal on a google doc first before we move to a KEP. Note that the plan is to initially host the API under the Kueue project to iterate fast on the api with the goal of upstreaming it eventually.

Are there KEPs for a multi-pod-template API in k/enhancement?

Not yet, as I mentioned above, I will share a google doc next week, it is easier to discuss such a significant proposal on a google doc first before we move to a KEP. Note that the plan is to initially host the API under the Kueue project to iterate fast on the api with the goal of upstreaming it eventually.

I see. Thanks for letting me know.

I will work on this issue after the kubeflow v1.7 feature freeze date since that date is coming up. Then, I will share the corresponding table for batch/v1 Job and training-operator Job feature in this issue.
If I find this issue with significant API changes, I will submit a proposal to this repository.
Also, I will work on the actual implementation after #1714 is done.

/cc @richardsliu

Maybe, we need to wait for the Indexed Jobs with unset completions parameter  feature to support Elastic PytorchJob.
ref: https://github.com/kubernetes/enhancements/issues/3715

Is elastic Pytorch the only training job that supports resizing?
Does it matter which workers get removed?

Is elastic Pytorch the only training job that supports resizing?

IIUC, we are supporting only one master replica for PytorchJob. So yes.
https://github.com/kubeflow/training-operator/blob/b87c6fa0be186ecf8bc901c74cdc52a529ddd536/pkg/apis/kubeflow.org/v1/pytorch_validation.go#L62-L66

Does it matter which workers get removed?

Maybe, It does not matter which worker is deleted since the Elastic PytorchJob uses a local elastic agent.
@gaocegege @zw0610 If I misunderstand the Elastic PytorchJob, can you correct me?

Also, we may use Indexed Jobs with unset completions parameter feature for MPIJob with Horovod.

The Elastic Indexed Job is supposed to graduate to beta in K8s 1.27. So we can work on this once we stop supporting k8s 1.26 (maybe next year?).

I agree

We may be able to introduce the JobSet instead of batch/job, although I think we need to wait for the JobSet API to be in beta.
https://github.com/kubernetes-sigs/jobset

As a first step, migrating to batch/job might be better. After that, we migrate to the JobSet.
Since directly migrating to the JobSet has too much influence on the training operator.

/lifecycle frozen

/assign
We're starting the discussion based on my enhancement proposal.


phpunit

Just installed skeleton.
Running php 7.1 and added phpunit 6.1
Get this error on starting unittest
Fatal error: Class 'PHPUnit_Framework_TestCase' not found in /var/www/html/vendor/silex/silex/src/Silex/WebTestCase.php on line 22

The Silex WebTestCase is not yet compatible with PHPUnit 6

will it be enough to use new namespaces in WebTestCase, or will it brake backward compatibility?

Silex can't require PHPUnit 6 I'm afraid, however you may be able to solve your problem by using a class alias:
if (!class_exists('PHPUnit_Framework_TestCase') && class_exists('PHPUnit\Framework\TestCase')) {
    class_alias('PHPUnit\Framework\TestCase', 'PHPUnit_Framework_TestCase');
}

class MyTest extends WebTestCase
{
}

(Note: I haven't tested, but it's worth a try)

The new namespaced class is available in PHPUnit 4.3.35 and in PHPunit 5.4+. So using the namespaced class for the TestCase will not make it require PHPUnit 6

Yep, I didn't know it had been backported to 4.8 and just learnt that after reading symfony/symfony#21534.
I'll make a PR that fixes the tests.

fixed


consider caring about older browsers

user report: TypeError: Object.values is not a function

Not enough complaints.


v1.12.0-next.2 version bump

Backstage release v1.12.0-next.2 has been published, this Pull Request contains the changes to upgrade to this new release
Please review the changelog before approving, there may be manual changes needed to enable new features:

Changelog: v1.12.0-next.2
Upgrade Helper: From 1.12.0-next.1 to 1.12.0-next.2

Created by Version Bump<PHONE_NUMBER>

Do not merge, there's an issue that will break the catalog views. Will follow up when I know more

@awanlin did you find out what the problem was here?

Sorry @benjdlambert, totally missed following up here. There was a bug in a change to the EntitySwitch was fixed pretty quickly and is good in 1.12.0. Going to close this in favour of the newer version though.


Bugfix: LeanAgent.init & .improve now returning Code

Thank you @ATheorell will get back on it promptly.


Added gradient drawing functions

I added some functions that work like sf2d_draw_rectangle and sf2d_draw_rectangle_rotate, only that draw it with a gradient instead of a solid color.

Looks good, gonna merge it


Model Addition Request [Feature]

Two model additions that would be great to have in automl:

catboost - in addition to existing lightgbm and xgboost, could provide some benefits in handling categorical features directly.

Keras - even a constrained handful of architectures, adding deep learning to automl to at least identify when it performs well.

Thanks for the suggestions! These are good features to add to automl, and we'll think about when to prioritize them. Could you also provide that feedback through this form?


ElevenLabs Python library

Summary
Refactored the implementation of the ElevenLabs API for voice synthesis in our chatbot.
Description
Transitioned from manually crafted requests to the ElevenLabs API to using their official Python client for text-to-speech synthesis. This change streamlines the process of voice generation, reduces the risk of API misusage, and simplifies our codebase. The voice validation system remains in place to ensure users provide valid voice names when using the /tts command.
Related Issue(s)

None

Motivation and Context
While our previous method of manually crafting requests to the ElevenLabs API was functional, transitioning to the ElevenLabs Python client offers more robustness and maintainability. By leveraging the official client, we ensure that our implementation remains consistent with any updates or changes made by ElevenLabs to their API.
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[x] Improvement (non-breaking change which refactors existing functionality)

Checklist:
Go over all the following points, and put an x in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!

[x] My code follows the code style of this project.
[x] I have read the CONTRIBUTING document.

Closing this PR due to a conflicting dependency version requirement with simpleaichat. The changes proposed in this PR cannot be merged at this time without causing potential issues. Will revisit these enhancements in the future.


[Bug Report] Theme builder - download function causes request timeout error

Element UI version
2.15.7
OS/Browsers version
Chrome v 97.0.4692.71
Vue version
2.6.14
Reproduction Link
https://github.com/wedbew/element
Steps to reproduce

Go to https://element.eleme.io/#/en-US/theme
Define color schema, you can basically change nothing
Click on download button
Then alert with Request Timeout appear.

What is Expected?
To download the theme variables
What is actually happening?
Request timeout, on mounted lifecycle hook -
e.onerror = function (t) {
ga('send', 'event', 'DocView', 'Ali', 'Outer'),
console.error(t)
},

i have same problem

me too

Same here :/


fix(button): use disabled prop instead of css attribute

The problem 🍿
I have noticed that the disabled attribute is not picked up when using custom anchor element styled with ${buttonStyle}.

Suggestion 🧑🏭
Use component disabled prop itself to style disabled buttons.

This would update the visuals but it wouldn't prevent the link from being clicked. If we are happy to still expect the consumer to prevent that then I guess there is no reason why this can't get merged

This would update the visuals but it wouldn't prevent the link from being clicked. If we are happy to still expect the consumer to prevent that then I guess there is no reason why this can't get merged

yeah I see the point - I think buttonStyle has been exported to allow the consumer to style any element like a button, not just an anchor element 🤔 so I guess preventing the click event itself from firing still needs to stay up to the consumer.
If we wanted to support anchor element within the Button we could implement a prop on it and use it like <Button as="a" ...> but it would probably still not cover all scenarios like Gatsby, NextJS etc

@steedems I wonder if there is much value in adding this. I feel teams will avoid using a Button link if they want to disable it. We tend to use a button using react-router-dom history.push function on an onClick.
Where do you plan to use this feature?

@raff-r I am using it on a component like this one
import { buttonStyle } from "@zopauk/react-components";
import { ButtonProps } from "@zopauk/react-components/types/components/atoms/Button/Button";
import Link, { LinkProps } from "next/link";
import { FC, MouseEvent } from "react";
import styled from "styled-components";

export const StyledA = styled.a`
  ${buttonStyle}
`;

export const ButtonLink: FC<LinkProps & ButtonProps> = ({
  href,
  styling,
  fullWidth,
  children,
  disabled,
}) => (
  <Link href={href}>
    <StyledA
      styling={styling}
      fullWidth={fullWidth}
      disabled={disabled}
      onClick={(e: MouseEvent) => disabled && e.preventDefault()}
    >
      {children}
    </StyledA>
  </Link>
);

I could implement my own button with the nextjs equivalent of history.push but I'd need to also implement the prefetch logic that nextjs Link includes out of the box - it'd have been handy to avoid doing that but it's definitely not a big deal.
I can close this and implement that way if we prefer 👍

Closing - implemented on NextJS as follows
import { usePrefetch } from "@utils/hooks/usePrefetch";
import { Button } from "@zopauk/react-components";
import { ButtonProps } from "@zopauk/react-components/types/components/atoms/Button/Button";
import { useRouter } from "next/router";
import React, { FC } from "react";

type ButtonLinkProps = { href: string; replace?: boolean } & ButtonProps;

export const ButtonLink: FC<ButtonLinkProps> = ({
  href,
  replace,
  ...buttonProps
}) => {
  const router = useRouter();
  usePrefetch([href]);
  const handleClick = () => {
    replace ? router.replace(href) : router.push(href);
  };
  return <Button onClick={handleClick} {...buttonProps} />;
};

@steedems lets re-open this to allow the styling on buttonLinks

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


While following the tutorial I get "can't find crate for test" while compiling for unit test execution

Hi there,
I'm using a custom build target for my Raspberry Pi bare metal kernel. After setting everything up and compiling the binary kernel for unit testing I get the compiler error "can't find crate for test".
Any clue what might be the root cause for this?
I'm not using cargo xbuild, but the new cross compile configuration in /.cargo/config like so:
[unstable]
build-std = ["core", "compiler_builtins", "alloc"]

Any help would be much appreciated.
Thanks in advance.

Hi,
specific to my tutorial, you would get this whenever rustc comes across a #[test] and not a #[test_case]  as it is emitted by the macro (https://github.com/rust-embedded/rust-raspberrypi-OS-tutorials/blob/master/13_integrated_testing/test-macros/src/lib.rs#L22).
I had this case while writing the tutorial and couldn't figure out whats going on. Turned out a third-party dependency that I pulled in through cargo had a macro that not only emitted code, but also a unit-test with it (it was the tock-registers). That was very hard to find.
I can't tell anything about building std with cargo, since I haven't touched that yet. Until now, just using the precompiled std for aarch64-unknown-none-softfloat is sufficient.

Closing this for now since no action on the issue.
Please reopen for follow-up questions.


Use cargo-component on CI

Right now our tests aren't working

I made tests again, though not with cargo-component.


MockHeader and test_is_within_trust_period

Initial mock and test for the Header and is_within_trust_period.
I hesitated on mocking the Commit because it ultimately requires Validator, which has a verify_signature method, which I think we'd like to avoid needing to test this core logic (ie. https://github.com/interchainio/tendermint-rs/issues/96#issuecomment-569360555).
We should consider some more changes to the traits to eliminate the need for this. It will make mocking everything much easier!

[ ] Referenced an issue explaining the need for the change
[ ] Updated all relevant documentation in docs
[ ] Updated all code comments where relevant
[ ] Wrote tests
[ ] Updated CHANGES.md

We should consider some more changes to the traits to eliminate the need for this.

I would definitely recommend using traits for these sorts of interfaces and making your mocks a struct which impls the trait you'd like to mock.
Libra pervasively uses this pattern, and the other added benefit is it makes the code more easily (re)composable.

@tarcieri we're already using traits for everything. The issue here is that mocking the trait would be too involved, because we need to mock a verify_signature method, and it's a method that's not even used in the module!
I think I solved it here: https://github.com/interchainio/tendermint-rs/pull/105. The solution was to make one trait (ValidatorSet) an associated type of the other (Commit). That eliminates the need for the verify_signature method to be exposed in the traits, because the Commit can access the underlying functionality of its associated ValidatorSet trait without being restricted to the trait interface. Wahoo!

Merging this into #96's branch. Will fix the build later and go through the changes of #107.


Acces Android storage FileDialog

Godot version
4.1.3
System information
ANdroid Oxygen OS 13.1    -  Android 10
Issue description
I saw some similar cases like this:
https://www.reddit.com/r/godot/comments/k05cqy/filedialog_in_android_pretty_useless/ without any solution valid
[edit] i came to this link from this link https://www.reddit.com/r/godot/comments/16cnwdr/how_to_use_android_native_file_picker_with_godot/
Open an android filedialog popups lead to an empty "/" with no authorized access even when using FileDialog.set_current_pass("res://")
Steps to reproduce
Open an android filedialog popups lead to an empty "/" with no authorized access even when using FileDialog.set_current_pass("res://")
Minimal reproduction project
N/A

Do you mean set_current_path? There's no set_current_pass

Now the first link is simply wrong because they are doing the wrong code, it should be: FileSelec.access = FileDialog.ACCESS_USERDATA
In your case it should be ACCESS_RESOURCES, have you set that?

Hard for me to test at the moment related to https://github.com/godotengine/godot/issues/84464

This works but i have no access to the android image or download directory, only res:// with shader_cache and vulkan dirs

You need to use ACCESS_FILESYSTEM to be able to access files located outside res:// and user://. Note that Android 11 and later require the use of scoped storage, and Android 10 may require adding permissions on the Android export preset for this to work.

So i tried that in android 13.1
$FileDialog.set_file_mode(FileDialog.FILE_MODE_OPEN_FILES)

  $FileDialog.set_access(FileDialog.ACCESS_FILESYSTEM)

  $FileDialog.set_current_path(OS.get_system_dir(OS.SYSTEM_DIR_DOWNLOADS))

but only have access to the folders: here what appears :+1: So how how can i do a correct setup

@tlloancy Is your issue solved?

i dont know reaally.

@tlloancy From your last comment it looks like you have successfully accessed Filesystem but you were only seeing folder, no files. Right? You need to enable storage permissions.
BTW, Native file picker is implemented on Android, it will be available from v4.4. You can test it in 4.4.dev4


Upgrade to React 0.14 and release a new major version

Discussion already has been starter in #77 but I think it's easier to track as a separate issue.
My suggestion would be

Upgrade the code to React 0.14
Release a new major version 3.0 of the package
Leave the 2.x as a maintenance branch for React 0.13 support

WYT?

Sounds good. Thanks a lot for all the help here. I added you as a contributor so that I don't slow you down. :)

Thanks! I'll try to commit something this week.

Glad  to hear that you plan upgrade soon.
I've just upgraded to 0.14.0 and I got below warning
Warning: React.findDOMNode is deprecated. Please use ReactDOM.findDOMNode from require('react-dom') instead.
beside that components seems to works well.

Yes, it will work with React 0.14 but this warnings are annoying. Thing will get broken by next release.

+1

Any updates on this one? Thanks for the awesome work so far :smile:

#84

Thanks @okonet ! Works great! No more warnings :+1:

We should thank @kumarharsh for that. 👏

Warning is gone many  @kumarharsh

:D


Support alignment with polar axis pointed away from celestial pole

Find a way to support alignment and tracking when the polar axis of a GEM mount is pointed far away from the celestial pole. For example, with the mount polar axis pointed to the west or east rather than near Polaris. First determine whether Gemini 2 supports this. If not, consider supporting mount alignment and modeling within Track.
Background: German equatorial mounts can't slew very far past the meridian before some part of the optical tube or other hardware collides with some part of the mount. When this occurs a meridian flip must be performed. A meridian flip takes tens of seconds to perform, often at the highest elevation (and therefore best) part of the pass. The highest elevation ISS passes cross the sky from northwest to southeast, or southwest to northeast, which means a meridian flip in the middle of the pass is always required. Visible high elevation passes are infrequent so losing imagery during the best part of these passes is a major loss.

Supported in https://github.com/seeing-things/track/pull/154


checkpoint_logged_out <- What is this?

Please follow the guide below

Issues submitted without this template format will be ignored.
Please read the questions carefully and answer completely.
Do not post screenshots of error messages or code.
Put an x into all the boxes [ ] relevant to your issue (==> [x] NO spaces).
Use the Preview tab to see how your issue will actually look like.
Issues about reverse engineering is out of scope and will be closed without response.
Any mention of spam-like actions or spam-related tools/libs/etc is strictly not allowed.

Before submitting an issue, make sure you have:

[x] Updated to the lastest version v1.5.7
[x] Read the README and docs
[x] Searched the bugtracker for similar issues including closed ones
[x] Reviewed the sample code in tests and examples

Which client are you using?

[x] app (instagram_private_api/)
[ ] web (instagram_web_api/)

Describe the Bug/Error:
Hi guys,
Recently I'm starting to receive this error. I have searched all over the internet and I just can't figure out what it means? Have you guys experienced something similar? Can you cast some light over what this means and how to combat this?
Thanks!

Paste the output of python -V2.7 here:
Code:
# Example code that will produce the error reported
from instagram_web_api import Client

proxy = 'my proxy here'
user_agent = 'Instagram <IP_ADDRESS>.95 Android (23/6.0.1; 640dpi; 1440x2560; ZTE; A2017U; armeabi-v7a:armeabi; qcom; en_US)'

API = Client(username, password, proxy=proxy, user_agent=user_agent)

Error/Debug Log:
Traceback (most recent call last):
  File "/var/www/FlaskApp/FlaskApp/routes/accounts.py", line 593, in login
    API = Client(username, password, proxy=proxy, user_agent=get_user_agent())
  File "/instagram_private_api/client.py", line 204, in __init__
    self.login(self.two_factor)
  File "/instagram_private_api/endpoints/accounts.py", line 51, in login
    'accounts/login/', params=login_params, return_response=True)
  File "/instagram_private_api/client.py", line 536, in _call_api
    ErrorHandler.process(e, error_response)
  File "/instagram_private_api/errors.py", line 137, in process
    raise ClientError(error_msg, http_error.code, error_response)
ClientError: Bad Request: checkpoint_logged_out

This is just another variant of the checkpoint challenge. As far as I know, it can be triggered when IG detects suspicious activity on your account (like logging in from a different geographical location).


allows symbols (e.g. ) in file names for QRDA uploads

some symbols caused problems with ASCII-8BIT versus UTF-8 in string comparisons.
previously these files just didn't show up in the list, even when there were errors

rubocop


files not found in starter branch.

URL of codelab
In which task and step of the codelab can this issue be found?
2nd task  - starter files
3rd task - Words app overview
Describe the problem
The files that are mentioned in the codelab 3rd task - Word app overview are not found in the starter branch
Steps to reproduce?

Go to 3rd task of given codelab
See the description of the files.

Versions
Android Studio version: 4.0
API version of the emulator: 30
Additional information
The files mentioned are -

but the starter branch has different files.
view here

it was a mistake

it was a mistake


Epoch directory src/main/{scala-2, scala-3}

Fixes https://github.com/sbt/sbt/issues/5895

Looks like sadly #5910 did not fix scripted hangs. I had to restart one of the builds.


[import/no-unused-modules] unusedExports reports false positives with absolute imports

When unusedExports option is used, exports that are imported with absolute paths are falsely reported as unused.
With settings:
"settings": {
  "import/resolver": {
    "node": {
      "paths": ["src"]
    }
  }
}

the following should not return any linting errors:
// src/module.js
import submodule from 'submodule';

submodule();

// src/submodule.js
const submodule = () => console.log();

export default submodule;

but the submodule export is unused according to this plugin. The export is not marked as unused if the import statement is relative:
import submodule from './submodule';

(Note that an absolute path starts with /, what you're describing is a bare specifier)
The issue, I think, is that src here is not what the resolver requires: https://github.com/benmosher/eslint-plugin-import/tree/master/resolvers/node which is indeed an absolute path, starting with /. This feature isn't meant to let you do alias requires, it's meant to mimic the (long deprecated) NODE_PATH environment variable.
Outside of eslint, how are you making these specifiers resolve?

Thank you for the reply, it seems to have solved my issue. I have gotten the above settings config from some blog post and it indeed works with import/no-unresolved but not with import/no-unused-modules.
What ultimately fixed the resolving for import/no-unused-modules was changing the settings to following:
"settings": {
  "import/resolver": {
    "node": {
      "moduleDirectory": ["node_modules", "src"]
    }
  }
}

If this is the intended usage of the settings it could be useful to have some references to this in the rule documentations as there seems to be some misinformation floating about in the blogosphere.
When it comes to resolving outside of eslint, it is done with webpack in this project.

In that case, you should use the webpack resolver, not just the node resolver (and then not include "src" in the node resolver at all)

That, of course, would be the best option in this case and after testing the webpack resolver it worked as intended. I will close this issue as it was only based on misunderstanding of the settings.


Dogecoin open source contributor

https://github.com/dogecoin/dogecoin/pull/2236

LG!!! Bitcoin is for everyone!
Tell your friends to use promo code DOGE for 10% off any Bitcoin 2022 passes on Tixr checkout, which also has a payment plan!
🌋
https://bit.ly/3AIOQGV


Update CI

Pull request checklist

[ ] Did you bump the project version?
[ ] Did you add a description to the Pull Request?
[ ] Did you add new tests?
[ ] Did you add reviewers?

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 80.52%. Comparing base (3e0135b) to head (7dce60c).

Additional details and impacted files
@@           Coverage Diff           @@
##           master       #4   +/-   ##
=======================================
  Coverage   80.52%   80.52%
=======================================
  Files           7        7
  Lines         190      190
=======================================
  Hits          153      153
  Misses         37       37

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


Request: a flutter team official permission handler plugin

Managing permissions across all android and ios versions has become quite complex due to the variety of changes through each new version. There are a few pub.dev plugins but none work correctly or are maintained. Please provide an  official solution maintained by the flutter team.

permission_handler is well maintained https://pub.dev/packages/permission_handler

permission_handler is well maintained https://pub.dev/packages/permission_handler

Nope, not anymore. Look at the issue list and the dates of PRs.

The plugin mentioned above appears to be actively developed based on recent commits, and is very popular based on pub.
Competing with a well-established, maintained plugin is not a good use of the Flutter team's limited resources, so this isn't a space we would get into.


feat: add NakWithDelay

For now if an error is returned from the handler, the message will be nacked. NATS JetStream, in turn, will try to send it back as soon as it receives a nack (if MaxDeliver > 1).

You can also control the timing of re-deliveries when messages are negatively acknowledged with Nak(), by passing a nakDelay() option (or using NakWithDelay()), otherwise the re-delivery attempt will happen right after the reception of the Nak by the server.
cc: NATS docs

For me, this is not quite the behavior that I would like to see. I would like the message to be sent again after some time.
To do this, the NakWithDelay function was added to NATS. In this PR, i have added an option to SubscriberConfig to control the delay of nacked messages.

This is a nice addition thanks.  I will try and merge next week - want to take a quick look at the option approach and see if that would open any additional doors vs calling NakWithDelay


#10766: Remove std::function for next set of ops

Issue : ##10766 , Tracking Issue : #10564

https://github.com/tenstorrent/tt-metal/actions/runs/10122118926 - passed


Cloud info: Add support for Oracle Cloud

@YoniKF @uriariel Status here?

PR is getting stale, closing.


Javadoc of Endpointservice is incomplete

The javadoc of com.adobe.acs.commons.adobeio.service.EndpointService need to be completed

https://github.com/Adobe-Consulting-Services/acs-aem-commons/pull/1502


How to ingore Discarded invalid value for parameter 'stacktrace' ?

sentry admin:

The event inspect from create_event
"%Sentry.Event{breadcrumbs: [], culprit: nil, environment: :prod, event_id: \"9e8d5a5cfbd14a169a9c7ca50e47a8bc\", exception: nil, extra: %{\"level\" => \"debug\", \"msg\" => \"client 105 from <IP_ADDRESS>:25505 connect\", \"name\" => \"gate\", \"time\" => \"2017-10-23T17:41:14+0800\"}, fingerprint: [\"{{ default }}\"], level: \"debug\", message: \"client 105 from <IP_ADDRESS>:25505 connect\", modules: %{hackney: \"1.10.0\", poison: \"3.1.0\", uuid: \"1.1.8\"}, platform: \"elixir\", release: nil, request: %{}, server_name: \"3pj\", stacktrace: %{frames: []}, tags: %{:env => \"production\", \"environment\" => \"jjh.zfxd.staging.3\", \"mem_addr\" => \"[:0000000e]\", \"server_name\" => \"jjh-server-1\"}, timestamp: \"2017-10-23T11:40:37\", user: %{}}"

event json
{
  "id": "a9628fbe05d04e34a73c25f0f77108c3",
  "project": 4,
  "release": null,
  "dist": null,
  "platform": "elixir",
  "culprit": "",
  "message": "client 105 from <IP_ADDRESS>:25505 connect",
  "datetime": "2017-10-23T11:44:18.000000Z",
  "time_spent": null,
  "tags": [
    [
      "server_name",
      "3pj"
    ],
    [
      "level",
      "debug"
    ],
    [
      "mem_addr",
      "[:0000000e]"
    ],
    [
      "app_env",
      "jjh.zfxd.staging.3"
    ],
    [
      "environment",
      "prod"
    ],
    [
      "host",
      "jjh-server-1"
    ],
    [
      "env",
      "production"
    ]
  ],
  "errors": [
    {
      "type": "invalid_data",
      "name": "stacktrace",
      "value": {
        "frames": [

        ]
      }
    }
  ],
  "extra": {
    "msg": "client 105 from <IP_ADDRESS>:25505 connect",
    "time": "2017-10-23T17:41:14+0800",
    "name": "gate",
    "level": "debug"
  },
  "fingerprint": [
    "{{ default }}"
  ],
  "metadata": {
    "title": "client 105 from <IP_ADDRESS>:25505 connect"
  },
  "modules": {
    "uuid": "1.1.8",
    "hackney": "1.10.0",
    "poison": "3.1.0"
  },
  "received":<PHONE_NUMBER>.0,
  "sdk": {
    "client_ip": "<IP_ADDRESS>",
    "version": "6.0.2",
    "name": "sentry-elixir"
  },
  "sentry.interfaces.Message": {
    "message": "client 105 from <IP_ADDRESS>:25505 connect"
  },
  "type": "default",
  "version": "5"
}

I'm seeing this error as well but moreso wanting to know why this happens and how to get my stacktrace in thee.

@lidashuang thanks for opening this!
@jalcine This error should only show for empty stacktraces.  If you see it in other cases, let me know.  As far as including stacktraces, Sentry.Plug and Sentry.Logger should both do it automatically.  If you're sending events yourself, https://github.com/getsentry/sentry-elixir/#capture-exceptions shows an example of including the stacktrace.

I've opened #224 to fix this.


Increase additional memory for proxy to 32 MB

Based on team findings in https://www.pivotaltracker.com/story/show/155945585, setting the default additional memory allocation to 32 MB should accommodate between 750 and 1024 concurrent connections without consuming the memory quota requested for the application instance itself. This default is also consistent with documentation at https://docs.cloudfoundry.org/concepts/http-routing.html#with-tls and with how this property has been set in several other environments.

Merged via https://github.com/cloudfoundry/diego-release/commit/37b175012089e69bf76f99eb72c596177dd4c1ca.


Update setup.py

The requirements list which is passed into install_requires in setup() is empty.
It should be populated with requirements_dev.txt, shouldn't it ?

Nope, I don't think so it is getting taken care of by requirements_dev.txt. Check it once by creating a new environment and installing it or installing it on colab.

Tried it out, packages in requirements_dev.txt aren't installed by python setup.py install

This is weird last time we tried doing this it worked.
cc: @khizirsiddiqui

@Het-Shah I didn't test it. :sweat_smile: Daily data limits + internet speed, pytorch is expensive.

wait I'll check on colab once.

Why is the import failing ?

Tried it out, packages in requirements_dev.txt aren't installed by python setup.py install

Yea this doesn't work. @NeelayS can you solve this issue?

Why is the import failing ?

I am able to import it on colab as well

Yea this doesn't work. @NeelayS can you solve this issue?

Yes, I'll do this

When I import VanillaKD, I have the same error 'No module named   KD_Lib.KD'.
I set a new conda virtual environment (python=3.6) for your project on linux, installed all requirements according to requirements_dev.txt(e.g. torch==1.5.0, torchvision==0.6.0), then I install with 'pip install KD-Lib'. Then I met this ModuleNotFoundError. Could you please tell me how to solve this issue?

Hi! Can you install KD_Lib from source. Basically follow these steps -
pip install transformers
git clone https://github.com/SforAiDl/KD_Lib.git
cd KD_Lib
python setup.py install

After running these try  from KD_Lib.KD import VanillaKD. I hope this will work.

@Het-Shah

Hi! Can you install KD_Lib from source. Basically follow these steps -
pip install transformers
git clone https://github.com/SforAiDl/KD_Lib.git
cd KD_Lib
python setup.py install

After running these try from KD_Lib.KD import VanillaKD. I hope this will work.

Hi, sorry for fussing around, but it seems installing the library from the source does not resolve the issue either :( I had a look at my virtualenv to see what's been installed, and it seems nothing have been installed, but __init__.py.

I suspect there is potentially something erroneous going on in setup.py?

Hey @eubinecto , thanks for debugging this, we are learning with package development, hopefully will sort this quick. Thanks again! :)

@eubinecto  we have fixed this on our side, please open another issue if you still face it. Thanks!


NRF52 HAL: Possible SPI lockup issue if switching between blocking and non-blocking API

There is code in hal_spi_txrx() that calls hal_spi_stop_transfer(). This code presumes that if you call TASKS_STOP when EVENTS_STOPPED is 0 you will always see EVENTS_STOPPED getting set to 1. I do not believe this is valid in all cases. I think that EVENTS_STOPPED will only get set if TASKS_START was called prior and EVENTS_STARTED is generated.

Indeed, calling hal_spi_stop_transfer() in hal_spi_txrx() could lock up the SPI. A fix for that particular issue will be committed shortly. However, there are some other issues which need to be addressed. Both of these issues may cause incorrect SPI bytes to be transmitted if the non-blocking driver is used.

The current non-blocking API uses the END_START shortcut if the buffer being transferred is > 255 bytes. This will not work if interrupts are disabled or delayed such that the END event occurs before the interrupt handler has time to update the TXD.PTR and and TXD.MAXCNT registers.  If this happens the peripheral will restart the transfer and incorrect bytes will be transmitted. I do not think it possible to guarantee this and thus I think the driver should be rewritten so that it does not use the END_START shortcut. This is not difficult and really the only drawback is that we will have to take the interrupt latency between spi transfers when doing transfers greater than 255 bytes. Note that this applies to the spi master API only (spi slave currently has a 255 byte transfer limit).

Anomaly 109 workaround is not present in our hal. This anomaly has to do with DMA possibly sending out an incorrect first byte. I believe that this anomaly should be handled in the non-blocking SPI interface. There will be a syscfg variable that can be turned on/off in order to compile in/out the workaround for this anomaly. Not sure if the default for this variable should be on or off. I am leaning towards off.

@wes3

In current implementation EVENT_END does not update pointers, this is done in EVENT_STARTED which is called just after transmission was started so they are ready for next transmission right away (registers are double-buffered). The only case I can think of where it could fail is if we have interrupts disabled/delayed for the duration of 2 consecutive transmissions so the EVENT_STARTED is not handled before starting 3rd transfer, which is at least ~500us when running at 8 MHz which is quite long. Current implementation was added in https://github.com/apache/mynewt-core/pull/1252/commits/1b53477bf4ffa4ad100a114b4044ccb0453377c7 - previously it worked as you described, i.e. was using EVENT_END to update pointers and restart transfer and it caused relatively long delays between consecutive chunks due to latency introduced by interrupt handling. So if we really want old, slower but safe implementation perhaps it's just enough to revert that patch (although I prefer current implementation).
We do not need that workaround since we always start SPIM manually thus HFCLK is running and it won't be disabled. The workaround is required only in case SPIM is started from PPI.

@andrzej-kaczmarek

Yes, I did indeed realize you would have to delay interrupts for that long and that it is unlikely but I think the end result could be pretty catastrophic. I am pretty paranoid about things like this and I think the delays between the 255 byte transfers should be relatively small (unless other interrupts are going). I guess we could raise the priority of this interrupt to help mitigate that. Given 255 bytes at 8 MHz is a 255usec transfer, that interrupt should be pretty quick so I cannot imagine it adding more than 20% to the whole transfer and that is only when large transfers are done (which I do not think are super common). I think that better than possibly writing erroneous things on the flash.

That part about the issue only occurring when starting from PPI confused me a bit I have to say. When I read section 3.2 of that document I did see it said "do not use PPI" but then there was some other wording about ensuring the CPU was on 1usec before using the serial engine and 16 usecs after or until transfer is complete. But if simply not using PPI to start this ensures that well all good then.

can we close this issue?

Yes, we can close this.


Update upgradeable attributes docs to include registryMirrorConfiguration

Issue #, if available:
Description of changes:
Testing (if applicable):
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/meow

/cherry-pick release-0.17


Quantization Code

Dear Author,
You've mentioned that to evaluate this method on Aachen Day-Night Benchmark, you did quantization for the matches. Will you release the code for the quantization part?

Hi @QsingHuan,
I will release the code for all evaluations in another repository image-matching-toolbox, to keep this repo clean. I plan to push the code for aachen benchmark next week in that repo.


Update pom.xml

added support for flyway plugins and log4j plugin in maven shade plugin fat jar generation

@TomBenjamins I missed this pull request and had already added the suggested changes in commit 302fbe7
Now closing this pull-request since the requested changes are already there