Add aria label

Adds an aria role application and aria label to announce navigatable math.

Quick test with NVDA works well, No more mode switching necessary, label is read on FF and IE11 Win10. Also first-string is read on IE11 and Chrome (though chrome does not read label and needs mode switching)

Virtually identical results in JAWS on Win10 (modulo their usual differences)

Addendum: JAWS+Chrome seems to read the window title instead of the label.
WindowEyes on Win10. FF works well but instead of the label, it voices "appllication application main window". But Chrome has deteriorated; speech seems to get cut-off by something else.

Windows Eyes still works flawlessly in Edge and IE11 on Win 10.
I do think the label is too long since it will be voiced on every equation.

Win7 support has deteriorated badly. NVDA and Window Eyes don't voice anything on Chrome and FF anymore.

Hm... Might be a broken Win7 VM. Will try a fresh one later.

Ok, NVDA on Win7. FF, Chrome behave almost as on Win10. Except that first speech string is lost on FF as well (on the bright side: the second Chrome bug with first elements on levels is fixed). IE9 voices labels, misses initial speech text.

Wait... how did I get it to run in IE9? I must have been dreaming that one.
Anyway, JAWS works as in Win10 for FF and Chrome (no IE9).

I do think the label is too long since it will be voiced on every equation.

So what could we announce? We should mention the key combination.

I don't think we should mention the key combo if we voice this at every equation without the user being able to modify this behavior. It's as annoying as alerts if you're reading a whole text.

Just "navigatable math" then?

Right, that came to mind given how some AT reads math. Personally, I never liked that much especially since the important information comes at the very end. I would suggest something very short possible like "math" when it comes to every equation.
I think we'll need some feedback from users on this.
As I wrote elsewhere, we could also think about announcing some information in the aria live region when the tool starts up.

Let's merge this and take it from there.

Shortened the Aria label. I will refactor the entire live region shortly and then make an initial announcement, if in page.


Automatic Trading fails

Please see the following Traceback:
> Trading Automatically for  ['2020_10']
#################################################################################################
Account Balance: $ 1000  BTC: $ 0  USD: $ 1000
#################################################################################################
##########################################   DAY  1    #########################################
Traceback (most recent call last):
File "Controller.py", line 75, in
auto_trader.runSimulation(x_test, prices)
File "/home/crypto-trading-ai-bot-basic/AutoTrader.py", line 54, in runSimulation
prediction = self.advisor.predict(np.array([samples[i]]))
File "/home/crypto-trading-ai-bot-basic/Model.py", line 73, in predict
prediction = np.array(tf.argmax(self.model.predict(sample),1))[0]
IndexError: too many indices for array: array is 0-dimensional, but 1 were indexed
Any idea what could be wrong?

I added a print statement above line 73 in Model.py and got the following:
Tensor("ArgMax:0", shape=(1,), dtype=int64)
followed by the same Traceback as above.

I am using ubuntu-1804-bionic-v20210129
my python version is 3.6.9
and pip freeze outputs the following:
absl-py==0.11.0
asn1crypto==0.24.0
astor==0.8.1
attrs==17.4.0
Automat==0.6.0
blinker==1.4
cached-property==1.5.2
cbpro==1.1.4
certifi==2018.1.18
chardet==3.0.4
click==6.7
cloud-init==20.4
colorama==0.3.7
command-not-found==0.3
configobj==5.0.6
constantly==15.1.0
cryptography==2.1.4
distro-info===0.18ubuntu<IP_ADDRESS>
gast==0.4.0
google-compute-engine==20190801.0
google-pasta==0.2.0
grpcio==1.35.0
h5py==3.1.0
httplib2==0.9.2
hyperlink==17.3.1
idna==2.6
importlib-metadata==3.4.0
incremental==16.10.1
Jinja2==2.10
joblib==1.0.0
jsonpatch==1.16
jsonpointer==1.10
jsonschema==2.6.0
Keras-Applications==1.0.8
Keras-Preprocessing==1.1.2
keyring==10.6.0
keyrings.alt==3.0
language-selector==0.1
Markdown==3.3.3
MarkupSafe==1.0
netifaces==0.10.4
numpy==1.19.5

AltLayer Airdrop Season One Update

🚀 Exciting Announcement! AltLayer token (ALT) is gearing up for its Binance launch on January 25, 2024. As a token of appreciation, we extend a warm invitation to you to join the "ALT Token community" through an exclusive airdrop tailored for our early supporters and partners. Here's a quick overview:

Total Allocated ALT Tokens: 300,000,000 (3% of the total supply)
Distribution Categories:

Ethereum Mainnet
Binance Mainnet

For a comprehensive breakdown of criteria and further details, refer to the complete announcement Oficial Website.
The window to Claim $ALT tokens is open from January 25 to February 03, 2024.
Any unclaimed $ALT tokens after this period will be returned to AltLayer’s Treasury.
We deeply appreciate your contribution to AltLayer's success! Stay tuned for more exciting developments in Season One.
Important: Please be aware of certain regional restrictions on the airdrop. Review the disclaimer before participating.
mvandermeulen, @BlackArbsCEO, @harshav167, @RKiding, @theo-dim, @Sepehr0011, @Quentin168, @HagridChan, @madr3z, @theinternetgy, @dmrd, @Rmarieta, @Balro, @colabpp, @jimmyg1997, @christianbitter, @hiejulia, @chintanjoshifin, @kelvinAI, @kckustomac


Not able to propagate baggage when helidon-tracing-tracer-resolver and jaeger-client used

Same issue as #6970, but with jaeger-client and tracer-resolver.
Environment Details

Helidon Version: 3.2.1 SE
JDK version: 17.0.5
OS: OL7
Docker version (if applicable): n/a

Problem Description
See problem description in #6970. Same issue, but with the below set of dependencies.
Steps to reproduce
Use these dependencies, and note that the original problem in #6970 still exists.
        <dependency>
            <groupId>io.helidon.tracing</groupId>
            <artifactId>helidon-tracing-opentracing</artifactId>
        </dependency>
        <dependency>
            <groupId>io.helidon.tracing</groupId>
            <artifactId>helidon-tracing-tracer-resolver</artifactId>
        </dependency>
        <dependency>
            <groupId>io.jaegertracing</groupId>
            <artifactId>jaeger-client</artifactId>
        </dependency>
        <dependency>
            <groupId>io.opentracing</groupId>
            <artifactId>opentracing-api</artifactId>
        </dependency>
        <dependency>
            <groupId>io.opentracing</groupId>
            <artifactId>opentracing-util</artifactId>
        </dependency>

Helidon currently does not support this way of working with Jaeger. @tomas-langer please confirm.


Adding a meaningful error message if FakeDb.Serialization encounters a duplicated Item ID

I tried to use the Serialization extension to FakeDb against some pre-existing serialised content on an old development machine, and I came across a situation where you got an unhelpful error message because of some bad data. So I've tried to improve the error to help any future developers who hit the same issue...
The situation was that at some point an item had been serialised, then renamed and serialised again. The serialisation folders hadn't been tidied up - so there were two files with different names but containing the same Item ID sitting on disk.
When I created a DsDbItem() that tried to read this tree (and hence encountered the duplicate ID) it raised an error - System.ArgumentException: An item with the same key has already been added. While that error is factually correct, it doesn't provide any help in tracking down what key was duplicated - and if you have a lot of serialised data that can be a bit of a pain. It's also not very helpful to new users of your tool - who might not immediately grasp why that error could be raised.
Hence I've added a new DuplicateIdException class, which has a more helpful message listing the ID in question as well as the two serialised files that are conflicting. When the SerializedIdToPathResolver.FindFilePath() extension method spots a duplicate, it raises this new exception instead of the default exception from the underlying Dictionary object. I've added some test data that causes the error, as well as a simple unit test which checks that deserialising an item with a duplicate ID raises the right exception.
Hopefully you think that's a helpful change. If there's anything I've done here that you don't like, then let me know - I'm happy to make edits if you want me to.

@jermdavis, thanks for providing the PR. Meaningful error message is always a good idea.
I'll take a look.

@jermdavis, your contribution is now released as v1.6.1! Thank you.

That's great! Thank you for all your work maintaining such a useful project.


[5.0] Route prefixing not working in some cases

Route '/' does not work after using $route->prefix('someprefix');

Can't recreate issue.

@taylorotwell, Issue reproduced in tests, add prefix directly and not by grouping

Can you send it to 5.1 branch?

@taylorotwell , of course.


Infinite Scrolling Issue

Hello,
Infinite scrolling indicator is the issue for me.
If I try to scroll up uitableview, then InfiteIndicator start animating.
Please check that
Thank you,

https://github.com/LawrenceHan/SVPullToRefresh


CaptionServiceName T1 in ST 436 and ATSC/53 Text Tracks

I have an MPEG2 in an MXF OP1a file with ATSC/53 and SMPTE ST 436 text tracks.  MediaInfo is reporting something I've never seen before:
      <extra>
        <CaptionServiceName>T1</CaptionServiceName>
        <CaptionServiceDescriptor_IsPresent>Yes</CaptionServiceDescriptor_IsPresent>
        <cdp_length_Min>82</cdp_length_Min>
        <cdp_length_Max>89</cdp_length_Max>
      </extra>

I'm not sure what a T1 service represents and I'm not seeing it in other tools. Full XML attached and caption byte payloads or the entire file available if needed.
UXKV_01_mediainfo.xml.txt

New option (CLI only for the moment, GUI will be with other options):
mediainfo UXKV-A_01_D01.scc.txt "--Inform=Text;%ID%,"
CC1,T1,
mediainfo UXKV-A_01_D01.scc.txt "--Inform=Text;%ID%," --File_CommandOnlyMeansEmpty=1
CC1,

This works from the command line as expected.
However, it doesn't seem to work when I use the Python bindings via:
self.mediainfo.Option_Static('File_CommandOnlyMeansEmpty', '1')
Is there any reason why these new parameters wouldn't work via the DLL directly?

Ah ok, this works:
self.mediainfo.Option('File_CommandOnlyMeansEmpty', '1')
What's the difference between Option and Option_Static?

@plondino while working on the GUI I remarked that there is an incompatibility between this request and https://github.com/MediaArea/MediaInfo/issues/674, so I added an option without incompatibilities at https://github.com/MediaArea/MediaInfoLib/pull/2085.
"Old" options are still there but the last one replaces the previous one, please use the new option instead when you can.
I also added extra/InternalDetectionKind field when no content is detected, with values Command (indicating that no 608/708 content was found, only commands) or Stream (indicating that no 608/708 content or command was found, only an empty 680/708 stream), in case it helps e.g. if you use self.mediainfo.Option('File_File_DisplayCaptions ', 'Stream') and then want to know if a content was actually detected . More relevant with a full parsing.

What's the difference between Option and Option_Static?

There was a tentative to do a difference between global options for all MediaInfo instances (the static one, usable in C++ without creating a single instance of a class) and options only for one instance (the non static one, usable in C++ only when an instance if a class is created) for avoiding too much mutex locks but in practice it is not a good way to do it, at long term we need to remove the difference and consider all the File_* and if they are without this prefix, and usable with or without an instance of the class.


explicity include for coverage in sonar

Sonarq is showing the wrong coverage, as it includes the tests directory in the calculation.
Add here some options to exclude those files (following the configuration file from calibpipe.
I think we will see if this works only after 'merge to main' and 'run unit tests on main'

Why are you not running coverage on merge requests? The reporting of the coverage on newly added / modified lines is I think one of the most valuable things about this kind of setup.

We are still using codecov for this.
First wanted to get familiar with sonarq and to fix the issues so that it gives consistent results for us.


C macros support?

Thanks for a great plugin!
C/C++ languages have macros like: __LINE__, __FUNCTION__, __FILE__ etc...
Would be great to add support for those, as opposed to the hard coded line number in the log message.

Thanks. Not being someone who regularly programs in C/C++, do you have an example of how that would be used?

OK, I've had a look at this. This is actually not that straightforward to do, with how debugprint currently composes its lines. I'll think about the best way to do this, but may not be a quick fix.

Thanks! Appreciate you taking time to look into this!


Feat/add axelar executor contract

Purpose
Add Axelar gateway executor in order to enable cross chain logic (see #8 for details).
Changes

added extra function lend which actually performs the NFT lend
used callContractWithToken so payment is taken care by Axelar (without relying on swing.xyz)
Added some unit tests
Testing for the cross chain behavior will be done on integration tests

I am not sure whether we want to keep the INFTMarketplace interface, since I guess that the rent and lend function can be made internal
Screenshots
Testing Instructions
Checklist

[x] Title follows the naming convention.
[x] Add a description.
[ ] Add screenshots (optional).
[ ] Add testing instructions.
[x] Add at least one reviewer.
[ ] Apply related labels (optional).
[ ] Leave comments on changes you would like to discuss.
[ ] Remove changes that are not related to this pull request.
[ ] Remove debugging code.
[x] Test your changes locally and on staging (if applicable).
[ ] Ensure test coverage value in config matches actual coverage (if applicable).
[ ] Ensure the build is passing.

I am closing this since this version of the protocol has problems


Add missing documentation of tokens

Add missing token documentation of defined constants, e.g. LINE_HEIGHT in src/constants/customizations.ts. The documentation of tokens are defined in src/stories/tokens.

@rschiffer This is done, right? Can we close this issue?


Fixes 1187 Adds ability to add host object.

Fixes #1187

✅ No public API change.

✅ No public API change.


I have a few of these errors. Am I using a character that I'm supposed to escape or something? If so, which one?

❱chat
Welcome to chatgpt. You can quit with 'exit' or 'q'.

Enter a prompt:
in bash how do you split a long line

chatgpt

In Bash, you can split a long line by using the backslash (\) character at the end of a line to indicate that the
command continues on the next line. Alternatively, you can use parentheses () or curly braces {} to group commands
together and split them onto multiple lines.

Enter a prompt:
demonstrate

Your request to Open AI API failed: invalid_request_error
We could not parse the JSON body of your request. (HINT: This likely means you aren't using your HTTP library correctly. The OpenAI API expects a JSON payload, but what wassent was not valid JSON. If you have trouble figuring out how to fix this, please send an email to<EMAIL_ADDRESS>and include any relevant code you'd like help with.)
1

❱chat
Welcome to chatgpt. You can quit with 'exit' or 'q'.

Enter a prompt:
in bash how do you split a long line

chatgpt

In Bash, you can split a long line using the backslash (\) character at the end of the line, indicating that the
command continues on the next line. For example:

echo "This is a very long \
line that needs to be split \
into multiple lines for clarity."

Alternatively, you can also use parentheses to group commands and split them across multiple lines. For example:

( command1 arg1 arg2 \
&& command2 arg1 arg2 \
&& command3 arg1 arg2 )

Enter a prompt:
"can you use parentheses () or curly braces {} to group commands together and split them onto multiple lines? if so please demonstrate."

Your request to Open AI API failed: invalid_request_error
We could not parse the JSON body of your request. (HINT: This likely means you aren't using your HTTP library correctly. The OpenAI API expects a JSON payload, but what wassent was not valid JSON. If you have trouble figuring out how to fix this, please send an email to<EMAIL_ADDRESS>and include any relevant code you'd like help with.)
1

well thats kinda what i always thought about the AUR's that point to git but I'm never sure.
The AUR says it was last updated  2023-03-31 11:10 (UTC) so ... i don't know. Im sure i could just download your code and use it directly just to test, but iv got some of my own code that is using it from the AUR binary. I don't want to get in a muddle and mess up what iv got.

I don't think you need to download the code. If you just reinstalled with paru -S chatgpt-shell-cli I think it should work 🤞
The last updated timestamp on AUR probably refers to the changes made in the AUR file itself.
But yes, you know your setup better. I am just curious if the changes are available immediately in the AUR.

Try also chatgpt-shell-cli-git.That one is 1:1 with this repo.

No, as far as i can tell it still does that same. I have removed chatgpt-shell-cli-git and installed chatgpt-shell-cli ver 0.2.2
2 aur/chatgpt-shell-cli-git 1.0.r161.ea41590-2 (+1 0.43)
Use OpenAI's ChatGPT and DALL-E from the terminal.
1 aur/chatgpt-shell-cli 0.2-2 (+3 1.77) (Installed)
Use OpenAI's ChatGPT and DALL-E from the terminal.

But unfortunately it still does exactly the same
❱chat
Welcome to chatgpt. You can quit with 'exit' or 'q'.

Enter a prompt:
in bash how do you split a long line

chatgpt In Bash, you can split a long line using the backslash character "\" at the end of the line to indicate that the command continues on the next line. For example:

echo "This is a very long \
line of text that needs to \
be split into multiple lines."

This will output the following on a single line:

This is a very long line of text that needs to be split into multiple lines.

Enter a prompt:
demonstrate
Your request to Open AI API failed: invalid_request_error
We could not parse the JSON body of your request. (HINT: This likely means you aren't using your HTTP library correctly. The OpenAI API expects a JSON payload, but what wassent was not valid JSON. If you have trouble figuring out how to fix this, please contact us through our help center at help.openai.com.)
1

Does your not do the same if you use the exact same prompts?
1st prompt :- "in bash how do you split a long line"
2nd prompt :- "demonstrate"
Everything else works fine for me but these two particular prompts throw this error.

well i pass. I have glow as well ^^
I did notice there is no chatgpt --version ?
Its not important to me as it was just something i stumbled across when i was testing. It's not something i'd ever come across again (i hope). I use it every day without any problems, so i really can't help.

No there is no --version. So far all changes are backwards compatible, meaning we never broke something to add something new. What you get from the repo is always the latest version.
Adding versioning would mean that it would require some version and release management and I think this is really not worth it for a simple one file script. But if in the future we need to add breaking changes then we would have to use versions to differentiate.

Unless it has something to do with the fact that I use FISH, I can't see how. Other than that, I would have to use your open code, look at the JSON as it's created, and figure out what's going on before it's attempted to be sent. But I'm busy with stuff :).

Ok, it was making me scratch my head. I removed all versions (the CLI, CLI- Git, and the Git folder where I had it cloned). Basically, I removed every remnant of it. I rebooted the system and reinstalled ChatGPT-Shell-CLI from the AUR, and it's working! :woozy_face:
Don't ask, but it looks like it was a "me" problem.
Thx for your help :smile:


Impossible to start text selection on unfocused SpinBox

Godot version
v4.1.beta.custom_build [d3651ea45]
System information
Windows 11
Issue description

It's not possible to start text selection on a SpinBox when it's unfocused.
Note: After a bit of digging in the code, I found that clicking on a SpintBox doesn't trigger SpinBox::gui_input no matter if it's focused or not. However, releasing mouse left button does trigger the function.
Steps to reproduce
See the gif.
Minimal reproduction project
It's simple to reproduce.

SpinBox::_line_edit_focus_enter gets called when the LineEdit of the SpinBox receives focus and during that the drag-selection gets canceled.
Bisecting lead to #64529

I confirm SpinBox in 3.x has the same issue, probably due to the cherry-pick of https://github.com/godotengine/godot/pull/64529.

cc @KoBeWi

You can select all with double click. There is also select_all_on_focus property.
The "regression" was mentioned in the PRs caveats 🙃 I'll see if it can be improved.


[WASM-1] Implement the obfuscated MTProto transport

This PR implements support for transport obfuscation. It is the first step towards a web port.
Changes I had to make to make this feasible:

Transport::unpack() now takes in a mutable reference to the buffer to do the decryption in-place.
~Transport::unpack() now returns Result<Vec<UnpackedOffset>>. This is needed since a read might, and frequently will, contain multiple transport payloads.~
~Transport::unpack() now returns an empty Vec instead of Error::MissingBytes when there's more data needed.~
ctr is a new dependency in grammers-mtsender.
Transport::unpack() must now be called with the same buffer and the buffer must be kept between calls.

~While changing the return type of unpack to a Vec doesn't also seem good, it was the only compromise I could think of to allow this transport to work without significant performance impact while also keeping the decryption contained inside of the transport implementation.~
I'm now storing the decryption state inside the transport itself. So should have almost zero overhead other than the encryption itself

@Lonami
I've amended my commit and implemented what we discussed in telegram (storing the decryption state inside of the transport itself).
I've also applied all the suggestions you mentioned in the review.


Crash when running my app with Flutter master branch

It works well in last weekend (4/15) , but after I pull the lasted Flutter master codes , crash happend.
this is the logs:

I could run same code on Beta branch.

Can you please add the output of flutter doctor -v?

@zoechi
[✓] Flutter (Channel master, v0.3.1-pre.35, on Mac OS X 10.13.4 17E199, locale zh-Hans-CN)
• Flutter version 0.3.1-pre.35 at /Users/*/Documents/work/flutter
• Framework revision 7b163c7c0b (8 hours ago), 2018-04-18 20:31:45 -0700
• Engine revision 3cc8d82895
• Dart version 2.0.0-dev.48.0.flutter-fe606f890b
[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
• Android SDK at /Users//Library/Android/sdk
• Android NDK at /Users//Library/Android/sdk/ndk-bundle
• Platform android-27, build-tools 27.0.3
• ANDROID_HOME = /Users/jonjon/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
• All Android licenses accepted.
[✓] iOS toolchain - develop for iOS devices (Xcode 9.3)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 9.3, Build version 9E145
• ios-deploy 1.9.2
• CocoaPods version 1.5.0
[✓] Android Studio (version 3.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 23.2.2
• Dart plugin version 173.4700
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
[✓] Connected devices (1 available)
• iPhone 8 • 3332829E-AB4B-4D91-8762-680A565135E0 • ios • iOS 11.3 (simulator)
• No issues found!

It seems fixed .


Bug when using your LLM API with prompt instances..

Hi, when using the model.generate API, I just run into this issue (200 dataset samples, stuck at 30%). If possible, could you provide any suggestions? This is really weird, as a rare case to this particular NL prompt, where your api runs smoothly with other prompt cases in my current tests.
Thanks in advance!

To be specific, I am testing on some sentiment transfer tasks, especially in positive transfer tasks with OPT models, I frequently find such issues occurred with several prompts (several positive prompts fail, but I see the same prompt does not fail with other LMs).

Hi! Thanks for reporting this! This seems like an issue caused by exceptionally long sequences. Can you share the code to reproduce this error so we can look into this?

Hi, I work with OPT-IML-1.3b models, and in addition to such phenomena, I find your results are inconsistent with a lot of other implementations, such as initial Huggingface API, and the DeepSpeed wrappers.
I do suggest you to experiment with OPT-IML series.
For the code, I am less likely to think it matters a lot, as I also experiment these prompts (yeah, they are long with100~200 tokens) with other model instances, such as OpenASSISTANT-pythia-12b, LLaMa-7B, etc. They all run smoothly...

Could you check again for OPT-IML instances?

Could you check again for OPT-IML instances?

Sorry to bother again, can you provide a concrete prompt example that can reproduce the error on opt-iml-1.3b?

Closing this issue as stale as there has been no discussion in the past 3 months.
If you are still experiencing the issue you describe, feel free to re-open this issue.


Doesn't work if scheme name contains space

Here's output from my terminal:
$ bash -l -c "$(curl -sfL https://raw.githubusercontent.com/bitrise-tools/codesigndoc/master/_scripts/install_wrap-xcode.sh) --scheme=Lead Radar Test"
 => Creating a temporary directory for codesigndoc ...
 => Downloading version: 0.9.16
 => Downloading codesigndoc from (https://github.com/bitrise-tools/codesigndoc/releases/download/0.9.16/codesigndoc-Darwin-x86_64) to (/var/folders/x1/_2ctrjwd67x60st1lpybwpmr0000gn/T/codesigndoc.OaFGuRaN/codesigndoc) ...
######################################################################## 100.0%
 => Making it executable ...
 => codesigndoc version: 0.9.16
 => Running codesigndoc scan ...

Please drag-and-drop your Xcode Project (.xcodeproj)
   or Workspace (.xcworkspace) file, the one you usually open in Xcode,
   then hit Enter.

  (Note: if you have a Workspace file you should most likely use that) : /Users/tadija/Documents/Temp/leadradar/leadradar.xcworkspace

INFO[16:33:32] 🔦  Running an Xcode Archive, to get all the required code signing settings...
INFO[16:33:32] $ xcodebuild "-workspace" "/Users/tadija/Documents/Temp/leadradar/leadradar.xcworkspace" "-scheme" "Lead" "clean" "archive"
Running and analyzing log ....

INFO[16:33:33]   💡  Saving xcodebuild output into file: /Users/tadija/Documents/Temp/leadradar/codesigndoc_exports/xcodebuild-output.log
INFO[16:33:33] Please check the logfile (/Users/tadija/Documents/Temp/leadradar/codesigndoc_exports/xcodebuild-output.log) to see what caused the error
INFO[16:33:33] and make sure that you can Archive this project from Xcode!

INFO[16:33:33] Open the project: /Users/tadija/Documents/Temp/leadradar/leadradar.xcworkspace
INFO[16:33:33] and Archive, using the Scheme: Lead

------------------------------
First of all please make sure that you can Archive your app from Xcode.
codesigndoc only works if you can archive your app from Xcode.
If you can, and you get a valid IPA file if you export from Xcode,
please create an issue on GitHub at: https://github.com/bitrise-tools/codesigndoc/issues
with as many details & logs as you can share!
------------------------------

Error: Failed to run Xcode Archive: Failed to Archive, error: Failed to run xcodebuild command, error: exit status 65

You'll notice that on the first line scheme name is full ("Lead Radar Test"), but later when xcodebuild is called wrong scheme name is used ("Lead").
Log file says the same:
xcodebuild: error: The workspace named "leadradar" does not contain a scheme named "Lead". The "-list" option can be used to find the names of the schemes in the workspace.

Thanks for reporting @tadija !
Duplicate of https://github.com/bitrise-tools/codesigndoc/issues/25 - please see the other issue for a solution, and sorry for the inconvenience.


load_node issue on IE 11- does not trigger ajax requests to get the data from server

--for example
load_node(myArray, function callback(){
setInterval(function(){
//code
},5)
});
the above code is not loading the nodes from myArray.

-- no traces of ajax request on network tab...

I need a more complete example in order to help. This is not a known issue and I can not reproduce it.

I will reopen when more info is provided and I can reproduce.


Colors of points in line chart doesn't update when chart.update("none") is set

Expected behavior
I wrote a function that changes the colors of every dataset in the chart when a button is pressed. When pressed i would expect the color of the line, line fill, point and point fill to change with no animation because chart.update("none") is set.
How i expect the chart to look after color change (original color is black)

Current behavior
When i press the button the color of the line and line fill changes like it should, but the color of the point and point fill doesn't change. However when i hover over a point it shows the correct color and when i hide a dataset, the entire chart updates and all colors are then correct.
This only happens when chart.update("none") is set and not when just using chart.update().
Whether i use borderColor and backgroundColor or pointBorderColor and pointBackgroundColor the behaviour is the same
How the chart actually looks after color change (original color is black)

Reproducible sample
https://codepen.io/AsgMog/pen/zYyRWzz
Optional extra steps/info to reproduce
No response
Possible solution
No response
Context
I'm trying to create a button that changes the color of the chart without the change being animated.
chart.js version
v4.4.0
Browser name and version
Firefox 115.2.1esr
Link to your project
No response

Quick Fix for now =>
newChart.options.animation = {   duration: 0 };
Looking into the issue

So why to use chart.update("none") when chart.update() is working properly.

Can we go about by manually changing the color for each dataset and after updation  call chart.update?

Can we go about by manually changing the color for each dataset and after updation call chart.update()?

Do you mean like this?
function changeColors() {

    //Change colors here...

    newChart.update("none");
    newChart.update()
  };

This works, but it still shows the wrong colors briefly in the animation

So why to use chart.update("none") when chart.update() is working properly.

Context
I'm trying to create a button that changes the color of the chart without the change being animated.

Can we go about by manually changing the color for each dataset and after updation call chart.update()?

Do you mean like this?
function changeColors() {

    //Change colors here...

    newChart.update("none");
    newChart.update()
  };

This works, but it still shows the wrong colors briefly in the animation

Can we go about by manually changing the color for each dataset and after updation call chart.update()?

Do you mean like this?
function changeColors() {

    //Change colors here...

    newChart.update("none");
    newChart.update()
  };

This works, but it still shows the wrong colors briefly in the animation

I'm looking into it.

function changeColors() {
newChart.data.datasets.forEach(function(dataset, datasetIndex) {
dataset.backgroundColor = 'new-color-value';
});
newChart.update({
    duration: 1000,
    onComplete: function() {

}
    });
}
Can I approach the issue in this way?

@AsgerMogensen Could you please help me as to where to make my changes?

hi there , this is the reproducible sample of issue with fixes:
https://codepen.io/rwyvbfow-the-bold/pen/MWZVvjv

I'm not quite sure what to reply?
This approach seems to work:
> newChart.update({
>     duration: 1000,
>     onComplete: function() {}
>})

@AsgerMogensen ok,so can i go about making the following changes?

@AsgerMogensen ok,so can i go about making the following changes?

I'm still not sure what to reply. What am i confirming?
Your solution changes the colors correctly, but it has occurred to me, that it's animated. There never was any problem when the update was animated.


Icons not saving

Love the plugin but im having a pretty big issue, when i save the icon in the CMS it seems to save ok and theres content in the database like this
{"icon":"category-icons\/Career Related.svg"}
but when i reopen it the field is blank again?
any ideas

Thanks for reporting this issue @keithmancuso. I've released an updated version of the plugin with the fix.
Try it out and let me know if you have any more problems.


Kingdom of Miscellania Favor

Does not display Favor during and after quest complete of throne of miscellania even if standing in miscellania

Can confirm, having this issue myself. The overlay just never seems to show up

I've never seen the code for this plugin, but try asking an NPC what your favour is and then re-log, see if that works!

Did not make a difference.

I think it may be a logic error under the hasCompletedQuest method so I'm trying to see if thats the case. Hopefully it's not an issue elsewhere because my membership conveniently ran out

Mine is working. Have the people having issues completed royal trouble?

Hm I didn't even consider that as a potential issue. I have completed royal trouble

That shouldn't be an issue seeing as Throne of Misc is a pre-req for Royal Trouble

i have not completed royal trouble but code only asks to check for throne of misc

It's possible that the varbit/flag/whatever for throne of misc changes after completion of royal trouble

Thats a very good point, I will look into it

Happening to me aswell - https://i.imgur.com/m3JOvtd.png, nothing shows up at all even after I cut a tree or ask a NPC what my favor is

I can confirm that this is still a bug.  I've got both Misc quests completed and this plugin has never worked for me.  I've toggled it many times, spoken to NPC's to check approval etc.  Nothing.

Fixed by #5212?


Need support for typescript

Is it possible to use this Library in a typescript project? If possible please tell me how I can use this.

https://www.youtube.com/watch?v=VqCdCLn9HQI


[PoC] Test more things to support FF simulcast

Description
This is a PoC that is still Work in Progress. Please, don't review or test it yet. I've been playing a bit with Firefox Simulcast since we still need to make some progress in order to support it. I'm stuck at some point where Firefox sends multiple streams, but I can't filter them properly.
There are some caveats: Firefox sends unannounced SSRCs for each RID, temporal layers seem to be somehow broken, I still don't understand how to properly configure layers in Firefox, etc.
[] It needs and includes Unit Tests
Changes in Client or Server public APIs
Not needed.
[] It includes documentation for these changes in /doc.

:(


vim plugin spyder_vim error

Description
What steps will reproduce the problem?

What is the expected output? What do you see instead?
Please provide any additional information below
File "D:\ProgramData\Anaconda3\lib\site-packages\spyder_vim\vim_widget.py", line 735, in on_text_changed
self.vim_keys(key, repeat)
File "D:\ProgramData\Anaconda3\lib\site-packages\spyder_vim\vim_widget.py", line 75, in call
method(repeat)
File "D:\ProgramData\Anaconda3\lib\site-packages\spyder_vim\vim_widget.py", line 505, in p
self.P(repeat)
File "D:\ProgramData\Anaconda3\lib\site-packages\spyder_vim\vim_widget.py", line 525, in P
if lines[0].strip():
IndexError: list index out of range
Version and main components

Spyder Version: 3.2.6
Python Version: 3.6.4
Qt Versions: 5.6.2, PyQt5 5.6 on Windows

Dependencies
pyflakes >=0.6.0 :  1.6.0 (OK)
pycodestyle >=2.3:  2.3.1 (OK)
pygments >=2.0   :  2.2.0 (OK)
pandas >=0.13.1  :  0.22.0 (OK)
numpy >=1.7      :  1.14.0 (OK)
sphinx >=0.6.6   :  1.6.6 (OK)
rope >=0.9.4     :  0.10.7 (OK)
jedi >=0.9.0     :  0.11.1 (OK)
nbconvert >=4.0  :  5.3.1 (OK)
sympy >=0.7.3    :  1.1.1 (OK)
cython >=0.21    :  0.27.3 (OK)
qtconsole >=4.2.0:  4.3.1 (OK)
IPython >=4.0    :  6.2.1 (OK)
pylint >=0.25    :  1.8.2 (OK)

Thanks for reporting. This is a problem with the spyder-vim plugin, not spyder itself, and should thus be directed to the spyder-vim repo. Be advised, due to our current funding situation, it be a while before it is fixed, but we will be adding built-in shortcut presets to Spyder 4 as well as expanded shortcut management features, to include vim (and emacs) shortcuts.

Issue moved to spyder-ide/spyder-vim #41 via ZenHub

I asked in chat but it must have got buried—I tried to move it, but couldn't find the button in Zenhub even after reading the Zenhub docs and googling it. Do only you have access to it?

@goanpeca, how can we give @CAM-Gerlach access to this feature?


policy-controller: Uninstalling the chart does not clean up leases

Description
There is an issue that occurs when you install the policy controller chart, uninstall it, and then install it again.
The problem is the leases are not being cleaned up from the namespace causing the reinstalled pods to fail to start.
# pods/policy-controller-policy-webhook

I0410 22:46:49.210762       1 leaderelection.go:248] attempting to acquire leader lease cosign-system/clusterimagepolicy.defaultingwebhook.00-of-01...

# pods/policy-controller-policy-webhook

{"level":"warn","ts":"2023-04-10T22:47:15.135Z","logger":"policy-controller","caller":"webhook/webhook.go:154","msg":"server key missing","commit":"89ef904-dirty"}
server.go:3230: http: TLS handshake error from <IP_ADDRESS>:52812: tls: no certificates configured
{"level":"warn","ts":"2023-04-10T22:47:16.135Z","logger":"policy-controller","caller":"webhook/webhook.go:154","msg":"server key missing","commit":"89ef904-dirty"}
server.go:3230: http: TLS handshake error from <IP_ADDRESS>:52824: tls: no certificates configured

# this is after uninstall

 kubectl -n cosign-system get leases.coordination.k8s.io
NAME                                                                                HOLDER                                                                                AGE
clusterimagepolicy.conversionwebhook.00-of-01                                                                    policy-controller-policy-webhook-5985d96f75-szpt6_39f3f639-fe73-4f35-bccb-22ee126c441a   5m40s
clusterimagepolicy.defaultingwebhook.00-of-01                                                                    policy-controller-policy-webhook-5985d96f75-szpt6_71ff5327-f0b9-4142-a0d9-cc22aa7da344   5m40s
clusterimagepolicy.github.com.sigstore.policy-controller.pkg.reconciler.clusterimagepolicy.reconciler.00-of-01   policy-controller-policy-webhook-5985d96f75-szpt6_6ab347b6-ad24-4c36-b80d-353c96664c99   5m40s
clusterimagepolicy.github.com.sigstore.policy-controller.pkg.reconciler.trustroot.reconciler.00-of-01            policy-controller-policy-webhook-5985d96f75-szpt6_f250d67a-8d6b-43b9-a0f0-768c31abc825   5m40s
clusterimagepolicy.validationwebhook.00-of-01                                                                    policy-controller-policy-webhook-5985d96f75-szpt6_6c977a6d-b0dc-415b-a9dc-47e0eb9979d9   5m40s
clusterimagepolicy.webhookcertificates.00-of-01                                                                  policy-controller-policy-webhook-5985d96f75-szpt6_1131c65e-3c5e-4272-921f-7a13a176723d   5m40s
policy-controller.defaultingwebhook.00-of-01                                                                     policy-controller-webhook-69dc7d6b4b-g4mxv_0b708261-c3b7-4971-a2eb-550fc38f9b34          5m39s
policy-controller.validationwebhook.00-of-01                                                                     policy-controller-webhook-69dc7d6b4b-g4mxv_f8603637-0216-450d-838e-a62657b3ecbf          5m39s
policy-controller.webhookcertificates.00-of-01                                                                   policy-controller-webhook-69dc7d6b4b-g4mxv_4b032a04-a0ff-4fdd-a778-6b53c85a2bfd          5m39s

Helm no longer manages namespaces for users so the fix is to instruct the user to delete the namespace (not ideal) or to use some sort of uninstall hook to clean up the leases. I think the latter is what we want.
Steps to reproduce

kind create cluster
kubectl create ns cosign-system
helm install -n cosign-system policy-controller sigstore/policy-controller
wait for healthy pods...
helm uninstall -n cosign-system policy-controller
wait for pods to be removed...
helm install -n cosign-system policy-controller sigstore/policy-controller
Check the pod logs and see errors

Version
Chart version: 0.5.1
App version: 0.7.0

Thanks for the issue @eddiezane, these leases are created by the knative services on start. For the moment, we recommend to manually delete the leases. But I agree we need to add an uninstall hook.

Can we add instructions for manually doing these if we can't do the hooks in a near future?

Let's fix it and avoid extra documentation: https://github.com/sigstore/helm-charts/pull/510


add meta information to customer story and webinar pages

Description

Related Issue(s)

Checklist

[ ] I have read the contribution guidelines
[ ] I have considered the performance impact of these changes
[ ] Suitable unit/system level tests have been added and they pass
[ ] Documentation has been updated

Not ready for review, one thing needs to be fix


Support general SIMD instruction

Making ndt_omp independent to the SIMD architecture

using compiler flag -march=native, instead of using sse flags immediately.
using aligned allocation std::vector of Eigen::Matrix

I'll close and re-open since I changed the target branch.

@kenji-miyake Please double-check this PR :pray:

Also, why the CI has failed? I think we should fix them.

The CI target is noetic and melodic. CI scripts for ROS2 is ready for review on #5

Let's merge this after #5 is merged and the CI is checked in this PR.
@KeisukeShima @harihitode Could you send PRs equivalent with #5 and #8 to https://github.com/koide3/ndt_omp?

@KeisukeShima Could you rebase this, please? :pray:

This repository does not allow force push, so I created a new PR. #9

hmm, actually it was possible.

@kenji-miyake It is good, although there is a question of whether the same results can be obtained on real machines on vehicles.


Start Channel Arbitrators concurrently

Followup of https://github.com/lightningnetwork/lnd/pull/9253. This makes sure we start the channel arbitrators concurrently with a maximum timeout of 5 min.

Ok I think this approach is not really good because you were raising a really good point here @guggero:
go func(arb *ChannelArbitrator) {
			defer wgChannelArb.Done()

			select {
			case channelArbErrs <- arb.Start(startState):

			case <-ctx.Done():
				channelArbErrs <- ctx.Err()

			case <-c.quit:
				channelArbErrs <- ErrChainArbExiting
			}
		}(arbitrator)

This call does block forever when we launch the arb.Start prior timeout, which we very likely will, the starting is not the problem but more the finishing.
Tho looking into the start() function I don't really see an easy way to spawn goroutines which could cancel because of a timeout. I think what we should garantee is, that the call to the external units should be timing out if the call blocks. So I think this change makes no real sense.

By easy way, I don't think it is appropriate design, cancels imo make only sense if we know we spawn goroutines in that function but our problem arises because a function call to a normal subsystem does not timeout, so I think we need to improve there.

what we could do which is the only way it could work is something like this:
      // Create a new goroutine for the actual Start call
        startErrChan := make(chan error, 1)
        go func() {
            startErrChan <- arb.Start(startState)
        }()

        // Wait for either the start to complete or context to be done
        select {
        case err := <-startErrChan:
            channelArbErrs <- err

        case <-ctx.Done():
            // Don't wait for Start to complete if timeout occurs
            channelArbErrs <- ctx.Err()

        case <-c.quit:
            channelArbErrs <- ErrChainArbExiting

basically starting a goroutine in a goroutine.

Ok I mean spawning goroutines might not be the best solution here because we need for each startup 2, but I implemented it nonetheless because maybe it will take a while until we have the hooks for external subsystems configurable with timeouts.

@Roasbeef this works as well and resolves the deadlock.


[release/v7.2]Use correct signing certificates for RPM and DEBs

Backport #21522
This pull request includes changes to the signing profiles in the CI pipeline configuration files to ensure consistency in naming conventions.
Changes to signing profiles:

.pipelines/PowerShell-Packages-Official.yml: Updated the signingProfile parameter for mariner_x64 and mariner_arm64 jobs to use 'CP-459159-Pgp' instead of 'CP-459159-pgpdetached'.
.pipelines/templates/linux-package-build.yml: Updated the signingProfile parameter for deb job to use 'CP-450779-Pgp' instead of 'CP-450779-pgpdetached'.

/azp run PowerShell-CI-linux

/azp run PowerShell-CI-windows

/azp run PowerShell-CI-macos


Analysis Circletracer how it's working as of now

This issue is to record analysis of how current Circletracer is working.
Purpose of this analysis is;

we need a GUI to select nodes for circle-partitioner and circle-opselector
we can (1) use/revise existing Circletracer (2) use netron (need to analysis this in another task) (3) rebuild from scratch

Required features are

just show graph of nodes from circle model
select one or more nodes and get the selected nodes by index, name, and ...
selection of the node shows property window
in the future this should show also other type of models like ONNX, TF, tflite
follow look and feel of Netron to be user friendly

Bug? running the command and select another model, existing pannel won't show that another model.

index.html in media changed
    <script src="_loadFileUri" nonce="_nonce"></script>
    <script src="_treeMapUri" nonce="_nonce"></script>
    <script src="_makeDataUri" nonce="_nonce"></script>
    <script src="_utilsUri" nonce="_nonce"></script>
    <script src="_circleInfoUri" nonce="_nonce"></script>
    <script src="_dagreUri" nonce="_nonce"></script>
    <script src="https://d3js.org/d3.v5.min.js" nonce="_nonce"></script>
    <script nonce="_nonce">
        treeMap(_Circletracer._circleToJsonData);
    </script>

to actual script by src/Circletracer.ts
    // Apply js and css to html
    html = html.replace(/_nonce/g, `${nonce}`);
    html = html.replace(/_webview.cspSource/g, `${webview.cspSource}`);
    html = html.replace(/_loadFileUri/g, `${loadFileUri}`);
    html = html.replace(/_treeMapUri/g, `${treeMapUri}`);
    html = html.replace(/_makeDataUri/g, `${makeDataUri}`);
    html = html.replace(/_utilsUri/g, `${utilsUri}`);
    html = html.replace(/_circleInfoUri/g, `${circleInfoUri}`);
    html = html.replace(/_dagreUri/g, `${dagreUri}`);
    html = html.replace(/_styleUri/g, `${styleUri}`);

_loadFileUri to media/Circletracer/loadfile.js and so on
why?

About return string staring with back-ticks( ` )...

https://stackoverflow.com/questions/47067319/back-tick-vs-single-quote-in-js

var value = 4;
var str = `text with a ${value}`
// str will be  : 'text with a 4'

src/Circlereader/circle-analysis/circle has generated .ts source to read/parse .circle files.

there are lots file files
generated files canbe generated at configure/build time not in the repo
circle-analysis folder name is odd
strange why return value is in string not in object.

How to debug vscode extension?

in debug instance, run command (Ctrl+Shift+P) Open Webview Developer Tools

close for now, reopen later if needed.


Fixed a bug

I found a bug in the pull request the other day, so I fixed it. I'm sorry. please confirm.

can you please rebase your fork to the current head of main?


CodePlex Issue API does not return issue Title

Issue (work item) details returned from CodePlex Issue API does not include the Title attribute.
The API should return the issue Id and Title attributes so no additional requests need to be made to get the title.
eg. https://netoffice.codeplex.com/project/api/issues/15922

  "WorkItem": {
    "AffectedComponent": {
      "DisplayName": "",
      "Name": ""
    },
    "AssignedTo": "",
    "ClosedBy": "",
    "ClosedComment": "",
    "CommentCount": 5,
    "Custom": "",
    "Description": "...",
    "HtmlDescription": "...",
    "PlainDescription": "...",
    "LastUpdatedBy": "SebastianDotNet",
    "LastUpdatedDate": "/Date(1371195199340-0700)/",
    "PlannedForRelease": "",
    "ReleaseVisibleToPublic": false,
    "Priority": {
      "Name": "Low",
      "Severity": 50,
      "Id": 1
    },
    "ProjectName": "netoffice",
    "ReportedBy": "ppratscher",
    "ReportedDate": "/Date(1306491685283-0700)/",
    "CanContactReportedByUser": false,
    "Status": {
      "Name": "Resolved",
      "Id": 7
    },
    "ReasonClosed": {
      "Name": "Unassigned"
    },
    "Summary": "System.AccessViolationException when writing Excel Cells",
    "Type": {
      "Name": "Issue",
      "Id": 3
    },
    "VoteCount": 1,
    "Id": 15922,
    "HasUserVoted": false
  },
  "FileAttachments": [

  ],
  "Comments": [
    {
      "Message": "...",
      "PostedBy": "SebastianDotNet",
      "PostedDate": "/Date(1306764862810-0700)/",
      "WorkItemId": 15922,
      "Id": 202982
    }
  ],
  "CanDeleteWorkItem": true,
  "CanDeleteComments": true
}

Thanks for the feedback. At present, we won't be changing the underlying APIs this tool uses to extract data from CodePlex.com.

This looks like a trivial change and should be implemented.

It is actually named the Summary and not Title.


How to call custom endpoint?

Hi,
I have a custom endpoint that is not the default CRUD...
Like /team/invite-external-member or something.
How can I call this using the plugin? Or do I have to use axios here?

Feathers is all-in on REST (the default CRUD), so the key is to either map your resources into REST (I've never found a scenario that didn't fit with slight variation) OR do the DIY version with Axios.
Your example is troublesome for two reasons.  First, because it focuses on the verb, but there is a noun in plain sight.  Just focus on the noun.

/team/invite-external-member <-- Verb version
/team/invites <-- Noun version

Second: Notice that I've also removed the "external-member" wording, because that's data.  That external status will almost certainly end up as isExternal: true on some record (or some form of that).   Your API will become much easier to maintain in the long run if you keep the data in the payload.
There's a potential third pitfall to your URL scheme depending on how you're using the routes.  Nested routes don't do anybody a favor, so technically the URL can become even simpler.

/team-invites
/invites

with payload { teamId: 5 }.  The way you're using it, currently, it's not REALLY an issue.  As soon as you try to do URL params, like /teams/:teamId/invites you're providing a user experience where none is really necessary.  It always ends up in being extra work for almost no reason.  I've only seen one scenario where it was really "required" to do nested route params.  The company had a proxy server that would ready the route params and would direct the traffic to the correct server based on those params.  This wasn't done for the sake of pretty URLs, it was all because the proxy server could redirect the request very quickly.
Hopefully I've answered your question somewhere in all of my unsolicited advice.  ;)

@smyth64 I'm closing this issue.  Feel free to reopen if you have further comment.


Implement go to beginning / end of line in TextEditBuffer / TextArea

Cmd+L/R

Make sure this works with holding shift to select

Done


Fully resolve correct @ngtools/webpack loader

By using the the direct import approach, the loader will be guaranteed to originate from the same package version/location as the other @ngtools/webpack imports (AngularCompilerPlugin for instance).
Fixes #13539

Question - do we need to upgrade our CLI to 8.x beta in order to get monorepo builds to work again, or downgrade to a version that isn't broken? Please advise, I only see this fix attached to an 8.x beta.

@krimple this should be in the next patch version of 7.x too.

Is that more than a week away? Was making progress on my project but am stopped and can't figure out how to back off of this - if I downgrade ngtools to 7.3.1 or 7.2.x it complains about the version of typescript. I downgrade typescript and still get an error that I have the wrong version.
Just not sure how to get back to a usable tool chain with an existing project.
Thanks, sorry for bugging you but this is a confusing area to troubleshoot.
Ken

We usually do releases every thursday, but there is some variance at times. There should be a release every week or so.

Ok, I can work around it. I'll just revert back to an earlier build with an
older yarn.lock file set.
Thanks again,
Ken
Ken Rimple
Training and Mentoring Services
Chariot Solutions
610-608-3935
@RimpleOnTech
On Wed, Feb 20, 2019 at 3:50 PM Filipe Silva<EMAIL_ADDRESS>wrote:

We usually do releases every thursday, but there is some variance at
times. There should be a release every week or so.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/pull/13549#issuecomment-465748600,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAQloIbNnmHyBMqO8GNT1rUFjQilK_aks5vPbUigaJpZM4abAJ6
.

@krimple actually, was looking at the commits in the patch branch (https://github.com/angular/angular-cli/commits/7.3.x), and I see this is released on 7.3.1+ already. So if you use<EMAIL_ADDRESS>(the matching version of the build system) you should get it.

Great. Thanks.
Sent from my iPhone

On Feb 21, 2019, at 3:46 AM, Filipe Silva<EMAIL_ADDRESS>wrote:
@krimple actually, was looking at the commits in the patch branch (https://github.com/angular/angular-cli/commits/7.3.x), and I see this is released on 7.3.1+ already. So if you use<EMAIL_ADDRESS>(the matching version of the build system) you should get it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Add alpha_spaces validation rule to the form_validation library.

The error occurred because of the change in .rst file because I tried to add the documentation, but changed the document back to the original (deleting the line I added) because I wasn't comfortable with " Sphinx " and was afraid that I'll break it.

I closed this request myself, because it wasn't tidy, I put another request.


Update from Node 12 to Node 14

dupe of https://github.com/stac-utils/stac-server/issues/133 (which is newer, but has a PR referencing it)


Improve code formatting settings

Editorconfig?

The current .editorconfig contains common properties and those special for IntelliJ trying to get close to the current Eclipse formatting and import order.
The file will be picked up automatically by IntelliJ. There is still some different formatting, esp. around chained method calls, which should be marked with // to avoid reformatting.


Update driver.compose.json

Add new device
"_TZE200_bjzrowv2",

this is linked to issue https://github.com/JohanBendz/com.tuya.zigbee/issues/815


fix(translation): fix some German typos

I think the other PR https://github.com/denverquane/automuteus/pull/219 makes this obsolete, right? Am I clear to close?

Correct, this can be closed

Von: Denver Quane<EMAIL_ADDRESS>Gesendet: Donnerstag, 5. November 2020 20:05
An: denverquane/automuteus
Cc: bin101; Author
Betreff: Re: [denverquane/automuteus] fix(translation): fix some German typos (#218)
I think the other PR #219 makes this obsolete, right? Am I clear to close?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/denverquane/automuteus/pull/218#issuecomment-722579131", "url": "https://github.com/denverquane/automuteus/pull/218#issuecomment-722579131", "name": "View Pull Request" }, "description": "View this Pull Request on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]


Kafka scaler: batch GetOffset requests

Signed-off-by: Lionel Villard<EMAIL_ADDRESS>
Send one request to get all topic offsets instead of one request per partition.
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[x] Changelog has been updated

Fixes #

Thanks @lionelvillard !


Upgrade temporal to v1.16.1 and Go to 1.18

Supersedes https://github.com/DataDog/temporalite/pull/64 (thanks @balchua!)

What changed?
Upgrade to temporal v1.16.1, recently released and ui-server to v0.13.0, and Go to 1.18. This also fixes https://github.com/DataDog/temporalite/issues/46

Why?
To keep pace with temporal releases

How did you test it?
Tested locally, by creating workflows.

Potential risks
There is a breaking API reported in temporal.  Refer to this

Is hotfix candidate?
No

Codecov Report

Merging #66 (a996217) into main (0797d11) will decrease coverage by 0.83%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #66      +/-   ##
==========================================
- Coverage   40.38%   39.55%   -0.84%
==========================================
  Files          12       12
  Lines         770      766       -4
==========================================
- Hits          311      303       -8
- Misses        437      441       +4
  Partials       22       22

Impacted Files
Coverage Δ

server.go
52.00% <ø> (-7.50%)
:arrow_down:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

@jlegrone thanks for updating the PR!


;; takes spec and hoon; no more 'idempotence' test

#1055 part 1
test plan: +solid
part 2: remove ++hard (forthcoming)

The "merge" commit also should fix the problem


RELATED: WEB-3600 embedded-image shortcode indentation

Build succeeded (gate pipeline).

https://checklist.intgdc.com/job/compliance/job/gooddata-docs-theme-oss-check/6/ : SUCCESS in 4s
https://checklist.intgdc.com/job/compliance/job/gooddata-docs-theme-fossa-scanning-oss-zuul/6/ : FAILURE in 4s (non-voting)


Don't crawl similar URL

Hi guys. I want to thank you for the great tool. And there are some suggestions.
As the pic above shows, there are many similar URL  in one site, can I have some method to ignore them. as just fetch one of them?

https://github.com/tomnomnom/unfurl

https://github.com/tomnomnom/unfurl

Thanks for the tool, but I‘d like to ignore when crawling not after.

@j3ssie any plans to add this to avoid duplicate URLs ?

@j3ssie any plans to add this to avoid duplicate URLs ? In my case gospider keeps crawling on the same URL and gets stuck / never ends, so I have to kill it manually.


RequestReduce having issues with Umbraco backoffice

I have a site that uses Umbraco.
The site renders as expected with Request Reduce.
However the Umbraco back office renders incorrectly (more than one  and head in page etc...)
I nice way to get around this issue would be to ignore the Umbraco back office pages for Request Reduce
Is there anyway to configure RequestReduce to ignore the Umbraco back office?
I tried the "javascriptUrlsToIgnore" property by setting it to "/umbraco/" but that didn't work

I had a similar issue, but it was with another part of the site. I was able to ignore certain urls using the PageFilter API on the url path with the following code (VB.net):
Namespace WSC
    Public Class StartupModule
        Implements IHttpModule

        Private Shared _lockObj As New Object()
        Private Shared _ran As Boolean = False

        Public Sub Dispose() Implements IHttpModule.Dispose
        End Sub

        Public Sub Init(context As HttpApplication) Implements IHttpModule.Init
            '-- lock
            If Not _ran Then
                SyncLock _lockObj
                    If Not _ran Then
                        ' everything we do here is blocking
                        ' on application start, so we should be quick.
                        RequestReduce.Api.Registry.AddFilter(New RequestReduce.Api.PageFilter(Function(x) Not x.HttpRequest.Url.Host.Contains("/specsheet.aspx")))
                        _ran = True
                    End If
                End SyncLock
            End If
        End Sub
    End Class
End Namespace


Appreciations

[This project is really good it helped me really thanks a lot I will be keeping up with these kind of stuffs because nowadays my mind is really rotating around learning mobile and desktop applications with visual studio thanks. :) ]

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

ID: 6ab89335-bb35-dd6e-cb41-2d889415a555
Version Independent ID: 72c891a7-6f2a-45e5-0935-0cdee220305c
Content: Xamarin.Forms Quickstart Deep Dive - Xamarin
Content Source: docs/get-started/quickstarts/deepdive.md
Product: xamarin
Technology: xamarin-forms
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Thanks for the feedback @aliyuago


Update statement on who has access to remove members from a channel

At https://docs.mattermost.com/help/getting-started/welcome-to-mattermost.html#channels under Private Channels section there is a sentence that says "Channel members can choose to leave at any time, but only the channel owner or Team Admin can remove other members."
The highlighted section is inaccurate and is correctly described here https://docs.mattermost.com/help/getting-started/organizing-conversations.html#removing-members-from-a-channel.
By default we are giving users the ability to remove users from public and private channels. If you have access to Advanced Permissions (https://docs.mattermost.com/cloud/cloud-user-management/advanced-permissions.html), then you can change the behaviour. https://docs.mattermost.com/help/getting-started/welcome-to-mattermost.html#channels should be updated to clarify it.
For https://github.com/mattermost/mattermost-server/issues/16857

Documentation updated via: https://github.com/mattermost/docs/pull/4339


Why not use approved PowerShell verbs - Run vs. Invoke/Start?

Describe the issue
To facilitate the learning and discovery process for new users, PowerShell uses a predefined set of verbs for all cmdlets and advanced functions to use. While I really like the new Run-ALValidation and Run-ALPipeline cmdlets, I also really like meaningful standards. :-) Cmdlets that run things should probably use either the Start verb (according to the documentation, "Initiates an operation"), or the Invoke verb ("Performs an action, such as running a command or a method").
Scripts used to create container and cause the issue
Get-Verb Run # this exists as an approved verb
Get-Verb Invoke # this does not exist as an approved verb
Full output of scripts
n/a
Screenshots
n/a
Additional context
A possible, backwards compatible solution would be to correct the function names, then add the old, flawed name as an alias.

I am totally aware that BcContainerHelper doesn't live up to high standards of PowerShell.
Not only the names, but also the piping and other things.
It is in my backlog to change this but I have no ETA.

OK, thanks. I hope to - some day - find the time to help fix some of those cases in a pull request.

Maybe we should start by adding an new alias to all command with a wrong verb. so we can do a soft migration.
at some day we will change the function name and add the old one as alias and throw a warning if the alias is used.
later we will remove the alias (old verb).


Update Assessment Screen analytics

https://openedx.atlassian.net/browse/MA-1397
Screen events for Course Dashboard, Course Outline, Course Sections, Course Unit Detail screens have been updated.
This PR also removes the unnecessary generic catching of Exceptions while we called the analytics code.
@aleffert @bguertin @1zaman plz review

:+1:

:+1:

:+1:


#4862669: Banner, Modal: separate padding config into paddingX/paddingY

Closes #4862669
Test Plan
tests performed

A Test Plan is used to show what you tested to make sure your code works fine. You should write here all that you did to test, and provide some results of your testing.

These results can be screenshots, query results, or even just pointers to unit tests that successfully passed.

tests not performed (domain coverage)

At times not everything can be tested, and writing what hasn't been tested is just as important as writing what has been tested.

An example of partial test is a field displaying 4 possible values. If 3 values are tested, with screenshots, and 1 is not, then it should be mentioned here.

Oppure no, ma tagghiamola come breaking

Taggata come breaking


Query Builder MERGE aka UPSERT

The ability to uniformly apply and UPSERT to multiple languages.
Great summary of the different SQL implementations: https://en.wikipedia.org/wiki/Merge_(SQL)
Possible Syntax: knex().insert({...}).upsert([keys]).update({...})

I'd like to see a discussion of the API, but upsert support would be great.

Duplicate of #54


[DOC] Add documentation for api of configuring notifications on Index Management operations

What do you want to do?

[ ] Request a change to existing documentation
[x] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
Version equals / greater than 2.8 will be affected.  In 2.8, admins can configure notifications for some long-runnig Index Management operations #4037 . We introduce some new APIs for this feature and we want to add new documentation to these APIs.
By using these APIs, users create configs to bind notification channels and conditions with the input task id or action. If task id is provided, this config is an ad-hoc config(normally used by front-end) and will be automatically deleted after the task end. The task id can be obtained by setting wait_for_completion parameter as false #3186 . If task id is null, this config will be binded with    the action type. It is a global setting and won't be deleted automatically. Every index operation of this type will use this config to send notification, no matter triggerred by front-end, command line API or ISM policy.
Here is the introduction for these APIs:

create

// example request
POST /_plugins/_im/lron
{
  "lron_config": {
      "task_id":"dQlcQ0hQS2mwF-AQ7icCMw:12354",
      "action_name":"indices:data/write/reindex",
      "lron_condition": {
        "success": false,
        "failure": true
      },
      "channels":[
          {"id":"channel1"},
          {"id":"channel2"}
      ]
  }
}

// example response
{
  "_id": "LRON:dQlcQ0hQS2mwF-AQ7icCMw:12354",
  "lron_config": {
    "lron_condition": {
      "success": false,
      "failure": true
    },
    "task_id": "dQlcQ0hQS2mwF-AQ7icCMw:12354",
    "action_name": "indices:data/write/reindex",
    "channels": [
      {
        "id": "channel1"
      },
      {
        "id": "channel2"
      }
    ]
  }
}

The lron_condition is true, true by default.

update

PUT /_plugins/_im/lron/{lronID}
{
   // request body is same with POST
   ...
}
// response is same with POST

get

// get one doc
 GET /_plugins/_im/lron/{lronID}
// get all docs
GET /_plugins/_im/lron

//example response
{
  "lron_configs": [
    {
      "_id": "LRON:dQlcQ0hQS2mwF-AQ7icCMw:12354",
      "lron_config": {
           xxxxxxxxx
      }
    },
   {
      "_id": "LRON:dQlcQ0hQS2mwF-AQ7icCMw:12355",
      "lron_config": {
           xxxxxxxxx
      }
    }
  ],
  "total_number": 2
}

delete

DELETE /_plugins/_im/lron/{lronID}

# response is same with DeleteResponse in Opensearch core

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
UX RFC: https://github.com/opensearch-project/index-management-dashboards-plugin/issues/687
API: https://github.com/opensearch-project/index-management/issues/700
The PR of the whole feature in documentation-website: https://github.com/opensearch-project/documentation-website/issues/4037

@zhichao-aws I'm assigned to this issue. Before getting started, I have a few questions:

Where do you think the documentation should be structured? Under this section https://opensearch.org/docs/latest/im-plugin/index/?
Do you have a draft of the developer documentation for this feature? If not, can we sync to discuss/demo?

Thanks!

Hi @vagimeli , I think it's good to put the document under this section https://opensearch.org/docs/latest/im-plugin/index/.


Type instabilities in referencing of MeshData, RefElemData tuples

function foo(rd::RefElemData,md::MeshData)
    @unpack Dr = rd
    @unpack x = md
    return x,Dr
end

is type unstable

This doesn't happen for
function foo(rd::RefElemData,md::MeshData)
    Dr = rd.Drst[1]
    x = md.xyz[1]
    return x,Dr
end

Fixed with https://github.com/jlchan/StartUpDG.jl/commit/b3c45c56d6f96218121ea13f83b625453e924e13
For reference: https://discourse.julialang.org/t/unexpected-type-instability-with-getproperty-but-not-setproperty/26975/10?u=jlchan

Fixed with https://github.com/jlchan/StartUpDG.jl/commit/b3c45c56d6f96218121ea13f83b625453e924e13
For reference: https://discourse.julialang.org/t/unexpected-type-instability-with-getproperty-but-not-setproperty/26975/10?u=jlchan


chore: configure dependabot to reduce noise

This is analogous to the PR in liferay-npm-tools here:
https://github.com/liferay/liferay-npm-tools/pull/490
Copying the rationale here:

Dependabot spams us with update PRs that we don't want to merge because of the reasons described here:
https://github.com/liferay/liferay-frontend-guidelines/blob/master/general/security.md
Most importantly, there are drawbacks to lockfile-only updates (they are too easily reverted or misunderstood, for example) and we prefer to batch our security updates together based on some human assessment of impact/urgency etc.
So, this setting file should ensure that Dependabot only keeps at most one PR open at a time (the default is 10, I believe), and it runs weekly (the default, I believe). Additionally, given that we want these PRs only as a cue for a human to schedule a periodic manual audit, we turn off automatic rebasing to further reduce noise.
Test plan: Sadly, I don't think I can test it, short of shipping it and then monitoring. At the moment we have 6 dependency update PRs open in this repo. I'll close them and replace them with a manual update ticket, and then we'll have to watch and see whether the PR count stays at 1 or below.

Want to merge this before closing the PRs mentioned in this issue.
Seeing as the approval for https://github.com/liferay/liferay-npm-tools/pull/490, I'm just going to assume this one is approved too.


DR6: drop bad CCD not exposure

Some CCDs (all amplifiers) are bad while the rest are fine. This example from S7 is example showing more than amplifier gains being wrong. This CCD should be rejected all together.
Add an "err_message" column to zeropoints files to log when a CCD fails and why but then can keep processing

fixed with 00c21db9


Remove triggerable unhandled exceptions from blacklist code

Please note you should reevaluate your blacklist function as well, I have not checked for other methods such as missing minimum stake checks, allowing unregistered checks, etc.
For instance, an exception is still possible to be thrown if the miner sets self.config.blacklist.allow_non_registered. Why a miner would do this when not on testnet, who knows.

Not using blacklist as miners are scored only on commit data, no axon/dendrite activity in this subnet


inclusion of empty glyphs (.null, space, CR)

Investigating another diff, this time for Afacad, and noticing that our glyph orders differ significantly, and this is due to the fact that fonttools is assigning glyph ids to a number of 'empty' glyphs like .null, CR, etc.
I suspect someone here will have more insight into this than I do, so opening an issue before I dig too deeply.
looks like there was some loosely related discussion in #185?

as far as I am aware, fontmake (or ufo2ft rather) only adds the .notdef glyph. The .null and CR are legacy glyphs recommended in the old TrueType spec but they are no longer required nowadays. If the source font contains those, of couse we build them, otherwise we don't.

looks like there was some loosely related discussion in https://github.com/googlefonts/fontc/issues/185?

hm I don't think these are related.

I see what's going on. the source fontains a glyphOrder custom parameter which is marked as disabled:

fontc is duly ignoring the parameter as if it wasn't there. However fontmake, or actually glyphsLib is ignoring the disabled flag and applying the custom glyphOrder.
I searched glyphsLib issue tracker and it appears to be a long-standing issue:
https://github.com/googlefonts/glyphsLib/issues/809
https://github.com/googlefonts/glyphsLib/issues/905
Basically glyphsLib (hence fontmake) doesn't bother checking the disabled flag most of the time, which is of course wrong.
So this an instance where fontc is correct and fontmake has a bug.
Ideally we'd fix fontmake in this case if it's not too much trouble. But as always, making even relatively small changes to glyphsLib is always a risk of getting sucked in deep rabbit holes..

with https://github.com/googlefonts/glyphsLib/pull/1036 applied, the GlyphOrder of Afacad is now reported as identical b/w fontc and fontmake (glyphOrder param gets ignored by both)

okay let's close this, since it looks like our behaviour is correct, and we'll get a match when that patch is merged.


Generate new constants from D2XX programmer's guide

I generated new constants using the D2XX programmer's guide. This should eliminate the licensing issue created by using PyUSB's definitions.
Refs #4

@catskull Thanks a lot for doing this. Have you already tested that this works? I don't have an FTDI setup anymore.

@catskull I reviewed they changes, and they look alright. If you run into issues, please let me know.

@snmishra Thanks, will do.


feat: lambda logging rules

Serverless Nag Pack - lambda logging rules
First rule of many to check if this is in-line with the team's standards

I've written up rules for the rest of the pack.
Just thought i'd get this Lambda Log rule through first so i can make sure the rest of the serverless pack implementation aligns


Unable to upgrade from Meteor <IP_ADDRESS> to 1.6.1 because of ClassyTestCase errors

@mitar
Hi,
I'm maintainer of Wekan https://wekan.github.io
I am currently stuck at at Meteor <IP_ADDRESS> . When I tried to upgrade to 1.6.1, I did first save babel
meteor npm install --save @babel/runtime
+<EMAIL_ADDRESS>
Then I get this error when starting Wekan:
The `stylus` package has been deprecated.

To continue using the last supported version
of this package, pin your package version to
2.513.14 (`meteor add stylus@=2.513.14`).
Presence started serverId=G2crLpHP2ybDjcSQB
/home/wekan/repos/wekan/.build/bundle/programs/server/node_modules/fibers/future.js:280
						throw(ex);
						^

ReferenceError: ClassyTestCase is not defined
    at packages/peerlibrary_computed-field.js:258:4
    at packages/peerlibrary_computed-field.js:264:4
    at packages/peerlibrary_computed-field.js:408:3
    at /home/wekan/repos/wekan/.build/bundle/programs/server/boot.js:411:36
    at Array.forEach (<anonymous>)
    at /home/wekan/repos/wekan/.build/bundle/programs/server/boot.js:220:19
    at /home/wekan/repos/wekan/.build/bundle/programs/server/boot.js:471:5
    at Function.run (/home/wekan/repos/wekan/.build/bundle/programs/server/profile.js:510:12)
    at /home/wekan/repos/wekan/.build/bundle/programs/server/boot.js:470:11

It looks like this ClassyTestCase issue https://github.com/peerlibrary/meteor-classy-test/issues/13
I did try adding that peerlibrary:computed-field as separately cloned to wekan/packages directory like there is already some other in my rebuild-wekan-meteor-1.6.sh script at https://github.com/wekan/wekan-maintainer/tree/master/virtualbox , I did not get it working.
I did also try removing those ClassyTestCase lines with:
sed '127,401d' wekan/.build/bundle/programs/server/packages/peerlibrary_computed-field.js

But Wekan javascript console did still show ClassyTestCase not defined errors.
Upgrading packages gives unhelpful messages https://github.com/meteor/meteor/issues/3536
I have not found a way to update all meteor packages https://github.com/meteor/meteor/issues/4610

Same issue.

@mitar any plan on resolving this issue?

I do not think this can be resolvable with this package? If you know how, tell me. I think this is bug in Meteor.

@WayneUong try to remove and then add again package which use peerlibrary packages as dependency.

Execute meteor list --tree command.
Found which one use peerlibrary packages
Then meteor remove packageName and meteor add packageName

It helped me.

That should be the same as updating meteor/.versions directly, no?

@mitar In my case (and, as far as i know, for others people too) editing version of package cause a dependency hell.
I have described process which helped me exactly how i executed it.

Thanks for feedback.
And which version you ended up then having in .versions?

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

@m-pokrovskii @mitar I got the same results. But you're basically downgrading the packages to even lower versions. E.g. peerlibrary:computed-field was downgraded from 0.7.0 to 0.3.1 as seen below. The app does compile successfully with these earlier versions, but it gives me a blank page in browser.
Waynes-MBP:nfc-meteor2 wayneuong$ meteor remove easysearch:components

Changes to your project's package version selections:

easysearch:components         removed from your project
peerlibrary:assert            removed from your project
peerlibrary:base-component    removed from your project
peerlibrary:blaze-components  removed from your project
peerlibrary:computed-field    removed from your project
peerlibrary:data-lookup       removed from your project
peerlibrary:reactive-field    removed from your project

easysearch:components: removed dependency
Waynes-MBP:nfc-meteor2 wayneuong$ meteor add easysearch:components

Changes to your project's package version selections:

easysearch:components         added, version 2.2.1
peerlibrary:assert            added, version 0.2.5
peerlibrary:base-component    added, version 0.14.0
peerlibrary:blaze-components  added, version 0.16.2
peerlibrary:computed-field    added, version 0.3.1
peerlibrary:data-lookup       added, version 0.1.0
peerlibrary:reactive-field    added, version 0.1.0

easysearch:components: Blaze Components for EasySearch

Yes, this is not a solution. You should get to 0.7.0 or 0.8.0 package version, depending on your CoffeeScript version.

Any update?

@m-pokrovskii
This is a bug in meteor, that does not allow upgrading. Ask for news at meteor bug https://github.com/meteor/meteor/issues/9609

A workaround that worked for me is :

Clone this package (computed-field) to packages/computed-field in your meteor project root

$ git clone git@github.com:peerlibrary/meteor-computed-field.git packages/computed-field

Change to the new directory and checkout the commit of version 0.7.0 (see package.js to ensure)

$ cd packages/computed-field && git checkout 3215d73f

Change line 13 in package.js from 'coffeescript',  to<EMAIL_ADDRESS>Add new line<EMAIL_ADDRESS>in your project .meteor/packages (project root)

@mahmost
Thanks, it works! I added pull request to fix this https://github.com/peerlibrary/meteor-computed-field/pull/14

This is the same as 0.7.0 package, no?

That pull request does not solve anything. Real fix would be to have all dependencies use CoffeeScript 2.

I released 0.9.0 which has been converted from CoffeeScript to JavaScript. Let's see if that will help you. Can somebody test please?

@mitar
Works for me, thanks a lot !
~/repos/wekan$ meteor update --release 1.6.1

Changes to your project's package version selections from updating the release:

accounts-base               upgraded from 1.4.0 to 1.4.2
autoupdate                  upgraded from 1.3.12 to 1.4.0
babel-compiler*             upgraded from 6.24.7 to 7.0.5
babel-runtime               upgraded from 1.1.1 to 1.2.0
boilerplate-generator       upgraded from 1.3.1 to 1.4.0
callback-hook               upgraded from 1.0.10 to 1.1.0
check                       upgraded from 1.2.5 to 1.3.0
coffeescript                downgraded from 1.12.7_3 to 1.0.17
coffeescript-compiler       removed from your project
ddp-client                  upgraded from 2.2.0 to 2.3.1
ddp-common                  upgraded from 1.3.0 to 1.4.0
ddp-server                  upgraded from 2.1.1 to 2.1.2
diff-sequence               upgraded from 1.0.7 to 1.1.0
dynamic-import              upgraded from 0.2.1 to 0.3.0
ecmascript                  upgraded from 0.9.0 to 0.10.0
ecmascript-runtime-client   upgraded from 0.5.0 to 0.6.0
es5-shim                    upgraded from 4.6.15 to 4.7.0
http                        upgraded from 1.3.0 to 1.4.0
id-map                      upgraded from 1.0.9 to 1.1.0
meteor-base                 upgraded from 1.2.0 to 1.3.0
minifier-css                upgraded from 1.2.16 to 1.3.0
minifier-js                 upgraded from 2.2.2 to 2.3.1
modules                     upgraded from 0.11.0 to 0.11.3
mongo                       upgraded from 1.3.1 to 1.4.2
ordered-dict                upgraded from 1.0.9 to 1.1.0
peerlibrary:computed-field  upgraded from 0.7.0 to 0.9.0
promise                     upgraded from 0.10.0 to 0.10.1
random                      upgraded from 1.0.10 to 1.1.0
reload                      upgraded from 1.1.11 to 1.2.0
retry                       upgraded from 1.0.9 to 1.1.0
server-render               added, version 0.3.0
shim-common                 added, version 0.1.0
socket-stream-client        added, version 0.1.0
standard-minifier-css       upgraded from 1.3.5 to 1.4.0
standard-minifier-js        upgraded from 2.2.3 to 2.3.1
url                         upgraded from 1.1.0 to 1.2.0
webapp                      upgraded from 1.4.0 to 1.5.0

* These packages have been updated to new versions that are not backwards
compatible.
wekan: updated to Meteor 1.6.1.

Oops coffeescript downgraded?

I removed coffeescript, and added coffeescript compiler, that really likes to add old coffeescript back:
$ meteor add coffeescript-compiler

Changes to your project's package version selections:

coffeescript           added, version 1.0.17
coffeescript-compiler  added, version 2.2.1_1

coffeescript-compiler: Compiler for CoffeeScript code, supporting the coffeescript package

$ meteor
[[[[[ ~/repos/wekan ]]]]]

=> Started proxy.

Changes to your project's package version selections:

coffeescript  added, version 1.0.17

=> Started MongoDB.
W20180226-17:49:26.961(2)? (STDERR) The `stylus` package has been deprecated.
W20180226-17:49:26.997(2)? (STDERR)
W20180226-17:49:26.998(2)? (STDERR) To continue using the last supported version
W20180226-17:49:26.998(2)? (STDERR) of this package, pin your package version to
W20180226-17:49:26.998(2)? (STDERR) 2.513.14 (`meteor add stylus@=2.513.14`).
I20180226-17:49:27.101(2)? Presence started serverId=vacc538xE5LZ2JBHL
=> Started your app.

=> App running at: http://localhost:3000/

Currently I have these versions:
$ cat .meteor/versions
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

I did try to got futher down to the rabbit hole with upgrading packages, but got lost. I don't know how downgrading coffeescript would affect apps, are there security fixes in newer versions of coffeescript.

I will assume this is the problem of: https://github.com/meteor/meteor/issues/8512

I cannot reproduce this. So closing for now. Please (re)open if this is still a problem.


xZoom with Magnific Popup counter always start from 1

Eventhough I click on the third thumbnail and it pops up correct image, the counter always start from 1.
This bug doesnot happen on magnific popup gallery itself.
Does anyone have any fix or update for this?

I ended up using this
`
var gallery = xzoom.gallery().ogallery; //get original gallery with start index 0
var i, images = new Array();
for (i in gallery) {
images[i] = {src: gallery[i], title: thumb[i].title};
}
$.magnificPopup.open({
items: images,
mainClass: 'mfp-pdp',
preloader: false,
type:'image',
gallery: {
enabled: true
},
image: {
titleSrc: 'title'
}
}, xzoom.gallery().index);
`

Thanks, for sharing your solution. I just didn't noticed there were a counter.


Fatal error on nulldevice

I added 6 new optional (required: false) drivers to the Ecobee package.
This causes your version-matching code to fail when you try to run an Update:
errorjava.lang.NullPointerException: Cannot get property 'version' on null object on line 936 (performUpdateCheck)
The reason is (obviously) because the existing install doesn't have that file installed, so it can't compare versions. I was able to get around the error by changing the code to:
[code]
for (driver in manifest.drivers) {
def installedDriver = getDriverById(state.manifests[pkg.key], driver.id)
if (driver?.version != null && installedDriver?.version != null) {
if (newVersionAvailable(driver?.version, installedDriver?.version)) {
[/code]
The ?.version won't fail if the target is null. That said, I think you want to be more direct - make it install the new/added item (if required: true), don't flag an error/upgrade if not.
Note that to make this "add a few more optional files" actually work, the user has to re-match the package. I think you need a way that the added items just get melded in, without the user having to do anything.

I agree with your fix. Good catch. They wouldn't need to do a match up, they could just go and do a Modify which will list the new optional packages.

That being said, I agree that's not exactly user friendly. If there are new required ones it should just install them and if there are new optional it should prompt you so you can decide. I'll get on that.

I tried that, and it didn't work - the optional devices didn't show up until I did the re-scan.

Hmm I wonder if it didn't work as a result of the first bug, it worked for me. Either way I'm going to build this into the update process because I agree it's confusing right now. I now added support where if there is a new required one it treats it as an upgrade. Now just need to add support for the optional.

This will be fixed in the next version.


Outdated documentation api.v1 vs api.v2

Hi,
the documentation here still seems to follow the old interface, while other parts discuss both v1 and v2. Is there a current equivalent to the example provided there, given that the regex parameter is no longer available in v2?
Thanks for a great tool!

regex was replaced by prefix that is less expensive.
For you API 2 you need to use another client: https://openreview-py.readthedocs.io/en/latest/api.html#openreview.api.OpenReviewClient
We will update the documentation soon, thanks!

Perfect, thanks!


[Styles Bug 🐛]: compact density show unnecessary scrollbar (overflow)

material-react-table version
1.10.0
react & react-dom versions
17.0.2
Describe the bug and the steps to reproduce it
Just by using
 initialState={{
        density: 'compact',
      }}

It adds an unnecessary scrollbar to the table container.
With default density the styles are ok (check bellow screenshots)
Thanks!
Minimal, Reproducible Example - (Optional, but Recommended)
https://stackblitz.com/edit/github-8af2aq?file=src%2FJS.js,src%2FTS.tsx,src%2FmakeData.ts
Screenshots or Videos (Optional)
With compact density:

With default density is ok:

Do you intend to try to help solve this bug with your own PR?
No, because I do not know how
Terms

[X] I understand that if my bug cannot be reliably reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

In what resolution is there scroll?
Is it in small size or large size?
I tested the link and it looks ok in large size!

also you can add this line    enableDensityToggle={false}

This bug will be fixed in the next patch

@mm0hammadi it is on smaller screen sizes (you can resize the browser window - until the scroll appears)
@KevinVandy thank you! 🚀

@mm0hammadi here is the recording, I hope now it is clear ))
https://drive.google.com/file/d/18IhiPvZIDVa9ebiBiKLS5_b1vWQZSDD5/view
Thanks

fixed in v1.11.0


Added Advanced Search bar

The search bar works by allowing users to input keywords or phrases related to the products they are looking for. When users type in their search queries and press the search button or hit Enter, the search bar triggers a search function within the website's backend. This function then retrieves relevant product listings matching the user's search query and displays them on the search results page.
The search bar typically features placeholder text to guide users on what they can search for, such as "Search for products..." or "Enter keywords...". It also includes a search button for users to initiate the search process manually.
In summary, the search bar facilitates efficient navigation and discovery of products within an online store by allowing users to quickly find what they're looking for based on their search queries.
@Anushkabh , I added a Search bar. Kindly Check it and merge it

resolve conflict

resloved conflict

Resolve the conflict and create a new PR


Attempting to pull in a single JS file results in odd things.

Hi.
I've got a project that would like to use https://github.com/kvz/phpjs/blob/master/functions/array/array_combine.js.
So I type bower install https://github.com/kvz/phpjs/blob/master/functions/array/array_combine.js --save and see ...
bower array_combine#*           cached https://github.com/kvz/phpjs/blob/master/functions/array/array_combine.js
bower array_combine#*         validate https://github.com/kvz/phpjs/blob/master/functions/array/array_combine.js#*
bower array_combine#*          install array_combine

array_combine bower_components\array_combine

This results in my bower.json file containing ...
"array_combine": "https://github.com/kvz/phpjs/blob/master/functions/array/array_combine.js"
At this stage, all looks good.
But the bower_components\array_combine directory contains 2 files. One called .bower.json and index.js.
The .bower.json contains ...
{
  "name": "array_combine",
  "_cacheHeaders": {
    "Content-Type": "text/html; charset=utf-8"
  },
  "main": "index.js",
  "_source": "https://github.com/kvz/phpjs/blob/master/functions/array/array_combine.js",
  "_target": "*",
  "_originalSource": "https://github.com/kvz/phpjs/blob/master/functions/array/array_combine.js",
  "_direct": true
}

and the index.js file is actually a HTML file (not included as it is quite big).
Using bower-installer results in the html file (index.js) in .\jslib\array_combine\index.js.
Something isn't right as I was expecting the file https://github.com/kvz/phpjs/blob/master/functions/array/array_combine.js in there somewhere.
Regards,
Richard.

https://github.com/kvz/phpjs/blob/master/functions/array/array_combine.js is a HTML file.
You meant https://raw.githubusercontent.com/kvz/phpjs/master/functions/array/array_combine.js

Well. Of course I do. Banging head on desk ... BANG BANG BANG !!!!


code object is not signed at all - fastlane

Expected Behavior
Upgraded from 1.6.0 to 1.6.4 and using xcode 10 + fast lane
Was working on 1.6.0, new version will not code sign
Actual Behavior
2019-02-04 07:30:41 +0000 [MT] Writing entitlements for <IDEDistributionItem: 0x7fccd7391810 'org.cocoapods.Leanplum' '<DVTFilePath:0x7fccd786b1b0:'/Users/jenkins/Library/Developer/Xcode/Archives/2019-02-03/test 2019-02-03 23.26.41.xcarchive/Products/Applications/test.app/Frameworks/Leanplum.framework'>'> to: /var/folders/z1/bqw2_ks13l9fbwq34j3q58hm0000gn/T/XcodeDistPipeline.752/entitlements6N7tUv
2019-02-04 07:30:41 +0000 [MT] Running /usr/bin/codesign '-vvv' '--force' '--sign' 'A77BD1151E6ACCFF3E86E690C6A05BA58ACE304D' '--entitlements' '/var/folders/z1/bqw2_ks13l9fbwq34j3q58hm0000gn/T/XcodeDistPipeline.752/entitlements6N7tUv' '--preserve-metadata=identifier,flags,runtime' '/var/folders/z1/bqw2_ks13l9fbwq34j3q58hm0000gn/T/XcodeDistPipeline.752/Root/Payload/test.app/Frameworks/Leanplum.framework'
2019-02-04 07:30:41 +0000  /var/folders/z1/bqw2_ks13l9fbwq34j3q58hm0000gn/T/XcodeDistPipeline.752/Root/Payload/test.app/Frameworks/Leanplum.framework: replacing existing signature
2019-02-04 07:30:41 +0000  /var/folders/z1/bqw2_ks13l9fbwq34j3q58hm0000gn/T/XcodeDistPipeline.752/Root/Payload/test.app/Frameworks/Leanplum.framework: code object is not signed at all
2019-02-04 07:30:41 +0000 [MT] /usr/bin/codesign exited with 1

Adding this to the build phase from following the manual steps in iOS fixed it
cd "${BUILT_PRODUCTS_DIR}/${FRAMEWORKS_FOLDER_PATH}/Leanplum.framework/"
lipo -remove i386 -remove x86_64 Leanplum -output Leanplum
We were following unity documentation on leanplum - no mention of this.
ta


[SMALLFIX] In some cases,DefaultFileSystemMaster#listStatus throws FileDoesNotExistException

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/950/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/951/
Test PASSed.

@witgo Can you create a jira ticket for this describing the behavior, so we can track the issue? Thanks!

@gpang  done

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/1021/
Test PASSed.


Restore test_substring_column

Fixes #8147.  rapidsai/cudf#13173 has been fixed, so this test can be restored.
This reverts commit 619afc6d64f7082d71661453ec4faecd7ba25eb1.

build


A bug with calendar display

Describe the bug
I'm using Memos on Firefox. Memos was deployed through Docker. In light mode, the calendar is displayed beautifully. However, in dark mode, there is some strange squares that I thought it was a bug. You can see it in the attachments.
Steps to reproduce

Access Memos via Firefox
Change between dark/light mode to see the differences.

The version of Memos you're using.
v0.22.4
Screenshots or additional context

This issue happens in Chrome as well.
To replicate you need to have memos on the dates from the previous month not shown in the calendar as well, in this case 28/07 - 31/07.
This triggers the teal background to get set

Related issue https://github.com/usememos/memos/issues/3751

Mighe be fixed with https://github.com/usememos/memos/commit/14194504ee7bd19d36d929f28f76136ad5294f71