text2image needs pango_training.so which in turn is not installed

Current Behavior
text2image needs pango_training.so which in turn is not installed
Expected Behavior
pango_training.so  installed.
Suggested Fix
https://github.com/tesseract-ocr/tesseract/blob/main/src/training/CMakeLists.txt#L405-L412
TARGETS text2image

change to:
TARGETS text2image pango_training

tesseract -v
No response
Operating System
Ubuntu 22.04 Jammy
Other Operating System
Android
uname -a
Linux leleliu008 6.5.0-28-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 28 23:46:48 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Compiler
Android NDK r26d (clang version 17.0.2)
CPU
aarch64
Virtualization / Containers
No response
Other Information
source: https://github.com/tesseract-ocr/tesseract/archive/refs/tags/5.3.4.tar.gz

Did you build Tesseract yourself (if yes: how)? And how did you install it?

I am curious:
Are there useful applications for training on Android?
And how did you create that nice dependency diagram?

Are there useful applications for training on Android?

I found this when I built it for Android, I think this problem is nothing to do with specific platform.

And how did you create that nice dependency diagram?

I create it in dot https://graphviz.org/doc/info/command.html

I found this when I built it for Android, I think this problem has nothing to do with a specific platform.

Why do you try to build training tools if you are not able/want to use them on your platform? Just to get extra issues?

I din't give you the reproduce steps, because it is very clear if you look at the source code https://github.com/tesseract-ocr/tesseract/blob/main/src/training/CMakeLists.txt#L405-L412

I see no reason why to install pango_training:
$ ldd build/bin/text2image | grep -i pango
        libpangocairo-1.0.so.0 => /lib/arm-linux-gnueabihf/libpangocairo-1.0.so.0 (0xb6660000)
        libpango-1.0.so.0 => /lib/arm-linux-gnueabihf/libpango-1.0.so.0 (0xb65f0000)
        libpangoft2-1.0.so.0 => /lib/arm-linux-gnueabihf/libpangoft2-1.0.so.0 (0xb3980000)

The reason is very simple - the official build process for training tools uses static linking.

If you want to static linking, you should change add_library(pango_training ${pango_training_src}) to add_library(pango_training STATIC ${pango_training_src})

It a feature not a bug, so I'm closing.


Android bundle can't read .env file

I'm using react-native-dotenv for my Android app. When building a debug or even a release apk, my app reads the env variables correctly. All works fine. The problem is when building the bundle .aab (that one  submit in Play Store). When I download my app from Play and install it my app can't read env variables! So why it is working good with debug/release apk and not with bundle .aab? Why this happens and how to fix it?
My babel.config.js
    plugins: [
      [
        'module:react-native-dotenv',
        {
          moduleName: '@env',
          path: '.env',
        },
      ],

I use an .env file and an .env.development file
and import my env vars like this
import {MY_ENV} from '@env'

I'm using the react-native-dotenv 3.1.1, RN 0.63.3 (bare workflow) and EXPO EAS for building the bundle.

IssueHunt Summary

Backers (Total: $2.00)

$2.00 have been anonymously funded.

Become a backer now!
Or submit a pull request to get the deposits!
Tips

Checkout the Issuehunt explorer to discover more funded issues.
Need some help from other developers? Add your repositories on IssueHunt to raise funds.

Hey, thank you for opening this issue! 🙂 To boost priority on this issue and support open source please tip the team at https://issuehunt.io/r/goatandsheep/react-native-dotenv/issues/302

Done. Hope you can help me with this.

Have you tried making sure your build.gradle has the productFlavors and stuff setup? https://medium.com/@ywongcode/building-multiple-versions-of-a-react-native-app-4361252ddde5

Thanks for quick response. No I didn’t know that, I’m new using this. Read the article but how to setup in order to work on bundle? So I need to add flavorDimensions "default" but how to setup productFlavors for the bundle (.aab). Mine is like below
    buildTypes {
        debug {
            signingConfig signingConfigs.debug
        }
        release {
            // Caution! In production, you need to generate your own keystore file.
            // see https://reactnative.dev/docs/signed-apk-android.
            signingConfig signingConfigs.debug
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
        }
    }

debug is going to be develop and release is going to be production. this is unless you use APP_ENV

I’m not using the APP_ENV prop. So adding flavorDimensions "default" and using the productFlavors {} with that configuration above should be working?

And do I need to use a .env.production file or using the .env.development and .env like I’m using currently is fine just fine?

It should follow dotenv flow priority to some extent https://www.npmjs.com/package/dotenv-flow#variables-overwritingpriority

Yes app_env is not necessary for most applications

It should follow dotenv flow priority to some extent https://www.npmjs.com/package/dotenv-flow#variables-overwritingpriority

Thanks again, man. So makes no difference using .env.production, it’s just for merging and priority. So do think that this problem with bundle could be related because I’m using Expo EAS for bundling? Have you ever use eas along with your package?

I have. Try taking a look at this example https://github.com/goatandsheep/chatkitty-example-react-native

I'm not sure? Try taking a look at this example https://github.com/goatandsheep/chatkitty-example-react-native

Mmm, my app is a bare workflow, not managed, have you tried with eas+bare workflow+react-native-dotenv? I’m seeing some people with same issue but no proper answer, so I’m not the only one.

I don't know...is it possible to provide a simple example repo so I can figure it out with you?

@hadnet Have you figured out what caused the issue? I think I am having the same problem here.

@hadnet Have you figured out what caused the issue? I think I have the same problem: environment variables are undefined when I install the .apk extracted from an .aab file

Sadly, nope! I really wish the library author had tested it with .aab, but unfortunately they didn't or just don't care. But if you manage to, I would really appreciate it if you let me know!

Hi @hadnet how does .aab work? Do you have an example repo?

Hi @hadnet how does .aab work? Do you have an example repo?

Sorry, nope. I don't have time now, but you, as the author, could create a simple project, generate the .aab file, and confirm that all envs remain undefined and try to fix this issue.

@goatandsheep For my project, I followed the process described here to create an Android app Bundle (.aab file) locally and extract the .apk from it
I use this process to build and install the Android version of my app for myself without having to publish it to the Play Store
While it's not exactly the same as publishing the app to the Play Store and obtaining the .aab from there, I think that my issue might be similar - environment variables cannot be loaded (I logged them in my app's JavaScript bundle and observed the log output with logcat -> undefined is returned)
Interestingly, environment variables do work fine when sideoloading the iOS build of my app onto my iPad

If you pay attention, I contributed $2. I'm from a third-world country, and dollars are not something small here. Just so you know, I lost my job because of this issue. So, what you're saying doesn't make any sense. I also help and contribute to the RN community in any way I can. I’m just saying that you need to be more careful when you publish final packages, test all cases like this or at least make a note. Just that.

I appreciate any and all contributions @hadnet .  Thank you! I have also updated my sample app https://github.com/goatandsheep/react-native-dotenv-expo-test
I am pushing for additional Expo updates but will also update this repo this month

Getting the same issue here too. For some reason android doesn't apply environment variables. The project I'm a part of will be launching soon and the workaround we found was just to hardcode the values. Everything will have to be changed later on but please a fix would be wonderful

@michaelessiet sorry to hear. Can you provide any example code? I haven't been able to create any example projects that didn't work

any news on this issue? because I have the same issue in my project :O ? I Can see that the expo build is picking up the values from env but when aab is compiled on android store , the aab file is not picking the values :O ? that wierd!

I have issue "Unable to resolve "@env" from "App.js"" looks like this project is no more maintained

@kriit24 no this project is being maintained. I haven't received any code examples of this not working. Is the library installed as devDependency or production dependency?

@moedeveloper I'll check again locally to see if the android bundle uses the environment values

This is an aab file I generated using the library. Do you see the result?
release.zip

@hadnet this template of yours shows react-native-dotenv installed as a production dependency. Please make sure that it is installed as such
https://github.com/hadnet/superb-rn-ts-template/blob/94efa068c38d086f711576c254efa70cd003b6f4/template/package.json
For everyone else, for your builds:

clear cache: either api.cache(false) in babel.config.js or --reset-cache
If you're using APP_ENV you cannot use development or production
Make sure your babel is configured properly with the plugin


Rate Limiter Bugfix

When using the rate limiter feature, responses from the API calls would break because glutton_ratelimit#times returns the number of times a block is repeatedly called.
I have it now returning the result of the block instead.
Please see Issue #67 for details.

@hebron-george Thank you for your help! If you can revert those cosmetic changes it would be great!
We have a Rubocop config here in Mikamai and I'll it to this repo ASAP!

@oeN done!


[Feature request] Refresh File

Is your feature request related to a problem? Please describe.
The problem is the when the file is externally modified, there is no way to refresh to get the most updated information. Currently, notepads would just inform that the file has been externally modified and user can only reopen the file which is annoying. For example, when modifying it through certain codes.
Describe the solution you'd like
The solution would be similar to notepad++. When the file is externally modified. There will be pop up menu that asks the user if you would like to reload the text file.
Describe alternatives you've considered
Another solution would probably just be having a shortcut key to refresh the file such as CTRL + R.
Thank you for your time.

Click on the file path and here you go:

The reason I am not forcing a pop-up window is simply because it is too annoying. As you already see, Notepads will notify you for the external edit. If you want to reload, just click the button in the above screenshot. Or Ctrl+Shift+R.

Oh wow! I didn't know you could click on the path! Yes, I agree that the pop up window is so super annoying. This is much better especially with a hotkey! I didn't know the bottom right texts can be clicked too! Amazing! Thank you so much for your time!


Discover data patterns by investigating leaf training samples

Generally speaking, ML trained models can be used to both make predictions and/or to better understand our data.
Until now, we have created visualisations for histogram of classes in leaves, split plots for the regressor leaves, but we don't have a way to find out more about training samples reaching those leaves.
I think it will be useful to have a method to return the leaf training examples and maybe some general stats about them.
Bellow, I have attached a screenshot with get_node_samples() from my library. I guess it could be pretty easy integrated in dtreeviz, taking in consideration that there is already built-in functionality to take the samples from a leaf.

I agree that get_node_samples() functionality would be useful but I think we already have in shadow.py:
    @staticmethod
    def node_samples(tree_model, data) -> Mapping[int, list]:
        """
        Return dictionary mapping node id to list of sample indexes considered by
        the feature/split decision.
...

I'd like to see more interpretation stuff that explained the path from the root down to the leaf. I.e., explain(test_vector) would tell me lots about why it gets the prediction it gets.  Perhaps we can add counterfactuals to indicate how to tweak a given record in order to make it select a particular class such as "give loan" or "do not predict cancer"

I agree that get_node_samples() functionality would be useful but I think we already have in shadow.py:
    @staticmethod
    def node_samples(tree_model, data) -> Mapping[int, list]:
        """
        Return dictionary mapping node id to list of sample indexes considered by
        the feature/split decision.
...

Nice, good to know :). I will add few examples of it in notebooks (will help also to make it more visible)

I'd like to see more interpretation stuff that explained the path from the root down to the leaf. I.e., explain(test_vector) would tell me lots about why it gets the prediction it gets. Perhaps we can add counterfactuals to indicate how to tweak a given record in order to make it select a particular class such as "give loan" or "do not predict cancer"

I have two types of visualisations for prediction path interpretation, but they require a facelift :))
Would be nice to keep the same visualisation as dtreeviz(), but to show only the prediction path. I will take a deeper look at how dtreeviz() is implemented and maybe I can adapt it to prediction path.

well, it already does the prediction path; you can take a look at the examples. It just doesn't combine all of the decision nodes into some readable English text that explains why somebody did not get their loan.  The decision trees we have already show those histograms so I think everything is already incorporated that you mention. :)

well, it already does the prediction path; you can take a look at the examples. It just doesn't combine all of the decision nodes into some readable English text that explains why somebody did not get their loan. The decision trees we have already show those histograms so I think everything is already incorporated that you mention. :)

yes, indeed. I was aware of it, but I thought that you mean a visualisation only for nodes from prediction path...

It just doesn't combine all of the decision nodes into some readable English text that explains why somebody did not get their loan.
I will think what we can do here. If you have any suggestions, let me know ;)

Oh right! Yes, a way to turn off non-prediction path nodes would be a useful option to the visualizer. should be a simple new boolean like "show_just_path" that works if they pass in a sample test record.  It would turn off the orange highlighting and just show the nodes on the path.

it will help especially if the tree is very deep.

We could summarize the "weight" of each  feature used to get through the path. currently i just highlight the feature in orange in test vector. We could use "avg contribution". see https://christophm.github.io/interpretable-ml-book/tree.html#interpretation-2

We could summarize the "weight" of each feature used to get through the path. currently i just highlight the feature in orange in test vector. We could use "avg contribution". see https://christophm.github.io/interpretable-ml-book/tree.html#interpretation-2

I guess this is a possible solution for "It just doesn't combine all of the decision nodes into some readable English text that explains why somebody did not get their loan." . Right ?
Thanks for the link. It seems like a book to read.

Yep. the link shows how to compute "gini drop" importance for a single instance. also i wonder if just combining all decisions < and > into a single range per feature could be useful.  I.e., "your income was in this range" and your education was in this range...

Ah. I think this RuleFit alg is what I'm thinking: https://christophm.github.io/interpretable-ml-book/rulefit.html https://arxiv.org/abs/0811.1679

Ah. see this stuff http://blog.datadive.net/interpreting-random-forests/

Also see https://scikit-learn.org/stable/auto_examples/tree/plot_unveil_tree_structure.html which shows how to do English descriptions like:
Rules used to predict sample 0:
decision id node 0 : (X_test[0, 3] (= 2.4) > 0.800000011920929)
decision id node 2 : (X_test[0, 2] (= 5.1) > 4.950000047683716)

hi @parrt. I added to tree_structure_example notebook few leaf sample investigations (created a PR also #76 ).
It looks something like that :

Right now to get the leaf samples, we need the following code :
node_samples = ShadowDecTree.node_samples(dtc, dataset[features]) dataset[features + [target]].iloc[node_samples[58]].describe()
It seems a little to much... I would like to wrap-up all the details into a method, something like this :
describe_node_sample(node_id=58, dataset[features]).
What is your opinion ? :)

looks great!  Hm...yeah, but don't we need the model in there? describe(mytreemodel, node_id, dataset[features])

yes, we need also the model as a parameter :)


[$500]  Invite members - blank row is displayed when removing user in offline mode

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v1.4.44-0
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal Team
Action Performed:

Navigate to 'Invite members' page of a workspace
Invite a user
Apply offline mode
Removed the user

Expected Result:
There shouldn't be any blank rows
Actual Result:
There is a blank row after removing the user
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/3a19f2de-45e6-4fb6-a0fd-3cd7e441594a
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01b21db9a428272553
Upwork Job ID:<PHONE_NUMBER>499994624
Last Price Increase: 2024-02-26

We think that this bug might be related to #wave8-collect-admins
CC @zanyrenney

This is a dupe of https://github.com/Expensify/App/issues/37109. Gonna close since it's known and we're working on fixing it when we implement the remove functionality in Simplified Collect.


Code Quality: Assign background/border properties in respective controls

Summary
This makes the app content area look more appropriate when the window a bit stuck or hang on startup because background and border will be rendered actually loaded. Previously Inner toolbar background are rendered without inner controls are loaded, before it actually loaded.

Assign background/border properties in respective controls
Unwrap from Border element
Removed unnecessary assignments to d:DesignHeight, d:DesignWidth, TabStripVisibility (always true) and so on.

Resolved / Related Issues
To prevent extra work, all changes to the Files codebase must link to an approved issue marked as Ready to build. Please insert the issue number following the hashtag with the issue number that this Pull Request resolves.

Closes #

Steps used to test these changes
Stability is a top priority for Files and all changes are required to go through testing before being merged into the repo. Please include a list of steps that you used to test this PR.

Open Files app
See no crash and visual change

I wonder if this wrapping by Grid is necessary and we should create one more row definition at the root Grid.
Removing visual tree element should help improve loading on startup.


fixed "this.log" => "console.log"

Errors:

this.log('This iteration's data length was different from the first.');
this.log(iterations: ${ this.i}, training error: ${ error });

Why?
"this.log" is not a function, it's boolean (inherited from "trainOpts.log")

This is incorrect.  This.log, is being checked for truthy.  It is a boolean or a function.

But also, ty for your hard work investigating.  I grappled with this when I first looked at the code as well.

Hi Robert,
according to this:
Training Options
train() takes a hash of options as its second argument:
net.train(data, {
// Defaults values --> expected validation
iterations: 20000,    // the maximum times to iterate the training
data --> number greater than 0
errorThresh: 0.005,   // the acceptable error percentage from
training data --> number between 0 and 1

 log: false,           // true to use console.log, when a function is

supplied it is used --> Either true or a function*
logPeriod: 10,        // iterations between logging out --> number
greater than 0
learningRate: 0.3,    // scales with delta to effect training rate
--> number between 0 and 1
momentum: 0.1,        // scales with next layer's change value -->
number between 0 and 1
callback: null,       // a periodic call back that can be triggered
while training --> null or function
callbackPeriod: 10,   // the number of iterations through the
training data between callback calls --> number greater than 0
timeout: Infinity     // the max number of milliseconds to train for
--> number greater than 0
});
it is misaligned with this:
// inherit trainOpts settings from neuralNetwork
neuralNetwork.updateTrainingOptions(options);
const { trainOpts } = neuralNetwork;
this.iterations = trainOpts.iterations;
this.errorThresh = trainOpts.errorThresh;
this.log = trainOpts.log;
this.logPeriod = trainOpts.logPeriod;
this.callbackPeriod = trainOpts.callbackPeriod;
this.callback = trainOpts.callback;
so, if *this.log *is *false OR a method *you are right, but if it is true,
you are wrong because it should use console.log.
In my pull request the case was:
this.log = true
so the following lines:
this.log(iterations: ${ this.i}, training error: ${ error });
and
this.log('This iteration's data length was different from the first.');
give error.
happy coding buddy!
M
On Tue, Feb 19, 2019 at 12:00 PM Robert Plummer<EMAIL_ADDRESS>wrote:

This is incorrect. This.log, is being checked for truthy. It is a boolean
or a function.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/BrainJS/brain.js/pull/361#issuecomment-465086140, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGuxeBJei_XYu7MjA3fjAt0onY6DlmZLks5vO9logaJpZM4a_DjU
.

Could you abstract this function for reuse perhaps, and reuse?: https://github.com/BrainJS/brain.js/blob/8455336e274277f571b236d98732b9f0890f5e63/src/neural-network.js#L368

The method is abstract enough, but in train-stream you have the neural
network object as property.
Inside the neural network the method is called, outside not.
const { trainOpts } = neuralNetwork;
should be
const { trainOpts } = neuralNetwork.trainOpts;
in a case like:
const config = { binaryThresh: 0.5, hiddenLayers: [3], activation:
'sigmoid', leakyReluAlpha: 0.01, trainOpts: { log: true } }; const net =
new brain.NeuralNetwork(config);
:)


Allow Expanding Search Result Items To Show More Details

Clicking on the arrow button will expand a result item to show its details.

Added in pds-wds-react: https://github.com/NASA-PDS/wds-react/commit/4541099c28c8fe8cd56de5cd62cd9a3f3d6c58ef

Going to call this task complete for now and review will occur we close out its parent epic #26

Hi @eddiesarevalo , can you add an estimate for this ticket ? Thanks


Add a requirements file for multi-backend cuda

Not totally sure if we should merge this now, or wait for tf 2.14, but figured I could put it up anyway so people could use it. With https://github.com/tensorflow/tensorflow/pull/59825 tf-nightly can be installed using cuda pip packages. Which means we can write a recipe for cross framework GPU support.
To install a local development version...
pip install -r requirements-cuda.txt
python pip_build.py --install

To install the official pip version...
pip install -r requirements-cuda.txt
pip install keras-core --no-deps

Note that --no-deps is required to avoid pulling in tensorflow and tf-nightly at the same time.
This should work in a clean python env, as long nvidia drivers are >= 520. No conda or cuda shenanigans required!

Thanks! This is great. I actually edited the requirements.txt earlier, please fix the conflicts.


adds notification whenever home location is changed

Now we're updating the home_location from messages we can reasonably add attribute notification. Obviously this won't work before notification messages were added (we probably should add documentation to state that, rather than just saying "notification not supported".
This fixes minor bug in #646

@peterbarker @mrpollo Please review and push in.

lgtm, :+1:


fix(build-config): inline core-js polyfills in bundled Node.js code

Would you mind rebasing with latest master..?

@dmbch rebased and removed direct dependency to core-js.


HTTP/2 remove unnecessary buffer operations

Motivation:
codec-http2 has some helper methods to write to ByteBuf in a big endian fashion. This is the default memory structure for ByteBuf so these helper methods are not necessary.
Modifications:

remove writeUnsignedInt and writeUnsignedShort

Result:
codec-http2 has less ByteBuf helper methods which are not necessary.

@Scottmitch ship it

4.1 (36c6a61)


Encoding performance improvements

Make significant performance improvements to BytesToHexIter and DisplayHex, see individual commits for details on the exact performance improvements.
Also deletes fn byte_to_hex_chars as it was repeating the functionality offered by Table::byte_to_hex.

This breaks #113, so I mark it as draft until #113 is merged, happy to be patient.
Please see https://github.com/tankyleo/hex-benchmarks for how I got the "Estimated Cycles" numbers in the commit messages.
Thank you for your time and feedback.

The second patch I'm ambivalent on, we typically try to avoid casts but in that case its super obvious what is going on. The char casting would be better done with char::from IMO.

I understand. Upon further thought, I'd be happy to drop the casts, and use from everywhere.

Rebase:

Drop all casts, replace with from.
Rename variables for clarity.
Name the return type explicitly for clarity.

Nice, thanks. Did your github username change? I got confused seeing patches with a familiar name/email address for the author with a different username.

I mark it as ready in case you'd like to merge this before #113

You can nominate your merge order preference if you want to.

@tcharding your call. I have a preference for #117 first. It seems to me kix might want to review #113 before it goes in, as he had some concerns in a prior PR.

He has had two weeks already I believe. @apoelstra is the merger round here though so he will take care of the order. Cheers.

Nice. Will do this one.
cc @RCasatta you might be interested in trying this on your profiling.

cc @RCasatta you might be interested in trying this on your profiling.

In https://github.com/rust-bitcoin/hex-conservative/issues/115 I am interested in the opposite conversion, but thanks a lot for citing me, very nice perf improvement and TIL iai


Remove #[unstable], #[stable], and #[deprecated] attributes

Fixes error: stability attributes may not be used outside of the
standard library

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see CONTRIBUTING.md for more information.

Thanks!


position absolute instead of fixed so its positioned with respect to parent

All the elements are position: fixed in excalidraw App. This. makes it difficult to render when used inside the host App. So. I changed it to absolute so it's positioned relative to its parent instead of viewport
cc @dwelle

The bottom left zoom menu seems to have regressed a bit (no left padding). Other than that, seems fine.

The bottom left zoom menu seems to have regressed a bit (no left padding). Other than that, seems fine.

good catch @dwelle. Fixed it.

thx


Desktop search broken in Safari

Hello,
Apple M1 8 Go
macOS Ventura 13.0.1
Safari Version 16.1 (186<IP_ADDRESS>.12)
Search is broken in safari, no result is displayed while in Chrome it works fine.
The first {q: Medusa} works partially, only the thumbnails are loaded most of the time.
When a query is done, no result is displayed.
In mobile it works fine for some reason

The search results for the desktop version of your the are displayed by the DesktopSearchModal component.
You can find this component in the src/modules/search/templates/desktop-search-modal/index.tsx file.
I remove the min-h-full in  this line

import { searchClient, SEARCH_INDEX_NAME } from "@lib/search-client"
import Modal from "@modules/common/components/modal"
import Search from "@modules/common/icons/search"
import { MagnifyingGlassMini } from "@medusajs/icons"
import DesktopHit from "@modules/search/components/desktop-hit"
import DesktopHits from "@modules/search/components/desktop-hits"
import SearchBox from "@modules/search/components/search-box"
import { InstantSearch } from "react-instantsearch-hooks-web"

type DesktopSearchModalProps = {
  state: boolean
  open: () => void
  close: () => void
}

const DesktopSearchModal = ({
  state,
  open,
  close,
}: DesktopSearchModalProps) => {
  return (
    <>
      <button onClick={open} className="flex items-center gap-x-2 h-full">
        Search
      </button>

      <Modal isOpen={state} close={close} size="large" search>
        <Modal.Body>
          <InstantSearch
            indexName={SEARCH_INDEX_NAME}
            searchClient={searchClient}
          >

                <MagnifyingGlassMini />
                <SearchBox close={close} />

                <DesktopHits hitComponent={DesktopHit} close={close} />

          </InstantSearch>
        </Modal.Body>
      </Modal>
    </>
  )
}

export default DesktopSearchModal

If someone could explain why this property triggered a bug in Safari (maybe something to do with b-fit?)


get_wallet_balance(self.wallet_id) results in Unknown Error

Hey there 👋
I have a wallet and full node running but upon starting the server I get the following:
INFO:root:Logging in: {'error': 'Unknown Error', 'success': False}
Traceback (most recent call last):
  File "/code/pool_server.py", line 153, in <module>
    asyncio.run(start_pool_server())
  File "/usr/lib/python3.8/asyncio/runners.py", line 43, in run
    return loop.run_until_complete(main)
  File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()
  File "/code/pool_server.py", line 128, in start_pool_server
    await server.start()
  File "/code/pool_server.py", line 31, in start
    await self.pool.start()
  File "/code/pool.py", line 170, in start
    res = await self.wallet_rpc_client.get_wallet_balance(self.wallet_id)
  File "/usr/local/lib/python3.8/dist-packages/chia/rpc/wallet_rpc_client.py", line 92, in get_wallet_balance
    return (await self.fetch("get_wallet_balance", {"wallet_id": wallet_id}))["wallet_balance"]
  File "/usr/local/lib/python3.8/dist-packages/chia/rpc/rpc_client.py", line 45, in fetch
    raise ValueError(res_json)
ValueError: {'error': '', 'success': False}

I have verified that I can communicate with the wallet via RPC so I am not sure what is going on here.
Are there any additional steps I am missing? Please advise.
I should note that I am pointing to the pooling branch here as opposed to master (when installing Chia).
Thank you!

Thank you

Upon digging a bit further, I see a preceding call, self.wallet_rpc_client.log_in_and_skip, make calls to "host": "https://backup.chia.net", is this just a placeholder for our own key management server?

Ok, I think I partly found the answer to my own question:

You can now backup your wallet related metadata in an encrypted and signed file to a free service from Chia Network at backup.chia.net. Simply having a backup of your private key will allow you to fully restore the state of your wallet including coloured coins, rate limited wallets, distributed identity wallets and many more.
...from this change log.
Closing for now.


How do i download multiple tracks at once ?

Like we have an option in wget , we can put all URLs in once text file and we can do
wget -i <filename>.txt
I have like 20 SC tracks, tried to do it in the same way, of course, it didn't work and later had to do it one by one manually for few.
For rest, I just wrote -
Soundscrape <url>
Soundscrape <url>
Soundscrape <url>
....
Soundscrape <url>

and watched it DL all tracks.
Any alternate way?

This is an interesting question!
Here are the answers from stack: http://unix.stackexchange.com/questions/149726/how-to-pass-each-line-of-a-text-file-as-an-argument-to-a-command
I think this should actually be a unix command itself..

Aaaand of course it is already. http://www.gnu.org/software/parallel/


Question about the learning rate assignment

In the demo of sentiment, I see the stack lstm is used for this classification task (this file).
I have some questions about the learning rate.
In line 105, the para_attr is a list, which contains the learning rate of fc_layer and lstm_layer.
In line 123, the fc_layer uses the param_attr to get the learning rate, but the following lstm does not have a param_attr.
Then could the second element of the para_attr be conveyed to lstm? How?

Hi, @CrossLee1
The lines from 103 to 105 sets parameter more  precisely. Actually, it is ok without these settings.
    inputs = [fc1, lstm1]
    for i in range(2, stacked_num + 1):
        fc = fc_layer(
            input=inputs,
            size=hid_dim,
            act=linear,
            param_attr=para_attr,
            bias_attr=bias_attr)
        lstm = lstmemory(
            input=fc,
            reverse=(i % 2) == 0,
            act=relu,
            bias_attr=bias_attr,
            layer_attr=layer_attr)
        inputs = [fc, lstm]

Because the inputs of fc_layer contains two layers. That is to say the input is a list of [fc_layer,  lstm].
The list of para_attr is used to set parameter attribute of each input layer. That is to say para_attr[0]  is the parameter attribute of the first input fc_layer, the para_attr[1] is the parameter attribute of the second input lstm.
If you want to know the details, you can see code of fc_layer.
https://github.com/baidu/Paddle/blob/develop/python/paddle/trainer_config_helpers/layers.py#L876

@qingqing01
I see. Thanks for your detailed explanation.
Closed#


New conda build

@msarahan - I have followed up your amazing PR (#58) with a few tweaks. Some are functional, some are just fixing technical debt accrued before the conda-build 1>2 move.

I have tested the CLI with a bunch of recipes, but have not yet tested uploading - that may very well still be a problem.

whoops - lots of stuff here I missed.  Was it stuff just not covered in the test suite?


Thank you for sharing

But there may be some bugs during re-running, ex. no init file, skip some imports, logic of some parameters. For example, I wondered that 'Non-existent config key: OWOD.CLUSTERING.UNK_THRESH' means 'UNK_THRESH' is not under 'CLUSTERING', but in two config files, it declared differently.
Looking forward for your further completion.

Hello, have you solved the problem

Hello, have you solved the problem @Yijing-c


Deploying PVnet to production

Deploying PVnet to production
Detailed Description

had a probably as the adjuster was turned on, but there were no ME results.

Context

the adjuster looks back at the last 7 days and finds the average error

Possible Implementation

add envvar to code to turn on and off adjuster, so its easy to turn on and off

Added this in datamodel 1.4.5


fix: bug 1642 - help icons need transparent background, not hardcoded

Set control's background to transparent and important to override Fabric's, yet handle colorized messages

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Convert Ellipse and 2-Point Line to script tools

Converted Table To Ellipse, Table To 2-Point Line, and Table To Point from Model tools to script tools.
Description
Converted Table To Ellipse, Table To 2-Point Line, and Table To Point tools from models to script tools.
Some other minor fixes are included as well.
Related Issue
Motivation and Context
Solve problems in Model Builder that won't be addressed until 10.3.
How Has This Been Tested?
Some ad-hoc testing and passing unit tests (except Feature Compare).
Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.

@ACueva @jrweakland
This one is done and ready to be reviewed if you guys are up to it. If not, let me know ASAP.
@lfunkhouser
@nfeuerstein

Still open and need someone to review.


ENG-4226 merge 7.1

hi @alepintus
please note there is something missing here: the version updating in the package.json file. I guess this branch has been created from the tag. Do you think we can updating either?

We can close this one since the PRs have been previously merged into both 7.1 branch and develop

Hi @avdev4j talking with @zonia3000, @antromeo and @cecchisandrone about this PR we are thinking to merge this commits to have the same history ant to avoid to have these commits if we have to merge again from the release branch.
WDYT?

yes, this is true. let's do it. Next time maybe do one PR to develop then to the release branch so we'll have to do merge that kind of merge commits.
In this case, it's mostly because we did both the dev and the release in a short time frame.


Start work on getting newton working

recheck

recheck 0785c70

mitaka didn't fail, that's a bug in my script somewhere.

recheck 0785c70


ci(travis): Change Node version

Downgrade Node version for tests to properly run until upgrade to Jest 24
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Compliance

[x] My change isn't breaking (it doesn't cause existing functionality to change).
[x] I have read the CONTRIBUTING document.
[x] My code follows the coding style of this project.
[x] I have properly formatted my commit messages with cz-cli, or manually, following the Angular Commit Messages Guidelines.
[x] I have updated the documentation accordingly, or my changes doesn't require documentation changes.
[x] I have added tests to cover my changes, or my changes doesn't require new tests.
[x] All new and existing tests pass.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


typo in equation

This equation says f(w) - f(ws) = x.T @ Lambda @ x
However, this should be f(w) - f(ws) = 0.5 * x.T @ Lambda @ x
Please veirfy

Please see my https://github.com/distillpub/post--momentum/pull/104 for the patch and reasoning.


Make data easier to consume in bulk

I'll use this bug to collect ideas to make it easier to consume OONI data in bulk.

[ ] Move files under <test_name> directories (e.g. autoclaved/jsonl/web_connectivity/...)
This will allow one to fetch or process a test type without having to go over all the tests. One may list all files, filter, then use that as input. However thousands of filenames as input does not work well with big data tools.
Even if the test_name is under the date directory, that would already be useful (I could process one data at a time). Similarly, the filename prefix could have the test name (it doesn't help to have it in the middle).

[ ] Move files under <country> directories (e.g. autoclaved/jsonl/web_connectivity/IT/...)
This will allow one to fetch or process a test in a country without going over all the data. This would also be in a filename prefix.

[ ] Use a uniform file format with balanced number of measurements. We can have a split file (e.g. measurements-XXXXX-of-01000.jsonl.gz) with about the same number of measurements each.
The grouping by report is not useful to consumers. The mix of json.lz4 and tar.lz4 prevents effective use of big data tools. Furthermore, LZ4 is not well supported, which also prevents the use of many tools.

[ ] Move HTTP bodies to a separate datastore.
Most of the data is HTTP request/response body, which is often not useful for bulk processing. They would live in parallel files instead, maybe with the same index as the measurements to make joining easy (e.g. measurements-01234-of-10000 joins with bodies-01234-of-10000).

Are any of those a low hanging fruit? For example, maybe rename the files to have test name and country as a prefix?

@fortuna I think the first point "Move files under <test_name> directories", is something I think is pretty important to do and it would benefit a larger audience too, but it's not exactly "low hanging fruit".
Currently our data processing pipeline depends quite a bit on having files layed out in a certain way and every measurement for a particular date being inside of the bucket prefix (YYYY-MM-DD), so it's not going to be so simple to change the schema of the already emitted measurements (i.e. the autoclaved).
It's probably going to be easier to add support for another format, such as parquet, and write those in a more comfortable format.

Move files under  directories (e.g. autoclaved/jsonl/web_connectivity/IT/...)

I am not sure this is something we should actually do. I think that in most cases, when you are consuming data in batch, you will actually be interested in having measurements from all the countries and actually our country classification sometimes has bugs (geoip is inaccurate), so we probably don't want to do this.

Use a uniform file format with balanced number of measurements

I think this makes sense for formatting the files of other data formats, though I believe that this file format is also something internally used by the data processing pipeline.
@darkk can probably say more on how hard this actually is.

Move HTTP bodies to a separate datastore

I can see why this is something that would be desirable for certain use cases, but maybe this is better solved by having specific pre-processed slices of the data that don't include fields that are not interesting to a user of that dataset.
As a general note, something to keep in mind is that the autoclaved/ are also the master dataset that our data processing pipeline uses internally. I think that to meet the need of end users, we are probably better off having some other batch export that is designed specifically for end user consumption, rather than trying to adapt the internals of our data processing pipeline the need of end users.
Does this make sense?

test_name prefix
I understand the need for the date buckets. I actually ran into the same issue when trying to figure out how to keep my data in sync. We can keep those, but having a <date_bucket>/<test_name> prefix would be helpful.
Public format
Good to know that autoclaved is your internal format. I agree with you: having a an export to a public format for end users makes sense.
On the body size, one test-agnostic heuristic I use is to trim all strings in the JSON to 1000 bytes. It saves a lot in the body field. Notice that if we had a columnar format, we could potentially just ignore that column, which would be great.
Parquet and friends
It seems parquet supports nested objects in their file format, but the serialization in the parquet, avro and Arrow Python libraries don't, as far as I can tell (at least I couldn't figure out). You'd need to roll out your own coder. The library pyspark seems to support nesting according to this Tutorial.
That would be convenient if you decide to use Spark.
One more thing: for a columnar format we may need to revist the schema. Currently there are fields like "headers", where keys can be arbitrary strings. The formats that require schemas don't like that. All keys must be known.
Instead of:
"headers": {
  "Foo": "foo",
  "Bar": "bar",
}

You'd need to restructure to something like
"headers": {[
  {"name": "Foo", "value": "foo"},
  {"name": "Bar", "value": "bar"},
]}

You wouldn't need to worry about the duplication of the keys because the format removes that for you.
Thanks for the follow up!

maybe this is better solved by having specific pre-processed slices

We're following the same idea in other places. E.g. PostgreSQL has the fields those are "interesting for sure". Maybe it actually makes sense to have a "shaved" version of autoclaved files without HTTP bodies and replacing them with derived values {title, body_length, body_sha256, body_simhash, body_text_simhash}.
HTTP bodies take 97% of lz4-compressed data size, so making the slice of the dataset that is 130 GiB compared to 4200 GiB is something that sounds like both a useful activity and a "low hanging fruit".

That would be helpful. The new metadata DB requires a complicated and fragile setup. I just need a data dump without most of the stuff I don't need.

@FedericoCeratto this is a useful thread to keep in mind.


[Enhancement] improve cloud native pk table memory use and tracker

This pr contains two parts:

Add cloud native primary key table's compaction state tracker
Improve memory alloc when do loading upsert/delete keys.

What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:heart_eyes: pass : 8 / 10 (80.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/lake/update_manager.cpp
1
2
50.00%
[575]

:large_blue_circle:
src/storage/lake/update_compaction_state.cpp
6
7
85.71%
[36]

:large_blue_circle:
src/storage/lake/rowset_update_state.cpp
1
1
100.00%
[]

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 13 / 20 (65.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/lake/update_manager.h
0
1
00.00%
[121]

:large_blue_circle:
src/storage/lake/update_manager.cpp
2
8
25.00%
[575, 577, 578, 579, 580, 581]

:large_blue_circle:
src/storage/lake/update_compaction_state.cpp
10
10
100.00%
[]

:large_blue_circle:
src/storage/lake/rowset_update_state.cpp
1
1
100.00%
[]

[BE Incremental Coverage Report]
:disappointed: fail : 13 / 20 (65.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/lake/update_manager.h
0
1
00.00%
[121]

:large_blue_circle:
src/storage/lake/update_manager.cpp
4
10
40.00%
[577, 579, 580, 581, 582, 583]

:large_blue_circle:
src/storage/lake/update_compaction_state.cpp
9
9
100.00%
[]

https://github.com/apps/mergify backport branch-3.1

https://github.com/mergify backport branch-3.1


Adds typed future_type for executor_traits

I wanted to use an executor that returns shared_futures not futures. This is how I did it,
but please suggest anything if I missed an obvious alternative.
Allows an executor to define and use a separate future type.
For example, a shared future instead of a default future. See
added test file.

Good catch, thanks!


Pkg 4582 update 12.4

Destination channel: defaults
Links

PKG-4582
Upstream repository
Upstream changelog/diff

Explanation of changes:
Previously, this was forked from conda-forge and some changes made for various reasons (see PR 1). Since then, conda-forge's recipe got updated to v12.4.
This rebases the changes we made onto their changes. It also removes the abs.yaml because we want to upload the packages to the main channel now.
There's an open issue upstream but I suggest we merge this rather than wait for it to be resolved, and catch it next time round.

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_477q8f53i1/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:336: license_file_overspecified: Using license_file and license_url is overspecified.

===== ERRORS =====

clone/recipe/meta.yaml:220: missing_tests: output "cuda-cudart-static": No tests were found.
clone/recipe/meta.yaml:138: missing_tests: output "cuda-cudart-dev": No tests were found.
clone/recipe/meta.yaml:336: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:336: missing_license_family: The recipe is missing the about/license_family key.
===== Final Report: =====
4 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_3akt6_pf57/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:336: license_file_overspecified: Using license_file and license_url is overspecified.

===== ERRORS =====

clone/recipe/meta.yaml:336: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:220: missing_tests: output "cuda-cudart-static": No tests were found.
clone/recipe/meta.yaml:138: missing_tests: output "cuda-cudart-dev": No tests were found.
clone/recipe/meta.yaml:336: missing_license_family: The recipe is missing the about/license_family key.
===== Final Report: =====
4 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_2d1wivkzc8/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:336: license_file_overspecified: Using license_file and license_url is overspecified.

===== ERRORS =====

clone/recipe/meta.yaml:138: missing_tests: output "cuda-cudart-dev": No tests were found.
clone/recipe/meta.yaml:336: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:220: missing_tests: output "cuda-cudart-static": No tests were found.
clone/recipe/meta.yaml:336: missing_license_family: The recipe is missing the about/license_family key.
===== Final Report: =====
4 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_c9mbo4s5_q/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:336: license_file_overspecified: Using license_file and license_url is overspecified.

===== ERRORS =====

clone/recipe/meta.yaml:336: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:336: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:220: missing_tests: output "cuda-cudart-static": No tests were found.
clone/recipe/meta.yaml:138: missing_tests: output "cuda-cudart-dev": No tests were found.
===== Final Report: =====
4 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_f6wkbp89k4/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:336: license_file_overspecified: Using license_file and license_url is overspecified.

===== ERRORS =====

clone/recipe/meta.yaml:336: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:336: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:220: missing_tests: output "cuda-cudart-static": No tests were found.
clone/recipe/meta.yaml:138: missing_tests: output "cuda-cudart-dev": No tests were found.
===== Final Report: =====
4 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_258mve_nhf/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:336: license_file_overspecified: Using license_file and license_url is overspecified.

===== ERRORS =====

clone/recipe/meta.yaml:336: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:138: missing_tests: output "cuda-cudart-dev": No tests were found.
clone/recipe/meta.yaml:220: missing_tests: output "cuda-cudart-static": No tests were found.
clone/recipe/meta.yaml:336: missing_license_family: The recipe is missing the about/license_family key.
===== Final Report: =====
4 Errors and 1 Warning were found


Scheduling error with flink that does not rely on hadoop

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
使用海豚调度器调度flinksql，建表语句可以正常执行，插入语句会报错
错误信息：
TaskLogLogger-class org.apache.dolphinscheduler.plugin.task.flink.FlinkTask:[63] -  -> [ERROR] Could not execute SQL statement. Reason:
java.lang.IllegalStateException: No Executor found. Please make sure to export the HADOOP_CLASSPATH environment variable or have hadoop in your classpath. For more information refer to the "Deployment" section of the official Apache Flink documentation.
Shutting down the session...
done.
What you expected to happen
写一个比较详细的flinksql调度过程  包括flink的版本 和所需要的环境
How to reproduce
在MySQL中创建三张表  字段一致  其中两张表中插入数据 然后写flinksql  同样是创建三张一样的表 关联到mysql的表 然后查询有数据的两张表插入到第三张没有数据的表   这样的flinksql写完之后放到海豚调度器上进行调度
Anything else
海豚调度flink是只支持on yarn部署的flink吗 kubernetes部署的是否支持调度
Version
3.0.0-beta-2
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

Dupliated with #10808.


Big refactor connected with ranges, semver class, comparators

This is a very big refactor which changes a couple of thing.
What was done?
Refactored requirements (closes #10)
Right now is called ranges, which is more accurate and intuitive.
This release introduce range processors which can simplify adding new range parsers.
Refactor comparators (closes #11)
Comparators using compare method.
Raname suffixTokens to preRelease (closes #14)
Semver object can be created only in strict mode (closes #15)
Semver right now represents a fully valid with RFC object, has all properties that are required (major, minor and patch). In the future there will be another type which loosy this requirements.
A lot of small fixes and code cleaning.

Introduce methods coerce and parse which allow to close #22.


Erln8 does not handle paths with spaces

Not that I care that much, but shell commands with unescaped arguments always make me worry. Any space in ERLN8_HOME will make the tool crash. Other arguments might be subject to such bugs too.

wont fix, see comment above.


Overlaps

This will:

Fix #8 by trying tries times (default 10) if there are overlaps and then returning None if overlaps were generating every time. This overlap check is quick because the index of the changed note is known.
Fix #57 in a possibly inefficient way, but I couldn't think of how to do it otherwise. The previous method doesn't work I think (but I left them there--please clean if this one looks fine). I also added a test case for this in test_data_structures. This overlap_check is set to False by default and True in make_dataset.py. (Related to #20).
Fix #46 by adding a flatten_tracks arg to read_note_csv and added a test for this. This is set to False by default and True in make_dataset.py.
Fix #59 by adding (the same) random number (between 0 and 200) to the onsets of all notes in each clean excerpt, before degrading, in make_dataset.py.

TODO:

The data_structures.fix_overlaps function adds around 6 secs per piece in PianoMidi. Should be less for PPDD since they are not full songs, but still... Still, be sure the test case passes. Also, clean up the remaining fix_overlap methods if this one is ok.

I was just thinking of a potentially faster method for fix_overlaps.
Rather than the double group by, just group by track, and the iterate through the rows in the same way as this fix_overlaps does, but have current_offset be a list of length 128 (1 per pitch), instead of a single value. That may be faster. I could try this later tomorrow, but honestly, as long as this works, I'll probably just concentrate on making the baselines.

The current version takes about 13 mins on my machine to clean all 3 datasets fully. It's not terrible, so I'm going to leave it for now.

Fix #59 by adding (the same) random number (between 0 and 200) to the onsets of all notes in each clean excerpt, before degrading, in make_dataset.py.

I'm not entirely clear why we don't just zero the onsets post degradation i.e.:

excerpt arrives with first onset = 0
it is degraded
degraded['onset'] = degraded['onset'] - degraded['onset'].min() before return

That would make it much more difficult to check for differences between the
degraded and clean excerpts, both for the ground truth in task 3, and just
for tests.
Because you might have a case where every note is then changed, if they
shift forward.
On Fri, Oct 11, 2019, 18:38 James Owers<EMAIL_ADDRESS>wrote:

Fix #59
https://github.com/JamesOwers/midi_degradation_toolkit/issues/59 by
adding (the same) random number (between 0 and 200) to the onsets of all
notes in each clean excerpt, before degrading, in make_dataset.py.

I'm not entirely clear why we don't just zero the onsets post degradation
i.e.:

excerpt arrives with first onset = 0
it is degraded
degraded['onset'] = degraded['onset'] - degraded['onset'].min()
before return

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/JamesOwers/midi_degradation_toolkit/pull/60?email_source=notifications&email_token=ACPDFPRQDN5CQORV2JWUMITQOBCQ7A5CNFSM4I7H5PF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA7OTBY#issuecomment-540993927,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACPDFPTWYGLQRTQJFAVUMC3QOBCQ7ANCNFSM4I7H5PFQ
.

Rather than the double group by, just group by track, and the iterate through the rows in the same way as this fix_overlaps does, but have current_offset be a list of length 128 (1 per pitch), instead of a single value. That may be faster. I could try this later tomorrow, but honestly, as long as this works, I'll probably just concentrate on making the baselines.

Agree - it's definitely something to note to speed up in future, but given that we're going to release the dataset, the speed of stuff is not as important just now.


Return error when config_file_path is put in the config file

It should be done once this PR is merged: https://github.com/meilisearch/meilisearch/pull/2745
This issue is a sub-issue of https://github.com/meilisearch/meilisearch/issues/2558
Once https://github.com/meilisearch/meilisearch/pull/2745 is merged, it will be possible to pass a config file to Meilisearch. When using a key that is not known by Meilisearch in the config file (for instance, "no_analytic" instead of "no_analytics"), Meilisearch returns an error when trying to read the config file.
Currently, if you enter the config_path_file key, Meilisearch does not return any error and ignores the key silently. We need to return an error saying this key is not accepted.

Is this the only key that would prompt such an error, or is / would there be a list of these such keys?

Hello @Celeo
So far, it's the only key with this specificity 😊

FYI https://github.com/meilisearch/meilisearch/pull/2745 has been merged and is ready to be implemented! 🎉

Not exactly.
Meilisearch accepts a config file since https://github.com/meilisearch/meilisearch/pull/2745 was merged.
To let Meilisearch know you have a config file, either your file is ./config.toml, or your file is passed via the --config-file-path flag.
But in the config file itself, we don't want to let the users define the path of the config file: it makes no sense, like a "loop", since you already are in the config file. Do you see what I mean?
That's why we would like Meilisearch to return a message saying the key config_file_path is not valid.


Format assertions should be enabled for optional/ecmascript-regex.json

Describe the bug
Format assertions should be enabled for optional/ecmascript-regex.json as the \\a is not an ECMA 262 control escape test is a format "format": "regex" that expects the result to be invalid.
    {
        "description": "\\a is not an ECMA 262 control escape",
        "schema": {
            "$schema": "https://json-schema.org/draft/2020-12/schema",
            "format": "regex"
        },
        "tests": [
            {
                "description": "when used as a pattern",
                "data": "\\a",
                "valid": false
            }
        ]
    }

https://github.com/json-schema-org/JSON-Schema-Test-Suite/blob/9fc880bfb6d8ccd093bc82431f17d13681ffae8e/tests/draft2020-12/optional/ecmascript-regex.json#L408-L421
Additional context
The current networknt json-schema-validator 1.4.0 doesn't pass the test but an upcoming version will.

Hey @justin-tay, I've raised https://github.com/json-schema-org/JSON-Schema-Test-Suite/pull/751 to fix the issue at source.

There is a related discussion on this specific test

https://github.com/json-schema-org/JSON-Schema-Test-Suite/pull/740

@justin-tay With https://github.com/json-schema-org/JSON-Schema-Test-Suite/pull/751 merged, I'm assuming this issue is now resolved?

Closing as resolved upstream.


Merge into brs-emu

It would be more convenient for brs-emu-app to be merged into brs-emu just so it's just cleaner overall.

I will not integrate, and I can explain why. There are at least two more projects/repositories I will release soon that also uses the brs-emu library, I'm actually even considering remove the web app to its own repository, and leave there only a simple example. The brs-emu is going to be a better npm package in the next release.
It makes easier to maintain then whole build and packaging, and give freedom to have independent releases, I've been releasing it together because it was the alpha and beta stages, but in the future I want each project to have its own timeline of releases.

I just found out that this is legitimately just a wrapper for brs-emu.


Add perf counter to calling tests

What

Add perf counter to calling tests

Move selector inner function outside to give it a function name so it could be visited as function.name in runtime
Add a perf counter in UI Test
Add a CI action to generate perf counter snapshot

Why

How Tested

Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

Close this since flakiness in calling is still not resolved, will revisit when we solve the flakiness problem in calling, could be valuable to enable this for chat first


python time.sleep() output

when you use time.sleep(), everything is outputted to the screen at the end of the program instead of printing output gradually as the program runs

I blame us using Atom's BufferedProcess.

All you have to do is to run your program with command line arguments -u.


Make change of  sheet view public

Hi,
I need to change sheet view to pageBreak, but because GetCTWorksheet is internal now it can set only via reflection. Please, make it public.

Is this what you want? XSSFSheet.Autobreaks
https://github.com/nissl-lab/npoi/blob/58d6f450f617f636dc4ccc25ed1cfb9568923c77/ooxml/XSSF/UserModel/XSSFSheet.cs#L2255

Is this what you want? XSSFSheet.Autobreaks
https://github.com/nissl-lab/npoi/blob/58d6f450f617f636dc4ccc25ed1cfb9568923c77/ooxml/XSSF/UserModel/XSSFSheet.cs#L2255

No, XSSFSheet.GetCTWorksheet.
https://github.com/nissl-lab/npoi/blob/58d6f450f617f636dc4ccc25ed1cfb9568923c77/ooxml/XSSF/UserModel/XSSFSheet.cs#L272-L281
Right now I need to use reflection:
MethodInfo methodInfo = sheet.GetType().GetMethod("GetCTWorksheet", BindingFlags.NonPublic | BindingFlags.Instance);
var ct = (CT_Worksheet)methodInfo.Invoke(sheet, new object[] { });

CT_SheetView view = ct.sheetViews.GetSheetViewArray(0);
view.view = ST_SheetViewType.pageBreakPreview;


Issue when upgrading and dbus not starting

Unit dbus.service cannot be reloaded because it is inactive.

I think this has to do with the system activation of systemd services during nixos-rebuild. I think it happens when dbus needs to be first stopped. cc @edolstra perhaps ignoring the error when reloading dbus is fine?

No I think the best would be to reload dbus is active, otherwise try to start it.

No reload-or-restart won't do it.


component gets initialized twice, when used in dynamic html

i want to use some components in dynamicly loaded markup. unfortunately they will be initialized twice. do you know of a way of avoiding this?
example:

Test..

{html='
hello
<vui-test></vui-test>'}, 2000)">

      <template x-data x-component="test" x-init="$api && $api.init()">

            <button x-on:click="console.log('hi from web component')">test</button>

    </template>

on codepen

This is a known issue because of the x-html internal implementation in alphinejs. Vimesh UI provides an alternative x-shtml, means safe html. For your problem, just replace x-html to x-shtml

This is a known issue because of the x-html internal implementation in alphinejs. Vimesh UI provides an alternative x-shtml, means safe html. For your problem, just replace x-html to x-shtml

You could also refer to /examples/spa/app.html , which is a minimal single page application framework with vimesh ui. x-shtml is used to load dynamic pages, with help of x-import:dynamic, these pages will be lazy loaded.

this is so cool! it just works! i really missed this x-shtml. i think it belongs on the README :) now i'm able to include alpine driven components in markdown. alpinejs should make this an official components extension.
or maybe it's time for a mesh-up: the best of petite-vue & alpine plus tight component support (with the least necessary new syntax/magix).
let's dream:

no build step, no tooling required
declarative style/ reactive
friendly to boring, old school server rendered pages (php, ruby, python ...)
components!
onboard devs: choose between x-* and v-*, support even react-like templating though template strings

all the best!


Added 'next or last project' feature

I decided to tackle #22. This PR adds a function that navigates to the next or previous project (and could easily be expanded to navigate n spots over), bound to ctrl-alt-shift-right and ctrl-alt-shift-left by default. I also tweaked the keymap (it had a cmd key for Windows/Linux functions and a ctrl key for Mac).

Oh, and the list is generated from the sidebar, so it will always determine the next or previous project based on how they're displayed on the user's screen. It will not break if additional sorting or filtering features are added.

I fixed both notification messages.

hey @DamnedScholar, please fix the conflict to this
{
    ".platform-darwin, .platform-win32, .platform-linux": {
        "shift-ctrl-alt-v": "project-viewer:toggle-select-view",
        "shift-ctrl-alt-b": "project-viewer:toggle-display",
        "shift-ctrl-alt-n": "project-viewer:toggle-focus",
        "shift-ctrl-alt-right": "project-viewer:next-project",
        "shift-ctrl-alt-left": "project-viewer:previous-project"
    }
}

Also, i am not able to traverse, it says no no project currently selected.


System tests

This implements a number of performance enhancements for the system tests (formerly called the sanity tests).

Written in Go instead of Python
Parallel execution of tests (ping, connect)
Parallel startup and teardown of containers
Parallel listener startup
Uses alpine image now for faster download and container startup/teardown
Overlayfs for maximum filesystem performance

The result of this work is that you get down to 800s on a lab box, which is better than the 1h30m that was  done in the systemtests before.
The systemtests themselves are all in one commit, please click on that to review independently. I took care to re-implement in spirit the python code, so it was easier to maintain for those already familiar with the code. I also abstracted most of the parallelism into a framework that should be easy-to-use for future tests that need to be created.
I also exposed a few bugs: one @shaleman has already fixed in master, but there's a netplugin panic that seems to be happening occasionally due to ovsdb driver code. I'll get more details in an issue soon.

@erikh There was a TC added to cover ACI via https://github.com/contiv/netplugin/pull/272. I didn't see it covered here.

@jojimt right now, the tests only run in the VMs, not on metal. Is this something I can do in the VMs? I will be happy to port it if so.
The limitations on bare-metal work are something I plan to fix, but I don't think it's necessary for the first candidate; I have not removed the sanity tests because of this.

Yes, this is run in the vagrant environment to cover the ACI mode -- it is not an e2e and does not require any physical infra.

@jojimt ok, I will convert them later today then. PTAL at the rest if you have time, that'll save us trouble later.

Overall structure looks good.
Some high level comments.
I'll add more specific comments on the code.

Looks like tests are run in vxlan mode only. We currently run most tests on both Vlan and Vxlan modes because code paths for the two are very different. Control plane, data plane and OVS features we use in two modes are very different. It'll be good to do the same here.
Random trigger test seem to be empty. It'll be good to add netplugin/netmaster restart trigger tests. Its perfectly fine if this comes in a subsequent PR.
As previously discussed, ACI, switchover and other recently added tests are missing. It'll be good to add those.
If you are planning to add these tests in a subsequent PRs, it'll be good to keep both old sanity and new system tests in jenkins runs so that we don't loose coverage during the period.
Since golang tests don't stop or error, it might become hard to debug failures. It might be good idea to add a stop-on-error option to tests.
Current tests look for errors in netplugin/netmaster logs after each iteration and fail if there are any errors. It'll be good to keep this practice.
It'll be good to add a test suite cleanup so that everything is cleaned up after the test suite is complete..

the test suite cleans up itself on boot, there's no point in cleaning it up after it finishes.
I already implemented the code to fail on netplugin log errors -- then quickly triggered it over and over again on no actual errors.
I'm not sure what you mean by the random trigger test seems empty, can you elaborate?
I'll do the additional tests that are in master now in this test. I will be expecting you guys to port the rest. I'm not sisyphus. :)

SOE options are going to be something you guys need to investigate, I looked at a few potential options in volplugin and found no good ones. Regardless, I didn't find this to be an issue while working with these tests, since you can run them independently by passing the -check.f flag.
I'll fix anything not mentioned later tonight.

I'm not sure what you mean by the random trigger test seems empty, can you elaborate?

TestTriggers() test isn't applying any triggers as far as i can tell..
python tests trigger (i) netplugin restart (2) netmaster restart OR (3) container restart randomly and test forwarding works after each trigger..

Ah ok. I will look into what I overlooked then. Thanks for reviewing it all!

so, everything but the vlan tests are here now. PTAL, I will have the vlan changes in later tonight, btu they will be very small.

btw, the changes I made are in the last commit, so if you've already read the original changes you can just look there. I will squash those on top of the originals before merge.

systemtestSuite.TestNetpluginDisconnect is failing randomly and I'm not sure why yet, so please do not merge this yet even if it passes.

https://github.com/erikh/netplugin/commit/6c5a2f744076e2331b83ac5bf032d65f7bc1a48a has the latest updates, and completes the patch. PTAL.

@erikh It largely looks good to me other than the minor comments..
See my comments on error checking and trigger tests..

@shaleman ok, I'll get this sorted out this evening. Thanks for the review!

I think I've resolved everything. PTAL and merge if ready.

Thanks for taking care of the comments @erikh
Pardon my nagging here.. I'm perfectly fine merging this PR and fixing these minor comments in subsequent PR..

I think this comment was missed in TestTriggerNetmasterSwitchover()
https://github.com/erikh/netplugin/commit/e685740b7a8bc23926af7caf699220981f2da273#commitcomment-16163186

We should be failing the test if new node is not elected as leader within a timeout period.
Currently, this might loop forever instead of failing the test..

also, it'll be good to rotate netmaster logs in TestTriggerNetmasterSwitchover()

finally, can we check for netplugin/netmaster log errors in individual tests than at the end of the test?
If we call node.checkForNetpluginErrors() during test teardown, Its very hard to say which test actually caused the error

finally, can we check for netplugin/netmaster log errors in
individual tests than at the end of the test?
If we call node.checkForNetpluginErrors() during test teardown, Its
very hard to say which test actually caused the error

Pretty sure all the tests will fail if the teardown does for one of
them, making it pretty obvious.
-Erik

never mind. Didn't realize TearDownTest() gets called after each test.. thats neat..

This should be ready after CI passes, the tests pass here.
This incorporates the fix for the netmaster leader election test.

LGTM

these patches are ready; please merge when appropriate.


[proposal] Add Prometheus metrics provider to support interference manager

What is your proposal:
To implement a metric provider, which plays a role as a Prometheus client. It sends query requests to Prometheus server once in a while, and provide the response metrics to interfernece manager.
Why is this needed:
Koodinator's interference metrics are collected and evicted by Prometheus now, we need a client to query them from Prometheus, parse the raw data into metrics struct/model, then interference manager can use them.

/assign

#6


Use with gitlab-ci

Using flightplan locally and everythings runs fine.  When trying to setup gitlab-ci job to run, it fails on any remote commands.  Connection is never made.  local.transfer works fine, but when setting up plan.remote the connection fails with the following error
Error connecting to XXX.XXX.XXX.XXX: Error: Authentication failure. Available authentication methods: publickey,password

Has anyone had any luck here.  I'm not sure why the transfer works fine but remote commands will not with the same user.

Is this still an issue or could you solve it? I think your private key is not recognized on the host running flightplan. Strangely enough the connection rsync connection seems to work fine. Do you need to enter a password when using local.transfer()?

I never did get it solved.  It would work with a password.  I believe I was not using the right key.  I will try it again soon and dig to make sure key is correct.


[ModuleInterface] Don't print extensions to implementation-only imported types

Extensions to implementation-only types are accepted at type-checking
only if they don't define any public members. However if they declared a
conformance to a public type they were also printed in the
swiftinterface, making it unparsable because of an unknown type.
Still accept such extensions but don't print them.
rdar://67282657

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test


Authorization for rgoogleslides fails when in the docker container

Summary
When I try to run rgoogleslides::authorize() inside a docker container, after I click Allow this happens:
This is true no matter the browser I use.

So if we do need to use rgoogleslides, which I think we will, I'll have to figure out a work around for this that allows us to still use the docker container.

So if I set up the .httr-oauth file outside of Docker, and then go back to Docker, I can use rgoogleslides fine because it just pulls that authorization. I don't love this, and feel like there should be a better way around it but I don't know enough about firewalls and etc to have yet come up with a more elegant solution.
Will have to do some more digging. I haven't pinpointed the exact problem of why Docker is blocking the authorization or how to stop it from doing that.

Been trying to dig into this problem more. Don't really have leads for solutions. I know that rgoogleslides is using the R package: httr  to get authorization and this uses something called Oauth2 token authentication to do this.
I also know that you can't seem to run from command line: Rscript -e "rgoogleslides::authorize()" because it won't successfully open the interactive window it needs.

You need to pass in the token, it's default is NULL in rgoogleslides::authorize:
So you need to do (assuming token is in .httr-oauth or wherever mounted on Docker:
token = readRDS(".httr-oauth")
if (inherits(token, "request")) {
    token = x$auth_token
}
rgoogleslides::authorize(token = token)

or simply Rscript -e "rgoogleslides::authorize(token = readRDS(".httr-oauth"))
Also may not be relevant, but another snag may that you want to try library(rgoogleslides); authorize(token=token) because of the behavior of that package's .onLoad: https://rdrr.io/github/hairizuanbinnoorazman/googleslides/src/R/zzz.R, which only gets executed.  That could be wrong, but worth a shot.

Thanks! This is helpful! But my main concern is how to instruct people to set up the httr.oauth file in the first place? Is there a not janky way to have someone collect that file or token for their own account?

On Apr 26, 2021, at 6:28 PM, John Muschelli @.***> wrote:

You need to pass in the token, it's default is NULL in rgoogleslides::authorize:
So you need to do (assuming token is in .httr-oauth or wherever mounted on Docker:
token = readRDS(".httr-oauth")
if (inherits(token, "request")) {
token = x$auth_token
}
rgoogleslides::authorize(token = token)
or simply Rscript -e "rgoogleslides::authorize(token = readRDS(".httr-oauth"))
Also may not be relevant, but another snag may that you want to try library(rgoogleslides); authorize(token=token) because of the behavior of that package's .onLoad: https://rdrr.io/github/hairizuanbinnoorazman/googleslides/src/R/zzz.R, which only gets executed. That could be wrong, but worth a shot.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Maybe this or something like it would be helpful? https://cran.r-project.org/web/packages/googleAuthR/vignettes/google-authentication-types.html

Yes, but I'd say, run token = rgoogleslides::authorize(); saveRDS(token, file = "auth-place.rds") or wherever you'd like to place the token rds.  You can also see https://gargle.r-lib.org/articles/non-interactive-auth.html for some other options, but rgoogleslides doesn't live in the gargle* family, but can take the client ID and secret from https://rdrr.io/github/hairizuanbinnoorazman/googleslides/src/R/zzz.R and use gargle.

Yes, but I'd say, run token = rgoogleslides::authorize(); saveRDS(token, file = "auth-place.rds") or wherever you'd like to place the token rds.  You can also see https://gargle.r-lib.org/articles/non-interactive-auth.html for some other options, but rgoogleslides doesn't live in the gargle* family, but can take the client ID and secret from https://rdrr.io/github/hairizuanbinnoorazman/googleslides/src/R/zzz.R and use gargle.

This is great! Will workshop this tomorrow!

I'm still finding the easiest way to get the httr-auth file is to just run through the authorize steps in a non-docker container and then push that file to github. I think this is what I will write in the getting_started.md as the steps for getting a Google Slides going.
These other options require Google Cloud Developer accounts or a lot of extra steps that seem more complicated and like a bigger hurdle than just generating the httr-auth file outside of Docker.

So we can't just upload the httr-oauth file. My next idea is to just store the rgoogleslides token as a GitHub secret. That wouldn't help people out for local development necessarily but would make the github actions work fine.
I guess I need to think more about how often this script would need to be run locally if github actions really is doing the heavy lifting.

My other concern is the set up for these courses from this template is growing more cumbersome the more github secrets we have. Probably also need to add some guidance about how to delete or modify some of these github actions if a course doesn't want or need them. Will make a new issue for that.

Ah. What if we supply the token upon building the Docker container through a Docker secret?
https://stackoverflow.com/questions/59143685/consume-secret-inside-dockerfile
https://docs.docker.com/engine/reference/commandline/secret_create/

My next plan or idea is looking into if there’s any easy way to grab GitHub secrets for local use if you have the right set of permissions.
Maybe this: https://git-secret.io/ has some useful functionality for this.

This is solved as well!


Build errors

Unable to compile after pod update when we create a new project.

I created a new project and installed latest version. I cannot reproduce this issue. Can you give me some insight into what compilation error you are getting? And what steps to reproduce?

Please create a new issue with reproduction steps and more information.


Upgrading from 8.2.6 to 10.0.1 leads to lots of errors: Cannot read property 'range' of null

Node: 10.13.0
eslint: 5.12.0
babel: 7.2.2
If I upgrade from 8.2.6 to 10.0.1 and then run the linter, lots of new errors (in the linter itself) start appearing. They all seem to look like this:
TypeError: Cannot read property 'range' of null
    at SourceCode.getTokenBefore (...\node_modules\eslint\lib\token-store\index.js:303:18)
    at checkSpacingBefore (...\node_modules\eslint\lib\rules\template-curly-spacing.js:54:42)
    at TemplateElement (...\node_modules\eslint\lib\rules\template-curly-spacing.js:119:17)
    at listeners.(anonymous function).forEach.listener (...\node_modules\eslint\lib\util\safe-emitter.js:45:58)
    at Array.forEach (<anonymous>)
    at Object.emit (...\node_modules\eslint\lib\util\safe-emitter.js:45:38)
    at NodeEventGenerator.applySelector (...\node_modules\eslint\lib\util\node-event-generator.js:251:26)
    at NodeEventGenerator.applySelectors (...\node_modules\eslint\lib\util\node-event-generator.js:280:22)
    at NodeEventGenerator.enterNode (...\node_modules\eslint\lib\util\node-event-generator.js:294:14)
    at CodePathAnalyzer.enterNode (...\node_modules\eslint\lib\code-path-analysis\code-path-analyzer.js:632:23)

I can't tell which files are causing this because that information isn't in the output. Still, I'd like to help out, so let me know if you need more information from me.

babel-eslint: ^9.0.0
eslint: ^5.13.0

i was getting the same range of null issue trying to use this parser, and for whatever reason, deleting node_modules and yarn.lock and then reinstalling dependencies cleared up the issue. i also changed the declared versions from a static to caret style, so maybe there's a small version mismatch in there somewhere which finally got unstuck with that bit of looseness?

I had to downgrade to the same version @worc post it. With babel-eslint ^10.0.1 wasn't working.
I tried remove node_modules, package-lock.json and install all dependencies again, didn't work either.

I have same package-lock.json without lockfile,
using npm install to get all dependencies, gets this range of null error,
using yarn to get all dependencies, it's all fine
using<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

I'm facing this problem too and I solved it also by removing node_modules and regenerating yarn.lock. However regenerating the whole lockfile shouldn't be considered a viable choice, because it collides with the concept of a lockfile (and it also breaks my system at other places). Are there any other known solutions to this problem?

Back when I ran into this, I upgraded to the latest version 11 beta, and that solved this issue. Recently though, I started to run into a different problem with babel-eslint, and searching through issues revealed that dropping back down to version 10 was the solution, so now I'm running 10.0.3 and everything works.

我有同样的问题
TypeError: Cannot read property 'range' of null
Occurred while linting E:\AQSC\fe\frontapp-vue-samples\src\store\modules\tpridmp\common\permission.js:7
    at SourceCode.getTokenBefore (E:\AQSC\fe\frontapp-vue-samples\node_modules\eslint\lib\token-store\index.js:303:18)
    at checkSpacingBefore (E:\AQSC\fe\frontapp-vue-samples\node_modules\eslint\lib\rules\template-curly-spacing.js:60:42)
    at TemplateElement (E:\AQSC\fe\frontapp-vue-samples\node_modules\eslint\lib\rules\template-curly-spacing.js:119:17)
    at listeners.(anonymous function).forEach.listener (E:\AQSC\fe\frontapp-vue-samples\node_modules\eslint\lib\util\safe-emitter.js:45:58)
    at Array.forEach (<anonymous>)
    at Object.emit (E:\AQSC\fe\frontapp-vue-samples\node_modules\eslint\lib\util\safe-emitter.js:45:38)
    at NodeEventGenerator.applySelector (E:\AQSC\fe\frontapp-vue-samples\node_modules\eslint\lib\util\node-event-generator.js:251:26)
    at NodeEventGenerator.applySelectors (E:\AQSC\fe\frontapp-vue-samples\node_modules\eslint\lib\util\node-event-generator.js:280:22)
    at NodeEventGenerator.enterNode (E:\AQSC\fe\frontapp-vue-samples\node_modules\eslint\lib\util\node-event-generator.js:294:14)
    at CodePathAnalyzer.enterNode (E:\AQSC\fe\frontapp-vue-samples\node_modules\eslint\lib\code-path-analysis\code-path-analyzer.js:632:23)
Process finished with exit code -1

works for me
    "rules": {
      "indent": [
        "error",
        2,
        {
          "ignoredNodes": [
            "TemplateLiteral"
          ]
        }
      ],
      "template-curly-spacing": [
        "off"
      ]
    },

@fangbinwei  Thanks

Thank you for the issue. Now that @babel/eslint-parser has been released, we are making this repository read-only. If this is a change you would still like to advocate for, please reopen this in the babel/babel monorepo.


ramifications of scan with skip_detect_devices

Question Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Question Subject
When using scan, what is the effect of running it with skip_detect_devices?
Question Description
We have a persistent issue when CI is under heavy load where scan times out like this:
$ xcodebuild -showBuildSettings -workspace ./MyWorkspace.xcworkspace -scheme Debug
Command timed out after 3 seconds on try 1 of 4, trying again with a 6 second timeout...
Command timed out after 6 seconds on try 2 of 4, trying again with a 12 second timeout...
Command timed out after 12 seconds on try 3 of 4, trying again with a 24 second timeout...
Command timed out after 24 seconds on try 4 of 4

I suspect it's timing out on simulator detection. We're not specifying device or devices in the scan config, so it's possible adding the device explicitly will solve this issue, but I'm intrigued by skip_detect_devices. However, the docs just say Should skip auto detecting of devices if none were specified without explaining why you'd want to do that or what happens if you do.

The PR that added the functionality has some background: https://github.com/fastlane/fastlane/pull/13285
Here is the code that is executed if the skip is not defined:
https://github.com/fastlane/fastlane/blob/24fb2c9552a3367f41101764abf31ecc548e27d4/scan/lib/scan/detect_values.rb#L169-L185


vanishing ships completely need help would definitely appreciate it thanks

The version of the mod I am using davincisvessels-1.12-6.340-full
my Minecraft version 1.12.2
my Forge version <IP_ADDRESS>94
The crash report or log however don't have one because it doesn't crash unfortunately however i do have pics of the build

hi it me crae a long loving fan of your mod even scene archimedes ship pre version i was building a ww2 custom air blimp for fun and i rain into problems with the build it seems to be when the ship get very large some reason and i don't know why so i went to the best people that would know the answer
here is a good look at the ship
here are the pics
this is to give you a good idea of the ship i am building

![2019-03-08_12 35 09](https://user-images.githubusercontent.com/37277242/54055433-edff9180-
41a1-11e9-88c2-bf216b63b3c5.png)
![2019-03-08_12 35 22](https://user-images.githubusercontent.com/37277242/54055436-ef30be80-
41a1-11e9-8c5d-05ca18c7c54c.png)

now a play by play what happens
left click the ships helm

left click the ships helm and then click the  assemble ship gui this will give you an idea of the size of the ship

then get in the ship

mounts the ship "time of the glitch"

does not crash and click shift

keep in mind that i set the config  to this that is why it is able to fly
New Text Document (2).txt

even an explanation will help a lot

brain flash does it have to do with the build being over 1 chunk size because if that the case it would be 2 chunks lon

just thinking

and i am only using 3 mod in the build so i don't think that would be a problem

and i have been noticing you haven't been answering these type of problems

why is that

Duplicate of #233

found a fix it is your render distance rase it  wtf why that's a thing but it works


Suggestion for abusing intra-realm and inter-realm attacks using pre2k

Hi,
Thank you for this tool!
I have a suggestion. I tested your tool in a parent-child (intra-realm) trust abuse scenario and in a bidirectional forest (inter-realm) trust abuse scenario. Basically I am trying to attack the parent/target domain or the target forest by executing the auth command using credentials from the related child/source domain or from the related source forest. This fails.
This is not very surprising since your tool uses the domain entered using the -d flag as both the domain for the authentication and for knowing which domain to attack. There is no way to enter a domain for authentication only.
Could this tool be updated to support the above scenarious? Perhaps keep the functionality of the current -d flag but add support for authentication the way Impacket does it. Ie [domain]/[username]:[password]" and of course corresponding NT hash, AES keys and Kerberos authentication?
Thanks!

Hey @jsdhasfedssad thanks for the suggestion. Will look into this soon and it shouldn't be hard to adjust the base_dn for the initial query and then set the target domain for the spray afterwards. I don't think I'll be adjusting the authentication syntax at this time though.

Fixed in #17


[BUG] Building Cython extension on Windows triggers TypeError

setuptools version
setuptools==70.2.0
Python version
Python 3.12
OS
Windows
Additional environment information
MSYS2 MINGW64
Description
Version 70.2.0 triggers a TypeError: unsupported operand type(s) for +: 'NoneType' and 'str' when building a Cython extension on Windows using MSYS2 MINGW64. Previous versions of setuptools work fine.
Expected behavior
The Cython extension should build successfully without any errors.
How to Reproduce

Create a directory with three files helloworld.pyx, setup.py, and setup.cfg:

# helloworld.pyx
print("Hello World")

# setup.py
from setuptools import setup
from Cython.Build import cythonize

setup(
    ext_modules = cythonize("helloworld.pyx")
)

# setup.cfg
[build]
compiler = mingw32

Launch a MINGW64 environment and go to the directory above.
Run: C:\path\to\python.exe setup.py build_ext --inplace

Output
running build_ext
Traceback (most recent call last):
  File "C:\Users\Daniel\Desktop\reproducer\setup.py", line 4, in <module>
    setup(
  File "C:\Users\Daniel\AppData\Local\Programs\Python\Python312\Lib\site-packages\setuptools\__init__.py", line 103, in setup
    return distutils.core.setup(**attrs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Daniel\AppData\Local\Programs\Python\Python312\Lib\site-packages\setuptools\_distutils\core.py", line 184, in setup
    return run_commands(dist)
           ^^^^^^^^^^^^^^^^^^
  File "C:\Users\Daniel\AppData\Local\Programs\Python\Python312\Lib\site-packages\setuptools\_distutils\core.py", line 200, in run_commands
    dist.run_commands()
  File "C:\Users\Daniel\AppData\Local\Programs\Python\Python312\Lib\site-packages\setuptools\_distutils\dist.py", line 970, in run_commands
    self.run_command(cmd)
  File "C:\Users\Daniel\AppData\Local\Programs\Python\Python312\Lib\site-packages\setuptools\dist.py", line 974, in run_command
    super().run_command(command)
  File "C:\Users\Daniel\AppData\Local\Programs\Python\Python312\Lib\site-packages\setuptools\_distutils\dist.py", line 989, in run_command
    cmd_obj.run()
  File "C:\Users\Daniel\AppData\Local\Programs\Python\Python312\Lib\site-packages\setuptools\command\build_ext.py", line 93, in run
    _build_ext.run(self)
  File "C:\Users\Daniel\AppData\Local\Programs\Python\Python312\Lib\site-packages\setuptools\_distutils\command\build_ext.py", line 329, in run
    customize_compiler(self.compiler)
  File "C:\Users\Daniel\AppData\Local\Programs\Python\Python312\Lib\site-packages\setuptools\_distutils\sysconfig.py", line 333, in customize_compiler
    cpp = cc + " -E"  # not always
          ~~~^~~~~~~
TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'

@jaraco would it be possible to transfer this issue to pypa/distutils as indicated in laska's analysis in #268.
@naveen521kk, would it be possible to help with this problem (as a potential unintended consequence of #184)?

I saw this then lost track of it. I've transferred it now. We should figure out how to give @abravalheri access to transfer (I did not realize it had not already been granted).

@lazka Thanks for the heads up! I’ll let you know if I encounter any issues.


DLib Extremely long to compile with clang on windows

Expected Behavior
Reasonable compilation time
Current Behavior
Compilation with clang on windows on a 20 core machine is taking approx. 20 minutes to compile this net architecture:
https://arxiv.org/pdf/1611.09326.pdf
My question is more, is there any trick that I could use? With Visual Studio standard toolset, it's not even compiling, but VC is not a good C++ compiler.
Steps to Reproduce
Unfortunately I cannot provide any code.

Version: master asof March 2018.
Where did you get dlib: this github
Platform: 64 bits Windows 7
Compiler: LLVM Clang + MSVC linker

Make sure you use 64-bit compiler on Windows. By default it picks 32-bit which usually runs out of memory compiling heavily templates code like dlib.

@edubois, is the dlib implementation of this specific network architecture available somewhere?

@reunanen : Yes: https://arxiv.org/pdf/1611.09326.pdf

@edubois Hmm, to me it looks like Theano / Lasagne, and not dlib?

I'm not sure I understand, but unfortunately, there are no dlib implementation public / that I can make public.
Because of this problem, and for this kind of network, I'm thinking of switching to caffe2.

Following


Simplify unit-one-sourcefile-remapped.swift round trip testing

No longer test the round trip remapping for the output file - we'll be
changing the reader to preserve the canonical output file path instead
of converting it back to local. Once all of the changes are complete, we
can swap this to verify it is canonical, but indexstore-db will also
check this with its own tests.

@swift-ci please smoke test

This will obviously fail. I should cherry-pick my rebranch changes to next, though it's likely there's further issues now.

@swift-ci please smoke test


Msal Js Supports Conditional Access

Conditional access is fully supported in Msal Js

well tested fully functional conditional access support

@pkanher617  can you add details / context here