Mac: Determine a better default location for the local cache

Currently we try to place the cache at /.gvfsCache. It should go to inside the user's home folder instead.

I think this is the best default. Users who have multiple drives and want to specify the location of the shared cache can use --local-cache-path on clone.

Might also be worth looking at improving the path expansion of --local-cache-path since currently if you use gvfs clone --local-cache-path=~/.gvfsCache <url> we don't create the cache in ~/.gvfsCache, but instead create it at ./~/.gvfsCache.

@mjcheetham interesting -- I can't repro that. But I also omit the =. I wonder if that is the culprit.

Yeah, the = pattern is something in the git option parsing, but not our verbs.

Re: expansion - we don't do any expansion today, the shell handles it for us. But that requires that it be at the beginning of a string, so @jrbriggs is correct that inserting the = breaks that. I'm not sure that we should do any expansion ourselves, I think that is the role of the shell, but if we want to do anything there, we should make sure it is applied to all path parameters, and it should be a separate issue.
Re: the topic of this issue, @jrbriggs I agree that the /.gvfsCache is not the correct location, but neither is ~/.gvfsCache. I believe this is covered by TODOs in the code, but our intent here is to discover the root of your current volume and place the cache there. The scenario to think about is: "I just went and bought a giant SSD to host my repo; why are you putting the cache on my puny drive that happens to host my home folder?"

The scenario to think about is: "I just went and bought a giant SSD to host my repo; why are you putting the cache on my puny drive that happens to host my home folder?"

Another scenario is the shared machine scenario.  If a team has a handful of Macs that are shared by multiple people, ideally they would all share the same .gvfsCaches.

@sanoursa @wilbaker those are both good scenarios to consider, but I think they're both lower priority than having the happy path be predictable.
I propose we use this issue to update the default on macOS to be ~/.gvfsCache, which at least allows clone to succeed with no special parameters. That's objectively better for early adopters than the state we're in today. We can file a subsequent issue to track lifting that cache to the volume root and managing acls on that path.
Thoughts?

Another good option, if we want to share cache between users, is to put it somewhere under /var ( like /var/cache/.gvfsCache), as that is a global location, that is meant for such data (https://www.granneman.com/tech/linux/thelinuxenvironment/topleveldirectories). Also, allowing to change it by setting an environment variable (or modifying git config) globally would be great, as passing cache location on each clone is certainly not a great UX.

Based on the discussion here:
https://unix.stackexchange.com/questions/23156/can-i-safely-remove-var-cache
I hesitate to put the directory inside /var/cache as VFS4G might have sub-optimal recovery if someone/something starts deleting pack files from inside the .gvfsCache folder.

I propose we use this issue to update the default on macOS to be ~/.gvfsCache, which at least allows clone to succeed with no special parameters. That's objectively better for early adopters than the state we're in today. We can file a subsequent issue to track lifting that cache to the volume root and managing acls on that path.

@jrbriggs for now my plan is to go with the approach you've suggested (including filing a follow up item to investigate the best location that can be shared by users).
+ @nickgra for his thoughts

One more data point:  In some basic testing I've found that by default root access is required to create subfolders inside /var.
Perhaps the installer could create a /var/VFSForGit/.gvfsCache directory with permissions such that non-root users could write into it?
If we can get this right from the start we'll avoid having to write (potentially complicated) migration/upgrade code later.
+ @alameenshah and @pmj for their thoughts as well on the best place to put this directory.

Historically, customers of our large repository put their clones of it on separate external drives (or partitions of a large drive). A sizable percentage of users have a very small OS partition (and thus home folder) so putting it in ~ might fill up their drive quickly when cloning a repo that requires VFS4G.

Perhaps the installer could create a /var/VFSForGit/.gvfsCache directory with permissions such that non-root users could write into it?

I like this more than the home folder idea (solves sharing between users) but I believe /var will always be in the boot volume so it won't help if it's very small.
Optimizing for those first customers, I think the best solution for them is to put the cache in /var/VFSForGit/.gvfsCache if the clone is going to be in the boot volume or put it in the root of the volume if it's an external drive/partition? That should let us avoid the problem of writing a folder into the top level / folder which requires root and is a rather nasty thing to do.
This does require two code paths though so I'm not convinced it's the best solution I'm afraid.

So why not chose a reasonable default, such as /var/VFSForGit/.gvfsCache, and allow to override it with an environment variable? Determining the "root of the volume" might be non trivial and brings little benefit over a clear and well documented way of overriding the default with an environment variable.


Bump coursier version to prevent possible dep resolution issue

I don't know why, but I was having some issues getting the project going on a new system. Bumping coursier helped. Here was the original error:
[info] Set current project to root (in build file:/home/brandon/workspace/monadic-html/)
[trace] Stack trace suppressed: run last monadic-rxJVM/*:ssExtractDependencies for the full output.
[trace] Stack trace suppressed: run last monadic-rxJVM/*:update for the full output.
[error] (monadic-rxJVM/*:ssExtractDependencies) coursier.ResolutionException: 1 not found
[error]     /home/brandon/.sbt/preloaded/org.scala-lang.modules/scala-parser-combinators_2.12/1.0.4/bundles/scala-parser-combinators_2.12.jar
[error] (monadic-rxJVM/*:update) coursier.ResolutionException: 1 not found
[error]     /home/brandon/.sbt/preloaded/org.scala-lang.modules/scala-parser-combinators_2.12/1.0.4/bundles/scala-parser-combinators_2.12.jar
[error] Total time: 3 s, completed Sep 25, 2017 1:57:58 PM
[IJ]> ;reload; set _root_.org.jetbrains.sbt.StructureKeys.sbtStructureOptions in Global := "download resolveClassifiers resolveSbtClassifiers" ;*/*:dumpStructureTo /tmp/sbt-structure.xml```

Thanks!


can't do any DOM manipulation before fingering the Ifram event

Normally my Iframe contains links. I want to catch the Iframe click event (which will open an external link) to show a message to user before opening the link.
                $('#myFrame').iframeTracker({                     blurCallback: function () {                         $('#WelcomeMessage').modal('show');                     }                 });
The Iframe event always triggers before showing the message.
I'm using Version 50.0.2661.66 beta-m (64-bit)

Can you provide a live example (using https://jsfiddle.net/ or http://jsbin.com/) ?
.modal is not native jQuery, which plugin are you using ?

Actually I'm tracking google ads, I tried to make any DOM change before the ad opens but It fails. forget about modal and try to do any change in DOM before the ad link opens.

Unfortunately, I can't help with so little information. I do not even know if you are using the old adsense code or the new asynchronous code. Please provide a live example.
I tried to do some DOM manipulation like this :
jQuery(document).ready(function($){
	$('#iframe_dummyads iframe').iframeTracker({
		blurCallback: function(){
			$('span.brand').append(" - DOM append");
			$('<div>').html("New div").insertAfter($('#wrap'));
		}
	});
});

And it works fine with the old adsense code (DOM is modified while the ads target link is opened in a new tab). It doesn't work with the async adsense code because the ads is not yet available at DOM ready. But I can make it work by binding iframeTracker after adsense rendering.
I'm testing on :
Google Chrome	50.0.2661.94 (Build officiel) m (32 bits)
Révision	0c319c380220abe3daf0277e40a2d0b22a7c4550-refs/branch-heads/2661@{#645}


Fix graph query for articles with slice machine

What does this change?
Following the slice machine changes reflected in the Prismic API, we have to change the graphQuery used to fetch articles from said Prismic API.
How to test
The graph query is valid: running yarn update-prismic-snapshots doesn't error
The pipeline tests pass using the updated prismic snapshots
How can we measure success?
No more errors in the alert channel
Have we considered potential risks?

Slack chats happened here


[No QA] Fix regression on web due to #4760

cc @marcaaron
Details
Making production web builds using npm run build fails with a webpack loader error
The problem is discovered as a regression here: https://github.com/Expensify/App/pull/4760#issuecomment-904349442
Because webpack statically analyzes all require calls - even those that might never happen we need to add react-native-flipper to includeModules
Fixed Issues

$ N/A
Tests

Same as the tests here: https://github.com/Expensify/App/pull/4760#issue-716300075
QA Steps

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

Ideally we want check that can be evaluated at compile time (such as if (canCapturePerformanceMetrics()) ) to exclude dead code from the bundle
It might be possible to configure babel, or at least webpack (not sure if metro supports this), but it would open the door for other regressions
Another approach is with the platform specific code. We can extract lib/Performance/index.js, lib/Performance/index.native.js and lib/Performance/BasePerformance.js
Base performance is pretty much a blank stub. index.js exports this "blank stub" while index.native.js uses react-native-performance and the flipper integration when canCapturePerformanceMetrics() is true
Say something if you want to open another PR with the platform specific changes (or modify the current one)

I don't have much context regarding this, But looking to previous work and PR's. I think we should see if we can configure our bundler to get rid of unused dependencies. If we're bounded by that, I'm fine with platform specific method. As I see, we had that before?
Let's see what @marcaaron says.
Anyways, this PR looks good to me.

Say something if you want to open another PR with the platform specific changes (or modify the current one)
I think we should see if we can configure our bundler to get rid of unused dependencies.

I think if this PR fixes the web builds then we should start here. I agree it would make sense to not bundle this code, but as far as we know we don't have an issue related to the JS bundle size. So maybe it's not worth prioritizing?
I found some documentation for how webpack handles this -> https://webpack.js.org/guides/code-splitting/#dynamic-imports
My only question is... does the conditional require work correctly on native? If it's only web that is bundling I'd say this matters less.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

My only question is... does the conditional require work correctly on native? If it's only web that is bundling I'd say this matters less.

RN does not support Dynamic Imports and doesn't have the await import() syntax yet: https://github.com/facebook/metro/issues/52
Both webpack and metro support the optional and inline requires - we already use them conditionally load a lib

for RN it gets bundled into the installation source code - no big deal
for web it gets bundled into app.js - might be a problem as it affects initial webpage load time

For the current item though the overhead added is negligible - about 10kb (there are also 30kb added by react-native-performance, but they are even harder to get rid of as we also conditionally use it in Onyx...)
It's possible to configure webpack to split chunks out of app.js even if they aren't dynamic imports - this should be enough to address the issue, it would extract a chunk like react-native-performance-flipper-reporter.hash.js. Even though it's still compiled it would only be loaded when the condition matches. This a bit advanced to configure properly and it's not esencial ATM
The other approach is "dead code elimination" which can happen at compile time. Since we only set ENV vars at compile time - CAPTURE_METRICS. webpack and metro should be able to statically analyze and derive that certain code will never be evaluated to true and run so they can strip it.
It's again a bit complex to configure (compared to writing .native or .web) as it requires babel plugin(s) and changing conditions to if(process.env.CAPTURE_METRICS === 'true') as these can be statically evaluated to true or false and then discarded
As a summary the easiest thing to do right now is to write Platform specific code, but it doesn't seem to be worth it just for the current case.
It's very like bundle splitting would be enabled at some point down the road which is one more reason to skip doing anything ATM

Thanks for the summary!

It's very like bundle splitting would be enabled at some point down the road which is one more reason to skip doing anything ATM

I agree with this. It does feel inevitable that we will want to optimize the JS bundle - but just isn't our focus right now.

🚀 Deployed to production by @roryabraham in version: 1.0.88-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

This has been deployed to production and is now subject to a 7-day regression period.
If no regressions arise, payment will be issued on 2021-09-08.  :confetti_ball:


Latex Processor Eats buckets

reposting from tekkit 2 bug tracker as requested from xJon
Basic details
Are you using a legitimate Minecraft account?: yes
Are you using Java 8, 64-bit?: yes
Did you add any additional mods: no
Crash/latest log link (if applicable): not applicable
Describe the issue
if a latex processing unit has less than a bucket left of room in it's latex tank then putting a latex bucket in there will destroy the bucket.
https://www.youtube.com/watch?v=-VM4McAUCEg

Patched as of ebde988aacbd2126074cd63636a517f3e3b1fe04.
I've uplodaded a new version to CurseForge.
You might need to wait for few minutes before it will show up.


Docs: fix some typos found ad hoc

Pull request checklist

[x] Signed the Contributor License Agreement
[x] Followed the commit message guidelines

Short description of the change(s)
Fixed some typos I found while reading the docs as a user, including using real apostrophes instead of the straight quote.

@molant fixed the redundancy from the merge!

Thanks, @melanierichards!


The HSQL statement executed by the sql task node has a permission vulnerability

When Kerberos authentication is enabled and different tenants use the same sql task node to execute hsql statements, the DS calls the same DS component authentication ticket by default, if different tenants are using this sql to run HSQL, then there is no way to tell the difference. The users who submit tasks should be the ticket for the DS component. For example: I have two tenants, one of which has access to hive, a just need to use the basic shell running script, then for the DS basic note I am authorized or not authorized access to the HIVE, authorized to use the hive permission, yes, can be used, but if a user who doesn't have the rights to hive finds that he or she can still use the hsql feature of hive, he or she may not be able to control his or her risk. I think there's a loophole, don't you?

#4450

#4450

#4450
Hive/Spark JDBC supports manual configuration of keytab parameters when using Kerberos authentication, and supports multi-tenancy when using Kerberos authentication for Hive/Spark data sources.

@shiliquan , good job,  and issue of #4450 also solve this problem, so I will close this issue

#4450
Hive/Spark JDBC supports manual configuration of keytab parameters when using Kerberos authentication, and supports multi-tenancy when using Kerberos authentication for Hive/Spark data sources.

@shiliquan , good job,  and issue of #4450 also solve this problem, so I will close this issue


Project status?

I'm considering this for my company's move to multi-cloud. However, I don't see any activity in the project for over a year. Am I missing something, or did the project somehow reach maturity already? Thanks!

idem! What is the status of the serverless-multicloud ?

Bumping as I'm also exploring some multi cloud solutions.

Is this project dead? or is there any plans for develoment


Doc revive

http://azure.github.io/azure-sdk-for-python/

Codecov Report

Merging #5013 into master will increase coverage by 0.1%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #5013     +/-   ##
=========================================
+ Coverage   49.16%   49.26%   +0.1%
=========================================
  Files        6456     6689    +233
  Lines      181146   186457   +5311
=========================================
+ Hits        89055    91853   +2798
- Misses      92091    94604   +2513

Impacted Files
Coverage Δ

azure-common/azure/profiles/__init__.py
82.81% <0%> (-3.86%)
:arrow_down:

...rregistry/v2018_02_01_preview/models/target_py3.py
28.57% <0%> (ø)
:arrow_up:

...containerregistry/v2017_10_01/models/target_py3.py
28.57% <0%> (ø)
:arrow_up:

...ainerregistry/v2018_09_01/models/event_info_py3.py
100% <0%> (ø)

...018_09_01/models/registry_usage_list_result_py3.py
100% <0%> (ø)

.../mgmt/storage/v2018_07_01/operations/operations.py
28.12% <0%> (ø)

...v2018_09_01/models/source_update_parameters_py3.py
44.44% <0%> (ø)

...ry/v2018_09_01/models/run_update_parameters_py3.py
66.66% <0%> (ø)

...re/mgmt/storage/v2018_02_01/models/resource_py3.py
55.55% <0%> (ø)

...inerregistry/v2018_09_01/models/run_request_py3.py
66.66% <0%> (ø)

... and 228 more

Continue to review full report at Codecov.

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


Saving to EDF with no precision loss

I'm using this script to save an MNE Raw to EDF, and it leverages pyedflib
https://gist.github.com/skjerns/bc660ef59dca0dbd53f00ed38c42f6be
What I've noticed is that any EDF file can be loaded by MNE's read_raw_edf() method, then save back to EDF using the above script with no loss.
I've verified this losslessness by using Numpy's array compare; data before the save is perfectly equal to data after the save.
However, trying to load up a Nihon Koden .EEG filetype using MNE's read_raw_nihon() method, then saving that Raw to EDF using this script, results in intolerable loss in precision. Numpy's array compare shows that exactly 0 of the elements in the array after the save are equal to the array before the save.
I could use help thinking through this problem and perhaps modifying this script to accommodate. Is there a way using pyedflib to save this data losslessly?

Dear @PhlipPhlops this is due to the implementation of EDF. Internally, EDF is stored as a INT16 stream, and then converted to float via the fields physical_min and physical_max. This means that EDF is not able to store all range of values.
If you load an EDF, and use the exact same header values, then of course the exact same values can be displayed. If loading other data formats this might not be case.
Unfortunately, this problem is inherent to the EDF+ standard. What you can do is use BDF instead (it has 24-bit precision instead of 16-bit), or play around with the physical min/max fields to increase precision. Also upscaling to a different voltage dimension (storing mV instead of V) can help increase precision.
I hope that clarifies the problem a bit, let me know if you have any questions


Browser Compatibility Issue

Hi @trungdq88 I still have an issue here #14 but cannot reopen. Would you be able to take a look and advise?
Many thanks.

I was trying to create a minimal example to reproduce this on Firefox but it seem not to works. Can you try to move the transition property inside .transition-appear-active class?
    .page {
        height: 100vh;
    	position: absolute;
    	top: 0;
    	right: 0;
        bottom: 0;
        left: 0;
     }

    .page {
      &.transition-appear {
        transform: translateY(100%);
        opacity: 0;
        z-index: 75;
      }

      &.transition-appear.transition-appear-active {
        transition: all 0.5s ease;
        transform: translateY(0);
        opacity: 1;
        z-index: 75;
      }

      &.transition-leave {
        transform: translateY(0) scale(0.5);
        z-index: 70;
      }

      &.transition-leave.transition-leave-active {
        transition: all 0.5s ease;
        transform: translateY(-25%) scale(0.5);
        opacity: 0;
        z-index: 70;
      }
    }

Close due to inactive.


$minErr module loading error can cause truncated URLs

Since the 2nd minErr argument is often the error's stack trace when trying to load modules, the url can often be cut off by the browser.
https://github.com/angular/angular.js/blob/bf6a79c3484f474c300b5442ae73483030ef5782/src/auto/injector.js#L756
This message should be replaced with something more intelligent, ideally showing which dependent module was missing or broken.

If the call stack is very long then the URL can also be very long. This is common when there are error messages in loading modules and in infinite digests. Also I think there is often some kind of recursion in the messages where you have to click through a number of times to get to the actual error message.
TLDR; improve the error messages from the core.

Depending on what causes it, the error will already show context. Otherwise this is just a special case of https://github.com/angular/angular.js/issues/14744


Support of auto line break on syntax highlighting

Now not be a new line at the time of the syntax highlighting.
example:

When a character does not fit on the screen,
I think that it should be a new line in the automatic.

We're making a clean sweep of piled up issues.
Auto line break might break source code. In the core of Marp Next, we have supported auto scaling of code block in several themes (marp-team/marp-core#23). This behavior also has a compatibillity with the other app. (e.g. Deckset)


Error with special chars and backticks

I'm using a database (mysql) with fields having ":" as part of it.
Usually i'm use "`" (backticks) running queries and all works ok.
However, it seems like (at least) in the "where" function of Medoo, the fields aren´t well parsed even having backticks.

As far as I understand, double quotes (which Medoo uses) require that the name of the columns/tables be an identifier. The identifier may contain the following characters (in the unexpanded version): [0-9a-zA-Z$_ ]. If you want to use other characters inside the name you have to backticks, which tells SQL that it is a real string rather than an identifier.
Swap in around 356 lines, double quotes with backticks.
I think it would be cool if Medoo noticed such conflict of characters and will change double quotes into backticks for strings containing characters different than default identifier characters, or statically maybe change them, because I don't see any contraindications.

I think the real problem is the Medoo's assumptions about permitted characters in identifiers, not considering others even quoted (at least on mysql).
Workaround?. Add the "special" character in the regexps.
I guess the solution is to have a way of "push" the char/chars in the regexps, i,e:
// [optional] Special char
	'special_char' => ':',

or something like that.

v1.5 will output by the database default quote identifier.
https://medoo.in/api/whatsnew


Problems with pydantic?

May I ask the dependencies for pydantic? I met several problems from pydantic
File "/home/spacex/miniconda3/envs/LiDAR-MOS/lib/python3.7/site-packages/pydantic/main.py", line 719, in __setattr__
    if self.__pydantic_private__ is None or name not in self.__private_attributes__:
  File "/home/spacex/miniconda3/envs/LiDAR-MOS/lib/python3.7/site-packages/pydantic/main.py", line 699, in __getattr__
    pydantic_extra = object.__getattribute__(self, '__pydantic_extra__')
AttributeError: __pydantic_extra__

The latest release of KISS requires pydantic>2 which doest not work with our code currently. I will update it soon.
You can for now install kiss-icp<0.3.0, this should still work.

Can you please try to see if it works on this branch?

I will have a  try

I will close this issue, please re-open if it did not help


Vulnerabilities in security configuration on your machines should be remediated : resource group exclusion do not apply

Describe the bug
VM in excluded resource group are reported in security configuration vulnerabilities.
To Reproduce

Set resource group exclusion on security policy
Create VM with security issu (like SMB v1 enabled for samba) in excluded resourcegroup

Expected behavior
Do not report security issues for VM in excluded resource group.
Screenshots
All VM below are databricks cluter in resource group excluded.

Desktop (please complete the following information if applicable):
Smartphone (please complete the following information if applicable):
Additional context

Hi @MasterKuat,
to exclude resources from evaluation, you can use the resource exemption feature which we've recently announced. Exemption on Resource Group level is not supported at this time.

Hi Tom,
Thnaks for your answer.
VM are dynamicly created and destroyed by Databricks each time a cluster is started or stoped. We do not have any control on it (tags or whatever).
Only resource group is common point for these VM.
So should be really usefull and meaning feature for that case.


Form editor can inert values in incorrect order when display orders are equal

https://gist.githubusercontent.com/anonymous/d206a201e54b12a2e79b

Yes we did


all selected addresses have no funds. it's correct?   Fantom

all selected addresses have no funds. it's correct?

Go and check all 9600 addresses!


[Python][C++] Slow table slice when the table has many chunks

Describe the bug, including details regarding any error messages, version, and platform.
When the pyarrow table has many chunks, the slice/take function is slow as demonstrated with the following code:
import sys
import time
import numpy as np
import pyarrow as pa

batch_size = 1024

batches = []
for _ in range(8555):
    batch = {}
    for i in range(10):
        batch[str(i)] = np.array([j for j in range(batch_size)])
    batches.append(pa.Table.from_pydict(batch))
block = pa.concat_tables(batches, promote=True)

# Without the below line, the time is 345s and with it, the time is 0.07s.
# block = block.combine_chunks()

start = time.perf_counter()
while block.num_rows > batch_size:
    block.slice(0, batch_size)
    block = block.slice(batch_size, block.num_rows - batch_size)

duration = time.perf_counter() - start
print(f"Duration: {duration}")

Several questions:

Is this slice slowness expected when a table has many chunks?
Is there a way to tell pyarrow.concat_tables to return a table with a single chunk so I can avoid an extra copy by calling combine_chunks()?

Component(s)
Python

Is this slice slowness expected when a table has many chunks?

I certainly wouldn't expect such a huge slowdown, but given that slicing a table with many chunks has inherently some more overhead (slicing each individual chunk each time), some slowdown can be expected. But we should maybe see if there some overhead that can be reduced (from a quick profile, I don't directly see something obvious though, a large part of the time is spent in the actual Array::Slice / ArrayData::Slice).
Maybe there could be some optimization when you are taking a slice that covers several chunks entirely, we don't actually call Slice on the chunks that are needed in full for the result.
In general, chunks incur some overhead, and a batch size of 1024 is quite small for pyarrow (pyarrow/Arrow C++ is not optimized to work on such small batch sizes). So probably best to use a larger batch size.

Is there a way to tell pyarrow.concat_tables to return a table with a single chunk so I can avoid an extra copy by calling combine_chunks()?

That's currently not possible, but note that concat_tables does not actually make a copy of the data (the original chunking is preserved), only combine_chunks does a copy.

Maybe there could be some optimization when you are taking a slice that covers several chunks entirely, we don't actually call Slice on the chunks that are needed in full for the result.

In my script, we actually do slice a single chunk (equal to batch_size).

Is the goal to iterate the table batch-by-batch?  Could you use Table.to_batches instead?

Is there a way to tell pyarrow.concat_tables to return a table with a single chunk so I can avoid an extra copy by calling combine_chunks()?

There is not an "extra copy" (at least, not an extra copy of the actual buffers of data).  concat_tables is a zero-copy operation in this case.  combine_chunks is not.  So these two operations combined will form a single copy.  I don't see much advantage in fusing them into a single method.

I recently started experiencing the same problem. I've got about 500-1000 chunks per dataset, all stored in memory, and take takes a few minutes to access a single (!) element. Regardless of how slow and outdated your hardware is such low speeds are beyond any comprehension.


528 - Present Additional Restrictions on the client

Issue Number
Closing #528
(This PR is based on the #527 branch.)
Purpose/Implementation Notes

Added "Additional Restrictions" item to bottom of Project Details table
Added "Additional Restrictions" to DownloadStart component, if populated
Updated the download modal heading Download [Project|Sample]. to Downloading [Project|Sample] when the download started

Types of changes

New feature (non-breaking change which adds functionality)

Functional tests
List out the functional tests you've completed to verify your changes work locally.
Checklist

[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

@davidsmejia you were auto-assigned since I added the client / front-end label. But I'll remove your temporarily and will add you back later  once I test my implementation with new API updates, thank you!


[Proposal] Directory define banken query methods to the Controller class without creating a loyalty class

When the rule is not complicated, It is convenient for us to add query methods directly to the controller class without creating a loyalty class:
class WelcomeController < ApplicationController
  def_banken_query_method_for(:index) { user.admin? || user.manager? }

  def index
    @records = Record.all
  end
end

Of course, when implementing complex logic that requires unit testing, there is no objection on the approach to implementing loyalty classes. I wanna use this feature, so I've implemented it.
Would you please tell me your opinion.

@yhirano55
I can understand that you want it. But I think that all logic for loyalty should be under app/loyalties/ even if it not complicated. To be able to define it in two places which is controller and loyalty means that it is necessary to confirm to which one is defined for checking logic for loyalty. Because we do not remember whether it complicates.
I guess that many people will not moved it to class when logic for loyalty in controller changed complicated. So in the future the consistency of the place to write it will be lost. That's why I want to bind with just one simple rule written it loyalty class under app/loyalties/.
Thanks your contributions. :+1:

Thanks for the code review, and I appreciate your opinion.
I'll make the another extension gem that has simple DSL like this pull request. I've thought again that the simplicity is a wonderful point in this gem. Banken is a great gem. Thanks a lot !!


Add example of using relay’s mock generator for tests

This is a stash of a quick attempt I still had lying around. Let‘s iterate on it.
Unsure if this massive query is the right place to do this. It definitely makes it easy to have the correct fixture data, but since it’s only being verified through a snapshot it’s a little hard to judge the result.

Things that could be improved upstream
check the following in 7 and fix if not already taken care of

fix aliases. make sure you can actually return data for an aliased field from the parent type.
do sanity check on returned data, to check it matches selections in the query.
change the 'mock-value-for-field-"blah"' to include path rather than just field name

also

export more types from react-test-utils/index.d.ts
prevent passing unused variables in QueryRenderer

shouldn't there be a corresponding change to GlobalMap-tests.tsx?

Nice 👌 Let's merge this then and follow-up with a mutation example etc

:rocket: PR was released in v1.18.19 :rocket:


AppCache is set to be depricated.

In Chrome I am receiving this warning:

[Deprecation] Application Cache API use is deprecated and will be removed in M82, around April 2020. See https://www.chromestatus.com/features/6192449487634432 for more details.

This seems to be the code causing the warning:
    function initAppcache() {         if (typeof window !== 'undefined' && window.applicationCache) {             if (window.applicationCache.status === window.applicationCache.UPDATEREADY)                 reload();             window.applicationCache.addEventListener("updateready", function () {                 if (window.applicationCache.status === window.applicationCache.UPDATEREADY)                     reload();             });         }     }
Whatever caching is needed will probably need to be handled by a service worker since this will stop working at least in Chrome in the near future.

OS: Mac 10.15.3
Browser Chrome 81.0.4044.113
Version [e.g. 22]

Interestingly I didn't see this error when we had our an autogened service worker created by workbox's webpack plugin however we couldn't fully load in pxt. We would get the start block, but the try with blocks would not load when running our app as a PWA. I'm not positive this caching strategy is what's causing our issues in the PWA, but everything loads fine when we are not caching with our service worker, and stops working when we add a service worker.

service workers added in https://github.com/microsoft/pxt/pull/6634 for the most part, but that does seem to be missing
@riknoll was there a reason I'm forgetting for https://github.com/microsoft/pxt/blob/master/webapp/public/run.html#L145 ? needs to be changed over / deleted I suppose

@alexistbell we have service worker in latest PXT. Check #6634. App cache code is only for legacy browsers.

Thanks, I still saw the app cache code so I didn't realize a service worker had also been added. Looks like any remaining issues are my own.


Deprecate #include "fildesh.h" way of including libfildesh header

Workaround
Use #include <fildesh/fildesh.h> instead.
Timeline

v0.1.6 will make the workaround possible.
v0.1.6 will require the workaround in dependent CMake projects.
v0.2.0 (or earlier) will require the workaround in dependent Bazel projects.

Like with CMake, the Bazel build appears to have broken #Include "fildesh.h" already. I'm not sure which version of Fildesh did it, but certainly before v0.2.0.


angular-cli: 1.0.0-beta-16; ng build --prod fails; either bits in dist are not complete or build fails

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
windows 7

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:
angular-cli: 1.0.0-beta.16
NODE: 6.5.0
os: win32 x64

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.
the app was created using the CLI
added components, service

The log given by the failure.

Normally this include a stack trace and some more information.
94% asset optimizationError in bail mode: [default] c:\Dev\angular2showcaseapp
src\app\app.component.ts:5:12
Cannot find name 'require'.

Mention any other details that might be useful.
contents of app.component.ts
import { Component } from '@angular/core';
@Component({
selector: 'app-root',
templateUrl: './app.component.html',
styleUrls: ['./app.component.css']
})
export class AppComponent {
title = 'Angular 2 Rocks hardcore!';
}

Thanks! We'll be in touch soon.

Same issue I am having.. whats your typescript version?

Same issue here. I used this workaround:
npm install @types/node --save-dev

Maybe it should be included in package.json.

fix : in typings.d.ts
add: declare var require: any;

Fixed in https://github.com/angular/angular-cli/pull/2528


[Feature Request] Multiple contentType in DocumentTypeDef ?

Hi there!
Currently, the type definition of DocumentTypeDef looks like this:
/* ...

/**
   * Default is `markdown`
   *
   * Choose `data` e.g. for a `.json` or `.yaml` file
   */
  contentType?: DocumentContentType

And DocumentContentType looks like this:
export type DocumentContentType = 'markdown' | 'mdx' | 'data'

Would it be possible to adjust contentType to be defined like this?
contentType?: DocumentContentType | DocumentContentType[]

And so, the generated types could turn from this:
export type PostSchema = {
  /* ...
  /** MDX file body */
  body: MDX
}

To this:
export type PostSchema = {
  /* ...
  /** MDX file body */
  body: MDX // [HERE] Could be also defined as: `/** MDX | Markdown file body */ body: MDX | Markdown`
}

It would not cause breaking changes, as defineDocumentType still could be used like this:
defineDocumentType(() => ({ filePathPattern: 'foo/**/*.mdx', contentType: 'mdx', name: 'Foo', fields, computedFields }

Or like this:
defineDocumentType(() => ({ filePathPattern: 'foo/**/*.{mdx,md}', contentType: ['mdx', 'markdown'], ...rest }

I thought about it because of some choices of implementation on my current experimental project.
Here are some details: https://github.com/Tirraa/dashboard_rtm/blob/main/doc/blog/00.quirks.md

:up:

hello stale bot


linux sdk not working on ubuntu 16.04

Hi!
The linux sdk is not working on ubuntu 16.04.
The test program fails with the following errors:
$ sudo PYTHONPATH=./nuimo python examples/test.py started discovery Traceback (most recent call last):   File "examples/test.py", line 92, in <module>     main()   File "examples/test.py", line 29, in main     nuimo_manager.start_discovery()   File "/home/dominik/workspace_other/nuimo-linux-python/nuimo/nuimo.py", line 324, in start_discovery     self.nuimos = self.create_nuimos(all_discovered_devices)   File "/home/dominik/workspace_other/nuimo-linux-python/nuimo/nuimo.py", line 338, in create_nuimos     return [NuimoController(device) for device in self.filter_nuimos(devices)]   File "/home/dominik/workspace_other/nuimo-linux-python/nuimo/nuimo.py", line 335, in filter_nuimos     return [addr for addr, attrs in devices.items() if attrs.get('name') == 'Nuimo'] AttributeError: 'str' object has no attribute 'get'
Python is installed from the default sources (2.7.12), the sdk was installed as specified in the Readme with pygattlib from the specified sources.
The issue appears to be this:
issue 27
If pygattlib is installed from https://bitbucket.org/OscarAcena/pygattlib everything works fine.
The fix: diff

Thanks a lot! We'll have a look into it.

Fixed with #4 – Nuimo SDK is now using the original repo as you also suggested. Thanks to @gross1989 for the PR!

For me, it only works, if I install it from here:
git clone https://github.com/matthewelse/pygattlib
My install.sh is still (cloned it on September, 8th):
pygattlib)         echo "Installing Pygattlib and dependencies"         set -x         sudo apt-get install pkg-config libboost-python-dev libboost-thread-dev libbluetooth-dev libglib2.0-dev python-dev         [ ! -d pygattlib ] && git clone https://github.com/matthewelse/pygattlib         cd pygattlib && sudo python setup.py install         ;;
I'm developing on a Raspberry Pi 3

The fork of matthewelse has a working discovery method similar to these proposals: 1 and 2, but it is some commits behind the original and less frequently updated or not maintained any longer.
I suggest to instantiate with the mac address, which works in any case.

Hi @gierdo, @naimo84 please try our all new Nuimo Python SDK. It now uses BlueZ's D-Bus API directly. Please find all information here: https://github.com/getsenic/nuimo-linux-python


Removing draft example notebook Untitled.ipynb

Codecov Report

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

@@           Coverage Diff           @@
##           master      #35   +/-   ##
=======================================
  Coverage   77.09%   77.09%
=======================================
  Files          20       20
  Lines        1004     1004
=======================================
  Hits          774      774
  Misses        230      230

Continue to review full report at Codecov.

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


Support certificates (insecure) for reporting to chef-visibility

Cookbook version
2.0
ERROR: SSL Validation failure connecting to host: lprsedifcha001v.int.asurion.com - SSL_connect returned=1 errno=0 state=error: certificate verify failed
ERROR: send_inspec_report: POSTing to https://lprsedifcha001v.int.asurion.com/data-collector/v0/ returned: SSL Error connecting to https://lprsedifcha001v.int.asurion.com/data-collector/v0/ - SSL_connect returned=1 errno=0 state=error: certificate verify failed

need to add insecure option for visibility

" But we should document that SSL certs can/should be placed in /etc/chef/trusted_certs
*when using visibility"  <-- from @jerryaldrichiii

@chris-rock submitted PR #152 which handles this well @vjeffrey

We may should still allow users to enable insecure here: https://github.com/chef-cookbooks/audit/blob/1ea498bb9ed6fcdf85299b3478273b375d676a49/libraries/collector_classes.rb#L54 as we do for chef-server https://github.com/chef-cookbooks/audit/blob/1ea498bb9ed6fcdf85299b3478273b375d676a49/libraries/collector_classes.rb#L276-L277


1.0 Release

Future wishful thinking (to keep the milestone open for now)

@lexual ah, didn't know this already existed .. let's close this in favor of #10000 as there has already taken place some more discussion


[CWS] secagent tests: simplify into one fxutil.Test invocation

What does this PR do?
Small simplification to how CWSConsumer fx dependencies are invoked in the test. The main goal is to have only one invocation run (one logger etc).

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


[mesheryctl] unable to ping kubernetes error

Description

I am unable to ping Kubernetes even when uploading system configs.
Configs tried :

kind
minikube

Expected Behavior

It should give "pinged successfully"
Screenshots

Environment:

Host OS:  Ubuntu 20.04
Meshery Version:
Client Version: 0.4.24 	  GitSHA: 8a95887a4c4ff9681d8c27ad8d3a83840f8524c8
Server Version: v0.4.25 	  GitSHA: 6b23b79
Kubernetes Version:
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.4", GitCommit:"d360454c9bcd1634cf4cc52d1867af5491dc9c5f", GitTreeState:"clean", BuildDate:"2020-11-11T13:17:17Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.1", GitCommit:"206bcadf021e76c27513500ca24182692aabd17e", GitTreeState:"clean", BuildDate:"2020-09-14T07:30:52Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}
Browser: Chrome

@uds5501 have a peak at this diagram - https://docs.google.com/drawings/d/1t40B6sn7RVH3z0ZVOvFD4wxv8YXemyq5JlHugy9_x7A/edit?usp=sharing

Also, give this a shot: docker network connect bridge meshery_meshery_1

@uds5501 you and I have a date on tomorrow's Newcomers call. Let's get you over this hump.
(yes, I said a "date" 😉 )


Support for Cocoapods

Support for Cocoapods would be nice. SPM and Carthage are great, but majority of older projects uses Cocoapods.

Hello @armandsLa , Cocoapods support has been added. Please use 2.2.2 version.
https://github.com/getkevin/kevin-ios/pull/62


Option not to utilize patch files

Describe the bug
Creating the patch file can take x4 the time it takes to generate a new version archive, while the file is marginally smaller.
I am releasing the updates on a raspberry pi 4 which is not a powerful computer but the target device is also a raspberry pi so I am restricted to that device.
Generating a new update archive takes around 10 minutes while the patch can sometimes take over an hour, the difference in the file size is only around 20-30mb. This behavior is consistent across multiple project that we are developing and use tufup.
To Reproduce
Steps to reproduce the behavior:

Create a project on Raspberry Pi
Pack the application with PyInstaller using directory option
Generate update and patch files
See error

Expected behavior
An option to skip the generation of patch files while creating a new release.
Screenshots

System info (please complete the following information):

OS: Raspbian
Python version [e.g.3.10.6]: 3.9

Additional context
python = "3.9.*"
numpy = "1.23.1"
sounddevice = "0.4.4"
tufup = "0.4.8"
pandas = "1.4.3"
pytz = "2022.1"
"RPi.GPIO" = "0.7.1"
spidev = "3.5"
setuptools = "61.0.0"
kivy = {git = "https://github.com/kivy/kivy.git", rev = "2.1.0"}
kivymd = "^1.1.1"

@kubapilch Although I am not strongly opposed to making patches optional, I'm not sure it is necessary in your case.
Perhaps your step 2 ("Pack the application with PyInstaller using directory option") must be done on the RaspberryPi, but, as far as I can tell, your step 3 ("Generate update and patch files") does not need to be done on the Raspberry Pi. You should be able to do that on another system, using the PyInstaller bundle created on the Raspberry Pi in step 2.
Have you tried creating the update archives on a "normal" desktop/laptop system? For example, on my old laptop, creating a diff for a 200MB archive takes up to a few minutes.

@dennisvang My team is using a whole development pipeline that automates a creation of new releases.
PyInstaller bundle has A LOT of small files that make transferring of the app folder over the internet undoable in a reasonable amount of time, doing that with a USB drive kills the whole CD pipeline.
If this is what we have to do, then we will adapt to that, but it would be a nice feature that our team would greatly benefit from.

... it would be a nice feature that our team would greatly benefit from.

@kubapilch The workflow is still not completely clear to me, but it sounds good enough. I'll have a look at adding the option.

... Maybe adding a callback function that will spit out the progress would be a way to go, to indicate that it is not stuck but still generating and how much longer it's going to take.

@kubapilch Thanks for the clarification. Looks like optional patches would indeed be the way to go. I've opened PR #68 so you can follow progress there.
Are you using Repository.add_bundle() directly, or are you using the command line interface?
As for the progress callback, that would be nice indeed, but, we use bsdiff4 and I don't think they provide any hooks to make that possible.

@dennisvang Thanks for such a quick response.

Are you using Repository.add_bundle() directly, or are you using the command line interface?

In our pipelines, we are executing slightly modified python scripts provided by you in the tufup example repository, so that is already solving the problem for us. Adding that to CLI would also be amazing.

As for the progress callback, that would certainly be nice, but, we use bsdiff4 and I don't think they provide any hooks to make that possible.

It is a shame, but fully understandable.

Thanks for the clarification. Looks like optional patches would indeed be the way to go. I've opened PR https://github.com/dennisvang/tufup/pull/68 so you can follow progress there.

I have subscribed to the repository notifications, so as soon as you release it to PyPI we will update our workflow.

@kubapilch After some testing it looks like this works. Note I renamed the make_patch argument to skip_patch, and added a --skip-patch (-s) option for the CLI command: tufup targets add -s ...
I've released v0.4.9, which is now available on PyPi.

Closing this for now. Please let me know if you run into any problems.


Return value of routing.GetDimensions: SwigPyObject not iterable

Hi,
in version 7.2 via Python, there is a call routing.GetDimensions().  How does one use it?  Let's say
r = routing.GetDimensions()

For list(r) I get
TypeError: 'SwigPyObject' object is not iterable

and for r[0] it is
TypeError: 'SwigPyObject' object is not subscriptable

Same for routing.GetAllDimensionNames().  Is there something missing?

These functions are not correctly wrapped, and thus should be removed from
the API.
Le jeu. 11 juil. 2019 à 02:51, sghb<EMAIL_ADDRESS>a écrit :

Hi,
in version 7.2 via Python, there is a call routing.GetDimensions(). How
does one use it? Let's say
r = routing.GetDimensions()
For list(r) I get
TypeError: 'SwigPyObject' object is not iterable
and for r[0] it is
TypeError: 'SwigPyObject' object is not subscriptable
Same for routing.GetAllDimensionNames(). Is there something missing?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1417?email_source=notifications&email_token=ACUPL3MRL45ZVLFJWRCJAV3P637D7A5CNFSM4IA5SD2KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G6STW2A,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3LMDRGA6JZXCCBN4SLP637D7ANCNFSM4IA5SD2A
.

For the time being, as you are creating the dimensions, you can store them in the python program.


Option to Disable OpenAI

Please, allow disabling of OpenAI integration in settings. It is not necessary and superfluous for many use-cases.

https://github.com/usememos/memos/pull/1539#issuecomment-1510027883


expose new message with different schema

Master Issue: #5141
Expose new message with different schema interface, which not required same parameterized type with the producer.
Since the producer and messages sent by it may have different inner types, it's better to have a type agnostic producer interceptor with a checkin method.

run java8 tests


Initialised BDD Testing

Codecov Report

Merging #107 (098e9f1) into main (f4e1969) will decrease coverage by 2.92%.
The diff coverage is 42.85%.

@@            Coverage Diff             @@
##             main     #107      +/-   ##
==========================================
- Coverage   98.02%   95.09%   -2.93%
==========================================
  Files           5        7       +2
  Lines         253      265      +12
==========================================
+ Hits          248      252       +4
- Misses          5       13       +8

Impacted Files
Coverage Δ

service/utils/log_handlers.py
27.27% <27.27%> (ø)

service/routes.py
98.78% <100.00%> (-0.02%)
:arrow_down:

service/utils/__init__.py
100.00% <100.00%> (ø)

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


id in GraphQl query bug for  text/turtle request

When requesting  text/turtle for a set of queries that has id, all queries must have id in their query.
Minimal failing config:
openapi: 3.0.2
info:
  title: Test site
  version: 0.1.0
paths:
  /example:
    get:
      summary: A simple path
      responses:
        '200':
          description: A simple response
          x-walder-input-text/html: template.pug
      x-walder-query:
        graphql-query:
          first: |
            {
              id @single
              comment @single @optional
            }
#adding id @single to this query makes it work correctly
          second: |
            {
              comment @single @optional
            }
        json-ld-context: |
          {
            "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
            "comment": "rdfs:comment"
          }
        datasources:
          sources:
            - http://localhost:8080/example.ttl

RDF source for reference:
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
@prefix owl: <http://www.w3.org/2002/07/owl#>.
@prefix foaf: <http://xmlns.com/foaf/0.1/>.
@prefix odapps: <http://apps4eu.eu/vocab/odapps#>.
@prefix apps4X: <http://semweb.mmlab.be/ns/apps4X#>.
@prefix schema: <http://schema.org/> .
@prefix dct: <http://purl.org/dc/terms/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix time: <http://www.w3.org/2006/time#> .
@prefix geo: <http://www.w3.org/2003/01/geo/wgs84_pos#> .
@prefix lode: <http://linkedevents.org/ontology/> .
@prefix dul: <http://www.loa-cnr.it/ontologies/DUL.owl#> .
@prefix rev: <http://purl.org/stuff/rev#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#>.

# ---------------------------------------- Metadata----------------------------------------------

<http://semweb.mmlab.be/ns/apps4X#>
	a owl:Ontology;
	rdfs:comment "odapps is an RDF vocabulary defined to facilitate the description of Open-Data-based ideas and applications published on the Web.";
	dct:title "The vocabulary for (L)OD ideas and applications"@en;
	dct:issued "2013-05-10"^^xsd:date;
        dct:modified "2013-07-24"^^xsd:date;
	dct:creator [foaf:mbox<EMAIL_ADDRESS>foaf:name "Anastasia Dimou"];
	dct:creator [foaf:mbox<EMAIL_ADDRESS>foaf:name "Pieter Colpaert"].

# ------------------------------------------ Classes --------------------------------------------

# Co-creation Event

# need to decide on the proper word to call it, is co-creation event? is it co-creation competition? is it competition? is it contest?
# or use alternative labels.
# A cocreation event may be an event on its own or it could be a competition in the frame of a broader event
apps4X:CocreationEvent a rdfs:Class ;
	rdfs:subClassOf lode:Event, schema:Event ;
	rdfs:label "Co-creation event" ;
	rdfs:comment "A co-creation event is a competition, a contest, a challenge etc. It's a subproperty as it is an event but with a certain scope" ;
	rdfs:isDefinedBy <http://apps4europe.eu/vocab/apps4X#>  .

# ---------------------------------------- Properties --------------------------------------------

#apps4X:award

#it could be more than one awards offered
apps4X:award a rdf:Property ;
	rdfs:label "award offered" ;
	rdfs:comment "one or more awards offered at this co-creation event" ;
	rdfs:isDefinedBy <http://apps4europe.eu/vocab/apps4X#> ;
	rdfs:domain apps4X:CocreationEvent , apps4X:Jury ;
	rdfs:range apps4X:Award .

We will need the full config file. This is not a full minimal failing example.

We will need the full config file. This is not a full minimal failing example.

Is this ok?

Yes, great!


⚠ Samsung has degraded performance

In 3a8e4ef, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2235 ms

Resolved: Samsung performance has improved in c8cba84.


put bash_autocomplete into .rack directly

Instead of making this ~/rack_bash_autocomplete we should put this in as ~/.rack/bash_autocomplete.
Thoughts?

Agree

Working on this now.

closed by #145


Under the ANGLE_D3D11 backend in Windows Chrome, the official demo displays random flickering noise.

Describe the bug
Under the ANGLE_D3D11 backend in Windows Chrome, the official demo displays random flickering noise. This appears to be a graphical glitch that occurs at irregular intervals.
To Reproduce
Steps to reproduce the behavior:

Set the backend to ANGLE_D3D11(by default).
Open the official demo on Chrome in Windows. https://google.github.io/filament/webgl/suzanne.html
Observe the screen for flickering noise.

Expected behavior
The demo should run smoothly without any flickering or noise. The graphics should be clear and steady.
Screenshots

Logs
FEngine (32 bits) created at 0x16ff30 (threading is disabled) filament.js:8
[WebKit], [WebKit WebGL], [OpenGL ES 3.0 (WebGL 2.0 (OpenGL ES 3.0 Chromium))], [OpenGL ES GLSL ES 3.00 (WebGL GLSL ES 3.00 (OpenGL ES GLSL ES 3.0 Chromium))] filament.js:8
Feature level: 1
Active workarounds: filament.js:8
Backend feature level: 1filament.js:8
FEngine feature level: 1content-script.js:2
SiteAdapters Retry 1/10: not found content-script.js:2
SiteAdapters Retry 2/10: not found content-script.js:2
SiteAdapters Retry 3/10: not found content-script.js:2
SiteAdapters Retry 4/10: not found content-script.js:2
SiteAdapters Retry 5/10: not found content-script.js:2
SiteAdapters Retry 6/10: not found content-script.js:2
SiteAdapters Retry 7/10: not found content-script.js:2
SiteAdapters Retry 8/10: not found content-script.js:2
SiteAdapters Retry 9/10: not found content-script.js:2
SiteAdapters Retry 10/10: not found content-script.js:2
Desktop (please complete the following information):

OS: Windows NT 10.0.19045
Chrome version:Chrome/120.0.6099.130
GPU: NVIDIA GeForce GTX 1060 6GB
Backend: ANGLE_D3D11

Additional context
This issue seems to occur randomly and does not appear to be tied to any specific actions or inputs within the demo. Sometimes it can be observed upon refreshing the page, or when resizing the window. Once it starts flickering, resizing the window might potentially restore it to normal.
Chrome about:gpu page
about-gpu-2023-12-28T04-06-11-023Z.txt

Took a look at the sample and could reproduce it. Refreshing sometimes turns it to normal as the author mentioned.
Also this parquet demo has the same issue. https://google.github.io/filament/webgl/parquet.html


No email notification when admin edits fixture

When an admin edit a fixture, there are no notification emails generated after saving.
Submitted data is however stored in the database.
Log:
BackgroundTask.BackgroundQueue|Exception when executing a IBackgroundTask.  System.InvalidOperationException: Sequence contains no matching element

Same is the case, when an admin edits a result

Resolved with #78


refactor: help prevent accidental breaking change release

Complete each step to get your pull request merged in. Learn more about the workflow this project uses.

[ ] Assign members of your team to review the pull request.
[ ] Wait for pull request status checks to complete. If there are problems, fix them until you see that all status checks are passing.
[ ] Wait until the pull request has been reviewed and approved by a teammate
[ ] After pull request is approved, and you determine it's ready add the label "Ready to merge" to the pull request. A bot will squash and merge the pull request for you after the label is added.

Pull request title looks good 👍. If this pull request gets merged, it will not cause a new release of the software.
Example: If this project's latest release version is 1.0.0. If this pull request gets merged in, the next release of this project will be 1.0.0.
To merge this pull request, add the label Ready to merge to this pull request and I'll merge it for you.

Fails

:no_entry_sign:

Danger failed to run dangerfile.js.

Error SyntaxError
missing ) after argument list
dangerfile.js:8
  warn(`

SyntaxError: missing ) after argument list
    at Object.compileFunction (node:vm:352:18)
    at wrapSafe (node:internal/modules/cjs/loader:1031:15)
    at Module._compile (node:internal/modules/cjs/loader:1065:27)
    at requireFromString (/home/runner/.npm/_npx/dfd88149c9d99ccd/node_modules/require-from-string/index.js:28:4)
    at /home/runner/.npm/_npx/dfd88149c9d99ccd/node_modules/danger/distribution/runner/runners/inline.js:157:68
    at step (/home/runner/.npm/_npx/dfd88149c9d99ccd/node_modules/danger/distribution/runner/runners/inline.js:52:23)
    at Object.next (/home/runner/.npm/_npx/dfd88149c9d99ccd/node_modules/danger/distribution/runner/runners/inline.js:33:53)
    at /home/runner/.npm/_npx/dfd88149c9d99ccd/node_modules/danger/distribution/runner/runners/inline.js:27:71
    at new Promise (<anonymous>)
    at __awaiter (/home/runner/.npm/_npx/dfd88149c9d99ccd/node_modules/danger/distribution/runner/runners/inline.js:23:12)

Dangerfile
---------------------^

  Generated by :no_entry_sign: dangerJS against 0878f5d1beda1dcaf454a5ec89dccd6a5bcaa8ed

:tada: This PR is included in version 1.1.0-alpha.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix Postgres support and miscellania..

Some huge diffs there... did your editor swap tabs and spaces?

Might just be the PEP8-ing (which I had no real excuse for avoiding anyhow). I might get the chance to look at this by EOD.

I'm not against switching, just wouldn't like to see PEP8 diffs mixed in with other code changes, makes it hard to understand.  So if we're switching we should do that in all files, in a new pull.

I don't have a 'de-linter' nor a delta commit with only the linted changes so I would essentially have to re-do the entire PR which I'd rather not go through.
There are two major changes worth noting: first, the split of the configuration file into ini-style for actual configuration and JSON-style for the repo list (with one eye on having a GUI for that part). Second, the use of explicit increment functions for the index columns, as Postgres doesn't do the auto-magic (and non-standard) row increment that sqlite does.

For DBInterface.py, the changes are concentrated in:
lines 57 - 86, as well as 162-164.

One other note, which I mentioned to Todd yesterday and I should maybe put in the readme, but Postgres >= 9.6 is needed for the IF NOT EXISTS clauses to work with CREATE INDEX.

I do understand this is a hassle to review: if you are able to review this PR as-is I will lint the rest of the Python source files and submit them as a separate change.

I can review as-is, and that's a good solution moving forward.
FYI, we'd moved away from providing example config files in this repo mostly because I think it was easier for our deployment mechanism to just keep the production ones separate, but I'm OK with returning to including them now that we have two separate files.

I don't think we should have the example repo config in this code.  It should stay in the ansible template

OK, done reviewing, everything looks pretty good. Just for my own edification I'll retest the SQLite codepaths after I get an answer to the inline comments before merging, but apart from the addition of sys.exit(1) above I don't see anything that'd change the current behaviour. Thanks!

Thanks for the reviews all, I'll re-test with sqlite3 after I do these changes to make sure it still works, which I should have done initially. I won't get everything in until Monday, however. As per a conversation with Todd, I'll go back to tabs on the next commit, but leave the rest of the PEP lint changes in (mostly function spacing and line length), which shouldn't be as bad to review.
@axfelix I had lots of issues with the INSERT INTO ... RETURNING consistently returning me the new row sequence number, and in the same format as sqlite3. I don't know why.
@usask-rc .trann OK on the repo list.

Is the change to HarvestRepository the only thing in the most recent commit that's not spaces to tabs?


Update cmdlets

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@robmazz Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@robmazz can you review this PR?

@MikePlumleyMSFT - these changes were made earlier, closing.


vision model use tp number of gpu

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily receiving feedbacks. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit tests to ensure the correctness.
If the modification has a dependency on downstream projects of a newer version, this PR should be tested with all supported versions of downstream projects.
The documentation has been modified accordingly, like docstring or example tutorials.

May update after #1845 (phi3-vision)

@irexyc may fix conflicts with main branch.


Initial implementation of Timer plugin

Here's my initial implementation of Timer plugin. See the demo page and implementation for more details.
It probably would be possible to tidy up the demo page further by generating HTML needed by the example cases dynamically. Also the actual implementation of timer is a bit crufty as "periodical" doesn't appear to work with methods the way I expected. It might be I just missed something simple. Feel free to clean up. :)

Time to close. :)


Fix: High CPU consumption when the connection is lost.

closes #363

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Disable adding <> to bracket-matcher

It would be ideal if there was a way to disable bracket matching < with > automatically. Right now I have to add the following to the bottom of ~/.atom/config.cson to override the package setting:
".latex.tex.text":
  "bracket-matcher":
    autocompleteCharacters: [
      "$$"
      "``"
      "{}"
      "()"
      "[]"
      "«»"
      "\"\""
      "''"
    ]

Could I ask the rational behind disabling it?
I don't think that this is something that should be brought into the main settings page, as it's a rather niche use case. Tweaking your own config.cson as you have is much cleaner for what you want to achieve.

I guess I'm unaware of the usage of <> as brackets in LaTeX. It seems reasonable to me that they might be more commonly used in typesetting inequalities such as 1<2 than as brackets, since \langle\rangle are the appropriate commands for angle brackets.
The other related issue is the lack of documentation that this package treats them as brackets. I expected $$ but was surprised to see <>, which I don't think appears in any other LaTeX package I've used. If you don't want to expose an option to customize the brackets defined by this package (I don't know how easy that is), it'd be convenient to add a note to the readme about what's being done and how to customize them.

Hmm, makes sense - have disabled the matching of <> and «».
Unfortunately, atom's bracket-matcher doesn't let you distinguish between pairs to auto close, and pairs to wrap selected text with currently, which would have been ideal.


Todo set

What feature would you like?
Todo set pls i cant use it wah
What cog would you like this to be added to? (if new please specify)
ToDo
What is your Discord name? eg. Jojo#7791
Jojo#7791
Additional information
I dunno how this works

Cool cool


Support @JsNullable to signal that a value can be null

Properties, method return types, and method arguments can be marked with jsinterop's @JsNullable to indicate that the value might be null. Without that set, many/most Typescript projects will not permit a null value to be used.
In these cases, the type should be modified to include null (and possibly undefined..?).
Example:
@JsType
public class Foo {
  @JsNullable
  public String name;
  @JsNullable
  public String getString() {
   return null;
  }

  public String getIfNotNull(@JsNullable String value) {
    if (value == null) {
      return "not provided";
    }
    return value;
  }
}

export class Foo {
  name:string|null;
  getString():string|null;
  getIfNotNull(value:string|null):string;
}

It may be more correct to use |null|undefined instead, I'm not sure. It might be better to start with both, and we can simplify to just null later.

There are many new cases of this that I've added to my .d.ts branch in deephaven-core, search for the annotation there.


Cool Crocodiles

It's a shame that the QT designer generates such ugly code, but overall this is a big pull request with lots of interesting stuff going on. I love that you guys are using stuff like pathlib and that you went as far as to make some art for the project. The design document is also a lovely touch.
For the most part, the code is inoffensive, but it does appear to be a bit blocky here and there, and could probably benefit from some extra readability.
Overall a very interesting pull request. Can't wait to test it out on Sunday.

@heavysaturn Thanks for the quick review.
I just want to highlight that our code does use unit tests, but due to the nature of Qt programming most of the methods have side effects, so only a few pure functions are tested.
I posted a patch in code jam chat for integrating unit tests into the Azure build pass/fail but as far as I know ours was the only team to actually do it.
For Sunday, without spoiling anything, all I can say is that it'll launch and run for you, but have fun actually getting into the app... some light reading may be required. This app hates you.


Seems pilot uses non-exist param value in Apple Connect API

fastlane pilot list --api_key_path XX.json --app_identifier "XX" --verbose

Traceback Output

Traceback (most recent call last):
	18: from /usr/local/bin/fastlane:23:in '<main>'
	17: from /usr/local/bin/fastlane:23:in 'load'
	16: from /Users/ben/.gems/gems/fastlane-2.171.0/bin/fastlane:23:in '<top (required)>'
	15: from /Users/ben/.gems/gems/fastlane-2.171.0/fastlane/lib/fastlane/cli_tools_distributor.rb:111:in 'take_off'
	14: from /Users/ben/.gems/gems/fastlane-2.171.0/pilot/lib/pilot/commands_generator.rb:18:in 'start'
	13: from /Users/ben/.gems/gems/fastlane-2.171.0/pilot/lib/pilot/commands_generator.rb:166:in 'run'
	12: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in 'run!'
	11: from /Users/ben/.gems/gems/fastlane-2.171.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in 'run!'
	10: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in 'run_active_command'
	 9: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in 'run'
	 8: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in 'call'
	 7: from /Users/ben/.gems/gems/fastlane-2.171.0/pilot/lib/pilot/commands_generator.rb:114:in 'block (2 levels) in run'
	 6: from /Users/ben/.gems/gems/fastlane-2.171.0/pilot/lib/pilot/tester_manager.rb:76:in 'list_testers'
	 5: from /Users/ben/.gems/gems/fastlane-2.171.0/pilot/lib/pilot/tester_manager.rb:111:in 'list_testers_by_app'
	 4: from /Users/ben/.gems/gems/fastlane-2.171.0/spaceship/lib/spaceship/connect_api/models/app.rb:344:in 'get_beta_testers'
	 3: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/forwardable.rb:230:in 'get_beta_testers'
	 2: from /Users/ben/.gems/gems/fastlane-2.171.0/spaceship/lib/spaceship/connect_api/testflight/testflight.rb:235:in 'get_beta_testers'
	 1: from /Users/ben/.gems/gems/fastlane-2.171.0/spaceship/lib/spaceship/connect_api/api_client.rb:113:in 'get'
/Users/ben/.gems/gems/fastlane-2.171.0/spaceship/lib/spaceship/connect_api/api_client.rb:193:in 'handle_response': A parameter has an invalid value - 'betaTesterMetrics' is not a valid relationship name (Spaceship::UnexpectedResponse)
	18: from /usr/local/bin/fastlane:23:in '<main>'
	17: from /usr/local/bin/fastlane:23:in 'load'
	16: from /Users/ben/.gems/gems/fastlane-2.171.0/bin/fastlane:23:in '<top (required)>'
	15: from /Users/ben/.gems/gems/fastlane-2.171.0/fastlane/lib/fastlane/cli_tools_distributor.rb:111:in 'take_off'
	14: from /Users/ben/.gems/gems/fastlane-2.171.0/pilot/lib/pilot/commands_generator.rb:18:in 'start'
	13: from /Users/ben/.gems/gems/fastlane-2.171.0/pilot/lib/pilot/commands_generator.rb:166:in 'run'
	12: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in 'run!'
	11: from /Users/ben/.gems/gems/fastlane-2.171.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in 'run!'
	10: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in 'run_active_command'
	 9: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in 'run'
	 8: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in 'call'
	 7: from /Users/ben/.gems/gems/fastlane-2.171.0/pilot/lib/pilot/commands_generator.rb:114:in 'block (2 levels) in run'
	 6: from /Users/ben/.gems/gems/fastlane-2.171.0/pilot/lib/pilot/tester_manager.rb:76:in 'list_testers'
	 5: from /Users/ben/.gems/gems/fastlane-2.171.0/pilot/lib/pilot/tester_manager.rb:111:in 'list_testers_by_app'
	 4: from /Users/ben/.gems/gems/fastlane-2.171.0/spaceship/lib/spaceship/connect_api/models/app.rb:344:in 'get_beta_testers'
	 3: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/forwardable.rb:230:in 'get_beta_testers'
	 2: from /Users/ben/.gems/gems/fastlane-2.171.0/spaceship/lib/spaceship/connect_api/testflight/testflight.rb:235:in 'get_beta_testers'
	 1: from /Users/ben/.gems/gems/fastlane-2.171.0/spaceship/lib/spaceship/connect_api/api_client.rb:113:in 'get'
/Users/ben/.gems/gems/fastlane-2.171.0/spaceship/lib/spaceship/connect_api/api_client.rb:193:in 'handle_response': [!] A parameter has an invalid value - 'betaTesterMetrics' is not a valid relationship name (Spaceship::UnexpectedResponse)

fastlane pilot export --api_key_path XX.json --app_identifier "XX" --verbose

Traceback Output

Traceback (most recent call last):
	17: from /usr/local/bin/fastlane:23:in '<main>'
	16: from /usr/local/bin/fastlane:23:in 'load'
	15: from /Users/ben/.gems/gems/fastlane-2.171.0/bin/fastlane:23:in '<top (required)>'
	14: from /Users/ben/.gems/gems/fastlane-2.171.0/fastlane/lib/fastlane/cli_tools_distributor.rb:111:in 'take_off'
	13: from /Users/ben/.gems/gems/fastlane-2.171.0/pilot/lib/pilot/commands_generator.rb:18:in 'start'
	12: from /Users/ben/.gems/gems/fastlane-2.171.0/pilot/lib/pilot/commands_generator.rb:166:in 'run'
	11: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in 'run!'
	10: from /Users/ben/.gems/gems/fastlane-2.171.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in 'run!'
	 9: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in 'run_active_command'
	 8: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in 'run'
	 7: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in 'call'
	 6: from /Users/ben/.gems/gems/fastlane-2.171.0/pilot/lib/pilot/commands_generator.rb:148:in 'block (2 levels) in run'
	 5: from /Users/ben/.gems/gems/fastlane-2.171.0/pilot/lib/pilot/tester_exporter.rb:16:in 'export_testers'
	 4: from /Users/ben/.gems/gems/fastlane-2.171.0/spaceship/lib/spaceship/connect_api/models/app.rb:344:in 'get_beta_testers'
	 3: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/forwardable.rb:230:in 'get_beta_testers'
	 2: from /Users/ben/.gems/gems/fastlane-2.171.0/spaceship/lib/spaceship/connect_api/testflight/testflight.rb:235:in 'get_beta_testers'
	 1: from /Users/ben/.gems/gems/fastlane-2.171.0/spaceship/lib/spaceship/connect_api/api_client.rb:113:in 'get'
/Users/ben/.gems/gems/fastlane-2.171.0/spaceship/lib/spaceship/connect_api/api_client.rb:193:in 'handle_response': A parameter has an invalid value - 'betaTesterMetrics' is not a valid relationship name (Spaceship::UnexpectedResponse)
	17: from /usr/local/bin/fastlane:23:in '<main>'
	16: from /usr/local/bin/fastlane:23:in 'load'
	15: from /Users/ben/.gems/gems/fastlane-2.171.0/bin/fastlane:23:in '<top (required)>'
	14: from /Users/ben/.gems/gems/fastlane-2.171.0/fastlane/lib/fastlane/cli_tools_distributor.rb:111:in 'take_off'
	13: from /Users/ben/.gems/gems/fastlane-2.171.0/pilot/lib/pilot/commands_generator.rb:18:in 'start'
	12: from /Users/ben/.gems/gems/fastlane-2.171.0/pilot/lib/pilot/commands_generator.rb:166:in 'run'
	11: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in 'run!'
	10: from /Users/ben/.gems/gems/fastlane-2.171.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in 'run!'
	 9: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in 'run_active_command'
	 8: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in 'run'
	 7: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in 'call'
	 6: from /Users/ben/.gems/gems/fastlane-2.171.0/pilot/lib/pilot/commands_generator.rb:148:in 'block (2 levels) in run'
	 5: from /Users/ben/.gems/gems/fastlane-2.171.0/pilot/lib/pilot/tester_exporter.rb:16:in 'export_testers'
	 4: from /Users/ben/.gems/gems/fastlane-2.171.0/spaceship/lib/spaceship/connect_api/models/app.rb:344:in 'get_beta_testers'
	 3: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/forwardable.rb:230:in 'get_beta_testers'
	 2: from /Users/ben/.gems/gems/fastlane-2.171.0/spaceship/lib/spaceship/connect_api/testflight/testflight.rb:235:in 'get_beta_testers'
	 1: from /Users/ben/.gems/gems/fastlane-2.171.0/spaceship/lib/spaceship/connect_api/api_client.rb:113:in 'get'
/Users/ben/.gems/gems/fastlane-2.171.0/spaceship/lib/spaceship/connect_api/api_client.rb:193:in 'handle_response': [!] A parameter has an invalid value - 'betaTesterMetrics' is not a valid relationship name (Spaceship::UnexpectedResponse)

All the error message is
A parameter has an invalid value - 'betaTesterMetrics' is not a valid relationship name
Refer to the code here
testers = app.get_beta_testers(includes: "betaTesterMetrics", limit: 200)

https://github.com/fastlane/fastlane/pull/15126#issuecomment-518738734
code here
https://github.com/fastlane/fastlane/blob/03da1cf3bd3fd21a0d14b4209b3f06307acbcb9f/spaceship/lib/spaceship/connect_api/testflight/testflight.rb#L233-L235
https://github.com/fastlane/fastlane/blob/d2419a710e21d5f9cca9b4568426eb0c9e9ad18a/spaceship/lib/spaceship/connect_api/api_client.rb#L90-L102
And the official document here.
https://developer.apple.com/documentation/appstoreconnectapi/list_users
I doubt the "include" parameter can only be the value of "visibleApps"?
But, the endpoint of "betaTesters" seems to be here, which has no official document.
https://appstoreconnect.apple.com/iris/v1/betaTesters
So, how to fix this basic action?
✅ fastlane environment ✅
Stack

Key
Value

OS
11.1

Ruby
2.6.3

Bundler?
false

Git
git version 2.29.2

Installation Source
/usr/local/bin/fastlane

Host
macOS 11.1 (20C69)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib

OpenSSL Version
LibreSSL 2.8.3

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
12.3

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:ios)

platform :ios do
  desc "Description of what the lane does"
  lane :custom_lane do
    # add actions here: https://docs.fastlane.tools/actions
  end
end

lane :release do
  app_store_connect_api_key(
    key_id: "XX",
    issuer_id: "XXX",
    key_filepath: "./XXX.p8",
    duration: 1200, # optional
    in_house: false, # optional but may be required if using match/sigh
  )

  # Automatically loads Actions.lane_context[SharedValues::APP_STORE_CONNECT_API_KEY]
  #pilot
  # pilot list
  # pilot(ipa: "./XX.ipa")
  username=<EMAIL_ADDRESS>  sh("fastlane pilot export")
  sh("fastlane pilot builds")
  sh("fastlane pilot list")
end

lane :release2 do
  sh("fastlane pilot list --api_key_path XX.json")
end

`./fastlane/Appfile`
# app_identifier("[[APP_IDENTIFIER]]") # The bundle identifier of your app
# apple_id("[[APPLE_ID]]") # Your Apple email address

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.171.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.3.0

slack-notifier
2.3.2

atomos
0.1.3

claide
1.0.3

colored2
3.1.2

nanaimo
0.3.0

xcodeproj
1.19.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

public_suffix
4.0.6

addressable
2.7.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

babosa
1.0.4

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.78.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.7

faraday_middleware
1.0.0

gh_inspector
1.1.3

mini_magick
4.11.0

rubyzip
2.3.0

security
0.1.3

dotenv
2.7.6

bundler
1.17.2

naturally
2.2.0

simctl
1.6.8

jwt
2.2.2

uber
0.1.0

declarative
0.0.20

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mini_mime
1.0.2

multi_json
1.15.0

signet
0.14.0

memoist
0.16.2

os
1.1.1

googleauth
0.14.0

httpclient
2.8.3

google-api-client
0.38.0

emoji_regex
3.2.1

CFPropertyList
3.0.3

plist
3.6.0

ruby2_keywords
0.0.2

faraday-net_http
1.0.0

faraday
1.3.0

fastimage
2.2.1

json
2.5.1

xcpretty-travis-formatter
1.0.1

rake
13.0.3

digest-crc
0.6.3

google-cloud-errors
1.0.1

google-cloud-env
1.4.0

google-cloud-core
1.5.0

google-cloud-storage
1.29.2

aws-eventstream
1.1.0

aws-sigv4
1.2.2

aws-partitions
1.414.0

jmespath
1.4.0

aws-sdk-core
3.110.0

aws-sdk-kms
1.40.0

aws-sdk-s3
1.87.0

forwardable
1.2.0

logger
1.3.0

date
2.0.0

stringio
0.0.2

zlib
1.0.0

ipaddr
1.2.2

openssl
2.1.2

ostruct
0.1.0

strscan
1.0.0

fileutils
1.1.0

etc
1.0.1

io-console
0.4.7

libxml-ruby
3.1.0

rexml
3.1.9

psych
3.1.0

mutex_m
0.1.0

generated on: 2021-01-04

I'm seeing this too when using the API key for authentication. Similar to https://github.com/fastlane/fastlane/issues/17821#issuecomment-770468463

I am having the same issue trying to export the tester CSV

The same for pilot list using API authentication.

I'm having this issue when trying to export the CSV though the API key authentication

Still relevant in fastlane-2.187.0 with fastlane pilot list, fastlane pilot import with API Key auth.
fastlane pilot export works good

I'm also still seeing this in 2.187.0

Still present in 2.189.0

Bump

Still present in 2.198.1

This similar ticket indicates that these commands are not available with a keyfile. https://github.com/fastlane/fastlane/issues/18650
If this is the case, Fastlane might provide a more informative error.

Still present

Is there any workaround for this issue?
Thanks,
Markus

Confirmed I still encounter this on 2.205.0

I still have this with 2.205.2


Review current status of code generation.

Objective
Its been a few weeks since we looked at the code gen project.  Let's all take a refresher of what is happening in that project so we know where its at.

This has been completed during a mob session or two.


Drag into project, then swift compile error

Problem : Swift compiler error in TagView .

I use cocoaPods in my project, but I need some customize in TagListView.
So I drag TagListView folder in my project. Then Swift compiler error... ( use Swift 4.1)

I create a folder references, then swift compile pass.

What do you mean "Swift Compile Error"? Fails to compile TagListView?

I drag TagListView into my project, then build it.  The Errors show up.

I guess there are some dependences issue in my project. Because I create a new project, it is work perfect.

Could you provide the smallest sample project which would cause this error?

I found the reason. I use SwifterSwift in my project.
SwifterSwift is installed by CocoaPods and  is global in my project.
It's cause overriding non-open var outside of its defining module in TagView.
I can not reproduce the global SwifterSwift to show the problem.
I only can import SwifterSwift in TagView to reproduce the error.
Error_Sample.zip

@CACRogerWang Could you use CocoaPods to manage all of your external packages?

If you need to customize a package, just fork it and push your changes to your fork.
You can specify git repo in the Podfile, as documented here.


Please refund me for Bootstrap Theme

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the contributing guidelines

Proposal
Dear Bootstrap Team,
I have been attempting to contact the creator of the Bootstrap Theme and the Bootstrap Marketplace, including through<EMAIL_ADDRESS>and their online form, without success. As a dissatisfied customer, this is my last resort to reach out to you.
My concerns include the lack of documentation, no response for technical support, and various issues with the code in the theme. Therefore, I kindly request a refund for Order #154715.
Thank you for your understanding.
Sincerely,
Onlineoj on GitHub
Motivation and context
I kindly request a refund for Order #154715.

Hey there, super sorry to hear about the poor experience, but this isn't the place for Themes support—none of the maintainers here have access to Themes or the billing/order information of them.


Add debouncing to subscription

Notes for Reviewers
This PR fixes #
The root cause of context polling issue seems to arise from the k8sSubscription itself ,  it is continuosly returning an updated version of the config ,  we prev fixed the comparison for checking if config is updated and it has reducted a few of the queries but in playground the config is really getting updated  frequently . (which  might have something to do with it being used by multiple player , not sure) . which then later invalidates the subscriptions to clusterresources other related ones inside the dashboard .   FY : the part of the config that gets changed is the context's updated_at field
I have debounced the callback for updating the config in subscription to 2sec for now which should slow down things for now . config is updated only inside the callaback .
Signed commits

[ ] Yes, I signed my commits.

this is continuosly sending updated contexts :

@MUzairS15 did we figure out what do here?

I went through the k8s subscription and server notifies the UI only in case of

When contexts are loaded and persisted from the config. (LoadAndPersist function)
User manually add or delete the context (KubeconfigHandler and DeleeKubeconfig)

Let's discuss this on the Meshery dev call tomorrow,
Please add this as your agenda item in Docs: https://docs.google.com/document/d/1Dg4Uz9rGTuGHmYZwIt47z1j5x3LmnpxD1M1SgypAkQ0/edit

Close?

yup


Inconsistent remapping detection

➜ forge remappings --lib-paths lib/
ds-test/=lib/ds-test/src/
standards/=lib/standards/src/
src/=lib/openzeppelin/src/
➜  ls lib
ds-test/src      openzeppelin/src standards/src    uniswapv2/src

Given multiple folders structured as dapptools libraries in lib/, forge only detects some, and of those, names some incorrectly.

just to confirm, this happens with master?

I just pulled a fresh install with cargo install --git https://github.com/gakonst/foundry --bin forge --locked and can reproduce.

I see, could you attach ls lib/**/*.sol?

Sure, any openzeppelin interface works lib/openzeppelin/interfaces/IERC1155.sol for example.

Here are the libraries.

Thanks,
oh ofc, I forgot to account for interfaces folders, guess I'll rewrite the remappings detection again. This turned out to be quite tricky actually, because we're trying to make this work with dapptools and node_modules deps a like.
By now I should have a better picture of possible edge cases to make this robust.

good catch - thank you @alcibiadeseth.
remappings detection that's robust across dir structures has indeed been tricky, hopefully we'll get to something robust soon..

Thanks, as always, guys. I'm always mind blown how quickly you guys respond to my QA issues :) cheers!

I am going to close this given the new readme and ability to detect remappings installed in that way.


Invalid URI "/services/data/v32.0/sobjects/Contact/describe"

jsforce has mostly been working correctly. However, I've been hitting this error lately and I'm not sure what's going on.
Here's my connection setup:
self.conn = new jsforce.Connection({
  instanceUrl: card.get('instanceUrl'),
  accessToken: card.get('accessKey'),
  refreshToken: card.get('refreshToken'),
  oauth2: {
    clientId: config.consumerKey,
    clientSecret: config.consumerSecret,
    redirectUri: config.redirectUrl
  }
});

And my query that errors out:
self.conn.sobject('Contact')
  .find({ OwnerId: self._sid })

Stack trace:
Unhandled rejection Error: Invalid URI "/services/data/v33.0/sobjects/Contact/describe"
  │   at Request.init (/Users/daniel/Projects/stacks/node_modules/request/request.js:413:31)
 |│   at new Request (/Users/daniel/Projects/stacks/node_modules/request/request.js:264:8)
 9│   at request (/Users/daniel/Projects/stacks/node_modules/request/index.js:50:10)
5m│   at /Users/daniel/Projects/stacks/node_modules/request/index.js:141:14
s │   at createRequest (/Users/daniel/Projects/stacks/node_modules/jsforce/lib/transport.js:88:13)
  │   at [object Object].promise.then (/Users/daniel/Projects/stacks/node_modules/jsforce/lib/transport.js:41:5)
  │   at [object Object].HttpApi.request (/Users/daniel/Projects/stacks/node_modules/jsforce/lib/http-api.js:70:47)
  │   at [object Object].Connection.request (/Users/daniel/Projects/stacks/node_modules/jsforce/lib/connection.js:320:18)
  │   at [object Object].Connection.describe.Connection.describeSObject (/Users/daniel/Projects/stacks/node_modules/jsforce/lib/c
  │nnection.js:845:15)
  │   at [object Object].$fn (/Users/daniel/Projects/stacks/node_modules/jsforce/lib/cache.js:199:10)
  │   at describeCache (/Users/daniel/Projects/stacks/node_modules/jsforce/lib/query.js:535:10)
──┤ at expandAsteriskField (/Users/daniel/Projects/stacks/node_modules/jsforce/lib/query.js:547:7)
- │   at /Users/daniel/Projects/stacks/node_modules/jsforce/lib/query.js:507:50
[n│   at Function._.map._.collect (/Users/daniel/Projects/stacks/node_modules/underscore/underscore.js:164:24)

Thoughts?

The error message seems the connection cannot build URL for API request. Confirm that card.get('instanceUrl') surely has the instance URL (e.g. https://na1.salesforce.com).

@stomita ahh, that was it. Thanks!