In progress: Initial draft of INDEX token KPIs for Issue #67 (TWG - Low Priority - Low Effort - INDEX token KPIs)

For Issue #67 (TWG - Low Priority - Low Effort - INDEX token KPIs), I've started working on this and have finished subtasks e-j
Since it's my first time contributing (still very excited to be a part of this), please let me know if I've done anything wrong or can fix my procedure / code to any standards.
https://github.com/SetProtocol/index-coop-analytics/issues/67#issuecomment-895696210

Short of refining the presentation into something like a slide deck, I think this is about the limit of presenting from a Jupyter notebook (files named 'showcase...' under kpis/index-token-kpis/). If you guys are okay with it, I think the PR is ready. I've also included a conda yaml virtual environment file so someone can install my environment and easily rerun the notebook (indexTokenKPIs.ipynb) to get updated stats.

@ericlinML one small edit that would be awesome - could you change the folder name to index-token-kpis instead of just index-token-kpi - sorry, I know it is small but I try to keep the folder structures uniform.
Then I am going to leave this issue and the PR in review for just a bit to give Matt and others a chance to respond and ask any follow ups. Thanks for your work here!

@josephd8 Not a problem with the folder naming, and it makes sense to get some eyes on it!

I waited to rename the folder (just renamed it now) and haven't heard from Matt Graham. Obviously no rush for this thing, but should I ping him?

@ericlinML - can we actually put these all in a sub-folder, so the structure would be index-token-kpis/[folder]/*
If you can make that update when you get a chance, then I will merge this. Sorry for the double take on the folder structure.

not a problem, i named it "index-eth-tokens-analysis" but let me know if you would prefer a different name!


ci: adding fossa scan

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

v3.0.1
GitHub release

Your semantic-release bot :package::rocket:


Fix CI

#157 shows that the regression test suite is currently broken.
These commits fix CI, unfortunately I cloud not figure out why targeting Puppet 6 installs an older version of voxpupuli-test instead of the latest shiniest one :shrug:

Nice, thanks @smortex .


Apply compact padding to small buttons with svg icons

The buttons on the repo release tab were larger in height than on other tabs because one of them contained the RSS icon which stretched the button height by 3px. Workaround this problem by applying the "compact" padding to any such button. They are within 0.4px in height now to non-icon buttons.
Before:

After:

For comparison, button on issue tab:

Actually there is a better fix: Increase the line-height on the button to like 18px or 20px so that the text height does not directly govern the button height and any added SVG will not go beyond the button height either. I will experiment with that.


openssl 1.0.2l (and probably since 1.0.2j) 64 bits version with mingw-w64

You assume in cryptlib.c and mem_dbg.c that a pointer can be casted as unsigned long which is false in 64 bits.so I try to build it with mingw-w64 64 bits version and must modify variables as unsigned long long,I am not sure that it will works well.....(I am trying to build a 64 bits debug version)

problem for openssl 1.0.2j and 1.0.2l....

I think I didn't have this problem for the 64 bits release version....

Please can you provide the build steps you followed including how you run config or Configure. What problems do you see because of this? Can you be specific about what you changed in cryptolib.c and mem_dbg.c?

(under msys2) ./Configure no_shared --prefix=/c/openssld debug
mingw32-make depend
then script because of a bug in make
then ming32-make
change in cryptlib.c l 447 id->val = (unsigned long long)id->ptr; and in  crypto.h l 448 typedef struct crypto_threadid_st {
void *ptr;
unsigned long long val;
} CRYPTO_THREADID;
for memdbg.c not already changed  but error l 326 ret = (unsigned long)a->addr;

change  l322 memdbg.c :static unsigned long long mem_hash(const MEM *a)
{
unsigned long long ret;
ret = (unsigned long long )a->addr;

ret = ret * 17851 + (ret >> 14) * 7 + (ret >> 4) * 251;
return (ret);

}
but l662 problem: BIO_snprintf(bufp, BUF_REMAIN, "number=%d, address=%08llX\n",
m->num, (unsigned long long)m->addr);

I don't know why there is an error l662 I have put: address=%016llX\n" but there is an error on format=

I don't really understand where BIO_snPrintf is defined,because I see the definition in b_print.c(_dopr) in bio but it is not compiled when I compile memdbg.c.so I don't know why I have this error l662 of memdbg.c....Need  I really to do a make depend, before the make ?

For 1.0.2, you must do make depend before building.

thank you richsalz,Ok I have already done it,I think I didn't have all these problems when I compiled the 64 bits release of 1.0.2j last year,so I think there is just problems for the 64 bits debug version

I want to build a 64 bits debug version of openssl because I want to build a 64 bits debug version of Qt.does a release version of openssl work with a debug version of Qt ? Otherwise I could try to use my release version of openssl with a debug version of Qt

./Configure no_shared --prefix=/c/openssld debug

This is wrong. The "debug" on the end here does not mean build OpenSSL in debug mode. It means configure for the "debug" platform. This is a developer platform (which is actually Linux). The target you need to build on mingw64 is....mingw64, i.e.
./Configure no_shared --prefix=/c/openssld mingw64
There is no debug-mingw64 target in 1.0.2.

I want to build a 64 bits debug version of openssl because I want to build a 64 bits debug version of Qt.does a release version of openssl work with a debug version of Qt ?

It should work fine.

OK thanks a lot mattcaswell,so  I have already a build ....my problem is solved


ci: merge staging to master

This is an automatic PR generated by the pipeline CI/CD. This will be automatically fast-forward merged if successful.

Pipeline Attempt on 642050305 for 49976889dbedd4ccb4316fc94e3e7d8f6e68a219
https://gitlab.com/MatrixAI/open-source/js-async-locks/-/pipelines/642050305

Pipeline Succeeded on 642050305 for 49976889dbedd4ccb4316fc94e3e7d8f6e68a219
https://gitlab.com/MatrixAI/open-source/js-async-locks/-/pipelines/642050305


DecoratingLogger throws JSON::GeneratorError on invalid encodings

Description
We log user agents in our Rails requests. Some clients send dubious http headers which might not be a valid string, and if we log those to NewRelic::Agent::Logging::DecoratingLogger, it throws a JSON::GeneratorError:
JSON::GeneratorError
Invalid Unicode [6e 7a 65 6e 64] at 113

activesupport (<IP_ADDRESS>) lib/active_support/core_ext/object/json.rb in to_json at line 43
newrelic_rpm (8.1.0) lib/new_relic/agent/logging.rb in escape at line 91
newrelic_rpm (8.1.0) lib/new_relic/agent/logging.rb in call at line 68
logger.rb in format_message at line 585
newrelic_rpm (8.1.0) lib/new_relic/agent/instrumentation/logger/prepend.rb in block in format_message at line 10
newrelic_rpm (8.1.0) lib/new_relic/agent/instrumentation/logger/instrumentation.rb in format_message_with_tracing at line 36
newrelic_rpm (8.1.0) lib/new_relic/agent/instrumentation/logger/prepend.rb in format_message at line 10
activesupport (<IP_ADDRESS>) lib/active_support/logger_thread_safe_level.rb in add at line 75
activesupport (<IP_ADDRESS>) lib/active_support/logger.rb in block (2 levels) in broadcast at line 26
logger.rb in info at line 528

One example agent is "Mac OS X / Safari 12 [Desktop]: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_5 (Ergänzendes Update)) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.1.1 Safari/605.1.15"
Expected Behavior
The logger should either replace invalid characters with � (as the standard Rails logger does), fail silently, or it might log a line saying something to the effect of "invalid encoding in log message".
Steps to Reproduce
Please be as specific as possible.
Rails.logger.info "Hello \xb3"

Your Environment
Ruby 2.7.4
NewRelic 8.1.0
Rails <IP_ADDRESS>

Thanks for reporting this issue, @jdelStrother! I'm taking a look today and will let you know what I discover.

Hi @jdelStrother  - we have a few possible solutions for this issue. The next step is for our team to determine the most performant option.

@jdelStrother  - The fix for this bug will be included in our next release! Thanks again for reporting the issue.


Promises non handled

I have a javascript code that uses promises (in my specific case a library that parses XML) and runs smoothly when run with quickjs, but when run thrugh javy and then run with wasmtime it does not run. I then tested a small script with just a simple promise that resolves immediatly but the code does not run.
Bottomline: are promises handled ? is there some change I must add to a code with promises to run correctly ?

Hey @captHarlock69 Promises are not handled at the moment. We have plans to support them at some point in the near future.


feat(pointcloud_preprocessing): enable to publish synchronized pointclouds

Description

This PR is part of the multi-lidar occupancy grid map generation.
It enables to pointcloud concatenate node to publish synchronized pointclouds in each sensors.

Related links

Tests performed

Notes for reviewers

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

Different patter is merged of this PR would be merged.


Cauldron backpack causes server to crash when trying to pick up water

At first i thought it might be some incompatibility between mods, but even with only this mod and fabric api in the mods folders of client and server, the server still crashes when trying to pick up water with bare hand and cauldron equipped in backpack slot.
No such issue in singleplayer.
crash-2024-06-25_14.41.47-server.txt

Oops, I was using a client only class on the server and the server couldn't find it. I'll get a fix out later today

Solved in 20.1-2.0.1 ;)


Added danish locale

The failure on Travis is fixed by pull request #32.

Looks good to me, thanks @bofrede! @tigrish Any chance of getting this merged?

I found out how to add a new locale in LocaleApp. @tigrish can you pull it from LocaleApp, please.
The only problem is that I am missing one field in LocaleApp:
da.helpers.page_entries_info.one_page.display_entries.zero: Ingen %{entry_name} fundet


PDE5 should give PDE5A first?

With an input of PDE5 (autocomplete on or off), i might expect to get PDE5A.  PDE5 is an exact synonym of PDE5A (it was the name for a long time).
But the top few hits are things like this:
{
    "curie": "PUBCHEM.COMPOUND:16066664",
    "label": "Pde5-IN-42",
    "synonyms": [
      "Pde5-IN-42",
      "CHEMBL1094365"
    ],

If you tokenize on - then there's an exact match to a token, but that seems not as good as the exact match to a synonym?

Hmm, good catch. I'll try to increase the boost for the synonym exact match and see if I can fix this.


TextInput clear() not working for number_pad keyboard type

Description
TextInput clear() method is not working when keyboard type is set to number_pad in react-native v0.63.4
React Native version:
System:
OS: macOS 10.15.7
CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Memory: 256.52 MB / 16.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 10.14.2 - ~/.nvm/versions/node/v10.14.2/bin/node
Yarn: 1.22.4 - ~/.yarn/bin/yarn
npm: 6.4.1 - ~/.nvm/versions/node/v10.14.2/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.0 - /Users/srdjandjenader/.rvm/gems/ruby-2.7.0/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.3, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
Android SDK: Not Found
IDEs:
Android Studio: 4.0 AI-193.69<IP_ADDRESS>26763
Xcode: 12.3/12C33 - /usr/bin/xcodebuild
Languages:
Java: 12.0.2 - /usr/bin/javac
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.63.4 => 0.63.4
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps To Reproduce
After upgrading to latest version of react-native clear() method is not working any longer when keyboard type is set to number_pad. focus() and blur() work as expected.
When change keyboard type to numeric, clear() works as expected

would be helpful having a reproducible example to quickly troubleshoot the issue.
Also not clear to me if this issue is for Android, iOS or both platform. Thanks

would be helpful having a reproducible example to quickly troubleshoot the issue.
Also not clear to me if this issue is for Android, iOS or both platform. Thanks

Ok, I figured what was this about. Looks like that was not RN, but React issue. Since in the project I have  React 17.0.1 and  currently Expo is with16.x.x I cannot reproduce
It is about class component, and am using ref to call clear() method.
This is not working:

triggerClear = () ={

   this.clearInput()
}

 clearInput = () => {
     this.inputRef.clear()
 }

...

render() {
   return(
        <TextInput
          keyboardType={"numeric"}
          ref={input => {
            this.inputRef = input;
          }}
          onChangeText={(num) => this.changeInputText(num)}
        />
   )
}

When I add early exit and timeout in clearInput() method, everything works fine
  clearInput = () => {
    if (!this.inputRef) return null
    setTimeout(() => {
      this.inputRef.clear()
    })
  }

For some reason, that happened when we upgraded RN and React to latest versions on both platforms.
Worked fine before on IOS and Android.

Ok, I figured what was this about. Looks like that was not RN, but React issue. Since in the project I have  React 17.0.1 and  currently Expo is with16.x.x I cannot reproduce
It is about class component, and am using ref to call clear() method.
This is not working:

triggerClear = () ={

   this.clearInput()
}

 clearInput = () => {
     this.inputRef.clear()
 }

...

render() {
   return(
        <TextInput
          keyboardType={"numeric"}
          ref={input => {
            this.inputRef = input;
          }}
          onChangeText={(num) => this.changeInputText(num)}
        />
   )
}

When I add early exit and timeout in clearInput() method, everything works fine
  clearInput = () => {
    if (!this.inputRef) return null
    setTimeout(() => {
      this.inputRef.clear()
    })
  }

For some reason, that happened when we upgraded RN and React to latest versions on both platforms.
Worked fine before on IOS and Android.


parity with js version

added important changes from new js version to cpp
removed issue with std::move. coords is now just an argument: simpler and safer.
simplified sorting (helped with previous point)
added tests to compare 5000 vertex triangulation with new js version

@morishuz thank you for PR! Unfortunately I have to suggest to close it:

Please note #3 and #6 ; it will change literally all files and complicated conflicts are inevitable. I suggest to continue with improvements after #6 is merged (or on top of #6 )
Please, avoid big multi-feature PR (this one can easily split on 4 PR's)
Before implementing parity with JS version code we need parity with JS version tests

Already fixed by other commits, see https://github.com/delfrrr/delaunator-cpp/issues/2


Bring back #3389 (PageLayout.Pane: Undo deprecation for position prop) + #3545 (Remove warning for the deprecated position prop)

Brings back 2 PRs:

https://github.com/primer/react/pull/3389 by @radglob
https://github.com/primer/react/pull/3545 by @broccolinisoup

Re-opened issue: https://github.com/github/primer/issues/1199
Reverted by https://github.com/primer/react/pull/3589
Missing changeset! Not sure if the previous one would apply, but here it is

Reasons for revert, copied from https://github.com/primer/react/pull/3589:

production (before)
upgrade branch (after)

Sidebar in hyperlist is on the left
Sidebar in hyperlist is on the right

Had to revert https://github.com/primer/react/pull/3389 because of a bug only caught in review-lab (not CI)
Also had to revert https://github.com/primer/react/pull/3545 because that was built on top of 3389
Because github does not allow reverting PRs that have changed content, had to revert the merge commit in cli

We would need to bring this change back in a way that it allows new behaviour without breaking existing behaviour.
Important: It seems like the same pull request number is also merged in next-major? Link to next-major release tracking That seems very fishy? Was this not supposed to be in main at all?

@siddharthkp should we take the implementation changes back (everything on PageLayout.tsx except the deprecation notice) and can tackle how to introduce the actual deprecation in a follow up PR? Reasons for that proposal:

The issue seems to be opened last year, we should stop folks using the position prop at least with the deprecation notice and docs update to prevent further inaccessible usage.
Seems like we will eventually need to fix the usages (re-order the Pane correctly after removing the position prop) at dotcom anyway to keep the UI same. So we can buy sometime by releasing the deprecation notice and see how to introduce the changes to dotcom

Thoughts?? cc @radglob

Oh funny thing is that I just saw that we have a task to re-order the PageLayout.Pane if position is in used in v36 issue https://github.com/github/primer/issues/2516 we can just deprecate and handle it as a v36 follow up?

@siddharthkp should we take the implementation changes back (everything on PageLayout.tsx except the deprecation notice) and can tackle how to introduce the actual deprecation in a follow up PR? Reasons for that proposal:

The issue seems to be opened last year, we should stop folks using the position prop at least with the deprecation notice and docs update to prevent further inaccessible usage.
Seems like we will eventually need to fix the usages (re-order the Pane correctly after removing the position prop) at dotcom anyway to keep the UI same. So we can buy sometime by releasing the deprecation notice and see how to introduce the changes to dotcom

Thoughts?? cc @radglob

Since warnings break in dotcom, we need another way to communicate that these changes need to be made. There's a PR merged into next-major that completely removes support for position. The change that was reverted in this was intended to still respond to the position prop if present. I had tested that in storybook, but I must have missed some detail.

No worries @radglob! We removed the warnings as well because they were breaking as you said (https://github.com/primer/react/pull/3545) but without the warnings, it still breaks dotcom. (Reference is the screenshot in the description and the pane moved to the right side but supposed to be on the left)

There's a PR merged into next-major that completely removes support for position.

This is great!

Since warnings break in dotcom, we need another way to communicate that these changes need to be made.

We have TS @deprecated annotation and this should be a good way to communicate the deprecation.
I feel like there is really not much else to do here. (Unless I am missing something). We can only release the @deprecated annotation in this PR and worry about the rest of the changes in the major release but seems like we already have a branch to merged to next-major to remove the support for position so maybe we are all good?

No worries @radglob! We removed the warnings as well because they were breaking as you said (#3545) but without the warnings, it still breaks dotcom. (Reference is the screenshot in the description and the pane moved to the right side but supposed to be on the left)

There's a PR merged into next-major that completely removes support for position.

This is great!

Since warnings break in dotcom, we need another way to communicate that these changes need to be made.

We have TS @deprecated annotation and this should be a good way to communicate the deprecation.
I feel like there is really not much else to do here. (Unless I am missing something). We can only release the @deprecated annotation in this PR and worry about the rest of the changes in the major release but seems like we already have a branch to merged to next-major to remove the support for position so maybe we are all good?

Yeah, that makes sense to me.

@radglob great! We can merge this once I clear the integration issues due to https://github.com/primer/react/pull/3561

Bump, is this something we want to revive or should we close? @broccolinisoup what do you think?

Thanks @lesliecdubs for the ping! This was supposed to be realised in a minor version until we remove the position prop in v36.
@joshblack Do you think it still worths to release the @deprecated prop in the meantime or if there is a chance/risk that we might not be able to include this change in v36? We can act depend on how the position prop changes are going in v36.

Just had a chat with @joshblack and it is better to close this PR because removing the position prop couldn't make its way to v36 due to roll out complications. We can add a @deprecated notice when we have a roll out strategy for removing the position prop 🔥


Qt program cannot run

Environment
Windows build number: 10.0.21390.0
Your Distribution version: Ubuntu 18.04 (Changed from WSL1)
Your WSLg version: 1.0.22

Steps to reproduce

launch cmake-gui

Expected behavior

popup a window

Actual behavior

aborted

 ✘ nekosu@LAPTOP-ID30VPC5  /mnt/c/Users/liaoh  cmake-gui
qt.qpa.xcb: could not connect to display <IP_ADDRESS>:0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

[1]    161 abort      cmake-gui

The output is almost the same as that when X server is closed

Remarks

The nautilus can open properly

 nekosu@LAPTOP-ID30VPC5  /mnt/c/Users/liaoh  nautilus

(nautilus:133): dbind-WARNING **: 11:28:30.125: Could not open X display

Although it says cannt open, it works fine.

nekosu@LAPTOP-ID30VPC5  /mnt/c/Users/liaoh  echo $DISPLAY
<IP_ADDRESS>:0

cmake version 3.20.3
build from sources, with ./bootstrap --prefix=/opt/cmake --qt-gui
qt: 5.15.0 installed from binary
g++: 7.5.0 from http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu
I'm not sure if message above matters.

The problem is that shell init DISPLAY to <IP_ADDRESS>:0(for old use). After changed to :0, everything works fine. That's all my fault.

The problem is that shell init DISPLAY to <IP_ADDRESS>:0(for old use). After changed to :0, everything works fine. That's all my fault.

This exactly, change your exported DISPLAY to ":0". Check .bashrc and .profile if bash, zsh, fish, do similar.


Remove VALIDHACKS

Symbolic should be able to infer when you don't need it.

Update: it's even worse now, it just doesn't use VALIDHACKS when it should.


Rename piranha-tree-sitter > piranha

Renaming the project from piranha-tree-sitter to piranha

Renaming the project.

This a name change only. LGTM.


include api and bulk import from url

This is awesome application but it lacks API to communicate with 3rd party apps like mobile apps. Do u have plan to include api?
secondly, how is it possible to upload or import images from bulk urls?
Thanks a lot

This issue will be closed because I'm not actively working on Lychee anymore. The repository of Lychee will stay available, but the main development continues under the Lychee Organisation. A fork maintained by the community. Important issues have been migrated. Feel free to re-add your issue(s) when necessary.


Fix StandartizationQueryDate issue

I'm sorry, but I made a mistake assuming StandartizationQueryDate must return date instead of string. Fixed

I know and i've already fixed it


pcm does not report QPI counters on Windows

On Windows, pcm.exe shows in output "Link  is disabled" for all QPI/UPI links on each socket,
and does not report any QPI/UPI statistics.
This is because of these lines in cpucounters.cpp:
// freeze enable
if (4 != qpiLLHandles[i]->write32(LINK_PCI_PMON_BOX_CTL_ADDR, extra))
The problem is in pci.cpp where for Windows, PciHandle::write32 does not return 4 upon success, since DeviceIoControl for IO_CTL_PCICFG_WRITE does not return any data and reslength is 0.
Code should be modified as follows:
BOOL status = DeviceIoControl(hDriver, IO_CTL_PCICFG_WRITE, &req, (DWORD)sizeof(PCICFG_Request), &result, (DWORD)sizeof(uint64), &reslength, NULL);
if (!status)
{
//std::cerr << "Error writing PCI Config space at bus "<<bus<<" dev "<< device<<" function "<< function <<" offset "<< offset << " size "<< req.bytes  << ". Windows error: "<<GetLastError()<<std::endl;
return 0;
}
return (int32)sizeof(uint32);
I tested with this change and was able to get the QPI/UPI statistics.

thanks for reporting. Could you please submit your change a pull request?

Actually it seems you are testing the old version of PCM where this code has been removed. Could you please check the latest from the master branch if it works for you?

I am testing with the 20181204 NDA version of PCM.
I haven't diff'ed the NDA and the public versions of PCM: what are the differences?

the latest PCM version from github master branch already includes all features of your version (incl. Cascade Lake and PMM support).

I tested the latest github version and it does report the QPI/UPI counters on Windows.
Sorry for the disturbance.

thanks for reporting and testing! Your suggestion still makes sense to make it comply with the interface requirements of the write32 method.

the change will be published soon (but it does not impact any functionality)


Refresh Feed + Profile view after successful recovery

Ensures the feed is populated when dismissing recovery mode after a successful recovery. Refreshing the profile is less important, given that the feed is the default tab, but probably still worth refreshing it to be safe.
I found a few other refresh and notification-centric issues too.
Changes

Refresh feed after successful recovery
Refresh profile after successful recovery
Refresh feed based on DetailStack notifications
Rename NotebookAction's for detail stack for consistency (succeedSaveMemo -> succeedSaveEntry)
Extract logic from NotebookModel that should be in DetailStackModel
Refresh Notebook when switching to Notebook Tab

@gordonbrander I've added tests for DetailStack for:

update audience
delete
move
merge


Winter 20 Pre-release - BGE UX - Design of entry form displaying with bad spacing between label and fields.

Multi-picklists and picklists are currently causing layout issues with the entry form on BGE(Winter 20' orgs).
Pre-Conditions: Org should be prerelease with Winter20
Steps to reproduce:
1- Go to Batch Gift Entry and create a batch that includes a picklist field.
2- Verify layout on entry form and separation between the labels and the fields.
Expected Result: Previous to this pre-release all the fields had a short distance between the label and the field, and it was the same for all types (see image 1 attached).
Actual Result: Only picklist fields show the same distance as previous versions between the label and the field itself. All other types currently have a much bigger separation. (see image 2 attached).
Actual:

Expected:

**lurch: attach W-035858

**lurch: attach W-035858

Tracking W-035858

Salesforce has determined that this issue will not be explored further.


qt - fatal bug - all tunnels are sometimes erased

failed testcase (doesn't reproduce the bug):

run for some time
restart via restart button
quit
start

observe 0 tunnels

This may be fixed by https://github.com/PurpleI2P/i2pd-qt/pull/78


Refs #22078 -- Added syndication test for feeds with static methods.

This PR applies the felixxm's comment about add test for feeds with methods decorated by @staticmethod

@mgaligniana Thanks :+1:


Revert "Add Samo Ordinals Collection"

Reverts ordinals-wallet/ordinals-collections#15

@Leovano99 had to revert, invalid inscription ids please open new pr


run with jetson nano

Hi, @saimj7  I want to ask that can we run this program with jetson nano ?

Hi, did not try this on nano but I think you can.


Integrate Sync Stack in Key Vault Administration package via AutoRest Generation

API change check
API changes are not detected in this pull request.

/check-enforcer override

Overriding due to constant issues fetching dependencies for MacOS VMs.


[Bug]: Onboarding text can conceal arrow with some languages

Describe the bug
When viewing new wallet on some languages this text can cover the dotted-line arrow. It would be good to remove the arrow if the text is too wide.
Reproduce

With Russian language on device
Open Bitkit with new wallet
Observe onboarding text

Screenshots / Recording
Russian language on Pixel 3a (Android 14)

Operating system
Android 14
Bitkit version
5dee7d29d2cc891d52d97475de4180e020278a01
Log output
No response

fix: onboarding text layout #1858 closing it

This was raised off the back of https://github.com/synonymdev/bitkit/pull/1858 ;)


moon: 1.19.0 -> 1.19.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/moonrepo/moon/releases.
meta.description for moon is: A task runner and repo management tool for the web ecosystem, written in Rust
meta.homepage for moon is: https://github.com/moonrepo/moon
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.19.3 with grep in /nix/store/cqwf7bmgnc335n4p3dlcszqqnw1fqlvf-moon-1.19.3
found 1.19.3 in filename of file in /nix/store/cqwf7bmgnc335n4p3dlcszqqnw1fqlvf-moon-1.19.3

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
moon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/cqwf7bmgnc335n4p3dlcszqqnw1fqlvf-moon-1.19.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A moon https://github.com/r-ryantm/nixpkgs/archive/c18514d90082921904c7c1bbf652bf4146bcf2c9.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c18514d90082921904c7c1bbf652bf4146bcf2c9#moon

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/cqwf7bmgnc335n4p3dlcszqqnw1fqlvf-moon-1.19.3
ls -la /nix/store/cqwf7bmgnc335n4p3dlcszqqnw1fqlvf-moon-1.19.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

moon

Maintainer pings
cc @flemzord for testing.

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

1 package built:

moon


Don't Merge! PR real time test for target branch full build

Docs Build status updates of commit 06caf92:
:clock10: Full build: the average full build time is 5 min(s) 9 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit 06caf92:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/testing.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.

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


Update Map.tsx

Fixed a minor issue in componentWillUpdate method

Q
A

Bug fix?
[X]

New feature?
NA

New sample?
NA

Related issues?
NA

What's in this Pull Request?
A minor issue in componentWillUpdate method to get the next props rather than the current props.

Thank you @anoopt for the fix!
It will be available in the next release.
In a meanwhile you can test it in beta version

Thank you @AJIXuMuK . I will contribute an updated version (using React functional components) for this control sometime in the future.


Make range inputs stay big while you're dragging them

Even if you move the mouse above or below the input.

So this doesn't actually do anything out of the box, it requires the user to add a custom class accompanies by presumably some javascript. This type of thing is a little outside the scope of this library.

Hey @calebeby What browser?
http://codepen.io/dbox/pen/LkwvkY
It stays large for me when dragging.

I mean if you are dragging and not hovering on the slider.
On Mon, Aug 29, 2016, 7:23 AM Daniel Box<EMAIL_ADDRESS>wrote:

Hey @calebeby https://github.com/calebeby What browser?
http://codepen.io/dbox/pen/LkwvkY
It stays large for me when dragging.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jescalan/axis/pull/306#issuecomment-243138705, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMmFoZn4F9w-S19ZvVLE15YEtyVomyxuks5qkutJgaJpZM4Ju2Gb
.

Ah, gotcha. Maybe just switch to :active from .active.

Yeah, that's what I meant. I can fix it later today.
On Mon, Aug 29, 2016, 7:32 AM Daniel Box<EMAIL_ADDRESS>wrote:

Ah, gotcha. Maybe just switch to :active from .active.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jescalan/axis/pull/306#issuecomment-243141678, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMmFoddvIRi46SzS5ZUxD23htK-Utjfxks5qku2BgaJpZM4Ju2Gb
.

Ok, changed .active to :active, but I can't understand why travis failed

You'll need to update the tests as well

How do I do that?

What does the test do?

@calebeby The tests verify that the code is putting out what we expect it to. its purpose is to make sure that no change can be made that has consequences we didn't know about. You can update the tests in the test folder. Here is the file used to verify how the range input mixin generates code. You can update this to reflect the change and then it should work!
Run the tests locally using npm test. Also, all of this is in the contributing guide that appears whenever you create an issue or PR 😁

Closing du to inactivity, and because we're moving axis over to a completely new version


Write proposal for NASA ROSES call E7

https://nspires.nasaprs.com/external/solicitations/summary.do?solId={958CF134-D655-E512-B5AD-84501D14A0C1}&path=&method=init
No due date yet

Closed in favor of using #161 .


Encountering PDF Error when Export to PDF

Hello,
After exporting to PDF in StackEdit, I'm encountering the following exception message:
This page contains the following errors:
error on line 1 at column 1: Document is empty
error on line 1 at column 1: Encoding error
Below is a rendering of the page up to the first error.
I tried to reduce the file that I was exporting to just a few lines of text with Markdown code. Same result, I encountered the exception message stated above.
I purchased a sponsorship so that I could take advantage of the Export to PDF option.
Any suggestions would be most appreciated.
Kind regards,
Tony Ventura
www.tonyventura.com

Please provide a markdown sample to reproduce the issue.

Not reproduced.


Add one environment total three added

When I add environment jdk1.7.0_79, total 3 versions are displayed:

1.7
<IP_ADDRESS>
oracle64-<IP_ADDRESS>

Is it the right result? If not, how can I remove the others?
Thanks

This result is correct, i'm not the developer of jenv, however i think this was done for simplicity, since java developers usually have one version of each major version there is, so you might want to swap to java 1.7 and you'll know which version that is, so you don't want to type out <IP_ADDRESS> or oracle64-<IP_ADDRESS>, however if you do have more then one version of the major versions say <IP_ADDRESS>, you will probably want to switch between the two, therefore you'll want to type <IP_ADDRESS> and the oracle64-X is if you also have openjdk.

Get it. Thank you very much.

I confirm that is the awaited result.


Project maintenance

Added some basic structure to the project: dependencies and project setup in Julia

Probably a README file here would also be quite handy...


Build failure: keycloak

Steps To Reproduce
Steps to reproduce the behavior:

build keycloak 24.0.4

Build log
@nix { "action": "setPhase", "phase": "unpackPhase" }
Running phase: unpackPhase
unpacking source archive /nix/store/nfnd31qz0qcmkzd5vfrhkkprwj19r8hc-source
source root is source
unpackPhase completed in 1 minutes 36 seconds
@nix { "action": "setPhase", "phase": "patchPhase" }
Running phase: patchPhase
applying patch /nix/store/zl685r71wzm7l0apbdbnk03y92zj5qwh-config_vars.patch
patching file bin/kc.sh
Hunk #1 succeeded at 34 with fuzz 2 (offset 2 lines).
@nix { "action": "setPhase", "phase": "updateAutotoolsGnuConfigScriptsPhase" }
Running phase: updateAutotoolsGnuConfigScriptsPhase
@nix { "action": "setPhase", "phase": "configurePhase" }
Running phase: configurePhase
no configure script, doing nothing
@nix { "action": "setPhase", "phase": "buildPhase" }
Running phase: buildPhase
patching script interpreter paths in bin/kc.sh
bin/kc.sh: interpreter directive changed from "#!/bin/sh" to "/nix/store/306znyj77fv49kwnkpxmb0j2znqpa8bj-bash-5.2p26/bin/sh"
Updating the configuration and installing your custom providers, if any. Please wait.
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fffdc30a583 (sent by kill), pid=48, tid=121
#
# JRE version: OpenJDK Runtime Environment (21.0+35) (build 21+35-nixos)
# Java VM: OpenJDK 64-Bit Server VM (21+35-nixos, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, parallel gc, linux-amd64)
# Problematic frame:
# J 765 c2 java.util.HashMap.resize()[Ljava/util/HashMap$Node; java.base@21 (356 bytes) @ 0x00007fffdc30a583 [0x00007fffdc30a360+0x0000000000000223]
#
# Core dump will be written. Default location: Core dumps may be processed with "/nix/store/ky1hi6jw9nx3a7d7s1842dv5662w1lp3-systemd/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /build/source/core.48)
#
# An error report file with more information is saved as:
# /build/source/hs_err_pid48.log
[57.475s][warning][os] Loading hsdis library failed
#
# If you would like to submit a bug report, please visit:
#   https://bugreport.java.com/bugreport/crash.jsp
#
/nix/store/xfhkjnpqjwlf6hlk1ysmq3aaq80f3bjj-stdenv-linux/setup: line 1594:    48 Aborted                 (core dumped) bin/kc.sh build

Additional context
System is currently running NixOS 23.11. The issue occurs when trying to upgrade to NixOS 24.05.
Notify maintainers
@ngerstle @talyz @nickcao
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.90, NixOS, 23.11 (Tapir), 23.11.20240509.9a9960b`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - nixpkgs: `/tmp/nixPath`

Add a :+1: reaction to issues you find important.

Does the update to 24.0.5 on master fix your issue?

I'm trying to understand what's going on, but it doesn't really make sense to me. I don't think 24.0.05 changes the situation.
When I build keycloak through my NixOS configuration on a different machine, it copies keycloak cache.nixos.org, but when I try to build on this machine, it builds keycloak from source and fails.
Running nix-shell -p keycloak -I nixpkgs=https://github.com/NixOS/nixpkgs/archive/nixos-24.05.tar.gz or nix-shell -p keycloak -I nixpkgs=https://github.com/NixOS/nixpkgs/archive/master.tar.gz works on both machines, as it will copy from the cache.
When I run nix-shell -p keycloak -I nixpkgs=https://github.com/NixOS/nixpkgs/archive/nixos-24.05.tar.gz --check on my other machine, I notice that the following:
checking outputs of '/nix/store/ca85xq2gi23xma760lr0c95k38rc1zxs-keycloak-24.0.4.drv'...
Running phase: unpackPhase
unpacking source archive /nix/store/nfnd31qz0qcmkzd5vfrhkkprwj19r8hc-source
source root is source
Running phase: patchPhase
applying patch /nix/store/zl685r71wzm7l0apbdbnk03y92zj5qwh-config_vars.patch
patching file bin/kc.sh
Hunk #1 succeeded at 34 with fuzz 2 (offset 2 lines).
Running phase: updateAutotoolsGnuConfigScriptsPhase
Running phase: configurePhase
no configure script, doing nothing
Running phase: buildPhase
patching script interpreter paths in bin/kc.sh
bin/kc.sh: interpreter directive changed from "#!/bin/sh" to "/nix/store/306znyj77fv49kwnkpxmb0j2znqpa8bj-bash-5.2p26/bin/sh"
Updating the configuration and installing your custom providers, if any. Please wait.
2024-06-06 07:06:10,925 WARN  [io.qua.dep.ind.IndexWrapper] (build-30) Failed to index org.apache.tools.ant.Task: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: PROD for keycloak@22d6f11
2024-06-06 07:06:10,938 WARN  [io.qua.dep.ind.IndexWrapper] (build-30) Failed to index org.springframework.core.io.DefaultResourceLoader: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: PROD for keycloak@22d6f11
2024-06-06 07:06:10,938 WARN  [io.qua.dep.ind.IndexWrapper] (build-30) Failed to index org.springframework.core.io.ResourceLoader: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: PROD for keycloak@22d6f11
2024-06-06 07:06:10,939 WARN  [io.qua.dep.ind.IndexWrapper] (build-30) Failed to index org.springframework.core.io.Resource: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: PROD for keycloak@22d6f11
2024-06-06 07:06:10,963 WARN  [io.qua.dep.ind.IndexWrapper] (build-30) Failed to index io.mashona.logwriting.ArrayStore: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: PROD for keycloak@22d6f11
2024-06-06 07:06:10,964 WARN  [io.qua.dep.ind.IndexWrapper] (build-30) Failed to index org.apache.activemq.artemis.core.journal.RecordInfo: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: PROD for keycloak@22d6f11
2024-06-06 07:06:10,964 WARN  [io.qua.dep.ind.IndexWrapper] (build-30) Failed to index org.apache.activemq.artemis.core.journal.Journal: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: PROD for keycloak@22d6f11
2024-06-06 07:06:10,968 WARN  [io.qua.dep.ind.IndexWrapper] (build-30) Failed to index jakarta.jms.XAConnection: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: PROD for keycloak@22d6f11
2024-06-06 07:06:10,968 WARN  [io.qua.dep.ind.IndexWrapper] (build-30) Failed to index jakarta.jms.XASession: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: PROD for keycloak@22d6f11
2024-06-06 07:06:10,969 WARN  [io.qua.dep.ind.IndexWrapper] (build-30) Failed to index jakarta.jms.XAConnectionFactory: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: PROD for keycloak@22d6f11
2024-06-06 07:06:10,982 WARN  [io.qua.dep.ind.IndexWrapper] (build-30) Failed to index jakarta.jms.Connection: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: PROD for keycloak@22d6f11
2024-06-06 07:06:12,660 INFO  [io.qua.dep.QuarkusAugmentor] (main) Quarkus augmentation completed in 3761ms
Server configuration updated and persisted. Run the following command to review the configuration:

        kc.sh show-config

Running phase: installPhase
Running phase: fixupPhase
shrinking RPATHs of ELF executables and libraries in /nix/store/v5kacj33gix24acf1lx2yn4k0asbif1b-keycloak-24.0.4
checking for references to /build/ in /nix/store/v5kacj33gix24acf1lx2yn4k0asbif1b-keycloak-24.0.4...
patching script interpreter paths in /nix/store/v5kacj33gix24acf1lx2yn4k0asbif1b-keycloak-24.0.4
/nix/store/v5kacj33gix24acf1lx2yn4k0asbif1b-keycloak-24.0.4/bin/federation-sssd-setup.sh: interpreter directive changed from "#!/bin/sh" to "/nix/store/306znyj77fv49kwnkpxmb0j2znqpa8bj-bash-5.2p26/bin/sh"
/nix/store/v5kacj33gix24acf1lx2yn4k0asbif1b-keycloak-24.0.4/bin/kc.sh.orig: interpreter directive changed from "#!/bin/sh" to "/nix/store/306znyj77fv49kwnkpxmb0j2znqpa8bj-bash-5.2p26/bin/sh"
/nix/store/v5kacj33gix24acf1lx2yn4k0asbif1b-keycloak-24.0.4/bin/kcadm.sh: interpreter directive changed from "#!/bin/sh" to "/nix/store/306znyj77fv49kwnkpxmb0j2znqpa8bj-bash-5.2p26/bin/sh"
/nix/store/v5kacj33gix24acf1lx2yn4k0asbif1b-keycloak-24.0.4/bin/kcreg.sh: interpreter directive changed from "#!/bin/sh" to "/nix/store/306znyj77fv49kwnkpxmb0j2znqpa8bj-bash-5.2p26/bin/sh"
stripping (with command strip and flags -S -p) in  /nix/store/v5kacj33gix24acf1lx2yn4k0asbif1b-keycloak-24.0.4/lib /nix/store/v5kacj33gix24acf1lx2yn4k0asbif1b-keycloak-24.0.4/bin
error: derivation '/nix/store/ca85xq2gi23xma760lr0c95k38rc1zxs-keycloak-24.0.4.drv' may not be deterministic: output '/nix/store/v5kacj33gix24acf1lx2yn4k0asbif1b-keycloak-24.0.4' differs

Although building from source does succeed on this other machine, the build does not appear to be reproducible.
Running the same command on the machine mentioned in this issue gives me the following:
checking outputs of '/nix/store/ca85xq2gi23xma760lr0c95k38rc1zxs-keycloak-24.0.4.drv'...
Running phase: unpackPhase
unpacking source archive /nix/store/nfnd31qz0qcmkzd5vfrhkkprwj19r8hc-source
source root is source
Running phase: patchPhase
applying patch /nix/store/zl685r71wzm7l0apbdbnk03y92zj5qwh-config_vars.patch
patching file bin/kc.sh
Hunk #1 succeeded at 34 with fuzz 2 (offset 2 lines).
Running phase: updateAutotoolsGnuConfigScriptsPhase
Running phase: configurePhase
no configure script, doing nothing
Running phase: buildPhase
patching script interpreter paths in bin/kc.sh
bin/kc.sh: interpreter directive changed from "#!/bin/sh" to "/nix/store/306znyj77fv49kwnkpxmb0j2znqpa8bj-bash-5.2p26/bin/sh"
Updating the configuration and installing your custom providers, if any. Please wait.
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fffdc38ed7c (sent by kill), pid=45, tid=142
#
# JRE version: OpenJDK Runtime Environment (21.0+35) (build 21+35-nixos)
# Java VM: OpenJDK 64-Bit Server VM (21+35-nixos, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, parallel gc, linux-amd64)
# Problematic frame:
# J 2379 c2 java.util.zip.ZipFile.getEntry(Ljava/lang/String;)Ljava/util/zip/ZipEntry; java.base@21 (59 bytes) @ 0x00007fffdc38ed7c [0x00007fffdc38eac0+0x00000000000002bc]
#
# Core dump will be written. Default location: Core dumps may be processed with "/nix/store/ky1hi6jw9nx3a7d7s1842dv5662w1lp3-systemd/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /build/source/core.45)
#
# An error report file with more information is saved as:
# /build/source/hs_err_pid45.log
[15.221s][warning][os] Loading hsdis library failed
#
# If you would like to submit a bug report, please visit:
#   https://bugreport.java.com/bugreport/crash.jsp
#
/nix/store/xfhkjnpqjwlf6hlk1ysmq3aaq80f3bjj-stdenv-linux/setup: line 1592:    45 Aborted                 (core dumped) bin/kc.sh build
error: boost::bad_format_string: format-string is ill-formed

The same happens when building 24.0.5 from the master branch.

I don't think this can be fixed on our side, but some openjdk internal issue that only manifests on specific hardware.

I see, that's unfortunate. I will have to submit a bug report to openjdk, but it might be difficult for them to fix this given that it's a hardware-specific issue, and my hardware is very old (AMD Turion II Neo N54L).

There is a potential workaround you can try: https://access.redhat.com/solutions/65104
That is setting -Dsun.zip.disableMemoryMapping=true

Thanks! I'll try that!

Also try building KeyCloak 25.0.1 which is already packaged on master
nix build -L github:NixOS/nixpkgs/master#keycloak

A few days after posting this issue, the build of keycloak succeeded and my system was upgraded, apologies for not mentioning this earlier. I have not yet figured out if this is because I added the setting @NickCao mentioned, or if something else fixed it. I will try building keycloak 25.0.1 as soon as I can.

@Danacus said they got past this, so closing this issue.


Latest build doesnt load

• ImprovedCameraSE version 1 (ImprovedCameraSE.dll, Improved Camera SE) disabled, fatal error occurred while loading plugin.

I cannot reproduce this on my machine. Maybe try downloading our mod again and reinstalling it?

Still the same, maybe  the update is now using an address another dll already reserved?

Shouldn't be the case, a popup would appear showing the address that is being used.

ok nvm i had ini from previous version that was the issue


[Bug]: crash in previews

Checklist

[X] This is not a bug caused by platform.
[X] Reviewed the README and documentation.
[X] Checked existing issues & PRs to ensure not duplicated.

What happened?
Preview crashes when calling StoreContext.getStore. It seems that the AtomRoot is not configured in the preview, although I am calling it as documented:
#Preview("PreviewTest"){
   AtomRoot {
      PreviewTest()
    }
}

Expected Behavior
Atoms should be usable in previews
Reproduction Steps

Reference any Atom in a preview

Swift Version
5.9.2
Library Version
0.4.2
Platform
iOS
Scrrenshot/Video/Gif
Snippet of diagnostic report:

This is shown if @ViewContext or @Watch is used. If the context is read directly in the view, the full assertion is shown.

@joprice
I've tried to replace this part of the example app with one using #Preview macro and it worked fine.
Please double check if there are any problems with your environment, Xcode version, simulator, PreviewTest view implementation, etc.


Reduce calls to clean path

Cleaning a path is expensive operation and needs to be performed only once on the initial string, instead of every time getParent is called.

alluxio-bot, merge this please


Allow specifying names for policies created by the module

Hi,
Thank you for this very useful module!
In the company I work for we have naming conventions for all resources created including policies.
It would be really great to have the possibility to allow passing names or a even an optional prefix and suffix for the Policy name instead of using the lambda name for it.
Thanks!
Simon

Found this is a duplicate of #61 , just another use case


 Searches that now go to Scryfall also count here.
(2) The speed of lint is also relevant.

I think my first step here rather than radical refactoring is just to mark tests that very clearly go off to the internet to do their thing and takes ages as "functional" tests and skip them when running make test. But still have jenkins run them and have some way to run them locally if so desired.

12d6317.


[BUG] Weird characters appears in attach buffers.

NeoVim Version
Output of nvim --version
NVIM v0.10.0-dev-3133+g3688735c2-Homebrew
Describe the bug
A clear and concise description of what the bug is.
Weird duplicated characters appear after attaching to the test. Everything works okay until I exit attach window and attach again. Then there will be as many duplicated characters as many I repeat this operation. I was able to find the commit that introduced this regression, this one =>  https://github.com/nvim-neotest/neotest/commit/972a7dc9dfe860649edaf89e08c514a98d3a2a09.
https://github.com/nvim-neotest/neotest/assets/45797239/a81914e8-09a0-4612-b243-f5dcd860a116
I don't think it's test/setup specific as it was working for me just fine before this commit. That being said If you need a more detailed setup just let me know.

Just dropping by to add that if you do that again, your input will be tripled (and quadrupled and so forth)

This should be fixed in latest master :smile:


Json module

I created module for matching json data. It exports function "has_key(str)" and string dictionary "keys". So for json {"hello": "world"} you can just write rule:
import "json"
rule test {
conditon:
json.has_key("hello") and json.keys["hello"] == "world"
}

Pardon me my question, but I wonder, what is the use case for this?

We are using yara not only to search in executables, but also in malware configs obtained from honeypots and in feed of newly registered certificates. These are all json formatted data so I assumed that maybe this module could also help others.

Would you consider adding some json list operations?    like "len" for lengths of json lists and "contains"  for whether a certain string is a json list?

This module looks interesting, but I've finally decided not to merge it.


fix bug to return star list grouped by subcategories

Added "order_by" to subcategories on the endpoint view.

You should use         employee_stars = Star.objects.filter(to_user=employee).values('subcategory__pk', 'subcategory__name').annotate(num_stars=Count('subcategory')).order_by('-num_stars')


Dispose everything

I want to dispose of everything in order to have the best performance, this still needs to be worked on.

Define "everything". Disposing only frees memory resources, it has no effect on performance.

edited


Fix/refactor admin posts

This PR refactors the _post partial by moving to two partials one for admin and one for front-end.  This removed a lot of icky spagetti switching code and made it easier to resolve some issues related to trying to share one partial between two concerns.
I also merged in the integration testing branch and extended it, so thats included in this PR as well.
This PR fixes #73, #42 and #20

@olliebennett can you do a quick review before I pull this?

Nice one :) This looks good - glad to see some integration tests too!


list available service kinds

Hi, there's a missing functionality for listing available cognitive kinds... how do we know which kind is available and on which region it's available?

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

ID: f60024e5-9f73-a991-c699-b334287845d2
Version Independent ID: 452c87e7-a404-0f3c-8520-c13ef8c789c4
Content
Content Source

For example az cognitiveservices list --kind or something like that. We as your customer want's to know how to use the CLI API ;-)

Any updates on this?

@yangyuan

I am working on it, targeting Sprint 45.
Will have a command like az cognitiveservices account list-kinds which returns a list of valid kinds

Thank you so much for the update @yangyuan!
I appreciate it!


add "id" as an optional value of the serializer fields returning the haystack internal id

This allows to get the full id of a content, for example:
[
    {
        "id": "organization_projects.project.2",
        "category": "Software",
        "languages": "Python",
        "premium": true
    }
]

Welcome, thanks for the PR and this great module!

Thank you very much @decibyte ❤


[Feature] Add support in navigateTo function for generic protocols

Summary
A user would like to navigate to a locally available page on obsidian. Since our navigateTo function does not recognize such protocols, the navigation forcefully prepends https to the URL. We should allow a more generous validation for URLs.
 Front conversations

I have another use-case, and several new protocols that I would like to add to this request.
FileMaker Pro previously used fmp:// for all files, but recently added the version number. So now there is fmp18://, fmp19://, etc. They also use fmnet:// for connecting to hosted files.
https://www.seedcode.com/filemaker-18-fmp-urls/
Perhaps the app definition could store a list of allowed protocols to treat as clickable links. This would be similar to the list of allowed file extensions for the File-Picker widget, but at the app level for protocols.
I've noticed standard https:// urls are automatically converted to clickable links in some places. If this functionality could be combined with a list of allowed protocols, it would greatly increase compatibility for integrating with other platforms. This would allow us to call up other apps and pass parameters to any new app/protocol, even local ones we create.

I also have use cases that rely on custom protocols, the prepending of https and/or stripping of the semicolon makes that impossible.

A user on Discord requested support for sms:// https://discord.com/channels/725602949748752515/1048442331130494986/1048442331130494986
We should add support for app URI schemes so that navigation works as expected on phones.

@satbir121 @bharath31 , we're seeing a lot more requests for other protocols lately in Discord. And it's leading to a lot of support threads, troubleshooting why these protocols are not working.
https://discord.com/channels/725602949748752515/1060004966837788784
It's mostly for tel:// and sms:// at this point, but it would be great if we could solve for this in a way that enables generic protocols as well.
Maybe we can have a few protocols that are allowed by default, then an option to enable all, or specify your own-- similar to the allowed file types dropdown in the FilePicker widget.

@GreenFlux thanks for flagging! I'm bumping the priority up.


undefined method `[]' for nil:NilClass if page is missing

Using the example form the docs trying to read all content types,
site_client.contents.messages.all({})

will raise an exception:
NoMethodError: undefined method `[]' for nil:NilClass
	content_entries.rb:23:in `index'

the issue appears when trying to access options which is defaulted with nil hence options[:page] will crash.
        PaginatedResources.new(list,
          options[:page] || 1,
          response.headers[:x_total_pages].to_i,
          response.headers[:x_total_entries].to_i)

PR following soon.

nevermind, seems to be fixed in master :)
def index(query = nil, options = {}, locale = nil)


Random question

Story
As a poll operator, I want to ask a question whose all answers  will be shuffled in random order each time someone opens the quiz.
As a poll applicant, I want to answer a question on my whatsapp account whose options don't show up the same every time I open the poll.
Question notice
The poll operator should be able to select whether or not responses should be shuffled
Kind of responses
The order of responses is not the same for different poll applicants or for the same poll applicant each time he connects. If the poll operator has selected the "shuffle answers options" we must have:

Poll applicant 1
Use case
Q: What is the colour of the sky ?

blue

red
white
black

Poll applicant 2
Q: What is the colour of the sky ?

red

white
blue
black

Poll applicant 1 for his second connection
Q: What is the colour of the sky ?

black

white
blue
red


Bundle exec is 2x slower than using binstubs

Running bundle exec rake --version is almost two times slower than running bin/rake --version. I tested this on both 1.0.21 and 1.1.rc. The RC results are also two times slower than the latest stable release results.
$ bundle -v
Bundler version 1.0.21
$ bundle > /dev/null; time bundle exec rake --version; time bin/rake --version
rake, version 0.9.2
bundle exec rake --version  3,87s user 0,50s system 98% cpu 4,436 total
rake, version 0.9.2
bin/rake --version  1,95s user 0,27s system 99% cpu 2,240 total

$ bundle -v
Bundler version 1.1.rc
$ bundle > /dev/null; time bundle exec rake --version; time bin/rake --version
rake, version 0.9.2
bundle exec rake --version  8,33s user 0,52s system 99% cpu 8,925 total
rake, version 0.9.2
bin/rake --version  4,19s user 0,28s system 96% cpu 4,622 total

What is causing this?

The same ratio on the Ruby 1.9.3-p0, but 2 times faster overall.
$ time bundle exec rake --version; time bin/rake --version
rake, version 0.9.2
bundle exec rake --version  1,69s user 0,19s system 86% cpu 2,173 total
rake, version 0.9.2
bin/rake --version  0,86s user 0,13s system 95% cpu 1,038 total

Santiago wrote a performance fix for bundle exec here: 2c838255ccadadeab5298b7c2bbc39035e59f248. That change has been released as part of 1.1 rc6, so if you could test and report back, that would be great. Thanks!

A performance regression seems to be fixed, but the difference between bundle exec and binstub remains about the same:
% bundle --version; time bundle exec rake --version; time bin/rake --version
Bundler version 1.1.rc.7
rake, version <IP_ADDRESS>
bundle exec rake --version  2,38s user 0,26s system 82% cpu 3,204 total
rake, version <IP_ADDRESS>
bin/rake --version  1,28s user 0,16s system 85% cpu 1,688 total

That's correct. Are you claiming that the difference is a regression from 1.0?
On Jan 12, 2012, at 2:33 PM, Semyon<EMAIL_ADDRESS>wrote:

A performance regression seems to be fixed, but the difference between bundle exec and binstub remains about the same:
% bundle --version; time bundle exec rake --version; time bin/rake --version
Bundler version 1.1.rc.7
rake, version <IP_ADDRESS>
bundle exec rake --version  2,38s user 0,26s system 82% cpu 3,204 total
rake, version <IP_ADDRESS>
bin/rake --version  1,28s user 0,16s system 85% cpu 1,688 total

Reply to this email directly or view it on GitHub:
https://github.com/carlhuda/bundler/issues/1508#issuecomment-3471814


Changes to support vulcan-material-ui

Pass all properties of fieldSchema.form on to the form component
Restore missing delete link

Awesome as always!


Uninstall-AzureRm should be Uninstall-Module AzureRm

Uninstall-AzureRm should be Uninstall-Module AzureRm
Thanks

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

ID: 71d1aafa-f084-6e0b-d743-7eb3aba81014
Version Independent ID: b3ce94fa-6e76-4ffe-e70e-07f7a321fcd4
Content: Uninstall Azure PowerShell
Content Source: docs-conceptual/azps-5.5.0/uninstall-az-ps.md
Service: azure-powershell
GitHub Login: @mikefrobbins
Microsoft Alias: mirobb

Sorry, this is correct but Uninstall-AzureRm didn't work for me

@BeMor81 Thanks for reaching out.
Just to clarify, the Uninstall-Module cmdlet only uninstalls one module at a time. To remove the AzureRm PowerShell module completely, you must uninstall each module individually. Whereas, the Uninstall-AzureRm cmdlet removes all AzureRm modules from a machine.

Sorry, this is correct but Uninstall-AzureRm didn't work for me

Could you please elaborate and let us know the exact error you ran into?
As mentioned in the document in question, if you have the Az module installed on your system and would like to uninstall AzureRM, there are two options. Which method you follow depends on how you installed the AzureRM module.
If you installed AzureRM with PowerShellGet, then you can remove the modules with the Uninstall-AzureRM cmdlet, available as part of the Az.Accounts module. If you're not sure of your original installation method, follow the MSI steps for uninstalling first.


atom_apm resource don't install packages

Hi,
I am using:
default['atom']['packages'] = %w(language-chef linter-chefstyle)
node['atom']['packages'].each do |pkg|
atom_apm "#{pkg}"
end
and the result is this:

atom_apm[language-chef] action install (up to date)
atom_apm[linter-chefstyle] action install (up to date)

But, it seems the packages are not installed at all.

Windows 7 SP1 with latest updates
chefdk 2.0.28
PowerShell 5.1
Microsoft Visual C++ 2010 x64 and x86

I'll see if this is fixed by the custom resource rewrite.

Windows 7 is no longer supported.
The new resource works in windows 2016.
Tested in version 0.3.00.


Fix assembly version attributes for C#

Fixes #6201 (thanks for reporting it!).

@jskeet, can you please review this small change?

LGTM. Will there be other PRs for other assemblies, or do they determine their versions from Grpc.Core?

Thanks for reviewing.
The Version.cs file is link-included by all other projects and grabs the data from VersionInfo.cs file, so no other changes are needed.

grpc-mac-node3 is failure is not related.


Download files via URL

Ability to download images via URL.

Use case?

Saveing images from imgur/discord/giphy into albums

Which you can easily achieve faster if you Right click -> lolisafe -> upload when you have the extension installed. I don't really see the point of this.

 Still seems kind of inconvenient to copy url, open lolisafe, paste and upload. Would be way better to see a small app that lets you Share to it and then it handles uploading directly to your lolisafe. If I find a nice way to add it to the current layout I'll work on it. I'll leave it open for now.


Problems with USGS WESM and TESM tile index files

As of May 2023, the issues with the index files seem to be resolved. I have not done extensive testing, but things seem to work OK.
The USGS TESM tile index has problems with some lidar projects. The problems are related to missing or bad geometries for some tiles and involves ~20 lidar projects (haven't really checked non-lidar projects). The queryUSGSTileIndex() function works correctly when the project being queried has good tiles but it may fail when there are missing or bad tile geometries within the project. USGS is aware of these problems but has been slow to correct them.
In addition, the TESM tile index does not include sufficient information to fully locate the tile (LAS/LAZ file) on the rockyweb server. The tile_id field in the TESM index is just a tile identifier and does not (usually) fully identify the file on the server. The logic used to create the actual file names seems to vary depending on the lidar project. For recent projects, the actual file names appear to be constructed using the project name and the year the point data were published. Older projects do not include information for the publication year in the file names.
While the WESM index contains a lpc_link field that is presumably the URL for the point files associated with a project, the URL is incomplete and does not include the actual folder containing the point files. Usually, the point files are in a folder named "laz" or "LAZ" but some projects have point files in a folder named "LAS". The lpc_link URLs are often missing the trailing "/" so code that uses them needs to check for the trailing "/" and add it if missing.
Example
The data for Glacier Peak in Washington state is identified in WESM by:

workunit = "WA_GlacierPeak_2014"
workunit = 18330
project = "Glacier_Peak_WA_QL1_LiDAR"
project_id = 18332
lpc_pub_date = "2016-08-08"
lpc_link = "https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_WA_GlacierPeak_2014_LAS_2016/"

Data for this area were collected in 2014-2015 and published in 2016. The point data files area actually located in "https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_WA_GlacierPeak_2014_LAS_2016/laz/" and individual files names look like this: "USGS_LPC_WA_GlacierPeak_2014_10TFU1514_LAS_2016.laz "
The record in the TESM tile index for the same tile contains the following:

tile_id = "10TFU1514"
project = "Glacier_Peak_WA_QL1_LiDAR"
project_id = 18332
workunit_id = 18330

For this project and tile, we can construct a URL as follows (R syntax using lubridate package for year() function):
URL <- paste0(WESM$lpc_link, "laz/", "USGS_LPC_", WESM$workunit, "_", TESM$tile_id, "LAS", year(WESM$lpc_pub_date), ".laz")
For projects where the lpc_pub_date is missing of set to NA, the URL may be as follows (but not tested for all projects):
URL <- paste0(WESM$lpc_link, "laz/", "USGS_LPC_", WESM$workunit, "_", TESM$tile_id, ".laz")

USGS seems to have cleaned up problems with the TESM index as of mid-2023 (probably earlier). I haven't done any testing recently but have used the index to query for data for several areas without problems. Previously, things would fail if an area was covered by any lidar projects where the tile information was bad. Not seeing this happen now.

Closing this for now. May reopen after more testing of if I run into problems with the index files.


Unknown option: base.cacheDirectory

I was trying the new 3.2.6-alpha.0 release but it has an error when used with storyshots because of https://github.com/storybooks/storybook/blame/master/app/react/src/server/config/babel.js#L6 which was recently added.
We must omit that in https://github.com/storybooks/storybook/blob/master/addons/storyshots/src/index.js#L41 and probably other places.
//cc @ndelangen

How do I test this?

Can you help me determine if this change fixes the problem?

Yep I will test it right now.

@ndelangen is does work, but shouldn't you apply the same fix to the react app?

Thanks for validating!

@ndelangen is does work, but shouldn't you apply the same fix to the react app?
It was already there..

@ndelangen Could we have a patch release with the fix? I'm kind of blocked because I need the newest version because of https://github.com/storybooks/storybook/pull/1554 available in 3.2.6 but at the same time I can't use it because of this bug.

@satazor https://github.com/storybooks/storybook/releases/tag/v3.2.7 👍


Types for getPeople().set() missing option for multiple props

It looks like getPeople().set() allows you to pass in an object of multiple props and values:
https://github.com/mixpanel/mixpanel-react-native/blob/4b3836366ff402b5b1c2ae352c8d29966330de5f/__tests__/index.test.js#L168-L172
but the types only reflect the single prop API:
https://github.com/mixpanel/mixpanel-react-native/blob/4b3836366ff402b5b1c2ae352c8d29966330de5f/index.d.ts#L38

@jpalmieri This issue should be fixed in v1.3.8, please feel free to re-open if any issue persists.


[DUOS-376][risk=no] User -> AuthUser

Addresses
Partially addresses https://broadinstitute.atlassian.net/browse/DUOS-376
Changes
Isolated class rename so that we can rename DACUser -> User in future multi-DAC work.

Coverage remained the same at 62.263% when pulling bbca47bc33d2a048ff9e640b788373688fd838f4 on DUOS-376 into c668eb2de42cbf0ced0b1e61d2970bfc5e17d05e on develop.

Thank you @MatthewBemis !

Thanks all!


Consider redirectTo timing option?

I just struggled with doing a redirect after login, and finally realized I couldn't rely on a state's resolves to be satisfied before a redirectTo hook was triggered. I also played with using a promise in the redirectTo hook, but this got really messy (and didn't work).
I ended up having to use a variation on the "returnTo" resolve pattern from the sample app, but even there, i needed to use a promise with an interval calling a recursive function, waiting for a value from one of the state's other resolves to return (basically, the data for my entire application, which contains the instructions for routing, which are persisted in the db).
It seems to me that a state's redirectTo should be able to be conditioned to run (or complete) only when all of the current state's resolves have been satisfied. If there's a way to do this already that I'm missing, please give an example. I'm not sure whether there's a way in a redirectTo of using the injected transition to get a hold of the condition of the state's resolves.
Thanks for any feedback, and please close if there is a way of doing this that I'm missing.

you might find the injector() on the transition useful.
resolve: {
  something: () => getSomethingPromise(),
  somethingElse: (something) => getSomethingElsePromise(),
  somethingElseElse: (somethingElse) => somethingElseElsePromise(),
},
redirectTo: trans =>
    trans.injector().getAsync('somethingElseElse').then(result => return getRedirect(result));

Aha, wish I'd asked this earlier. I will try that out and see if it does what I need. Thanks for your help.
As it is, I assume there must be a reason that the redirectTo doesn't automatically wait for all resolves to complete before triggering, but I'm not sure.

As it is, I assume there must be a reason that the redirectTo doesn't automatically wait for all resolves to complete before triggering, but I'm not sure.

The idea is that the redirect can happen before any expensive resolves (or resolves that might fail) are fetched.
Consider this example:
.state({
  name: 'parent',
  resolve: {
    spensive: (SpensiveApi) => SpensiveApi.get()
  }
})
.state({
  name: 'parent.child',
  resolve: {
    dataForChild: (ChildApi) => ChildApi.failsWhenUnauthenticated()
  },
  redirectTo: trans => {
    let AuthService = trans.injector().get('AuthService');
    if (!AuthService.isAuthenticated()) return 'login'
  }
})

By processing the redirect first, we avoid making an expensive API call.  We also avoid the dataForChild resolve rejecting (due to HTTP 403, etc) when the user is unauthenticated.
If the resolves must be fetched to process the redirectTo we can either fetch them inside the redirectTo hook using the injector(), or we can declare the resolves as EAGER.  The redirectTo hook is an onStart() hook at default priority (0).  The EAGER resolves are also an onStart() hook, but are high priority (1000).
To specify the parent resolve as eager:
.state({
  name: 'parent',
  resolve: {
    spensive: (SpensiveApi) => SpensiveApi.get()
  },
  resolvePolicy: {
    when: 'EAGER'
  }
})

Thanks for the details. I think my design (legacy, on which I'm doing a refactor with ui-router) is just a particular case. I was trying to think top-down with 1.5.x component architecture,  and every component from the "master" parent on down depends on data that comes with authentication (it's sort of like a Redux single-store, but that's where the comparison and quality ends).
I did try using the EAGER resolvePolicy, but at least the way I'd architected things at that point in time, it didn't help. I still thing a redirectToPolicy could make sense, but the option to use getAsync in the redirectTo callback, and to inject resolves at that point, should work fine. I'm trying to implement that now and will report back.

Not exactly still on topic, but if anyone would like to help contribute to docs with answers provided here in issues, is there a guide for this? Looks like a lot of auto-generated HTML in the meat of the documentation.
Regarding this and another issue, I would suggest putting many concrete examples in your answers somewhere around here:
Interface StateDeclaration ->
Injecting resolves into other things ->
During a transition, Resolve data can be injected into ...

I'd also link from the highest-level tutorial pages. Lots of concrete examples of how to inject resolves into other things, including other resolves and redirectTo methods (sync and async) would be very helpful.

A guide for contributing to docs and website is a great idea!
The short version is:
the website is at https://github.com/ui-router/ui-router.github.io . It is a Jekyll site hosted on github pages.
The API docs are generated using Typedoc from the block comments in the source code.

Thanks. I will give a shot at a PR for something simple. I did fork that repo in order to try to contribute some edits, but wasn't sure how to proceed.

I've added docs for all injectables: https://ui-router.github.io/ng1/docs/latest/modules/injectables.html
Also added a blurb to redirectTo about getAsync: https://ui-router.github.io/ng1/docs/latest/interfaces/ng1.ng1statedeclaration.html#redirectto

Thank you for the updates. The API is deep, and I know it's difficult to
document everything well.
On Wed, Jan 11, 2017 at 2:26 PM, Chris Thielen<EMAIL_ADDRESS>wrote:

I've added docs for all injectables: https://ui-router.github.io/
ng1/docs/latest/modules/injectables.html
Also added a blurb to redirectTo about getAsync:
https://ui-router.github.io/ng1/docs/latest/interfaces/
ng1.ng1statedeclaration.html#redirectto
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/angular-ui/ui-router/issues/3207#issuecomment-272015404,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAvFd8YVfqosSfcITOHnffaJ2A2kxGOqks5rRVcFgaJpZM4LOwfE
.


Create python-package-conda.yml

Problem with pytest:
Cant run tests without X server. Need to mock pynput KeyCode obj.
`Run conda install pytest
Collecting package metadata (current_repodata.json): ...working... done
Solving environment: ...working... done
All requested packages already installed.
ImportError while loading conftest '/home/runner/work/t9keyboard/t9keyboard/tests/conftest.py'.
tests/conftest.py:6: in
from pynput.keyboard import KeyCode
/usr/share/miniconda/lib/python3.10/site-packages/pynput/init.py:40: in
from . import keyboard
/usr/share/miniconda/lib/python3.10/site-packages/pynput/keyboard/init.py:31: in
backend = backend(name)
/usr/share/miniconda/lib/python3.10/site-packages/pynput/_util/init.py:76: in backend
raise ImportError('this platform is not supported: {}'.format(
E   ImportError: this platform is not supported: ('failed to acquire X connection: Can't connect to display ":0.0": [Errno 111] Connection refused', DisplayConnectionError(':0.0', '[Errno 111] Connection refused'))
E
E   Try one of the following resolutions:
E
E    * Please make sure that you have an X server running, and that the DISPLAY environment variable is set correctly
Error: Process completed with exit code 4.`


fix(connectGeoSearch): correctly dispose the connector

Summary
Right now there are two issues with the connector when the dispose function is called. The first one is that the parameter insideBoundingBox is not reset. The second one is that we always reset the parameters on the provided state argument instead of resetting the parameters on the new created value. It means that only the latest call will be reflected on the SearchParameters.
The PR fixes those two issues.

Should we have this PR on feat/2.7 @bobylito ?

Should we have this PR on feat/2.7 @bobylito ?

why should it be in 2.7?


How to webpack the lsp-sample

Trying to publish my LSP extension I ran into missing dependencies and a warning that I needed to pack my .ts files (due to number of files).
I have a hard time wrapping my head around trying to webpack the lsp-sample. My code base was started using this sample and still has the same structure.
Am I correct in saying that I need 2 entry's, one for client (extension) and one for server?
I just don't have a clue how to make that work...
I have found other webpack examples for vscode extension samples, but they don't deal with these 2 entry points...
I now have copied the extension webpack config file from the vscode extension manual, but that makes the client crash (F5)...
https://code.visualstudio.com/api/working-with-extensions/bundling-extension

@obiwanjacobi you may want to look at the eslint extension here which is web packed. It can act as a blue print since it is very similar to the lsp-sample. https://github.com/microsoft/vscode-eslint
Does this help?

Ah I see. Will investigate further. Thanks for now.

@obiwanjacobi I found that https://github.com/Microsoft/vscode-extension-samples/blob/master/webpack-sample/webpack.config.js works for https://github.com/ghdl/ghdl-language-server/tree/master/vscode-client, as long as you remove the "module": "es6" option from ts-loader.

I get compile errors (all vscode dependencies not found) when I add that to the client.

TS2307: Cannot find module 'vscode-languageclient'

I was thinking that maybe this warning I'm getting (2 of them) was the issue:

WARNING in ./server/node_modules/vscode-languageserver/lib/files.js 79:36-54
Critical dependency: the request of a dependency is an expression

I think that means that webpack cannot correctly intercept the import/require in that code. I could see how that would lead to something not working.
Here's my client webpack config file.
Here's my server webpack config file

I get compile errors (all vscode dependencies not found) when I add that to the client.

TS2307: Cannot find module 'vscode-languageclient'

Yes, I meant to comment it out: https://github.com/1138-4EB/ghdl-language-server/blob/bundle/vscode-client/webpack.config.js#L31-L35

Here's my client webpack config file .
Here's my server webpack config file

Honestly, this is a blind suggestion, but it might work: have you considered installing webpack in https://github.com/obiwanjacobi/Zingularity/blob/master/Source/Language Server/client/package.json and building the client only from there?

Honestly, this is a blind suggestion, but it might work: have you considered installing webpack in https://github.com/obiwanjacobi/Zingularity/blob/master/Source/Language Server/client/package.json and building the client only from there?

So install webpack twice and run client and server in their own 'instance'?
This is my command (script) "webpack": "npm run clean && webpack --mode production --config ./client/webpack.config.js && webpack --mode production --config ./server/webpack.config.js"
I cannot see how that would be any different - so I have not tried it (yet).
The webpack operation does produce results for the client and server.
Running the webpack (client) output in the extension host (F5) results in

[Error - 10:39:12] Starting client failed
1
being displayed in the extension host and a popup that my extension failed. I use --disable-extension in my launch file - so there are no other extensions messing things up.

Is there a more detailed log where I can see what is going wrong? I suspect it is probably a dependency that cannot be loaded, but I have no way of knowing.

I cannot see anything I am doing wrong, that leaves these two warnings when webpacking the server:

WARNING in ./server/node_modules/vscode-languageserver/lib/files.js 79:36-54
Critical dependency: the request of a dependency is an expression
@ ./server/node_modules/vscode-languageserver/lib/main.js
@ ./server/src/server.ts

WARNING in ./server/node_modules/vscode-languageserver/lib/files.js 280:15-28
Critical dependency: the request of a dependency is an expression
@ ./server/node_modules/vscode-languageserver/lib/main.js
@ ./server/src/server.ts

The reason for this is that the LSP libraries needed a fix to be able to work with webpack but the sample is not requiring the latest version. I fixed this.

I think you mean you've updated the engines/vscode value in package.json?
Anyway I have taken that sample and tried to make a webpack version (attached).
It has the same problem I have. I would really appreciate it if someone could look at it.
I have added some dev-dependencies and some scripts. Check out the readme.md for more info on how I think this should work.

After npm run webpack the code does not run correctly in vscode debug mode (launch client).
After 'npm run package(and having changed the publisher field) andcode --install-extension lsp-sample-1.0.0.vsix` the extension also fails.

If I can be of any help, let me know.
lsp-sample_webpack.zip

Can you fork the original repository and create a branch. Makes it easier to work on than using a ZIP.
And how does the extension fail?

And how does the extension fail?

Looks to me like the client is starting fine but the server does not start.
But it says:

[Error - 10:39:12] Starting client failed
1

I hope I did this right:
https://github.com/obiwanjacobi/vscode-extension-samples
Branch name: 191-webpack-issue

I had a quick look and when running out of dev you need to webpack differently. Have a look at the eslint example here: https://github.com/Microsoft/vscode-eslint/blob/master/package.json#L321
Or does this fail from a vsix install

And one mistake on my side: you need to use next version to have no error when packing the server.
"vscode-languageclient": "5.3.0-next.8"
"vscode-languageserver": "5.3.0-next.9"

Sorry for that.

I made (and pushed) the changes you suggested. I deleted all node_modules and out folders and ran npm install again. The I ran the new script webpack:dev and tried running the extension in the extension host (F5). It came back with the same error as before:

Or does this fail from a vsix install
After that I ran webpack for production and made a vsix package and installed it locally. That also does not seem to work (as before). I do not see any errors in this case, though...

I am having the same exact issue. Using the eslint setup as a blueprint, i can bundle both server and client with no problems, but when you run them in the extension host i get the following:

[Error - 13.14.04] Starting client failed
1

Is anybody still working on this?

I see the issue is labelled with 'needs more info'.
What info do you need?

Has there been any resolution on this issue?  Encountering same issue.

Nope I'm being ignored...

I managed to get this to work, but there are some rough edges https://github.com/elm-tooling/elm-language-server/commit/60640c7a12df183435d0808e53d461216260e5cf
You also probably don't want the wasm stuff

[Error - 13.14.04] Starting client failed
1

I got the same vague error message. What fixed it for me was updating my versions of vscode-languageclient and vscode-languageserver from 4.x to 6.x.

It would be really good to have an official sample for this.

Ok, I managed to do something like below, and it worked well:
// webpack.config.js
entry: {
  extension: './src/extension.ts',
  fileServiceServer: './src/files/server/fileServiceServer.ts'
}, // the entry point of this extension, 📖 -> https://webpack.js.org/configuration/entry-context/
output: {
  // the bundle is stored in the 'dist' folder (check package.json), 📖 -> https://webpack.js.org/configuration/output/
  path: path.resolve(__dirname, 'dist'),
  filename: '[name].js',
  libraryTarget: 'commonjs2'
},

// fileServiceClient
private getOptions(): { serverOptions: ServerOptions, clientOptions: LanguageClientOptions } {
        let serverModule = path.join(Settings.getInstance().extensionRoot, "dist", "fileServiceServer.js");
[...]

It's working so far.

with me it doesn't work. I have to put it or this code
HI. chez moi sa marche pas. je dois le mettre ou ce code.
GREENTING
Ok, I managed to do something like below, and it worked well:
Provenance : Courrierhttps://go.microsoft.com/fwlink/?LinkId=550986 pour Windows 10
De : Felipe @.>
Envoyé le :lundi, 29 mars 2021 16:48
À : @.>
Cc : @.***>
Objet :Re: [microsoft/vscode-extension-samples] How to webpack the lsp-sample (#191)
Ok, I managed to do something like below, and it worked well:
// webpack.config.js
entry: {
extension: './src/extension.ts',
fileServiceServer: './src/files/server/fileServiceServer.ts'
}, // the entry point of this extension, 📖 -> https://webpack.js.org/configuration/entry-context/
output: {
// the bundle is stored in the 'dist' folder (check package.json), 📖 -> https://webpack.js.org/configuration/output/
path: path.resolve(__dirname, 'dist'),
filename: '[name].js',
libraryTarget: 'commonjs2'
},
// fileServiceClient
private getOptions(): { serverOptions: ServerOptions, clientOptions: LanguageClientOptions } {
    let serverModule = path.join(Settings.getInstance().extensionRoot, "dist", "fileServiceServer.js");

[...]
It's working so far.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/vscode-extension-samples/issues/191#issuecomment-809441608, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASBMXOHZF3GR2SYVQOYRWRLTGCHM7ANCNFSM4H2RS2MQ.

I created an example through https://github.com/microsoft/vscode-extension-samples/pull/398.

I made lsp-user-input-sample webpack friendly. It can be used as a blue print for how to web pack a client extension with a node LSP server.

@dbaeumer A .vscodeignore would also be welcome to show what can be left out.


Add Optional Watermark to PDF

Summary
Add Optional Watermark to PDF
Background
A stakeholder has requested that we add a watermark on our preview PDFs to indicate that they should NOT sign (via pen and ink). In this use case, contributors would want to download the PDF and share it with their legal department for approval. Once approved, the contributor could use our tool to sign the document via DocuSign. To support this, and to avoid confusion, we should add a "Not for Execution" watermark to the PDF prior to streaming the template back to the user for UI display and download.

Example of what the PDF should look like (watermark example)

Tasks

[x] Review ticket #1604 - which describes how to identify the ICLA and CCLA for a given CLA Group.
[ ] Create a new API endpoint for fetching a given template for a CLA Group. Inputs are CLA Group and cla_ type: icla or ccla.  Add an optional watermark flag to the query as we may want to use this API for non-watermark use-cases. Normally the UI can directly download the template since it's public read-only, but in this case, we need an API/logic to overlay the watermark.
[x] Investigate this PDF library with examples (example repo here) to see if we can easily add the watermark to existing PDF documents.  This library appears to require a license fee.
[x] If possible, identify an open-source library that can do this.  We can ask around the community to see if anyone can recommend a library if a search comes up empty.
[ ] Determine if we should:

add the watermark on-the-fly. This is the best option and would easily solve all use-cases. Simple case.
add the watermark when we generate the template - save a version without the watermark for DocuSign and a version with the watermark for preview/download.  Note: for non-Apache templates, we have a manual upload process (not auto-generated). We get @WillsonHG or developer to manually add existing PDFs to the S3 bucket. In this case, we would need to post-process the uploaded PDFs to make a version of the PDF with the watermark.  More complex.

Gotchas:

[ ] need to add /v4 path pass through in the API-GW (no LF Login required) - may want to add Google Auth check?
[ ] ideally, do not write/read from disk - do everything in-memory if possible
[ ] we've had trouble with the API properly setting the mime/application type. Data was, by default, base64 encoded (no reason to base64 encode a PDF document).

User Story

As a contributor, I want to download the ICLA or CCLA template and share it with my legal team.
As a project manager, I want contributors to download a copy of the ICLA or CCLA template with a watermark to indicate that they should not sign with a pen, but use the EasyCLA tool to execute/sign the document.

Assumptions

The library referenced above can add watermark as described
The watermark library can update all pages in the document

Questions
List any questions or clarifications that are needed to addressed to satisfy this request.

N/A
N/A

Acceptance Criteria
The "done" criteria when this feature or problem is resolved. Such as:

Unit Tests added and running in CI
Functional Tests updated to cover feature, if applicable
Demonstrate the set of capabilities to the product team while the code is running in the DEV environment.

References

See above links.

For now we'll go with this open source library instead of the payed one : https://github.com/pdfcpu/pdfcpu

Verified that the issue is fixed. Attaching the document for reference
https://app.zenhub.com/files/194341141/9e8c3074-d3de-4d6e-a039-2ff84fe17275/download


On simulating Behavior tasks

hi, I am trying to use OmniGibson to simulate Behavior tasks and seeing if I can use the action primitives to complete some of them. It seems like to use behavior tasks we must hand-code the list of objects that need to be rendered for each task. Is there any way to get the simulation to automatically load the objects that a given behavior task requires and then use action primitives to finish it?
The relevant example: action_primitives.wip_solve_behavior_task fails to run correctly at the moment.
/omnigibson-src/omnigibson/controllers/controller_base.py:134: FutureWarning: elementwise comparison failed; returning scalar instead, but in the future will perform elementwise comparison   if command_output_limits == "default" 2024-05-07 17:36:59 [14,630ms] [Warning] [omni.syntheticdata.plugin] SdRenderVarPtr missing valid input renderVar DistanceToCameraSDhost Traceback (most recent call last):   File "/micromamba/envs/omnigibson/lib/python3.10/runpy.py", line 196, in _run_module_as_main     return _run_code(code, main_globals, None,   File "/micromamba/envs/omnigibson/lib/python3.10/runpy.py", line 86, in _run_code     exec(code, run_globals)   File "/omnigibson-src/omnigibson/examples/action_primitives/wip_solve_behavior_task.py", line 64, in <module>     main()   File "/omnigibson-src/omnigibson/examples/action_primitives/wip_solve_behavior_task.py", line 42, in main     env = og.Environment(configs=config)   File "/omnigibson-src/omnigibson/utils/python_utils.py", line 90, in wrapper     func(*values.args, **values.kwargs)   File "/omnigibson-src/omnigibson/envs/env_base.py", line 77, in __init__     self.load()   File "/omnigibson-src/omnigibson/envs/env_base.py", line 371, in load     self._load_robots()   File "/omnigibson-src/omnigibson/envs/env_base.py", line 242, in _load_robots     self.scene.reset()   File "/omnigibson-src/omnigibson/scenes/scene_base.py", line 493, in reset     self.load_state(self._initial_state)   File "/omnigibson-src/omnigibson/utils/python_utils.py", line 508, in load_state     self._load_state(state=state)   File "/omnigibson-src/omnigibson/scenes/scene_base.py", line 681, in _load_state     self._registry.load_state(state=state, serialized=False)   File "/omnigibson-src/omnigibson/utils/python_utils.py", line 508, in load_state     self._load_state(state=state)   File "/omnigibson-src/omnigibson/utils/registry_utils.py", line 340, in _load_state     obj.load_state(state[obj.name], serialized=False)   File "/omnigibson-src/omnigibson/utils/python_utils.py", line 508, in load_state     self._load_state(state=state)   File "/omnigibson-src/omnigibson/utils/registry_utils.py", line 340, in _load_state     obj.load_state(state[obj.name], serialized=False)   File "/omnigibson-src/omnigibson/utils/python_utils.py", line 508, in load_state     self._load_state(state=state)   File "/omnigibson-src/omnigibson/robots/manipulation_robot.py", line 1424, in _load_state     for arm in state["ag_obj_constraint_params"].keys(): KeyError: 'ag_obj_constraint_params'

You might want to confirm in your config file (something.yaml) the mode of the arm. It should be

Is the problem "KeyError: 'ag_obj_constraint_params'  for action_primitives.wip_solve_behavior_task " solved?

There might be some inconsistency for the grasping mode between when you dump the state and when you load the state.
This KeyError occurs because during load_state, self._grapsing_mode != "physical". However, the state you tries to load is dumped when self._grasping_mode == "physical".
One thing you can try is to configure the grasping mode to be "physical" before loading the state.


[Blackhole bringup] Writes to higher addresses in DRAM mismatching

TODO: explore whether tests that read from dram and hang are caused by the same issue

From Kevin Greig: "The upper 16MB is not addressable (there's a bug that we couldnt ECO in time for BH tapeout)"

For now we can work around this by reducing the dram bank size in our soc desc yaml


Replace deprecated use_auth_token with token

Fix partially #1550.
Requires:

[x] #1589

Codecov Report
Patch coverage: 83.33% and project coverage change: -7.15% :warning:

Comparison is base (310a27d) 99.37% compared to head (28ac757) 92.23%.
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1578      +/-   ##
==========================================
- Coverage   99.37%   92.23%   -7.15%
==========================================
  Files           6       77      +71
  Lines         161     5461    +5300
==========================================
+ Hits          160     5037    +4877
- Misses          1      424     +423

Flag
Coverage Δ

jobs_cache_maintenance
?

services_worker
92.23% <83.33%> (?)

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

Files Changed
Coverage Δ

services/worker/src/worker/utils.py
81.16% <50.00%> (ø)

.../src/worker/job_runners/config/parquet_and_info.py
87.50% <100.00%> (ø)

...ker/src/worker/job_runners/dataset/config_names.py
96.77% <100.00%> (ø)

...ker/job_runners/split/first_rows_from_streaming.py
90.27% <100.00%> (ø)

...nners/split/opt_in_out_urls_scan_from_streaming.py
94.79% <100.00%> (ø)

... and 78 files with indirect coverage changes

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


Change AngularJS to Angular

AngularJS is older framework with poor performance and does not support modern tooling. Angular is the successor with much better performance and better tooling.

Pull request merged #292


UI overhaul

UI overhaul of Splash, Setup Bluetooth, Home, Test Questions, Test Confirmation, Menu, Settings screens

The code looks pretty good. I did notice that the image you added fails to render though. What was wrong with the original svg?

fixed


Docs/migrate: add global controllers breaking change

It's suspiciously absent from the docs.

@Narretz isn't this https://github.com/angular/angular.js/blob/master/CHANGELOG.md#breaking-changes-18 enough?

It should be in migrate, too.
If you upgrade, you shouldn't have to check two docs.