WebExt Theme updates

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details
There was some incorrect information on those MDN pages, notably that:
you needed to use frame and frame_inactive instead of accentcolor when only the latter is needed
the alias for textcolor was tab_text when it's actually tab_background_text

Please put me/someone familiar with the topic in the loop for technical review next time these docs are updated.
It also mentioned the following incorrect info, but that's our fault for the short notice:
The properties were removed in Firefox 70 as opposed to 69
toolbar_text is no longer deprecated/removed

Anyway, I've updated the doc regarding manifest.json to fix this incorrect info. Chris, would it be possible to get an editorial review ? Also, the 2 other docs I mentioned (and potentially others) have to be updated as well.
Need to update the following pages as well:
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Themes
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Themes/Theme_concepts
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/theme
See Bugzilla #1567684 for more details.
Acceptance criteria

[ ] All pages listed above have been appropriately updated
[ ] Changes have been reviewed

@irenesmith Some of these examples need to be updated to use the new properties too: https://github.com/mdn/webextensions-examples

@irenesmith, we're going to reference these docs in a blog post that goes live tomorrow at 8am PST; can they be updated by then? @ntim is the technical reviewer for these docs.
@reblooor, would you be able to update the examples?

I'm sorry but I didn't even see this message until now (11:15EDT) so no,
but I had planned on working on it today anyway, so I will do as much as I
can.
Irene
On Wed, Jul 24, 2019 at 5:47 PM Caitlin Neiman<EMAIL_ADDRESS>wrote:

@irenesmith https://github.com/irenesmith, we're going to reference
these docs in a blog post that goes live tomorrow at 8am PST; can they be
updated by then? @ntim https://github.com/ntim is the technical
reviewer for these docs.
@reblooor, would you be able to update the examples?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mdn/sprints/issues/1867?email_source=notifications&email_token=AABO6WRS4DTHCPTT6QNMH2LQBDEWFA5CNFSM4IGPDKJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2XWTUA#issuecomment-514812368,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABO6WVRQKWARG5HTQGPLTTQBDEWFANCNFSM4IGPDKJA
.

This issue is no longer valid. Because I couldn't accommodate them sooner, the web extensions team has updated the documentation and reviewed the change. Closing this issue.

@irenesmith While I did make most corrections, there might be some that I missed.
Post-reviewing again, this section still contains inaccurate info about frame_inactive and accentcolor: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/theme#Aliases
The line in question in the table can simply be removed.
More importantly, the examples+the docs all need to be updated to use new property names. I browsed around a bit and I still see some docs with the old property names (accentcolor, textcolor, headerURL) mentioned:

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Themes/Using_the_AMO_theme_generator
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Themes/Theme_concepts
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/theme/getCurrent
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/theme/update
https://github.com/mdn/webextensions-examples (there are some theme related examples in there)
I might have missed some...

For all of these you can simply do a find and replace with the new properties (frame, tab_background_text, theme_frame).
Please let me know if you've got any questions.

Rob made a list of things to update: https://bugzilla.mozilla.org/show_bug.cgi?id=1472740#c34

Hi all, Richard Bloor is taking care of this.


Add changelog

Hi,
I'm trying to understand what has changed between 1.4.1 and 1.5.0 to assess what I may need to update in my code. Are there any plans to create proper per release changelog?
Thanks for the awseome library!

We are now posting all changes to https://postmarkapp.com/updates. We will also add a "Libraries" category to make it easier to find updates to related to our official libraries.


Fix/disable IMDSv1

What this PR does / why we need it:
We have to disable the IMDSv1. The test will fail without a token. So we request a token from IMDSv2 and provide it for our current test case.

@Akendo Thanks for taking care. Porting it to rel-1312 now, and I've noticed you merged with a merge commit. I'm used to squash merge which makes it easier to cherry pick PRs. This is a thing where github remembers what you did last, I'd ask you to do squash merges in the future.


Signed comparison -- difference between sim and Verilog generation

This starts with a bug in my nMigen -- I perform a comparison between unsigned and signed values.   If this means behavior is undefined, then we can just close this issue.
It seems that simulation treats this as an unsigned comparison, while the generated Verilog has a signed comparison.
On https://nmigen.info/nmigen/latest/lang.html, I found "Similar to arithmetic operations, if any operand of a comparison expression is signed, a signed comparison is performed."   This is reflected in Verilog generation.
This is the example, with both simulation and Verilog generation:
from nmigen import *
from nmigen.sim import Simulator, Delay
from nmigen.back import rtlil, verilog

class DoubleCompareInstruction(Elaboratable):
    def __init__(self):
        self.in0 = Signal(32)
        self.out0 = Signal(1)
        self.signed_five = Const(5, signed(32))

    def elaborate(self, platform):
        m = Module()
        m.d.comb += [
            self.out0.eq((self.in0 < self.signed_five)),
        ]
        return m

if __name__ == "__main__":
    dut = DoubleCompareInstruction()
    sim = Simulator(dut)

    def process():
        for i in range(10):
            yield dut.in0.eq(i-2)
            yield Delay()
            print("(unsigned)", (yield dut.in0), "< (signed)5 --> ", (yield dut.out0))

    sim.add_process(process)
    sim.run()

    with open("dut.v", "w") as f:
        f.write(verilog.convert(dut, name='Dut', ports=[dut.in0, dut.out0]))

Simulation output; output values indicate an unsigned comparison:
(unsigned)<PHONE_NUMBER> < (signed)5 -->  0
(unsigned)<PHONE_NUMBER> < (signed)5 -->  0
(unsigned) 0 < (signed)5 -->  1
(unsigned) 1 < (signed)5 -->  1
(unsigned) 2 < (signed)5 -->  1
(unsigned) 3 < (signed)5 -->  1
(unsigned) 4 < (signed)5 -->  1
(unsigned) 5 < (signed)5 -->  0
(unsigned) 6 < (signed)5 -->  0
(unsigned) 7 < (signed)5 -->  0

Generated Verilog (note the signed comparison):
/* Generated by Yosys 0.9+3796 (git sha1 832f6aa7, clang 10.0.0-4ubuntu1 -fPIC -Os) */

(* \nmigen.hierarchy  = "Dut" *)
(* top =  1  *)
(* generator = "nMigen" *)
module Dut(out0, in0);
  (* src = "./bug.py:15" *)
  wire \$1 ;
  (* src = "./bug.py:8" *)
  input [31:0] in0;
  (* src = "./bug.py:9" *)
  output out0;
  assign \$1  = $signed(in0) < (* src = "./bug.py:15" *) $signed(32'd5);
  assign out0 = \$1 ;
endmodule

This is clearly a bug and should be fixed.

This is clearly a bug and should be fixed.

Thanks for the report!


No Sync

This issue tracker is only for technical issues related to Ravencoin.
General Ravencoin questions and/or support requests and are best directed to the Ravencoin Discord).
For reporting security issues, please direct message one of the core developers in discord.
Describe the issue:
When I start Paprikacoin Core the block list cannot be downloaded. This means I cannot synchronize or use my Wallet
Can you reliably reproduce the issue? -If i startup the Paprikacoin Core
Expected behaviour
Tell us what should happen
Actual behaviour
Tell us what happens instead
Screenshots.
If the issue is related to the GUI, screenshots can be added to this issue via drag & drop.
What version of Ravencoin are you using?
List the version number/commit ID, and if it is an official binary, self compiled or a distributio

n package such as PPA.
Machine specs:

OS: Windows 10

CPU: i7 11700
debug.log

RAM:

Disk size: 2 TB

Disk Type (HD/SDD): M.2 HDD

Any extra information that might be useful in the debugging process.
This is normally the contents of a debug.log or config.log file. Raw text or a link to a pastebin type site are preferred.
Firewall and Antivirus was deaktivatet while testing

Manual add of node solve Problems:

Fixed in current version


Is this possible now?

I need exact this functionality: https://user-images.githubusercontent.com/2826764/130787814-283f3d26-6c9d-448b-b2c7-879e60a3b05d.gif
Is this possible now? I mean X axis values, bacground grids and updatable text with interaction on touch? I've checked the api but couldn't see any api related to these

Hello,
if have the same question. The GIF https://user-images.githubusercontent.com/2826764/130787814-283f3d26-6c9d-448b-b2c7-879e60a3b05d.gif shows a legend for the x-axis. I created my ChartData with String, Double pairs. But I only get the selected data point value displayed in the title but no value labels at the x axis
I searched through the coding, but from what I was able to read there it seems for me that there is currently nothing implemented that would be able to show a chart like this.
Did I do something wrong or is this feature displaying not yet available?

same problem  😭

Same. Is there any progress on this?

Same, still nothing new?

Please see this comment/thread.
https://github.com/AppPear/ChartView/issues/243#issuecomment-1203537337


upgraded minimist dependency to latest version

As 0.0.8 version of minimist has security vulnerabilities, upgrading it to latest version

@substack Can you please review

@substack any update on this?. Could merge this PR if it is correct.?

Actually looks like this whole package is redundant now https://nodejs.org/api/fs.html#fs_fspromises_mkdir_path_options
Or use this fork which sometimes uses that method^ https://github.com/isaacs/node-mkdirp

Active mkdirp maintenance is over here now: https://github.com/isaacs/node-mkdirp
This issue was fixed 3 months ago: https://github.com/isaacs/node-mkdirp/commit/c5b97d17d45a22bcf4c815645cbb989dab57ddd8
Version 1.0 of mkdirp doesn't use minimist at all.

@isaacs Thank you for the info!

@isaacs Is there a way to add a note on the read me to indicate this repo is not longer being maintained & https://github.com/isaacs/node-mkdirp should be used? Or possible to archive the repo so others are aware?

That's a question for @substack.


Rename new lambdas from two to TS

Proposed changes
What changed

Renaming the lambdas from "Two" to "TS" for clarity
Pointing the API at the new name
Why did it change

API calls would error otherwise
Issue tracking

Checklists
Environment variables or secrets
Other considerations

Good idea, I took your work and split it up into multiple separate PRs - thanks!


Chronological Instructions in Docs

Do we think we could combine the "Copy your Model ID " and "Adding the classifierID" sections so the steps read more chronologically? Specifically it would be more natural for a user to copy and paste each field into XCode independently (ie making step 2 in "adding the classifierID" come after step 3 in "Copy your Model", etc).
Following current instructions, users are likely to replace Model ID with apikey in clipboard -> paste wrong fields into XCode.

@yalonIBM It is an issue when you have to go between multiple apps more than once. Is this what you were envisioning? Does it seem easier to follow?
Configuring the project

In Watson Studio on the custom model overview page, click your Visual Recognition instance name (it's next to Associated Service). Scroll down to find the Custom Core ML classifier you just created.
Copy the Model ID of the classifier.
Open the project in XCode.
Paste the ID into the classifierID property in the ImageClassificationViewController file.
Back in Watson Studio, go to the Visual Recognition instance overview page. Click the Credentials tab, and then click View credentials.
Copy the api_key or the apikey.
In XCode, paste the key into the corresponding property in the ImageClassificationViewController file.

Perfect! Thank you.


Enable HDFS audit logging

Currently, we do not use HDFS's security/audit logging. This log will be useful in analysis when HDFS goes down due a non-obvious cause.
To enable HDFS audit logging; based on our log4j.properties, we need to add the following Java variables to the environment variable HADOOP_NAMENODE_OPTS:
-Dhadoop.security.logger=INFO,RFAS -Dhdfs.audit.logger=INFO,RFAAUDIT
Eg:
cat /etc/hadoop/conf/hadoop-env.sh
...
export HADOOP_NAMENODE_OPTS="$HADOOP_NAMENODE_OPTS -Xms752m -Xmx752m -XX:ParallelGCThreads=14 -XX:+UseParNewGC -XX:+UseConcMarkSweepGC ... -Dcom.sun.management.jmxremote.port=10111 -Dhadoop.security.logger=INFO,RFAS -Dhdfs.audit.logger=INFO,RFAAUDIT”
...

Restart the NameNode services and check the /var/log/hadoop-hdfs/hdfs-audit.log.

Should we tune log rolling and backup for hdfs audit and other logs?

PR merged. Closing this.


Make token optional, allow delay of init()

Allow Userback to just "load" when no token is provided and not call init().
This will allow developers to delay the full initialization of a Userback widget until they know which token they want to use.

This is something I'd really appreciate as well!
Looks like a simple PR

Thanks for the PR @ekwoka, I have cut a v0.3.0 release which contains your PR.
I believe to fully complete this Issue there still needs to be a change to handle passing undefined explicitly to @userback/widget/init(). The issue is window.Userback.init() does not support this usage currently!
The only thing that would happen when @userback/widget/init(undefined) is called, is it would not error but load the  widget bundle and be ready to accept a follow up init() call that actually includes the token and runs the UserbackWidgetLoader.onLoad()  code to properly initialize.
We might look at tweaking the upstream window.Userback.init() in some upcoming work which could make this easier but just incase we don't or if anyone would like to see this earlier and create a PR I will leave the ticket open to note this.
Otherwise thanks again for the improvements made in your PR @ekwoka as it should make implementing this much easier.


Diff with ignress analysis tests

new diff tests with ingress objects, changes descriptions in commit messages

closing, as it was merged into #202


azcopy list a single file and output the filename

Which version of the AzCopy was used?
10.18.0
Note: The version is visible when running AzCopy without any argument
Which platform are you using? (ex: Windows, Mac, Linux)
Linux
What command did you run?
azcopy list "<container_url>/<container_directory>/<blob_filename>?<sas_token>"
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
What problem was encountered?
I can list all the files in the directory but when i list a single specific file it doesn't output the filename only:
INFO: ;  Content Length: 482.81 KiB
I tried using available attributes in --properties it does find the attribute of the single file i use in my command but still no filename in the output
How can we reproduce the problem in the simplest way?
By running the command to list a single file (blob). You won't get the filename as output.
azcopy list "<container_url>/<container_directory>/<blob_filename>?<sas_token>"
Have you found a mitigation/solution?
When listing a single file also show the filename in the output

This is expected behavior given the way the listing operation works, but we can correct this in 10.19.0.
I'll assign this to myself now and get a PR out soon.

Fixed in 10.19


Release new version of cdrs-tokio and cassandra-protocol

I would appreciate a new release of these crates, I can make a PR to bump the versions if thats helpful?

cdrs-tokio needs a breaking release due to the upgrade of tokio-rustls which is exposed in the public API of cdrs-tokio
cassandra-protocol can be a non-breaking release as I didnt see any breaking changes since the last release.

If we are unable to release cdrs-tokio at this time, then a patch release of just cassandra-protocol would be helpful.
Thanks.

cdrs-tokio doesn't need a version bump - TLS changes have been already published and introduced no changes to the API. The only changes since the last version were clippy-related. I will publish cassandra-protocol in a few minutes.

Thanks!


windows 8.1 generators installed but not showing

None of my globally installed generators are being listed or can be called, but they appear to be installed in Program Files (x86).  I.e.,
C:\Users\riesbeck\workspace>yo --help
Usage: yo GENERATOR [args] [options]

General options:
  -h, --help     # Print generator's options and usage
  -f, --force    # Overwrite files that already exist

Available Generators:

C:\Users\riesbeck\workspace>

But the appropriate directories seem to be there are and are non-empty
C:\Users\riesbeck\workspace>dir "C:\Program Files (x86)\nodejs\node_modules"
Volume in drive C has no label.

What else can I check? Here's the requested platform info. NODE_PATH is not set and there's no gruntfile.js. This is all part of a new setup to use yeoman with gulp and angular.
C:\Users\riesbeck\workspace>yo --version && echo %PATH% %NODE_PATH% && node -e "console.lo
g(process.platform, process.versions)" && type Gruntfile.js
1.4.6
C:\Coding\Ruby\Ruby193\bin;C:\Program Files\Java\jdk1.7.0_51\bin;C:\Coding\Java\apache\db-derby-<IP_ADDRESS>-bin\bin;C:\Coding\Java\apache\apache-ant-1.9.4\bin;c:\Users\riesbeck\\bin;C:\Users\riesbeck\AppData\Local\Box\Box Edit\;C:\Users\riesbeck\AppData\Local\.meteor;C:\Program Files\MongoDB\Server\3.0\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\SlikSvn\bin;C:\Coding\Python\Python27;C:\Coding\Python\Python27\Scripts;C:\Program Files x86)\Git\cmd;C:\Users\riesbeck\bin\;C:\Users\riesbeck\AppData\Roaming\npm;C:\Program Files (x86)\nodejs\;C:\Coding\HashiCorp\Vagrant\bin %NODE_PATH%
win32 { http_parser: '1.0',
  node: '0.10.36',
  v8: '<IP_ADDRESS>',
  ares: '1.9.0-DEV',
  uv: '0.10.30',
  zlib: '1.2.8',
  modules: '11',
  openssl: '1.0.1l' }
The system cannot find the file specified.

You can manually set NODE_PATH to C:\Program Files (x86)\nodejs\node_modules.
As to why you have the issue, I don't know, but my guess is that npm prefix isn't the value you expect. Maybe you have two versions of npm installed and they're not installing in the same directory or something like that.

Thanks very much for the prompt response! I did this
set NODE_PATH="C:\Program Files (x86)\nodejs\node_modules"
Alas, it didn't fix the problem, and doctor became unhappy. As I read the message, it's saying that path is already there in the npm root
C:\Users\riesbeck\workspace>yo --help
Usage: yo GENERATOR [args] [options]

General options:
  -h, --help     # Print generator's options and usage
  -f, --force    # Overwrite files that already exist

Available Generators:

C:\Users\riesbeck\workspace>yo doctor

Yeoman Doctor
Running sanity checks on your system

√ Global configuration file is valid
√ No .bowerrc file in home directory
√ No .yo-rc.json file in home directory
x
npm root value is not in your NODE_PATH

[Info]
  NODE_PATH = "C:\Program Files (x86)\nodejs\node_modules"
  npm root  = C:\Program Files (x86)\nodejs\node_modules

[Fix] Append the npm root value to your NODE_PATH variable
  If you're using cmd.exe, run this command to fix the issue:
    setx NODE_PATH "%NODE_PATH%;C:\Program Files (x86)\nodejs\node_modules"
  Then restart your command-line. Otherwise, you can setup NODE_PATH manually:
    https://github.com/sindresorhus/guides/blob/master/set-environment-variables.md#window
s

Found potential issues on your machine :(

Oops. My error with those string quotes.
set NODE_PATH=C:\Program Files (x86)\nodejs\node_modules
fixes the yo --help
Now to figure out why
THANKS!


401 unauthorized with cors.bridged.cc

Is this guide no longer current?
https://medium.com/bridgedxyz/cors-anywhere-for-everyone-free-reliable-cors-proxy-service-73507192714e

https://github.com/gridaco/base/issues/23


Run our *.md documents in this repo through the Grammer.ly service and update

Issue Summary
We would like to get our English polished up throughout the repo.
Aceptance Criteria

Every .md file in this repo has been run through the Grammer.ly service and updated accordingly

I'm on it. Please assign it to me @thinkingserious

Thank you @ays14, it's all yours!

@thinkingserious are the other two tasks as listed in the PR comment relevant to this issue. I thought they are not because of the two tasks were related to code so I did not check them. Is it fine? Please let me know if I missed something or did something wrong.

Closing all open issues and PRs. This repo is no longer maintained. Please use https://github.com/sendgrid/sendgrid-nodejs/tree/master/packages/client instead.


Serialization error is thrown when creating layout or page in the dashboard when using Layouts in a Web Farm.

Make Model Serializable for use in Web Farms with session state stored in a database. Currently a Serialization error is thrown when creating layout or page in the dashboard.

Hi @Garpo001, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

The fix is good, but it looks like something that could not use sessions at all. Could be stored in local storage and sent in the POST when necessary for the server.

The reason Element state is stored in Session is to support the following scenario:

User opens Editor Dialog for a specific element.
Element state is posted to the server (no need for session at this point).
The Element Editor page (loaded in an iframe inside the dialog) could provide multiple screens for the element editor experience. For example when adding multiple Slides to a SlideShow element, involving multiple redirects to various pages.

Although this could be done using post backs only, it would require the element developer to always post back the element state, as subsequent screens may need this information.
It would work, but it would make the implementation for element developers more complex I think.

I think it would be a breeze to inject a string (the json) in a hidden input in the form. Also, how many elements need multiple pages so far?
In MVC we tend to prevent any usage of Sessions, the only one so far has been for notifications (TempData).


customize the reading mode for each category

Describe your suggested feature
Could you please add a feature allows to customize the reading mode for each category
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.16.1.
[X] I will fill out all of the requested information in this form.

No. Also you didn't consider what happens when a manga is in two categories did you?


Tester unification

Currently, we have three tester interfaces:

Circuit ("synthesizable") tester, the only tester included in chisel3 (everything else lives in a separate repo). The testdriver, like the DUT, is synthesizable hardware and is written in Chisel.
Peek-poke tester, where Scala drives the device-under-test through peek, poke, and check commands. Obviously non-synthesizable, since it's possible to peek values, do some compute in Scala-land, and poke the results back.
Advanced tester, like the peek-poke tester, but provides parallel actions with a limited amount of interfaces (like Decoupled).

Of course, all these testers have their problems and advantages (some fundamental, some engineering):

Neither peek-poke nor advanced tester are available in the chisel3 repository. You have to include a separate dependency. Minor usability nit, though I think many like Python's approach of "batteries included".
Circuit tester is great for lightweight or concurrent tests, but sequencing events in time usually requires the test writer to manually write a state machine. Not fun.
Circuit tester is synthesizable, meaning that full testbenches can be deployed on FPGA (and generally are self-contained). Apparently some people actually do this.
Circuit tester doesn't support any backends other than Verilator, and Verilator has a high compilation cost. The chisel3 standard tests usually take several minutes to run, probably a good percentage of that time is compiling design through Verilator.
It's difficult to specify concurrency (see #547) in the peek-poke tester, and advanced tester only allows limited concurrency models. The circuit tester has concurrency native from its circuit nature.

The goal here is to unify all the different testers into a single tester included in Chisel3.
Reasoning:

support all the different backends (mainly for performance reasons: chisel3 tests may run faster through the FIRRterpreter)
unify the test specification model (which may be a hybrid approach, as detailed below)
include it in base chisel3 (tests aren't optional for engineers serious about hardware design).

Some hybrid approaches have been suggested:

If synthesizability isn't useful, then it's possible to write the circuit tester programming model in the peek-poke tester framework. Only the step command needs to be added to the peek-poke tester.
It is also possible to translate series of step, check, and pokes to synthesizable hardware, having Chisel generate the state machine. There would be no poke support, since the testbench would be standalone and not have a Scala testdriver.

Several attempts have been made before with systems like these, for whatever reason they have never gained traction.
This may make testvector literal specification a non-issue, since all test constructs live in Chisel-land and  can seamlessly use Chisel literals and future features like Bundle literals.

@jackkoenig @jackbackrack @sdtwigg @dt27182 @chick @azidar @aswaterman

As a heavy user & developer of peekpoke testers 1~3 years ago, I strongly disagree with this suggestion unless the following issues are resolved:

The main reason I stopped using peekpoke testers is it's extremely hard to use in the development mode. Once you have a submodule of chisel-testers in your project, you need to local-publish chisel, firrtl, and firrrtl-interpreters altogether. Don't tell me I need to local-publish them with this change. This sounds like adding additional dependencies on chisel, which will worsen #499.
For the above reason, I switched all peek-poke testers to hw testers to cut out the dependencies.(e.g. ucb-bar/riscv-mini#2) Never tell me I should change testers again with this change.

So there are two separate goals for this issue:

Determine the underlying programming model (or a hybrid approach). Synthesizable circuit-based, Scala-driven peek-poke, synthesized check-poke, etc...
Determine the implementation strategy, include packaging strategy. I would advocate for everything to be included in chisel3 instead of the current chisel-testers and dependency hell we have right now.

So having a peek-poke programming model isn't mutually exclusive with not having dependency hell, and we should make sure to discuss the pros and cons of each issue separately.

You're right that there are two separate goals, but I think @donggyukim is right in that fixing the packaging strategy should be super high priority because the current system doesn't really work. Unifying the repos won't fix the problem because this problem affects anyone who wishes to create a repo with their own Chisel utils or custom Firrtl passes (eg. https://github.com/ucb-bar/barstools).
To the best of my knowledge, sbt does not have an easy way of doing development with local versions (as we have discussed in #499). I recently found a couple of StackOverflow posts that might be helpful:

http://stackoverflow.com/questions/14351940/setting-up-sbt-environment-to-hack-on-multiple-libraries-at-once
http://stackoverflow.com/questions/14623138/how-to-toggle-between-project-and-library-dependencies-in-sbt

I'd be kind of upset if you entirely remove the peek-poke setup. It's super easy to get started with and mimics how some people would write (non-synthesizable) test benches.
And I agree that the packaging strategy right now is a huge nightmare. Every time I want to update something, I hate to go through 5 different dependencies and all publish-local and hope that I'm on compatible versions.
I spent a good hour last night just updating firrtl and everything else and hoping that no dependency broke. (and then I ran into the problem of barstools still not actually compiling...).

+1 on the sbt packaging issues
It seems like there are 2 options for getting everything that we what (easy concurrent test drivers and easy sequencing of events in time).
One option is to stick with the scala based software test model and implement some sort of event driven scheduling system. This option provides the full power of scala in writing the driver logic, but writing a event scheduler seems like a lot of work and a step back to verilog ...
The other options is to synthesize peek (check?), poke, step into Chisel state machines. This option provides good backwards compatibility with the existing hardware based tests, so people don't have to rewrite the tests yet again, which is a pretty big pro. However, there is less power in how to sequence the peek, poke, steps and there might be issues with running very large test vectors with this system since everything has to be synthesized into hardware.
I think I prefer the synthesized peek, poke, steps approach. Very large software driven tests probably don't need to concurrent drivers since they are whole system tests, so they can probably be written against the verilator produced C++. Also, don't we already have the SteppedHWIOTester? Is nobody using that anymore?

@shunshou when you want to write non-synthesizable testbenches, is it because you want to be able to control things in timesteps, or because you need to do some compute in Scala? The first could be solved in a synthesizable test specification model by having a framework to generate a state machine from check / poke / step commands, while the second is pretty much incompatible with a synthesizable framework.
One issue with synthesizable testbenches would be the delay model to use, since a common programming model is waiting until some condition (like signal valid) is true. A solution might be just wait(expr), which steps until expr === true.B.
It also seems like everyone here hates the packaging setup. What does everyone want to see there? A mega-repo of chisel3, FIRRTL, FIRRterpreter, and chisel-testers? Or some other split of those repositories?
It seems the SteppedHWIOTester is still there, but not much work has happened on it. Which I think is a good reason we should unifying testers...

Mega repo with git submodules seems like a logical solution. What was the reason for moving away from that model before? I know rocket had some issues with it. What where they?

@dt27182 The mega repo with git submodules is still the goal, the problem comes from dependencies between these submodules and sbt's lack of support for specifying that you want to use a local build instead of the library dependency. I'm trying to figure out how to work around this (see the StackOverflow links above), but I'm pretty sure it's impossible to do 100% with sbt, so we can look into using some sort of setup script or possibly environment variables to workaround.

@ducky64 for both reasons. Synthesizable tb makes sense, but only after I do sufficient debug with peek/poke. It's like I personally prefer to peek and stare at stuff before I convert everything into expects.

@jackkoenig
Sbt does support using local builds via sbt subprojects right? (I think this is what we were using before) Is it just that sbt doesn't allow a way to switch between subprojects and library dependencies?
And what is the reason we want to publish the subparts as sbt libraries?

@shunshou do you think the peek-for-debug could be replaced with a cycle-dependent printf?

@ducky64 a single mega repo is a one time solution that doesn't fix the fundamental problem. Anyone who wants to create a chisel library that uses an sbt library dependency in the common case but can also be used in development mode will run into the same problem.
@dt27182 That is correct, and I think you've hit the nail on the head.
Should we be publishing the subparts all separately? We currently have a 1-to-1 mapping of git repos to sbt libraries. Perhaps it would be better to publish everything together again. The repos can stay separate and instead the chisel-release repo publishes them as a single library.

Publishing together still doesn't solve the problem of separate chisel libraries though. I have an idea that might work:
Libraries like barstools have two sbt projects in them: barstools and barstools-dev. barstools has a library dependency on chisel3 and whatever else. barstools-dev is kind of a raw project that is intended to be used as a git submodule and have a parent project handle it's dependencies. Does this make sense? I'm kind of just spitballing here.

@ducky64 does the printf thing work w/ Verilator?

@shunshou Yes it does! And checkout the chisel3 wiki page about printing (if you don't know about Chisel's custom string interpolator for printf).

Basically, you can do stuff like
val (cycle, _) = Counter(true.B, 10)
val myReg = Reg(UInt(32.W))
printf(p"At cycle $cycle: myReg = $myReg\n")

@jackkoenig so my issue there is -- at least for PeekPokeTester, I can't peek/poke internal signals with Verilator. Idk how using an inline printf resolves this issue. Please explain?

Ah yeah it doesn't fix that

But you're saying that if I printf IO, I can do it even with Verilator?
Printf stuff makes sense with firrtlInterpreter, since you have access to internal nodes, but at least with PeekPoke, I can bring the internal signals out and hook it up to Verilator.
If I don't have the PeekPoke connection to Verilator, idk how that helps me any.

build.sbt can be configured to support either subproject or libraryDependencies for a project (it does use Scala after all) but:

it's not pretty,
it requires a triggering mechanism (how do you know which flavor to build)

We should make packaging a separate issue (from tester unification).

Ok, the summary so far seems to be (and please correct me if I'm wrong):

The packaging issue sucks, bad. Will be discussed separately in #556, but whatever new tester we make should be in chisel3 (main repository) to avoid dependency hell.
It seems no one has a solid use case for peek that printf can't address (internal signals aside). We might want to find some way for tester-level printf to work with internal signals.
I've seen no one really advocating for Scala-driven (peek-poke) test flow, so this seems like an unimportant use case. Especially since tester concurrency would require basically reimplementing Verilog.

And from the initial post we have:

Some people actually want to synthesize tests to FPGA.
The step-by-step testvector specification model is useful.

So the solutions seems to be:

Synthesizable testbench
Figure out printf on internal nodes / with Verilator
check/poke/step commands generated into a hardware state machine. This could be a general Chisel utility rather than a tester-specific construct.

Possibly additional timing constructs, like waitFor. We'll need to figure out a good unifying model so that this is sufficiently general.

Concurrency model to be determined. Possibly synthesized fork/join concurrency and/or synthesized LTL constructs. This would be on top of any concurrency constructs provided by base Chisel HCL.

Does this sound like a good solution that addresses everyone's use case?

It now seems that there are people who want to advocate for the Scala-driven testers (I think mostly for hardware models written in Scala?), which vastly complicates things now...
We're going to have a meeting next week about this. If you have thoughts and example use cases, please make them known on this thread. If you have a serious stake in this are are interested in attending, let us know...

Interested in attending

Ok, results from today's meeting:
Internal testing model
The fundamental testing model is circuit-based, with the DUT and test driver(s) being modules that are hooked up in a circuit simulator. The whole thing may or may not be synthesizable.
Rationale:

This defines a common tester API (between the DUT and tester environment).
Multiple test driver modules allow test drivers to be composed and split (i.e. instantiate different peripherals).
While we will need an event simulator to sequence circuit activity, this model may allow us to use Verilog.

Tester User APIs
We don't expect to be able to unify the tester API while supporting all possible use cases. Additionally, the above testing model allows a lot of flexibility in the implementation of each test driver module (such as calls to Scala code in black box test drivers).
Instead, we will focus (for now) on developing a testing API that will be the "default" for Chisel. These are the requirements we came up with:

Allow people to accomplish common testing tasks
Must have a sequential test specification API (i.e. poke, check, step), since this is a common way to write tests. This can synthesize into circuits.
This will probably be synthesizable overall.
Some kind of concurrency model would be nice, details TBD
Must have documentation, including limitations and recommendations for use cases past those limits.
Test literals specified as Chisel lits using literal extraction (rather than Scala types). This allows the use of near-future features (like Bundle literals and better enums) without a clunky parallel API.

Concurrency Model
Concurrency was discussed and is overall a hard problem. The model we were thinking of was a parallel ("threading") model, but with checks to prevent people from shooting themselves in the foot. The simplest is a dynamic check, which ensures within a cycle, peek results are not changed by poke results from another "thread" (and will assert out otherwise).
More advanced checks based on static (combinational dependence) analysis may be possible.
Misc
Misc notes that may be helpful:

There is some overlap (perhaps interop?) with MIDAS, a testing framework also being developed here.
Main argument for software testers was the ease of writing things in software and ability to use libraries. One specific use case was the ability to read out a circuit value and perform a fuzzy check (like partial Bundle check or FixedPoint check with tolerance).
SVA (SystemVerilog Assertions) is also interesting, basically LTL on circuits. Many can be synthesized, but some are difficult. At one point, this was a Chisel project.
Scala will ultimately likely be the top-level test driver (as opposed to C++, like for Verilator). Communications with C++ should be done using a high performance mechanism like JNI, since sockets are very slow. Bad performance was one of the reasons rocket has its own test infrastructure.

As always, thoughts and feedback are welcome!

I'd like to add build directory management must be overhauled.  There are two competing use case

When developing a circuit, a local, unchanging build directory makes inspection of files, e.g. firrtl output, annotations, etc makes life better
Libraries and chisel repos, have many tests, often with distinct tests run against the same chisel circuit which leads to collisions when scalatest parallelizes its tests.

In this case test need to be accessible but named in some way to avoid collision
It would be really nice if there was some friendly cleanup of these files because they can become an annoying waste of disk space

Superseded by #725.


Add a Mute button to the main UI, sync it with Mute button in right-click menu

I find myself toggling the mute on and off fairly regularly. I have mechvibes enabled on startup, and I always have the UI open, so it's easy to access things there and a bit cumbersome to open the tray, right click mechvibes, and click the mute button. This PR adds a mute button to the UI which is synced with the right-click menu in the tray.

@NotLazy


osiris cs2 branch has been released

if you aren't aware of it, the cs2 branch for osiris has been released, you can find it here:
https://github.com/danielkrupinski/Osiris/tree/cs2
or

@ImsilverDev Have you injected

mine not injecting

Dont think its ready to be injected.

@ImsilverDev Have you injected

its not ready, its just published

Anyway It has no features


How to add an item to firebase?

Can you please help me add an item with AR functionalities to the Firebase realtime database?

Solved the issue thanks


Build on Linux

Hi,
This project is awesome, congrats!
I'm trying to build it on ubuntu but it uses windows.h. Do you have any work around?
Thanks!

Hello, thank you 🙂
Right now i dont have workaround . Sorry.
Lukas
Dňa ut 5. 12. 2017, 19:03 Gabriela Olinto<EMAIL_ADDRESS>napísal(a):

Hi,
This project is awesome, congrats!
I'm trying to build it on ubuntu but it uses windows.h. Do you have any
work around?
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sekys/sk.seky.soccerball/issues/2, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHt93DSH9OPWMcz6H-a7YVsB-ip_sPFMks5s9YVsgaJpZM4Q2t6y
.


property order for multiple_prop PTs

It would be good to have and understand ‘rules’ for the ordering of properties in multiple_prop PTs. (It isn’t currently very clear how ordering is created for the options in a PT—I believe it has to do with the document-order in which properties appear in RDA-Vocabularies RDF/XML and the way that the recursive templates processes these.)
If possible**, the following are desirable:

Property order in multiple-property PTs is the same for the given PT in the Sinopia RT, in the property-list sub-list at the top of the HTML RT, and in the PT details section in the HTML RT
Property order follows some ‘rule’, for example, they are ordered by P-number, they are ordered alphabetically by English-language label, etc.

I asked @cspayne whether meeting the above bulleted requirements would be possible. But the more I think about it, I realize that this depends on mostly (all?) XSLT processing, not Python processing (but Python code for eliminating duplicate prop IRIs is related somewhat). I need to look at stylesheets and follow up.
CC @pan-zhuo

Preference for @pan-zhuo would be to present alphabetically by English-language element name

multiple_prop PTs are now alphabetical in Sinopia and html templates!


Launching Firefox

Any idea, why do I get this error, while trying to launch Firefox?
[Start] Browser Integration :: Opening new Firefox instance.
Exception in thread Thread-12:
Traceback (most recent call last):
  File "./threading.py", line 901, in _bootstrap_inner
  File "./threading.py", line 858, in run
  File "browser_integration_launch in C:\Users\grzegorz.krzyminski\AppData\Roaming\Sublime Text 3\Installed Packages\Browser Integration.sublime-package", line 28, in open_browser
  File "browser in C:\Users\grzegorz.krzyminski\AppData\Roaming\Sublime Text 3\Installed Packages\Browser Integration.sublime-package", line 29, in connect
  File "selenium.webdriver.firefox.webdriver in C:\Users\grzegorz.krzyminski\AppData\Roaming\Sublime Text 3\Installed Packages\Browser Integration.sublime-package", line 43, in __init__
  File "C:\Users\grzegorz.krzyminski\AppData\Roaming\Sublime Text 3\Installed Packages\Browser Integration.sublime-package\selenium\webdriver\firefox\firefox_profile.py", line 58, in __init__
    WEBDRIVER_PREFERENCES)) as default_prefs:
FileNotFoundError: [Errno 2] No such file or directory: 'C:\\Users\\grzegorz.krzyminski\\AppData\\Roaming\\Sublime Text 3\\Installed Packages\\Browser Integration.sublime-package\\selenium\\webdriver\\firefox\\webdriver_prefs.json'

[End] Browser Integration :: Opening new Firefox instance.

Hi,
I haven't looked at this plugin for a while. Firefox support has never
been completed, and probably with newer versions of either Firefox or
Selenium, or even Sublime, things will break. Let me take a deeper
look and I'll get back to you as soon as I have an answer.
Thanks for sharing!
Ale.
On 8/10/15, gkrzyminski<EMAIL_ADDRESS>wrote:

Any idea, why do I get this error, while trying to launch Firefox?
[Start] Browser Integration :: Opening new Firefox instance.
Exception in thread Thread-12:
Traceback (most recent call last):
File "./threading.py", line 901, in _bootstrap_inner
File "./threading.py", line 858, in run
File "browser_integration_launch in
C:\Users\grzegorz.krzyminski\AppData\Roaming\Sublime Text 3\Installed
Packages\Browser Integration.sublime-package", line 28, in open_browser
File "browser in C:\Users\grzegorz.krzyminski\AppData\Roaming\Sublime Text
3\Installed Packages\Browser Integration.sublime-package", line 29, in
connect
File "selenium.webdriver.firefox.webdriver in
C:\Users\grzegorz.krzyminski\AppData\Roaming\Sublime Text 3\Installed
Packages\Browser Integration.sublime-package", line 43, in init
File "C:\Users\grzegorz.krzyminski\AppData\Roaming\Sublime Text
3\Installed Packages\Browser
Integration.sublime-package\selenium\webdriver\firefox\firefox_profile.py",
line 58, in init
WEBDRIVER_PREFERENCES)) as default_prefs:
FileNotFoundError: [Errno 2] No such file or directory:
'C:\Users\grzegorz.krzyminski\AppData\Roaming\Sublime Text 3\Installed
Packages\Browser
Integration.sublime-package\selenium\webdriver\firefox\webdriver_prefs.json'
[End] Browser Integration :: Opening new Firefox instance.

Reply to this email directly or view it on GitHub:
https://github.com/apiad/sublime-browser-integration/issues/6


Replace some cs["string"] with cs[CONF]

What is the change?
Swapping out some (low priority) cs["string"] usages for cs[CONF_SETTING].
Why is the change being made?
Consistency! Plus I'm tired of having to grep for the string when you can just alt-click on the CONF setting in vscode and jump straight to it.

Checklist

[x] This PR has only one purpose or idea.
~Tests have been added/updated to verify that the new/changed code works.~

[x] The code style follows good practices.
[x] The commit message(s) follow good practices.

~The release notes (location doc/release/0.X.rst) are up-to-date with any important changes.~
[x] The documentation is still up-to-date in the doc folder.
[x] The dependencies are still up-to-date in setup.py.

I thought these were left out due to a circular import happening downstream.
Perhaps we should move the big block of imports into the method in question?

I thought these were left out due to a circular import happening downstream.

I haven't noticed any issues with anything downstream. I haven't run the full gamut of tests, but so far it seems ok. I could very well be missing something though.

Perhaps we should move the big block of imports into the method in question?

Which method? Sorry, I'm confused on this one.

Which method? Sorry, I'm confused on this one.

You can see def setOptionsFromCs(self, cs): already has two imports for CONF_ strings at the top of the method.
As I (albeit vaguely) recall, this was because one of our internal processes imported ARMI and got a circular import error otherwise. Though, to be honest, I don't remember which project.
We can talk about testing offline, if you like.

Looks like #1185 dealt with the circular import issue.
Happy to chat offline or when @opotowsky gets back. Either way, this is so low on the priority list it's arguably not on there at all lol.

That PR fixed a circular import issue.
If we merged this PR it would cause the same circular import again.
So, can you please move the relevant imports you added so you can use them in setOptionsFromCs() inside the setOptionsFromCs() method?
Or, we can talk offline, sure.


Module 1 exercises [Celestina Deku]

Please "drag & drop" exercise 1 file below.

WS2_M1E1_Submission.docx
2. Please UPDATE THE TITLE of this "Issue" in the title bar above with your name.

If you haven't done so, please go back to Module 1 and make sure to take
the post-training survey.

Thank you for your successful submission to the practice exercise! Please be sure to fill out the post-Module survey.


feat: add web-worker example

Experiment https://github.com/users/hi-ogawa/projects/4/views/1?pane=issue&itemId=80967865
todo

[x] reload browser on worker hotUpdate
[x] test
[ ] demo

[x] render in worker
[ ] rsc in web worker?

[ ] solve https://github.com/vitejs/vite/issues/7439
[ ] what to do with build?

need worker -> client build ordering
but need client build first to discover worker entries
replace during renderChunk?

feedback

[ ] environment.webCompatible should be included in optimizer hash

#113  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @hi-ogawa and the rest of your teammates on  Graphite

Merge activity

Sep 27, 9:07 PM EDT: @hi-ogawa started a stack merge that includes this pull request via Graphite.


[bug] failed to detect CBZ files using Add directory button

Describe the bug
Not sure if it is a bug or feature to implement.
When I want to add CBZ files using Add directory button I get 'Source directory is empty.' error. There is not such problem using Add file button with CTR + A all files from the same directory.
To Reproduce
Steps to reproduce the behavior:

Click on Add directory button
Choose a folder with CBZ files
Click on Convert button
See error

Expected behavior
Program should (?) format all CBZ files into desired format one by one chosen in drop down menu.
Screenshots

Desktop (please complete the following information):

OS: macOS 14
Device macbook pro M series

Add directory is for adding a folder of images, not cbz.

@axu2
For now I am using KCC from a clone I made recently, but I didn't want to stash my changes in repo just to make a screenshot so I made a screenshot of installed program I used to use.
Okay, so it could be a feature then

Also merged in some PR's just now that might affect yours.


Update CONTRIBUTING.md

Fixed a grammatical error in line 42 and rephrased line 3. @jnadroj please review.
⭐ Title
📝 Description
Include a summary of the change and which issue is fixed.
List any dependencies that are required for this change.
Please also include relevant motivation and context.
Fixes #(issue)
📷 Attachments
Include images, videos, GIFs or any other resource that shows the added functionality or bug fixes.

LGTM 💯


Skip disambiguation checkbox - not working?

The "skip disambiguation checkbox" does not work anyhow, so it is confusing. @KataBoku, am I correct?

For column classification it is even more confusing:

Solution: Hide if not implemented, correct/hide for classification dialog

@tomas-knap @KataBoku This checkbox was meant function only as a part of feedback (and affect the next, repeated run). It may be so, that it will have immediate effect, but definitely not in this iteration. I have added it to the list of components to disable in #52 .


[improvement](jdbc catalog) Disallow non-constant type conversion pushdown and implicit conversion pushdown #42102

cherry pick from #42102

run buildall


As an insecure FYP student, I have to be able to ring or notify my professor(s) for help via the platform

... so that I get the immediate help that I require.

Similar to #3


fix socketio import error

i think this changed at some point
from socketio import SocketIOServer
ImportError: cannot import name SocketIOServer

it looks like the failing tests are because of updated requirements i think pip install . gets django 1.8.
i'll try to fix it at some point tomorrow.

Thanks. I'll merge this but you should be aware this library is woefully out of date.
There's an issue with a lengthy discussion linked at the top of the readme describing what needs to happen. If you do intend to put any effort into this library, I'd strongly suggest focusing on that rather than anywhere else.
Thanks again!

BTW if you can let me know when you're done with everything you want to look then I can push a new patch release to PyPI.

yes this was meant to be the start to get the server running with latest gevent-socketio, i will attempt to get it working but i can't guarantee. At least if the server starts others can contribute. @krishn2014 mentioned he could contribute.
The tests passed locally on this one but because the repo wasn't updated for a while the tests broke anyway, i think if you run the latest master before this on travis will still fail

No problem at all! There's no obligation of course, just wanted to make sure your efforts weren't misdirected :-)
Thanks again.


Adding support for SOLID donut graphs

This single-line fix aims to add tooltip support for donut graphs created with the donutSolid:true parameter.
Without this patch, the tooltip plugin only looks to SVG DOM elements having the '.ct-slice-donut' class. The result is that the tooltip plugin actually fails to work, and is not functional on solid Donut charts.
As a chart created with the 'donutSolid:true' parameter lead Chartist to assign the '.ct-slice-donut-solid' class to the SVG DOM elements slices, it is therefore needed to perform an additional test in the tooltip plugin.
This patch will test if chart.options.donutSolid is true, and then define the tooltipSelector to '.ct-slice-donut-solid' instead of '.ct-slice-donut', which is relevant (and functional) only when chart.options.donutSolid is set to false.

Perfect Eduardo @ealves-pt ;-)


Per Pixel Transparency does not work from Godot 3.2.2 onward

Godot version
3.2.2 and onward
System information
Windows 10 Not so cool edition
Issue description
in 3.2.1:
Settings -> Per Pixel Transparency Allowed = true
Settings -> Per Pixel Transparency Enabled = true
Ready func:
func _ready():
get_viewport().transparent_bg = true;
works like a charm :)

in 3.2.2:
Settings -> Per Pixel Transparency Allowed = true
Settings -> Per Pixel Transparency Enabled = true
Ready func:
func _ready():
get_viewport().transparent_bg = true;
works like poop :)

I seriously don't know how to explain this better, but here are things that I tried and absolutely did nothing to fix it:

Changed default environment color to be transparent.
Changed renderers from 3.0 to 2.0.
disabled batching since 2D batching was introduced in 3.2.2.
Banged my head against the wall.

I searched some things, and it might have to do something with this, but I'm not that smart to know https://github.com/godotengine/godot/pull/38629
Steps to reproduce
in 3.2.2:
Settings -> Display -> Window Per Pixel Transparency Allowed = true
Settings -> Display -> Window Per Pixel Transparency Enabled = true
set up a 2D scene with a godot icon in the middle and have a script with a Ready func like this:
func _ready():
get_viewport().transparent_bg = true;
Minimal reproduction project
Be sensitive with it, okay...
Glass.zip

@DarkTimeStudio Can you (or anyone else) still reproduce this bug in Godot 3.4.4 or any later release?
If yes, please ensure that an up-to-date Minimal Reproduction Project (MRP) is included in this report (a MRP is a zipped Godot project with the minimal elements necessary to reliably trigger the bug). You can upload ZIP files in an issue comment with a drag and drop.
You can test https://github.com/Calinou/csgo-crosshairplus where I can confirm per-pixel transparency works on Linux with Godot 3.5beta4.

@Calinou Yes, it's still happening even after all this time. Here's a screenshot:

And here's the project, Maybe this a Windows only issue... not too sure.
Transparent.zip

@DarkTimeStudio Could you test the project I linked?

@Calinou Oh, It Actually worked! But I do not know the reason

Wait, never mind... that didn't work now that I am looking at it...

@DarkTimeStudio Which graphics card model and driver version are you using? Try updating to the latest driver version provided by your graphics card vendor (not your laptop/desktop OEM).

@Calinou Sorry for the delay in answers since I had finals last month.
I have 2 GPUs, an Intel HD 4000 with the latest driver and a Nvidia NVS 5200m with the latest driver.


[proposal] use gpu-memory or gpu-memory-ratio to identify whether the Pod is a multi-instance request

What is your proposal:
Currently, gpu-core is used to judge whether a Pod is a multi-instance request, but it is more accurate to use gpu-memory or gpu-memory-ratio to identify it. The reason is that gpu-core does not necessarily require setting. When multiple Pods share the same GPU, assuming that the isolation provides a time-sharing mechanism, it can ensure that multiple Pods can get computing resources. However, GPU Memory is different and must be set. The settings shown are only safe to run, otherwise OOM may be triggered more easily.
Is there a suggested solution, if so, please add it:
use gpu-memory or gpu-memory-ratio to identify whether the Pod is a multi-instance request

/assign

In v1.4.x, we will use koordinator.sh/gpu.shared as GPU Share main resource name.


Reference Implementations

Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/329
Originally created by @pnadolny13 on 2022-02-14 17:17:53

I'm not sure where the SDK docs are managed but there are some other good code samples and reference implementations that can get added. Right now the list is limited https://sdk.meltano.com/en/latest/code_samples.html.
Also linking to the academy repo and MeltanoLabs might be good resources too.

View 3 previous comments from the original issue on GitLab


prep-info-file generation for amplicon

Created seqpro_mf executable to perform seqpro work using amplicon mapping-files instead of sample-sheets.
Currently undergoing testing against actual run-directory.
unit-tests not added.

Ready for review! Many of the 19 affected files in this PR are due to the creation of an Amplicon-specific example run-directory. I created a new seqpro binary 'seqpro_mf' so I could preserve the original's command-line. However I now think I could merge them both back into a single seqpro, with a check to see if it looks like a sample-sheet or has mapping file columns and go from there.

For reference we decided to merge this and in a future PR:

merge functionality of seqpro_mf and seqpro
add individual tests, extra from the integration tests

Right now, we do need the files for testing. I can write something that generates the directory during the setup phase but for now, yes.
Will definitely add some unittests!


fix: swap branch exclusion for release-please on report gates diff workflow

it was based on the target branch, should be based on source branch.

Tested to show it skips properly


running php-cs-fixer to fix assertCount change

Codecov Report

Merging #2 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #2   +/-   ##
=========================================
  Coverage     92.56%   92.56%
  Complexity     1606     1606
=========================================
  Files            32       32
  Lines          3939     3939
=========================================
  Hits           3646     3646
  Misses          293      293

Continue to review full report at Codecov.

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


Support sorting items

Hello, thanks for greate library! I'm wondering if you can provide sorting items function base on column height, for example the shortest column will have next items. Looking foward to this function :D

Hello, it is not possible for now to add next items in the shortest column.
I don't plan to implement it but it's a nice feature. PR are welcome if you want to help.
Thanks


[VL] Fix Velox Parquet Write UT

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
(Fixes: #ISSUE-ID)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

@JkSelf
the test case before always fallback which is actually not cover velox native write scenario

@JkSelf / @zhouyuan
the test case before always fallback which is actually not cover velox native write scenario

ping again


Implement class gui::items::Cursor (cpp)

Needed to keep on implementing class avt::AVTWindow.

Completed; Compiles; Still to be tested.


Fix for fitInsideTheChart when tooltip is below or above the chart area

Fixes situation where the tooltip, having set fitInsideTheChart, goes above or below the chart area.
Was:

Is:

And please change the target to dev.
Thanks!

@imaNNeoFighT I changed the base branch to dev, and squashed all commits into one so it's nice and clean.


Updated WPF .NET Core project for LocalServices 100.10

Deleted and regenerated deployment config file to remove ArcMap components

@ZackAllen This PR is for your branch: updates the .NET Core project to v100.10 and corrects the deployment config file.


improve the responsiveness of courses section

I would like to work on this issue as a GSSoC participant!

Go ahead @murtuzaalisurti


Change Docs Order

What this PR does / why we need it:
Which issue(s) this PR fixes:
https://github.com/spidernet-io/spiderpool/issues/518
Special notes for your reviewer:
make sure your commit is signed off

HI @weizhoublue and @windsonsea , thanks for review . Can the PR be merged ?

/lgtm


[Bug] deserialization bug for sub model type

For the sub model type, when trying to deserialize it twice, the result is different:

The root cause is https://github.com/Azure/autorest.python/blob/7e14ddd7cddb55a73d52b6dd693df2762a12f0ea/packages/autorest.python/test/azure/legacy/Expected/AcceptanceTests/AzureBodyComplex/azurebodycomplex/_serialization.py#L461-L465
pop will change the original data

Current LRO logic for python is:

call internal xxx_initial to get initial response (e.g. here
wrap initial response and deserialization logic into poller from azure.core (e.g. here)
poller of azure-core will poll until get final response when users call .result() of poller
after get final response, poller will callback deserialization logic.

When get initial response, SDK has already deserialized the initial response (e.g. here). If azure-core poller find that initial response is already done, it will callback deserialization logic with initial response directly, which equals the initial response

https://teams.microsoft.com/l/message/19:meeting_Yzk1ZDlkNzAtZTAzZi00OTQzLWE1MDAtNTFiYTljODcwYzc4@thread.v2/1715740856459?context={"contextType"%3A"chat"}

add kwarg enable_deserialize which looks like: [WIP] Fix deserialization error for LRO which has discriminator by msyyc · Pull Request #2589 · Azure/autorest.python (github.com)
mark initial operation as stream operation.
We have 2 solutions and after discussion we choose the second one

fixed by https://github.com/Azure/autorest.python/pull/2628


Simple improvement to build.gradle.template

Operating system or device - Godot version:
Android: Godot 2.2
Issue description:

Integrating Firebase and so, need applicationId to be pressed in build.gradle
but changing
defaultConfig {
minSdkVersion 15
targetSdkVersion 23
$$GRADLE_DEFAULT_CONFIG$$
}
to
defaultConfig {
applicationId "com.godot.game"
minSdkVersion 15
targetSdkVersion 23
$$GRADLE_DEFAULT_CONFIG$$
}
inside platform/android/build.gradle.template seems to fix.
Steps to reproduce:
current build from 2.2-legacy for android

Problem is that we can change package/appId at export...

Ya, I kinda looked into it.


Wrong calculation in Programmer mode: 3000 * 80 = -22144

In Programmer mode the result for 3000 * 80 is -22144, which is wrong, while in Standard and Scientific mode the result is correct (240000).
Steps To Reproduce

Switch to Programmer mode
Type 3000 * 80
(I did not test it on other machines)

Screenshots

Device and Application Information

OS Build: 10.0.17134.0
Architecture: X64
Application Version: 10.1904.31.0
Region: ru-RU
Dev Version Installed: False

Requested Assignment
I'm just reporting this problem.  I don't want to fix it.

@Edgar-P-yan click on the word toggle button you will realize that the answers will be changing based on that. So from reading, i found out that the word type is 16 bits and thus 240000 will be evaluated to a 16-bit  binary number which is the 2's complement for-22144.
I may be wrong about the explanation but yeah. Just ensure that the button you have D-Word to be safe.

@MelulekiDube is correct.  This is "By Design".  In your example, you were looking at numbers defined as WORD, so the negative answer that you're seeing is simply due to integer overflow.

@HowardWolosky , @MelulekiDube. Now i see. Thank you for explaining


Warn when a private member is not used in a class/struct

Code analysis already does this.

I updated the description. It is up for grabs now.


specify in documentation to make a within before click or type

move in https://github.com/Orange-OpenSource/uuv/issues/252


feat(Documentation): quick setup with virtual environment

Do you mind incorporating this into the GettingStarted doc --> https://github.com/MultiAgentLearning/playground/blob/master/GettingStarted.md please?


Speed up segment Intersection

Currently uses an $O(n^2)$-time algorithm to find line intersections. This can be sped up to $O(n\log n)$ using appropriate data structures like an AVL tree.

New algorithm has been tested against all examples in the data set, though the new algorithm can produce different (hopefully better) results due to an adaptive epsilon versus a fixed epsilon with the old algorithm. Here is a graph comparing both algorithm running times on all examples of the instagram data set, resulting in a roughly ~50x speed up on average. Most significant improvement is for processing example 304, which for the old algorithm took ~12 minutes but for the new algorithm takes ~2 secs.


confusing treatment of context function literal

Compiler version
3.4.2
Minimized code
File1:
def foo() =
  (x: Int) ?=> x + 1

File2:
def foo() =
  println()
  (x: Int) ?=> x + 1

Output
File1: no error
File2:
-- [E172] Type Error: Main.scala:3:20 ------------------------------------------
3 |  (x: Int) ?=> x + 1
  |                    ^
  |    No given instance of type Int was found for parameter of (Int) ?=> Int
1 error found

Expectation
Both files should compile. Or both files should fail to compile.

Similar to https://github.com/scala/scala3/issues/19021
https://docs.scala-lang.org/scala3/reference/contextual/context-functions.html
Context functions require that the expected type is a context function and the expression is a context function literal. Otherwise a context function value gets applied.
Maybe the doc needs to be more explicit, and also show what does not work.
Maybe the "implicit function types" blog could be updated and added to the docs.

There are two rules that guide type checking of implicit function types.

references to implicit functions get applied to implicit arguments in the same way as references to implicit methods.

The second rule is the dual of the first. If the expected type of an expression t is an implicit function type then t is converted to an implicit closure, unless it is already one.

The broader context is that the feature is a way to simplify the syntax for passing implicit context. It is not merely a different way of writing { implicit x => } anonfun literals. (That is a feature people ask for back.) In this sense, it does not cater to folks writing explicit arrows, which is to restore boilerplate.
Leaving this ticket open for the doc enhancement.

"Context functions require that the expected type is a context function and the expression is a context function literal." makes sense to me, but even with that in mind, I still find the compiler's behavior confusing.
In particular, neither File1 nor File2 specifies foo's return type, so "the expected type is a context function" is false in both cases. Yet File1 compiles and File2 doesn't.
Furthermore, if I change File2 to
def foo(): (Int) ?=> Int =
  println()
  (x: Int) ?=> x + 1

to make it clear that a context function is expected, compilation fails with this error:
-- [E007] Type Mismatch Error: Main.scala:3:2 ----------------------------------
3 |  (x: Int) ?=> x + 1
  |  ^^^^^^^^^^^^^^^^^^
  |  Found:    (Int) ?=> Int
  |  Required: Int
  |
  | longer explanation available when compiling with `-explain`
1 error found

Which doesn't make sense to me. Where does Required: Int come from?
In contrast, a similar change to File1 is totally fine.
Additionally,
def foo() =
  val f = (x: Int) ?=> x + 1
  f(using 10)

compiles fine. But in val f = (x: Int) ?=> x + 1, there is no expectation for f to be a context function either (no explicit type is given to f), so compilation should fail with a similar message as File2 (the first version), to be consistent.
At the risk of side tracking, I would like to mention another confusing behavior, because it somehow seems related:
def foo() =
  given Int = 10
  val f = (x: Int) ?=> x + 1
  f

compiles. But
def foo() =
  given Int = 10
  (x: Int) ?=> x + 1

fails with
-- [E172] Type Error: Main.scala:3:20 ------------------------------------------
3 |  (x: Int) ?=> x + 1
  |                    ^
  |    No given instance of type Int was found for parameter of (Int) ?=> Int
1 error found

Example for inferring a context function when the RHS is a context function literal: https://github.com/scala/scala3/blob/main/tests/run/implicitFuns.scala#L8
It's not sufficient that the RHS is a block that may later turn out to have a context function result expression.
I, too, made up a brief catalog.
I wrote: "There must be a pop quiz on Coursera that asks which of these compiles as expected?"
I retracted the comment, but I think it's funny because one wouldn't expect this to be that tricky. (As I'm sure you agree.) Maybe I'm wrong that this is only a doc issue; maybe they've come up with an improvement in ergonomics.
def foo(): Int ?=> Int =
  println()
  (x: Int) ?=> x + 1

def bar() =
  (x: Int) ?=> x + 1

def baz() =
  println()
  (x: Int) ?=> x + 1

def buz(): Int ?=> Int =
  println()
  val f: Int ?=> Int = (x: Int) ?=> x + 1
  f

def f: Int ?=> Int = (x: Int) ?=>
  println()
  x + 1

buz is your side-tracking example, but it doesn't compile as I would expect, since it does not return f unmolested. It has an extra closure, but I see that is eliminated in erasure, so, "no harm no foul".
The useful option is -Vprint:parser,typer. The docs emphasize that the rewrites happen early, that is, before type checking; for example, invoke(e) becomes invoke(x ?=> e) to make the implicit arg available in e.
foo (which is when you naturally give it an explicit CF return type) is actually
    def foo(): (Int) ?=> Int =
      {
        def $anonfun(using contextual$1: Int): Int =
          {
            println()
            {
              def $anonfun(using x: Int): Int =
                {
                  x.+(1)
                }
              closure($anonfun)
            }
          }
        closure($anonfun)
      }

where the "outer" function wrapper must return an int
and the difference with buz that typechecks:
    def buz(): (Int) ?=> Int =
      {
        def $anonfun(using contextual$2: Int): Int =
          {
            println()
            val f: (Int) ?=> Int =
              {
                def $anonfun(using x: Int): Int = x.+(1)
                closure($anonfun)
              }
            f.apply(contextual$2)
          }
        closure($anonfun)
      }

def foo() =
  given Int = 10
  (x: Int) ?=> x + 1

has the apply inserted at the block (!).
    def foo: <error no implicit values were found that match type Int> =
      {
        final lazy given val given_Int: Int = 10
        {
          def $anonfun(using x: Int): Int =
            {
              x.+(1)
            }
          closure($anonfun)
        }
      }.apply(/* missing */summon[Int])

that is the same as baz, but is a more interesting puzzler during happy hour.

Thank you for the explanation. But I still can't deduce a clear set of rules which I can use to reason about the compiler's behavior. Most importantly, why is apply(summon[Int]) or apply(contextual$2) added in some cases and not others?

That is rule one. (There are two rules.)
def f(i: Int)(implicit ord: Ordering[Int]) = ???
f(42)
f(42)(Ordering_Int)

analogously
def f: Int ?=> Int = ???
f
f(given_Int)

compare with
scala> def f(i: Int)(implicit ord: Ordering[Int]) = i+1
def f(i: Int)(implicit ord: Ordering[Int]): Int

scala> Option(summon[Ordering[Int]]).map(f(42))
val res0: Option[Int] = Some(43)

where f(42) is applied or not depending on the expected type.
The details page in the reference says:
Context function literals (x1: T1, ..., xn: Tn) ?=> e are automatically created for any expression e whose expected type is scala.ContextFunctionN[T1, ..., Tn, R], unless e is itself a context function literal. This is analogous to the automatic insertion of scala.Function0 around expressions in by-name argument position.
The analogy holds in the other direction, where p reference to a by-name parameter usually means evaluation, except in eta-expansion.
So rule two is when apply is not inserted. It says your ordinary expression is wrapped in a context function where that is expected ... unless it is already a context function literal, which is the case you ask about.
Probably one of the usual suspects will come along to provide clarifying insight.

OK, I think I understand now.
The Rules

A context function literal always simply produces a context function value, no matter the context of use.
In a context where a context function is required/expected (based on explicitly/user provided type signatures), an expression which is not a context function literal will be rewritten to be wrapped inside an auto-generated context function literal. This is done even if the expression's type is a context function (but the expression is not a context function literal).
In other contexts, if an expression has a context function type, but is not a context function literal, then it is rewritten such that an invocation of "apply(summon[...])" is attached to it.

Note that when a block expression appears in a Rule2-context, the context DOES NOT propagate to the block expression's last sub-expression. For example, in
def foo(): (Int) ?=> Int =
  given Int = 10
  val f = (x: Int) ?=> x + 1
  f

Because of the explicit return type for foo which asks for a context function, the block expression {given Int = 10; val f = (x: Int) ?=> x + 1; f} will receive a Rule2-rewrite. But f, the last sub-expression, which is a context function but not a literal, will receive a Rule3-rewrite.
Case 0
def foo() =
  (x: Int) ?=> x + 1

def foo(): (Int) ?=> Int =
  (x: Int) ?=> x + 1

Both compile because of Rule 1.
Case 1
def foo() =
  println()
  (x: Int) ?=> x + 1

In this case, the compiler encounters TWO expressions with context function type. First the compiler comes across (x: Int) ?=> x + 1. The compiler leaves it be (Rule 1). As such, the compiler then comes across { println(); (x: Int) ?=> x + 1 }, which has type (Int) ?=> Int, so the complier rewrites it to { println(); (x: Int) ?=> x + 1 }.apply(summon[Int]) (Rule 3). Even knowing the rules, this could be surprising, because one may not realize that the multi-line body of a method is in fact an expression. But it is, and thus we get the compilation error:
-- [E172] Type Error: Main.scala:3:20 ------------------------------------------
3 |  (x: Int) ?=> x + 1
  |                    ^
  |    No given instance of type Int was found for parameter of (Int) ?=> Int
1 error found

The error message unfortunately adds to the confusion. As it makes it seem like the compiler has added apply(summon[Int]) to the literal. But really the compiler has added apply(summon[Int]) to the block expression.
Case 2
def foo(): (Int) ?=> Int =
  println()
  (x: Int) ?=> x + 1

Similar to Case 1, except { println(); (x: Int) ?=> x + 1 } is now in a context where a context function of type (Int) ?=> Int is expected, thus Rule 2, not Rule 3, is triggered. So the block expression is rewritten to (_: Int) ?=> ({ println(); (x: Int) ?=> x + 1 }: Int). Hence the compilation error:
-- [E007] Type Mismatch Error: Main.scala:3:2 ----------------------------------
3 |  (x: Int) ?=> x + 1
  |  ^^^^^^^^^^^^^^^^^^
  |  Found:    (Int) ?=> Int
  |  Required: Int
  |
  | longer explanation available when compiling with `-explain`
1 error found

Once again, in addition to the rules, it is key to realize that method foo's whole body is a block expression. As such, the expectation of an (Int) ?=> Int context function as foo's return value is applied to the block expression (but not to the last expression (i.e. the literal) within the block, as explained in The Rules)
Case 3
def foo() =
  given Int = 10
  val f = (x: Int) ?=> x + 1
  f

Two expressions with context function types. First (x: Int) ?=> x + 1, no rewrite (Rule 1). Then f, Rule 3 adds apply(summon[Int]). As such, the block expression { given Int = 10; val f = (x: Int) ?=> x + 1; f } has type Int, and is in an unconstrained context, so no more rewrites. Compilation passes.
Case 4
def foo() =
  given Int = 10
  (x: Int) ?=> x + 1

Two expressions with context function types. First (x: Int) ?=> x + 1, no rewrite (Rule 1). Then { given Int = 10; (x: Int) ?=> x + 1 }, Rule 3 adds apply(summon[Int]). Since apply(summon[Int]) is outside the block, it cannot see given Int = 10, thus the compilation error:
-- [E172] Type Error: Main.scala:3:20 ------------------------------------------
3 |  (x: Int) ?=> x + 1
  |                    ^
  |    No given instance of type Int was found for parameter of (Int) ?=> Int
1 error found

Rules Changes to Reduce Confusion
If the rules are changed to the following, the compiler's behavior may be less confusing.

A context function literal always simply produces a context function value, no matter the context of use.
In a context where a context function is required/expected (based on explicitly/user provided type signatures), an expression which is not a context function literal will be rewritten to be wrapped inside an auto-generated context function literal. This is done even if the expression's type is a context function (but the expression is not a context function literal).
In other contexts, if an expression has a context function type, but is not a context function literal or block expression, then it is rewritten such that an invocation of "apply(summon[...])" is attached to it.


send_resolved does nothing on Pagerduty receiver

Per the Pagerduty receiver docs, we have our configured with send_resolved: true.
Experimentally, it doesn't seem to do anything. I manually stopped a service in a way that would trigger a pagerduty alert from the alertmanager, and after the alert fired and I got the page, I restored the service and watched the alert clear from Prometheus and the Alertmanager. The Pagerduty incident neither changed nor recorded having received any additional input.
I would have expected send_resolved to put the incident in the "resolved" state.
(h/t to @stapelberg's Pushover feature request for reminding me to verify this behavior)

send_resolved: true is the default state for the PagerDuty receiver:
https://prometheus.io/docs/alerting/configuration/#pagerduty-receiver-pagerduty_config
To confirm: An alert ceases firing in your Prometheus, so it no longer appears in Alertmanager, but the alert in PagerDuty is not being automatically resolved?

Correct.

Can you provide some additional information about your setup? Version, OS, if you're using one of our binaries or one you compiled yourself, etc.
Also, have you checked the logs to confirm whether or not Alertmanager is attempting to send a request to PagerDuty to resolve? I'm wondering if Alertmanager is sending an incorrect resolved message, or if it's not sending one, or what.

Sure. We're using the 0.5.0.linux-amd64 release from the Github releases, Ubuntu 14.04. The pagerduty config is the only endpoint on that receiver, and it's just the service key and the send_resolved, so nothing too fancy.
I'll try to find some time to check the logs later. I can tell you that Pagerduty has a little history of all the activity it has on an alert, and it only showed the initial notification from Alertmanager.
Thanks!

Sure thing. Have you tried the 0.5.1 release?

We just upgraded to it, I'll try my manual reproduction again when I can carve out some time for it.

We had a production issue yesterday that happened to confirm correct resolution behavior via the Pagerduty API. Not sure if 0.5.1 fixed it or if there was something wrong in my original manual test.

I am experiencing the same issue on 0.5.1 for the Opsgenie receiver.

We are still experiencing this with PD and Alertmanager `v0.18.0. The alerts no longer appear in Alertmanager, but the incidents in PD don't get auto-resolved

We have experienced the same situation with v0.21.0. Alert resolution does not resolve the incidents in PD.
We need to resolve the incidents in PD every time.

Maybe the alerts were silenced or inhibited while they resolved? See #226.

We didn't do any silencing or inhibiting action during the incident 🤔

Same problem here for resolution of resolved alerts with Opsgenie (Alertmanager v0.21.0). They just never get resolved in Opsgenie when they stop firing in Alertmanager.
I've created a separate issue for that before finding this one.

Any update on this issue ?

Any update on this issue?

Running into this issue.   Issue is resolved when looking in alerts but no resolution sent to PagerDuty.    Multiple alert types.

still running into this issue


dotty-bench.epfl.ch sometimes records running time of 0 seconds, skewing moving average

Lately, https://dotty-bench.epfl.ch has looked pretty eratic:

Zooming out and enabling "min", we see that some points are incorrectly recorded as 0 second long:

cc @mbovel @hamzaremmal

Sorry this issue has been standing for so long. I plan to clean up the data when merging the new visualiser (#21720) and the new benchmarks infrastructure (#21719). This should be done in a few weeks.


Update EmailSuggester.java

Personal experience - on mobile devices I often incorrectly write 'homtail', feel free to add if you deem that information useful!

Thanks @ed-george !

Not a problem


Create CWL workflow tool to run RNAseq matrix using CIBERSORT docker image

Get access to the CIBERSORTx docker image (https://cibersortx.stanford.edu/download.php) and run on the CCRCC mRNA expression matrix to get patient-specific cell predictions.  Ideally we'd build a CWL command line tool that will take as input the MRNA matrix file and return as output the sample-by-cell output. I'm not sure which matrix to use, but perhaps we can download a few to see which have the best input for CIBERSORT.

CIBERSORTx requires obtaining a license before using it. I need to wait for their approval. I should be able to get it tomorrow or Friday. I have run the test cases following the tutorial, seems straight forward using their online portal. But might need test once I got the docker image


Add tracing to arbiter core

it would be nice for us to have more information from our tracing and logs or at least optionality for more verbosity.

The verbosity will be decided by the user's tracing subscriber so we just have to set up logs to emit from logical spots 😁
I'll take this one ser


execute_mdx_dataframe can't extract string value?

Hi, @MariusWirtz
I have constructed a valid mdx using mdxpy but failed to retrieve value via execute_mdx_dataframe. ""test22" is a string value.
It gives me the following errors:
raceback (most recent call last):
File "pandas_libs\parsers.pyx", line 1141, in pandas._libs.parsers.TextReader._convert_tokens
TypeError: Cannot cast array data from dtype('O') to dtype('float64') according to the rule 'safe'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "c:\testMDXClear.py", line 43, in
df = tm1.cubes.cells.execute_mdx_dataframe(mdx)
File "C:\Users\AppData\Local\Programs\Python\Python38\lib\site-packages\TM1py\Utils\Utils.py", line 52, in wrapper
return func(self, *args, **kwargs)
File "C:\Users\AppData\Local\Programs\Python\Python38\lib\site-packages\TM1py\Services\CellService.py", line 1012, in execute_mdx_dataframe
return self.extract_cellset_dataframe(cellset_id, top=top, skip=skip, skip_zeros=skip_zeros,
File "C:\Users\AppData\Local\Programs\Python\Python38\lib\site-packages\TM1py\Utils\Utils.py", line 52, in wrapper
return func(self, *args, **kwargs)
File "C:\Users\AppData\Local\Programs\Python\Python38\lib\site-packages\TM1py\Services\CellService.py", line 1703, in extract_cellset_dataframe
return pd.read_csv(memory_file, sep='~', **kwargs)
File "C:\Users\AppData\Local\Programs\Python\Python38\lib\site-packages\pandas\io\parsers.py", line 688, in read_csv
return _read(filepath_or_buffer, kwds)
File "C:\Users\AppData\Local\Programs\Python\Python38\lib\site-packages\pandas\io\parsers.py", line 460, in _read
data = parser.read(nrows)
File "C:\Users\AppData\Local\Programs\Python\Python38\lib\site-packages\pandas\io\parsers.py", line 1198, in read
ret = self._engine.read(nrows)
File "C:\Users\AppData\Local\Programs\Python\Python38\lib\site-packages\pandas\io\parsers.py", line 2157, in read
data = self._reader.read(nrows)
File "pandas_libs\parsers.pyx", line 847, in pandas._libs.parsers.TextReader.read
File "pandas_libs\parsers.pyx", line 862, in pandas._libs.parsers.TextReader._read_low_memory
File "pandas_libs\parsers.pyx", line 941, in pandas._libs.parsers.TextReader._read_rows
File "pandas_libs\parsers.pyx", line 1073, in pandas._libs.parsers.TextReader._convert_column_data
File "pandas_libs\parsers.pyx", line 1147, in pandas._libs.parsers.TextReader._convert_tokens
ValueError: could not convert string to float: 'test22'

duplicate of https://github.com/cubewise-code/tm1py/issues/248

Thanks.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Marius Wirtz @.>
Sent: Friday, March 12, 2021 6:16:07 PM
To: cubewise-code/tm1py @.>
Cc: tm1sir @.>; Author @.>
Subject: Re: [cubewise-code/tm1py] execute_mdx_dataframe can't extract string value? (#510)
duplicate of #248https://github.com/cubewise-code/tm1py/issues/248
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/cubewise-code/tm1py/issues/510#issuecomment-797316767, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAZQV7NXDP264VTHUS6DEJLTDHEUPANCNFSM4ZBPUBPA.


Clean up coverage tests in checks_test.go

This PR cleans up code coverage tests starting in checks_test.go to reduce duplicated code and reduce the likelihood of method name typos that were previously too easy to make.

@nightlark  - if you have time to review this PR, that would be greatly appreciated.  Thank you!


#2642 Release notes for 0.7.3

Codecov Report

Merging #2668 (c875003) into release-0.7.3 (a8301e1) will decrease coverage by 12.54%.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##           release-0.7.3    #2668       +/-   ##
==================================================
- Coverage          35.08%   22.54%   -12.55%
==================================================
  Files                158       49      -109
  Lines               9205     1091     -8114
  Branches             195      195
==================================================
- Hits                3230      246     -2984
+ Misses              5480      819     -4661
+ Partials             495       26      -469

Flag
Coverage Δ

moduleA
22.54% <ø> (ø)

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

Impacted Files
Coverage Δ

cli/cmd/send.go

...-service/event_handler/start_evaluation_handler.go

cli/pkg/version/ketpn_version_checker.go

helm-service/controller/action_handler.go

lighthouse-service/event_handler/handler.go

cli/cmd/send_event.go

cli/pkg/websockethelper/websocket_helper.go

gatekeeper-service/pkg/handler/handler.go

api/handlers/event.go

eventbroker/main.go

... and 99 more

Continue to review full report at Codecov.

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


Zero plane displacement heights in forests

PET option 5, the Penman-Monteith method is optimized for relatively even grass/crop surfaces. In these areas, the zero plane displacement height, d, is typically less than the wind speed and/or relative humidity measurement height. This is important because estimating surface resistance, rs, requires taking the natural log of the measurement height, z, minus d. The natural log of a negative number (i.e., d > z) is NaN.

Equation from FAO.
Current behavior
When PET is run with option 5 in forested locations (d > z), it returns NaN. Part of this is because we are using AORC forcing data, which assumes z for wind is 10 m and z for humidity is 2 m. If running option 5 with above-canopy met towers, this would not be a problem.
Expected behavior
We should be able to estimate PET in forested locations using P-M as other researchers have done. We need to either modify the z estimate to be less than the measurement height or substitute empirically derived resistance values. E.g., 43–67 s/m from Amatya et al. (2016).

Thanks, Keith.  I'd like to add that the equation ra was the aerodynamic resistance; the surface resistance rs was assigned to a constant in /src/pet.c as model->pet_forcing.canopy_resistance_sec_per_m   = 50.0

Closed with PR #13, #15, and #16


Example Contract is not compiling with Cairo 1.1

I'll provide the error stacktrace here later

Is it Cairo 1.1 or main?

Is it Cairo 1.1 or main?

I'm not sure, I installed cairo using the script in the book without setting the TAG to anything


Fix/opencv3

Should compile on 16.04 with OpenCV 3 and 14.04 with OpenCV 2
Using catkin_simple
Updated README

This addresses #13 .

Why are you sending me email?
From: supitalp<EMAIL_ADDRESS>Sent: Tuesday, January 24, 2017 7:04 AM
To: uzh-rpg/rpg_dvs_ros
Cc: Subscribed
Subject: Re: [uzh-rpg/rpg_dvs_ros] Fix/opencv3 (#15)
@supitalp approved this pull request.
lgtm!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/uzh-rpg/rpg_dvs_ros/pull/15#pullrequestreview-18178411 , or mute the thread https://github.com/notifications/unsubscribe-auth/ADWA4ZHbaTIDDX8fkmMQI7ea3M_NZ6gJks5rVhLWgaJpZM4LirK0 .  https://github.com/notifications/beacon/ADWA4a5p8MwHIANaprVZikqNbgi7MB8Mks5rVhLWgaJpZM4LirK0.gif


Add DEI doc @ /anti-racism

Add DEI Committee's Anti-racism, accountability, and support resources doc

cool thanks.


add forNoKeyUpdate and forKeyShare

https://knexjs.org/guide/query-builder.html#fornokeyupdate
https://knexjs.org/guide/query-builder.html#forkeyshare

Would be great to get this in!

Looks all good, thank you @wilsonianb!


add KUBERNETES_NODE_NAME param

support kubelet arg --hostname-override

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

@liubog2008 looks good to me, thanks!


Cherry-pick new aggregation function endpoints

Into v2-alpha for alpha 3

Specifically https://github.com/gchq/Gaffer/pull/2670

Closed by https://github.com/gchq/Gaffer/pull/2672


fix #5831 - updated CMSPluginBase._get_render_template to raise Impro…

…perlyConfigured exception
Description

Method CMSPluginBase._get_render_template used to raise ValidationError, now it raises ImproperlyConfigured exception.
Related resources

https://github.com/django-cms/django-cms/issues/5831

#...
#...

Checklist

[x] I have opened this pull request against develop
[x] I have added or modified the tests when changing logic
[x] I have followed the conventional commits guidelines to add meaningful information into the changelog
[x] I have read the contribution guidelines  and I have joined #workgroup-pr-review on Slack to find a “pr review buddy” who is going to review my pull request.

@Kaushal-Dhungel Good one. Please follow conventional commit style when committing to the project. https://www.conventionalcommits.org/en/v1.0.0/


Gradio YOLOv5 Det demo version upgrade

I upgraded my own project Gradio YOLOv5 Det v0.3 to v0.4, adding some features.

This project is also synced to my project in Gradio Blocks: https://huggingface.co/spaces/Gradio-Blocks/Gradio_YOLOv5_Det

Sorry for the late reply, but this looks good, thank you!


Remove PSPs and references to it from the Rancher chart

Issue: https://github.com/rancher/rancher/issues/39734
Problem
Helm fails on upgrade or delete to remove PSP resources if the release had been created on K8s <1.25.
Solution
The v2.7.2 Rancher release should not create PSP-related resources in the first place, as it will be the first Rancher release that will support K8s v1.25.
Testing

Engineering Testing
Manual Testing

Automated Testing

QA Testing Considerations

Regressions Considerations

The CI is failing because of tests that involve PSPs, but not this PR. I believe team2 is aware of these tests being now run against K8s v1.25.

Will this keep PSP to be available and supported in 2.7.2 for K8S pre-1.25? So can we deploy and upgrade Rancher to 2.7.2 using PSPs in case the customer is not yet ready for PSA / PSP removal?

@Martin-Weiss, this change is for Rancher's internal use of PSPs and does not affect how PSPs are supported in Rancher for users.

Tested with a hardened cluster. Used this chart and the webhook chart from https://github.com/rancher/webhook/pull/171.
Had to disable the PSP in the API server, add a PSA enforce: privileged on the cattle-system namespace. Then tried to uninstall the rancher release. Everything worked smoothly. Both rancher and rancher-webhook releases were successfully deleted with no errors.


Change link to personal website

I've recently decided to host my content on my own website again. The one on my website is also up to date with the latest changes to the repo.

Thanks for helping keep this up to date!


feat: print version

This pull request prints the XSpec version number in several places. The version number is taken from the Oxygen add-on version number.
The version number is stored in src/common/VERSION and referenced by these components:

batch/shell scripts
compiler
HTML reporters
Oxygen add-on configuration file

Though updating the VERSION file is not automated, it is unlikely to lose sync. Releasing each Oxygen add-on version inevitably involves updating the VERSION file.
Examples
Batch/Shell Scripts
$ bin/xspec.sh
...
XSpec v2.0.3

Usage: xspec [-t|-q|-s|-c|-j|-catalog file|-h] file
...

Compiled Stylesheet
$ bin/xspec.sh tutorial/escape-for-regex.xspec
...
Running Tests...
Testing with XSpec v2.0.3 and SAXON HE <IP_ADDRESS>
No escaping
...

Test Result Report HTML
See the upper right
Coverage Report HTML
See the upper right

Turned out to be non-viable. Reverting in #1159.
When we retry implementing the same feature, it should be simulated like #940.


allow no-global-function-names to be auto fixed with --fix

Some of the other rules support this, and it seems like it should be possible to replace instances of, e.g. percentage with math.percentage.

After looking at the docs for this rule, it looks like I can use sass-migrator instead. https://sass-lang.com/documentation/cli/migrator/


[HUDI-2458] [WIP] Relaxing metadata compaction reliance on inflight data table operations and archival in data table reliance on metadata table compaction

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contribute/how-to-contribute before opening a pull request.

What is the purpose of the pull request
(For example: This pull request adds quick-start document.)
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@nsivabalan do we still need this? cc @danny0405

Closing this PR as we already have a solution merged on master.


[peertube] Added extractor

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[x] New extractor
[ ] New feature

Description of your pull request and other information
Adds the ability to download videos from peertube.touhoppai.moe thus resolving #16301

@dstftw please review

@dstftw Made the required changes. Please review.

@dstftw Made the changes. Please verify.

@h-h-h-h made the changes, check now.