text:
fbgate interaction dont work.

Impossible enter on fbgate furnis.

Can  you post a screenie please?

Edit: Works Fine.

Impossible enter on fbgate furniture.
I think no bad coded, just packet error.
Video: http://tinypic.com/player.php?v=2wpo58o>&s=9#.V5syjxWLS70

Did you tried click directly in the gate?

Yes, and dont work ^^.

Sad. We will try to fix it in LINUX branch Release's. But, we are currently busy by rewriting the entirely Emulator..


text:
Can add Loader ,   give schema and []byte , parse to map or struct ?

I previously used github.com/xeipuuv/gojsonschema to validate JSON schema and extract data from JSON requests, but it has not been maintained for a long time. I'm considering switching to another library, but I noticed that it doesn't have the Loader functionality. Is there any plan or possibility to add it in the future?
Need
// w http.ResponseWriter, r *http.Request
result,err := jsonschema.SchemaDataLoader(r.Body)
if err == nil {
    data := result.(map[string]interface{}) // or some struct
}

Thank you~

see following examples from godoc (https://pkg.go.dev/github.com/santhosh-tekuri/jsonschema/v5)

FromString
FromStrings
UserDefinedLoader

source: gharchive/issue

repo: santhosh-tekuri/jsonschema

license_type: permissive

license_source: github-api


text:
🛑 KONGA_KONG_GUI_URL is down

In 9371067, KONGA_KONG_GUI_URL ($KONGA_KONG_GUI_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: KONGA_KONG_GUI_URL is back up in 0b22a4d after 16 minutes.

repo: santomaharaj/upp

license: MIT


text:
🛑 GRAFANA_URL is down

In d463c97, GRAFANA_URL ($GRAFANA_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: GRAFANA_URL is back up in 7169b44 after 37 minutes.


text:
[BUG] multiple content file copied to "js" folder  and html file for content file

Describe the bug

copying multiple content files to js folder does not work. creates js.js file instead

creates html files for each content file

To Reproduce
1)
added to vue.config,js
const CopyWebpackPlugin = require("copy-webpack-plugin"); to top
and replaced
  configureWebpack: {
    output: {
      filename: `js/[name].js`,
      chunkFilename: `[name].js`
    },

with this
  configureWebpack: {
    output: {
      filename: `js/[name].js`,
      chunkFilename: `[name].js`
    },

no chnges in vue.config.js

Use Vue cli create project

Vue CLI v5.0.1
? Please pick a preset: Manually select features
? Check the features needed for your project: Babel, TS, CSS Pre-processors, Linter
? Choose a version of Vue.js that you want to start the project with 2.x
? Use class-style component syntax? No
? Use Babel alongside TypeScript (required for modern mode, auto-detected polyfills, transpiling JSX)? Yes
? Pick a CSS pre-processor (PostCSS, Autoprefixer and CSS Modules are supported by default): Sass/SCSS (with dart-sass)
? Pick a linter / formatter config: Prettier
? Pick additional lint features: Lint on save
? Where do you prefer placing config for Babel, ESLint, etc.? In dedicated config files
? Save this as a preset for future projects? No

Install chrome-extension-cli Plugin

? Name of the Chrome Extension? chrome-extension-name
? Description for the Chrome Extension? chrome extension
? Version for the Chrome Extension? 0.0.1
? manifest_version for the Chrome Extension? 3
? delete Initial file? (src/main.js src/components public/index.html public/favicon) Yes
? Please select the required components : background, popup, content

See error something error...

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
please complete the following information:

Node Version: [16.14.0]
OS: [Mac OS Big Sur]
Vue Cli Version [5.0.1]

Additional context
Add any other context about the problem here.

this plugin use fs.readdirSync function in entry folder.
so, other js file not recommend in this folder .
please create new foler put other js folder.
because entry folder just generate extension file , like popup.html .

this plugin use fs.readdirSync function in entry folder. so, other js file not recommend in this folder . please create new foler put other js folder. because entry folder just generate extension file , like popup.html .

Thanks for the reply
Sorry
I did not understand


text:
Please, add an easy way to copy the text that generates.

It would be great to be able to copy the text it generates. Not always we are looking for code, but for analysis, explanations and critique+improvements.
But it's great. Can't complain.

v1.0.6 now has the ability to export tasks to markdown. I hope this helps you get what you were looking for, but if not feel free to re-open with more specifics.

authors: iHopist saoudrizwan

repo: saoudrizwan/claude-dev


text:
Deploy Your Multi-Target Application (MTA)

Tutorials: https://developers.sap.com/tutorials/btp-app-cap-mta-deployment.html
Write here how you think we can improve the tutorial ...
I had a few issues with Step 8.

When running "mbt build -t ./" it dropped an error "Error: could not build the MTA project: could not execute the "make -f Makefile_20220918093942.mta p=cf mtar= strict=true mode= t="./"" command: exec: "make": executable file not found in %PATH%"
although I followed the previous steps when configuring MTA, the PATH variable had not been updated in the system. To resolve this, the PATH variable should be it. For me it was "C:\Program Files (x86)\GnuWin32\bin" to PATH.

At the beginning of the step it says "Delete your older package-lock.json to avoid errors due to use of older versions.", which I did (although I re-named it to "package-lock.json_old"), but the it failed with the following error

"npm ERR! The npm ci command can only install with an existing package-lock.json or
npm ERR! npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or
npm ERR! later to generate a package-lock.json file, then try again."
It looks that it did not attempt to re-create the file, but was just stopping because the file was not found.
When I added the file back by re-naming from "package-lock.json_old" to "package-lock.json", it did not work because package.json and package-lock.json were no in sync.
In order to resolve the error I had to re-create package-lock.json with "npm install --package-lock-only"
After this, it all worked well.
Please consider to add these two notes if anyone else has encountered the same issues.

Hi @kirillgromyko ,
Thank you for taking time to provide your feedback. Regarding the first issue are you using git bash as we describe here? We are working on adding the command for recreating the package-lock.json.
Thanks and best regards,
Manju

Hi @kirillgromyko,
Please take a look and follow the steps in Step 2: (For Windows) Install make tool.
It mentions specifically to add C:\Program Files (x86)\GnuWin32\bin to your PATH variable and restart VS Code afterwards.
Hope this helps.
Please let us know in case you have other issues.
Best regards,
Svetoslav

Hi @kirillgromyko,
Thank you for your feedback. We haven't heard from you in a while, so we are closing the issue. If you still have questions, feel free to open a new issue.
Best regards,
Iwona

authors: iwonahahn kirillgromyko manjuX slavipande

repo: sap-tutorials/Tutorials


text:
Bypass sni ingress proxy in the shared kubernetes client factory

This should fix hanging node observeratory watches we had in the past one one if the control plane nodes goes away without warning.
We already use this for the controller-manger and scheduler were we didn't observe hanging client to my knowledge.

@BugRoger ping

source: gharchive/pull-request

repo: sapcc/kubernikus

license_source: bigquery


text:
Offer alternative sort orders

Sorting icons alphabetically seems like the right default, but would you be opposed to allowing sorting by ctime or something in addition to that? The problem with alphabetical is that the content codepoints shift, so you can end up with icon classes pointing at the wrong icons (if you have a caching issue or if, like us, you have dynamically loaded css (versioned) but have to manually upload fonts for CORS reasons and didn't realize that until someone pointed out that our brand icon was suddenly the twitter icon). If they were sorted by ctime, new icons would always go at the end, and therefore couldn't mess up previous icons.

You can just store codepoints to a file using codepointsFile.

Is there an example of that? Do I have to make the file the first time or if I specify a file that doesn't exist, will it create it?

No, you don’t need to create a file. grunt-webfont will create it and the will add any new codepoints.

Ok, we'll give it try, thanks.

Oh, so that's a json file. That could go in the README. I wasn't sure what extension to give it. The values in the codepoint file are like 58880, but in the stylesheet, they're \e600 . . . is that correct?

I can add some stuff to the README here shortly. Just want to understand and make sure it worked correctly.

The values in the codepoint file are like 58880, but in the stylesheet, they're \e600 . . . is that correct?

Sure, both are numbers. But the only way to store hex numbers in JSON is to convert them to strings.

Ok, that's the part I wasn't sure about. Thanks.

authors: sapegin tandrewnichols

repo: sapegin/grunt-webfont

license: mit


text:
There is no search button in the generated flame graph.

Is there a flag to turn it on?

correct, we open for contribution

You can use the browser search capabilities

authors: cloud-fan saquibkhan wokier

repo: saquibkhan/javaFlameGraph


text:
[BUG] Players not working properly after exit Fullscreen

Describe the bug
I'm trying to make a GirdView with couple of videos. It works perfect(even when I switch videos randomly) on original screen. But once get into a full screen, and get back to the original screen, then the bug occurs.
Following unexpected situation occurs randomly (occurs together sometimes).
(1) Controller(play, pause, bottom bar, etc.) disappears but video still goes playing.
(2) Controller alives but plays audio only, with screen paused.
(3) Only play, pause buttons alive. Bottom bar disappears. Then, (2) happens to other videos.
To Reproduce
Below is my part of code. I'm using youtube_player_flutter: ^6.0.3+2
_controller = new List<YoutubePlayerController>();
_url = [
  "https://youtu.be/GAJgbyzSsxg",
  "https://youtu.be/93QS6CReUbQ",
  "https://youtu.be/qch5tdUQvYk",
  "https://youtu.be/-7XFvZmIcTE",
  "https://youtu.be/9w7e02i39lM",
  "https://youtu.be/HtNL9-35xaI",
  "https://youtu.be/baHYYZScKaw"
];
for (int i = 0; i < _url.length; i++) {
  YoutubePlayerController tmp = YoutubePlayerController(
    initialVideoId: YoutubePlayer.convertUrlToId(_url[i]),
    flags: YoutubePlayerFlags(autoPlay: false),
  );
  _controller.add(tmp);
}

// ...

child: GridView.count(
  crossAxisCount: 2,
  shrinkWrap: true,
  physics: NeverScrollableScrollPhysics(),
  crossAxisSpacing: 5,
  primary: true,
  children: List.generate(_url.length, (index) {
    return Center(
      child: YoutubePlayer(
        controller: _controller[index],
        onReady: (){},
      ),
    );
  }),
),

Technical Details:

Device: Samsung Galaxy S9+

Thank you for making good plugin :)

@sarbagyastha  i am also facing the same issue, video player after exit of fullscreen i am not able to make the video player fullscreen again.

Should fix with v7.0.0. Feel free to reopen if the issue persists.

authors: joelnv sarbagyastha wookje


text:
Full screen not working in ListView

Describe the bug
Full-screen mode is not working in listview. When we click on the
the full-screen icon just rotates the screen and doesn't show the video in full screen.
Screenshots

Technical Details:

Device: Oppo F11
OS: Android 10

Hi, may i know does this issue fixed?

How to solve this problem

How to solve this problem

Still, I am unable to solve the issue waiting for the response,

This fork works for me


text:
Render photos

Value proposition
As a user,
I want to have a list of my photos
so that I have a quick overview and don't have to remember all of my clothes.
Description

Acceptance criteria

[ ] Items (photos) are rendered
[ ] The button is always at the bottom
[ ] Photos scroll beneath the button
[ ] Items wrap

Complexity
Small
Tasks

[ ] Create branch
[ ] Add base styles
[ ] Setup Storybook for button
[ ] Implement button component
[ ] Write specs for button
[ ] Add button to app
[ ] Render photos in an unordered list

Hey Sarina,
nicely done.
My suggestions:

I would suggest to phrase the value proposition a bit more specific, for example:

As a user,
I want to have a list with photos of my clothes
so that I have a quick overview and don't have to remember all the clothes in my closet.

in your scribble you can indicate photos with a crossed out box :) As well, as I understand correctly the add-button will not have any functionality yet, therefore it should not be included in this story (neither in the scribble nor the acceptance criteria and tasks etc.)

authors: ahohnsen sarina-nikolic

repo: sarina-nikolic/capstone-project


text:
Install directly

Hello,
If i dont' have any possibility to git clone this module, how can I add it to my PS 1.7? There's another solution?

Thx for the fast answer!
I downloaded the composer but, when I try to create somethign I receive the "composer unavailable" message.
I add the zip then all is blocked....
What I have to do? :/

Assuming you are on Windows, you can follow this to install composer: https://getcomposer.org/doc/00-intro.md#installation-windows

Ok, I'm here and now I click on the install all packages. What I miss now? Where I can find it after the install? :)

Once you run composer, some files should be generated in D:\..\gamifications\vendor\ folder. Please check if you you see autoload.php, if so, you are good to go. Then move gamifications directory to your PrestaShop modules/ folder and install it from Back Office.

WAAAAAAAAAAAAAAAAAAAAAAAAAAA!!
<3 thank you master!!

T_T Why I don't see it into the modules section of PS?
I'm using PrestaShop: 1.7.2.4

repo: sarjon/gamifications


text:
🛑 Tian is down

In 69c2df3, Tian (https://www.tianaix.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Tian is back up in e553dfc after 37 minutes.

repo: sarpaykent/uptime


text:
🛑 Tian is down

In 683d027, Tian (https://www.tianaix.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Tian is back up in e396670 after 14 minutes.


text:
Build failed after adding fabric plugin.

I added fabric plugin in my ionic 3 app. It's working in android but for iOS it has a problem.
When running ionic build ios --prod or ionic build ios I am getting following error:
`/Users/abc/Library/Developer/Xcode/DerivedData/MyApp-fgpvbdhjneqliicfyhoiuvrrhbfs/Build/Intermediates/MyApp.build/Debug-iphonesimulator/MyApp.build/Script-FE794D9BFDB14C30B9E39200.sh: line 2: /Users/abc/Desktop/NS: No such file or directory
** BUILD FAILED **
The following build commands failed:
PhaseScriptExecution Fabric.io:\ Crashlytics /Users/abc/Library/Developer/Xcode/DerivedData/MyApp-fgpvbdhjneqliicfyhoiuvrrhbfs/Build/Intermediates/MyApp.build/Debug-iphonesimulator/MyApp.build/Script-FE794D9BFDB14C30B9E39200.sh

(1 failure)
Error: Error code 65 for command: xcodebuild with args: -xcconfig,/Users/abc/Desktop/NS H iOS 2/platforms/ios/cordova/build-debug.xcconfig,-workspace,MyApp.xcworkspace,-scheme,MyApp,-configuration,Debug,-sdk,iphonesimulator,-destination,platform=iOS Simulator,name=iPhone 5s,build,CONFIGURATION_BUILD_DIR=/Users/abc/Desktop/NS H iOS 2/platforms/ios/build/emulator,SHARED_PRECOMPS_DIR=/Users/abc/Desktop/NS H iOS 2/platforms/ios/build/sharedpch`

I have resolved this. I root project folder name have spaces. I removed all spaces. Now working fine.

repo: sarriaroman/FabricPlugin


text:
Error loading 'livecell_coco_train.json' using pycocotools

Hello.
I am trying to write a data generator to use LiveCell data to train a Keras model. While trying to read the annotation file 'livecell_coco_train.json' using pycocotools with the following code:
from pycocotools.coco import COCO
coco = COCO(annFile)
The following error is raised:

loading annotations into memory...
Done (t=28.31s)
creating index...

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
/tmp/ipykernel_57/539935055.py in <module>
     12     json.dump(dataset, f)
     13
---> 14 check_ANNT = COCO(ANNT_TRAIN_COPY)

/opt/conda/lib/python3.7/site-packages/pycocotools/coco.py in __init__(self, annotation_file)
     87             print('Done (t={:0.2f}s)'.format(time.time()- tic))
     88             self.dataset = dataset
---> 89             self.createIndex()
     90
     91     def createIndex(self):

/opt/conda/lib/python3.7/site-packages/pycocotools/coco.py in createIndex(self)
     96         if 'annotations' in self.dataset:
     97             for ann in self.dataset['annotations']:
---> 98                 imgToAnns[ann['image_id']].append(ann)
     99                 anns[ann['id']] = ann
    100

TypeError: string indices must be integers

I am not sure how to correct this error or if this is the wrong approach  to read the annotation file.

This seems to be a duplicate of #4, please check if that is helpful.

Thanks. I will try that solution.

authors: RickardSjogren alxndrdiaz

repo: sartorius-research/LIVECell


text:
error: Uncaught (in promise) Error: Request to v1/page/… failed

6월 30일경부터 액션 실패 중
Task wiki deno run --allow-read --allow-env --allow-write --allow-net wiki.js
error: Uncaught (in promise) Error: Request to v1/page/%ED%8B%80%3A%ED%94%84%EB%A1%9C%EC%84%B8%EC%B9%B4%20%EC%95%85%EA%B3%A1%20%EB%AA%A9%EB%A1%9D failed
      throw new Error(`Request to ${endpoint} failed`, { cause: data });
            ^
    at WikiActionClient.request (file:///home/runner/work/femiwiki-prsk-music-list/femiwiki-prsk-music-list/lib/wikiapi.js:32:13)
    at eventLoopTick (ext:core/01_core.js:168:[7](https://github.com/saschanaz/femiwiki-prsk-music-list/actions/runs/10337916744/job/28615331152#step:7:8))
    at async WikiActionClient.edit (file:///home/runner/work/femiwiki-prsk-music-list/femiwiki-prsk-music-list/lib/wikiapi.js:48:12)
    at async file:///home/runner/work/femiwiki-prsk-music-list/femiwiki-prsk-music-list/wiki.js:24:22
Caused by: {
  message: "Error: exception of type Error",
  httpCode: 500,
  httpReason: "Internal Server Error"
}
Error: Process completed with exit code 1.

당시 페미위키는 미디어위키 1.41에서 1.42.1^1로 업그레이드했습니다.

HTTP 500이 뜨는 건 미디어위키 버그 같은데 API 변경사항이 있어서 발생한 건지 그냥 버그인지 자세한 정보가 없어서 곤란하네요 🤔

repo: saschanaz/femiwiki-prsk-music-list

license: ISC


text:
Goals

I like that you added your goals. Maybe you can add in your reflection how it went and what went good and wrong etc.

Good point! Done

authors: Hilal-Tapan sasjakoning


text:
Programmatically change segment index

Hi, thanks for great lib :) I have a few questions.
Is it possible to change the selected segment programmatically, and if yes, how can I do that?
And my second question is:
is it possible not to have any index selected at all? Say, set the index to -1?
Thanks

Hi @khoren93,
I am really happy that you like it :)
With the next release that I am planning to publish soon, I will expose a property that you will be able to use to set the selected segment programatically.
Unfortunately, currently it is not possible to have the index set to -1, i.e. not to have any selected segment. However, I like your suggestion and I will try to implement this one in the next release as well.
Cheers,
Sasho

Hi @khoren93,
I just wanted to give you an update regarding your requested feature :)
I have just published a new version of the library (v. 1.1.0) in which I have exposed a property and a method for setting the current segment.
You can use the currentSegment property to set the currently selected segment to a different index that ranges from 0 to segmentsCount-1. You should set this property in the viewDidAppear(_:) method because at this points all subviews of the segmented control have been created. By setting this property, the segment will change without an animation.
If you need to change the segment programmatically with an animation, you can call the setCurrentSegmentIndex(_:animated:) method and pass in a bool for the animated parameter.
I hope that this answers your question and satisfies your needs :)
Cheers!

repo: sasojadrovski/SJFluidSegmentedControl


text:
Vulnerability in node-sass > sass-graph > yargs > cliui > strip-ansi > ansi-regex

NPM version (npm -v): 6.14.15
Node version (node -v): v14.18.0
Node Process (node -p process.versions):

{
node: '14.18.0',
v8: '8.4.371.23-node.84',
uv: '1.42.0',
zlib: '1.2.11',
brotli: '1.0.9',
ares: '1.17.2',
modules: '83',
nghttp2: '1.42.0',
napi: '8',
llhttp: '2.1.3',
openssl: '1.1.1l',
cldr: '39.0',
icu: '69.1',
tz: '2021a',
unicode: '13.0'
}

Node Platform (node -p process.platform): darwin
Node architecture (node -p process.arch): x64
node-sass version (node -p "require('node-sass').info"):

node-sass	6.0.1	(Wrapper)	[JavaScript]
libsass  	3.5.5	(Sass Compiler)	[C/C++]

npm node-sass versions (npm ls node-sass): node-sass@6.0.1

There is the following dependencies tree:
─┬ node-sass@6.0.1
│ └─┬ sass-graph@2.2.5
│   └─┬ yargs@13.3.2
│     ├─┬ cliui@5.0.0
│     │ ├─┬ strip-ansi@5.2.0
│     │ │ └── ansi-regex@4.1.0
When ansi-regex@4.1.0 have the following vulnerability issues:
https://snyk.io/vuln/npm:ansi-regex@4.1.0
Is there a chance that sass-graph@2.2.5 dependency can be updated in order to fix the issue?

https://github.com/sass/node-sass/pull/3044

@alexarsh I had the same issue today. After a lot of trial and error I finally noticed this error message:
npm WARN EBADENGINE Unsupported engine { package: 'node-sass@6.0.1',
npm WARN EBADENGINE   required: { node: '>=12' },
npm WARN EBADENGINE   current: { node: 'v10.22.1', npm: '7.21.1' } }

So I ran nvm install v14.18.1 to update my version of node to 14 and it fixed the issue for me. Good luck to you.

For many projects dart-sass is substantially slower so is not a viable solution in a lot of cases. In some of our foundation-sites projects the incremental compilation moves from 5 seconds to approximately 5 minutes or longer. There is a new dart VM hosted compilation module in the works but its still very much experimental and no webpack integration yet.
Possibly the best approach is to absorb sass-graph module into node-sass in its current state and then update the dependencies in node-sass accordingly? Would allow node-sass to remain in maintenance mode successfully for a while until the other options mentioned above are available.

Any updates on this?  Has any work been done to absorb sass-graph into node-sass as suggested in the previous post?

I opened #3202 to absorb sass-graph as suggested, but the maintainers haven't responded anything yet. not sure what else I can do...

sass-graph does not seem to be maintained, is there any update to node-sass?

sass-graph@4.0.0 has been released with a patch for this.

Fixed in 7.0.1.

authors: EchoZhaoH alexarsh driskell fmaddenflx katannshaw kiskoza matt-cote xzyfer

repo: sass/node-sass


text:
Add support for lists in functions.

Hello.
I was a bit surprised that all Sass value types were supported except List. I would find List useful in my own project, would you like to have it in, too?
Thank you!

Thanks!

authors: bolandrm kaukas

repo: sass/sassc-ruby


text:
Rules explicitly turned off if not listed ESLint style

It's not clear if rules not present in sass-lint.yml files are turned off automatically (ESLint 1.0 style) or not.
With early runs of gulp-sass-lint, that does not seem to be the case; for codebases that have both Sass & SCSS litn files, it seems there's issues propagating from gonzales-pe unless trailing-semicolon is explicitly set to 0 rather than merely omitting the rule altogether:

Seemingly any rule not listing in the sass-lint.yml should be turned off (severity of 0)  since that's the clearest way for users of the plugin-in to communicate they are not concerned of that rule being applied to their codebase.
Overtime, it can be more work for them to apply rules they don't care about in their codebase than the rules they care about as rules become simultaneously more useful & complex.

I originally had it so that user config overrode the default configuration instead of merging, but found that if someone only wanted to change indentation, for instance, they needed to be explicit with their whole configuration.
One option is to not have anything configured by default.

That sounds very sensical to me actually; for the ESLint-style behavior, perhaps it's a flag?

authors: Snugug lozandier

repo: sasstools/sass-lint


text:
chore: version up

Summary by CodeRabbit

New Features

Updated the project version to 0.6.1, indicating potential enhancements or bug fixes.

Bug Fixes

Minor version update may include resolved issues from the previous version.

coverage: 85.357%. remained the same
when pulling 4f5decadc559ad3d3751765f9d4ace07e2cc2d43 on v0.6.1
into e434fca8398f4367face7f9dbe62483ca84f6aaf on main.

authors: coveralls satoren


text:
add .travis.yml and update README.md

Summary
Please add .travis.yml and update README.md file.
Pull Request

#4

Merged #4

repo: satosystems/macrm


text:
hide a tab if it contains empty data

Hi,
I Have a tabbar contains 3 tabs: elearning, stages and documents each of them contains some data and may some tabs not contain anything, what I want is:
if stages tab didn't contain any data so it should not be displaying in tabbar that means in this cas I will have just 2 tabs elearning and documents.
how can I do that?
thank you

Hello Team,
Is the above mentioned functionality  achieved?

Reopen this issue.


text:
Sharing SQLite database between apps

Thank you for making Sugar ORM available to the development community — it’s an extremely useful and well-documented solution for using SQLite.
Can Sugar ORM facilitate the sharing of a database between two apps? In my case, the apps have exactly the same namespace, sharedUserId, and meta-data entries in the manifest (DATABASE, VERSION, DOMAIN_PACKAGE_NAME). Both apps have “com.orm.SugarApp” for android:name.
One app writes records and the other tries to read them. Only one app is active at a time. The first app can create and read records no problem. But the second app returns zero records for the exact same query used on the first app (e.g. List allMyPojoRecords = MyPojo.listAll(MyPojo.class);

For know this is not possible to achieve. But in the future we will be adding a metada tag to support these. If you have an idea on how to solve this, please submit a Pull request and I will code review it.

I believe you could share your database using Content Provider, this PR #556 will add Content Provider for Sugar, but it will be a breaking change

repo: satyan/sugar


text:
fix: get all encounter associated resources

Fixes the panic for newly created patients when no associated resources are found

Review Checklist

Summary*

[ ] fix: Bug fix for Add the items tackled here as checklists
[x] feat: Completed task
[ ] chore: Incomplete task

[ ] test: Sub-task 1

Structure*

[ ] The Pull Request has a proper title that conforms to our MR title standards
[ ] The Pull Request has one commit, and if there are more than one, they should be squashed
[ ] The commit should have a proper title and a short description
[ ] The commit must be signed off
[ ] Unused imports are not present
[ ] Dead code is not present
[ ] Ensure dry running library to confirm changes

Tests

[ ] Proper and high quality unit, integration and acceptance(if applicable) tests have been written
[ ] The coverage threshold should not be lowered

Sign off*

[ ] All comments have been resolved by the reviewers
[ ] Approved by Czar {replace_with_czar_name}
[ ] Signed off by second reviewer {replace_with_name}
[ ] Ensure all checks are done before merging :warning:
[ ] All PRs needs to be signed before merging :warning:

N/B:

Add a checklist if more than one item is done.
Add screenshots and/or images where necessary
Indicate any breakages caused in the UI :exclamation:
Where necessary, indicate which issue the Pull Request solves (Closes #)
Any new files are updated in the folder structure in the README

Pull Request Test Coverage Report for Build 8323258636
Details

25 of 25 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 82.172%

Totals

Change from base Build 8296403801:
0.04%

Covered Lines:
7089

Relevant Lines:
8627

💛  - Coveralls

authors: KathurimaKimathi coveralls

repo: savannahghi/clinical


text:
Is it possible to put the logseq-plugin to hugo site?

I use the table of content plugin in logseq.
Let me think that is possible to put the plugin function into the hugosite.

On the other hand,the hugo site has some function that is similar to logseq-plugin.
Maybe we can let it replace automatically.

For example:

https://adityatelange.github.io/hugo-PaperMod/posts/papermod/papermod-features/#show-table-of-contents-toc-on-blog-post

I suppose the table of content plugin in Logseq works the same as toc in Hugo. It will use header (like ## This is my header 1) and automatically generate a toc from these. So you would simply need to setup a toc in your Hugo site. I suppose the one you've linked would do.


text:
chore: release main

:robot: I have created a release beep boop
baggie: 2.4.0
2.4.0 (2024-01-16)
Features

react: Add FadeContent (24b35f7)

react: 1.3.0
1.3.0 (2024-01-16)
Features

react: Add FadeContent (24b35f7)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/saxofonsolo/baggie/releases/tag/baggie-v2.4.0 :sunflower:

:robot: Release is at https://github.com/saxofonsolo/baggie/releases/tag/react-v1.3.0 :sunflower:

repo: saxofonsolo/baggie


text:
ScrollIntoView does not work when item is not within cache

Describe your issue
Hi all, and first of all, thanks for maintaining this package.
I have a ListBox whose panel is a VirtualizingWrapPanel, similar to the following one, with item grouping. The ItemsPanelTemplate is set in code, because we have different templates based on different options, but I leave here the one the uses the VirtualizingWrapPanel
 <ItemsPanelTemplate>
                            <vwp:VirtualizingWrapPanel Orientation="Vertical">
                                <vwp:VirtualizingWrapPanel.Resources>
                                    <DataTemplate DataType="{x:Type XXXl}">
                                    </DataTemplate>
                                </vwp:VirtualizingWrapPanel.Resources>
                            </vwp:VirtualizingWrapPanel>
  </ItemsPanelTemplate>

<ListBox
                             ScrollViewer.HorizontalScrollBarVisibility="Disabled"
                             SelectionMode="Extended"
                             SelectionChanged="DetailList_OnSelectionChanged"
                             VirtualizingPanel.IsVirtualizing="True"
                             VirtualizingPanel.IsVirtualizingWhenGrouping="True"
			     VirtualizingPanel.IsContainerVirtualizable="True"
 			     VirtualizingPanel.CacheLengthUnit="Item"
			     VirtualizingPanel.CacheLength="15"
			     VirtualizingPanel.VirtualizationMode="Recycling">
            <ListBoxEx.GroupStyle>
                <GroupStyle>
                    <GroupStyle.HeaderTemplate>
                        <DataTemplate>
                            <TextBlock Text="{Binding Path=Name}"
                                       Margin="0,5,0,5"
                                       Padding="2,2,2,2"/>
                        </DataTemplate>
                    </GroupStyle.HeaderTemplate>
                </GroupStyle>
            </GroupStyle>
        </ListBox>

The issue is that when I call ListBox.ScrollToViewModel, it only works if the ViewModel is within the range of view models currently being cached. It works if:

I disable virtualization (which for obvious reasons is not an option)
I make the cache very large so all elements in the list fall within the cache (this is essentially equivalent as disabling virtualization, so it is not an option)
It works if I replace the ItemsPanelTemplate for a VirtualizingStackPanel or a WrapPanel, so I suspect something is not properly implemented in VirtualizingWrapPanel

I've also tested different parameter combinations unsuccessfully (e.g. different CacheLengthUnit, VirtualizationMode, etc.)
I've dived bit into the code, and this is what I've found so far. Calling ScrollToViewModel on a ViewModel outside cache range (this is not called on items within range), ends up calling protected override void BringIndexIntoView(int index)
https://github.com/sbaeumlisberger/VirtualizingWrapPanel/blob/f25434e1cc1996d3990eb75986842d9c8475dd98/src/VirtualizingWrapPanel/VirtualizingWrapPanel.cs#L374
which in turn calls SetVerticalOffset
https://github.com/sbaeumlisberger/VirtualizingWrapPanel/blob/f25434e1cc1996d3990eb75986842d9c8475dd98/src/VirtualizingWrapPanel/VirtualizingPanelBase.cs#L384
In such a method, Offset is set to the desired offset to scroll and measure is invalidated so MeasureOverride is called.
In MeasureOverride, the problem is that my VirtualizingWrapPanel has an ItemsOwner that is a IHierarichicalAndVirtualizationScrollInfo
https://github.com/sbaeumlisberger/VirtualizingWrapPanel/blob/f25434e1cc1996d3990eb75986842d9c8475dd98/src/VirtualizingWrapPanel/VirtualizingPanelBase.cs#L262
so Offset gets overwritten at
https://github.com/sbaeumlisberger/VirtualizingWrapPanel/blob/f25434e1cc1996d3990eb75986842d9c8475dd98/src/VirtualizingWrapPanel/VirtualizingPanelBase.cs#L282
with the location of groupItem, which is not yet updated to the proper offset and contains the previous one.
What I suspect is that BringIndexIntoView is not correctly implemented. According to documentation (https://learn.microsoft.com/en-us/dotnet/api/system.windows.controls.virtualizingpanel.bringindexintoview?view=windowsdesktop-7.0), this method should "When implemented in a derived class, generates the item at the specified index location and makes it visible.". The current implementation is not doing this, but deferring the creation of the desired items to MeasureOverride (where things go wrong).
Looking at VirtualizingStackPanel source code, which works properly, https://referencesource.microsoft.com/#PresentationFramework/src/Framework/System/Windows/Controls/VirtualizingStackPanel.cs,1576 the desired items are created and made visible right there.
What do you think?
Thanks for the help
Version Info
1.5.7 and 1.5.8
Net Framework 4.7.2
Microsoft Windows 10 Enterprise Version	10.0.19044 Build 19044

Thanks for reporting. I have been able to reproduce your issue and am working on a fix.

New preview package with a fix is available: https://www.nuget.org/packages/VirtualizingWrapPanel/2.0.0-preview5
The stable release will follow soon.

The stable version has just been released: https://www.nuget.org/packages/VirtualizingWrapPanel/2.0.0

Closing this now. Feel free to open a new issue if there is any problem.

authors: ArnauPrat sbaeumlisberger

repo: sbaeumlisberger/VirtualizingWrapPanel


text:
remove __getitem__ from Mongoengine models

__getitem__ is typed to return Any since we don't have a way to derive overloads based off the class properties.
Instead of __getitem__ users can use getattr if they really want to access properties dynamically.

Fixed by #45. 0.13.0 has this change

authors: chdsbd sbdchd

repo: sbdchd/mongo-types


text:
One more example!

Just a comment:
how about inserting in the HowTo section an example which does not involve the use of data frames?
Let's say I have such data
x = np.arange(0,100)
x= np.arange(0,100,0.1)
y =[]
for i in range(1,5):
y.append(x**2)
how shall I use Joyplot with x and y?
Thanks!

I've added an example in the notebook and also fixed a bug that probably prevented you to use it with your data.

authors: capitanevs sbebo

repo: sbebo/joypy


text:
Add Pressure display in Temperature-Sensor

Hi Sebastian,
Can you add an option to display the Pressure value on the Temperature-Sensor ?
or Can you create a Pressure Sensor ?
I have several Xiaomi Temprature Sensor that can report Pressure

Thanks,
Vincent

Leider sind schon beide Info-Felder belegt. Du könntest Dir aber z.B. mit dem Additional Info-Feld weiterhelfen. Reicht das? VG!

authors: sbormann vgeannin


text:
Provide setting for using prompt from sbt-git if desired

This adds a setting freshUseGitPrompt and a flag useGitPrompt which defaults to false. If enabled sbt will be configured to use the prompt from the sbt-git plugin.
The sbt-git prompt will be activated by using the GitBranchPrompt plugin if needed. The regular prompt will be added to the common settings.
Further changes:

add .ensime_cache directory to .gitignore file
update sbt-header dependency to 1.8.0
update sbt-scalafmt plugin to 0.5.6
add text version of agpl3 license (I forgot that one in the previous pull request. :disappointed_relieved:)

Thanks!

FYI: 2.4.0 released with your contribution

Great, thanks! :grinning:

repo: sbt/sbt-fresh


text:
Update tools list of zinc users

Added mill, sorted list, added links to each tool.
This may replace #970 which is probably a bit unfair in terms of ordering, but seems stale.

To validate this pull request against other sbt modules, please visit this link.

authors: lefou typesafe-tools

repo: sbt/zinc


text:
Add polygon zkevm and zkevmTestnet to punk-wallet ui

Include polygon zkevm and zkevm testnet to punk-wallet.
I also noted that the uris for mumbai are incorrect and thought it would be appropriate for mumbai to sit under polygon.
Implementation:
mumbai updates

move mumbai below polygon
update mumbai urls

Punk-Wallet Chain List (add zkevm)

...
polygon
mumbai
zkevm
zkevmTestnet
...

colors
-zkevm is purple (#800080)
-zkevm testnet  is medium purple (#9370DB)
demo

zkevm-punk-wallet.surge.sh
0xb622e7e197E86c1Ad17cc9B9464Ef32c3c6FfBD7 - contract deployed on goerli

repo
zkevm-punk-wallet
commits

update mumbai uris
add polygon zkevm and zkevm to ui; move mumbai under polygon

questions

should the changes for mumbai and the addition of zkevm be different prs?

getting a page not found error when selecting an existing wallet - and this in the url - https://zkevm-punk-wallet.surge.sh/pk#metaPrivateKey_backup1682051861965

repo: scaffold-eth/punk-wallet


text:
Update sbt to 1.6.1

Updates org.scala-sbt:sbt from 1.4.9 to 1.6.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Scalafix Migrations

org.scala-sbt:sbt:1.5.0

https://gist.githubusercontent.com/eed3si9n/57e83f5330592d968ce49f0d5030d4d5/raw/7f576f16a90e432baa49911c9a66204c354947bb/Sbt0_13BuildSyntax.scala
Documentation: https://eed3si9n.com/syntactic-scalafix-rule-for-unified-slash-syntax

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: library-update, early-semver-minor, semver-spec-minor, scalafix-migrations, commit-count:n:2

Superseded by #61.

repo: scala-bones/scatonic-ideal


text:
Interop feature for the ** operator of ECMAScript 2016

See #4619. We need some interop feature for the ** operator introduced in ES 2016.

In addition to the compatibility issues, which can be solved by introducing @JSOperator, there is one design choice here. What do we do when emitting ES < 2016? I see 4 possibilities:

Emit the ** operator anyway, potentially breaking if run in an interpreter that doesn't support it.
This doesn't actually work with the GCC output because it breaks early, so not really an option.
Refuse it at link time in the Analyzer -- this is what we do for new.target, for example.
Replace by Math.pow -- that works for numbers but not for bigints. That could be deemed acceptable given that if we emit for ES < 2016, there "shouldn't be" bigints (which are ES 2020+). But if one feature-tests for bigints being supported at run-time, that is not going to do the right thing.
Replace it with a custom $pow function that accurately implements the semantics of ** both for numbers (with Math.pow) and bigints (by repeatedly applying *, although that's slow).

If only there was a non-syntax-based way to call the exponentiation operation on bigints, it would be cheap to implement 4. Unfortunately we cannot do anything but the slow repeated *. Note that we cannot polyfill in the sense of feature-testing to use the native ** if it's present, because it is syntax, so it would cause an early SyntaxError. We have to always use our slow implementation instead.
The new.target precedent is tempting for its simplicity. Its story was different, though, since there was no way to implement it correctly. Moreover, it would be nice to be able to write linkingInfo.esVersion-based branches that choose to use bigints and ** when targeting ES2020+. With 2., that's not possible, because the ** would survive when the optimizer is disabled, and so the Analyzer has to flag it as an error even if it is dead code after optimizations. A concrete example where that would be useful is in Float.parseFloatDecimalCorrection:
https://github.com/scala-js/scala-js/blob/c56b30fcfc3b963cc8cdb346a2033635f1635813/javalib/src/main/scala/java/lang/Float.scala#L232

Have you considered using eval to get around the syntax restriction? Basically an option like 4, that implements $pow via eval (like #4619). That also removes any concerns about forward compatibility. (What if ** starts supporting more types in the future).

Some environments have a hard stop on eval and other similar features. So we cannot rely on that.

Hmm... By hard stop you mean irrecoverable exception on usage or failure to load module on presence (IIUC with strict mode, eval is always recognizable statically)?
In general: I'm unsure whether it is a good idea to provide a polyfill in core for something the core doesn't need and where the trade-offs are not super clear cut (in environments where eval works, that might be the better / more performant option).
Thinking about this more, I think it might be valuable to break down what we provide:

The ability to use a later ES feature on a lower ES level via polyfill. This is not something we offer to user space code (and never have). We only do this if we need a certain feature in core (e.g. Symbols, Maps, fround).
The ability to write library code targeting different ES levels with decision at linking time. We are offering this through LinkingInfo.esVersion + inlining in the optimizer. This is a real problem for **. However, note that new.target suffers from the same limitation.
The ability to dynamically detect whether a feature is supported for the purpose of targeting a lower ES level statically (e.g. use BigInt's but don't assume Object.getOwnPropertyDescriptors is present). This seems like theoretical problem, form ES2015 to ES2016, ** is the only thing we use. For ES5.1 this would indeed be an issue (as in: a ES5.1 runtime that supports **), but it seems unlikely to be an issue in practice.
The ability to dynamically detect whether a feature is supported for the purpose of falling back to a different implementation if it is not. This is not specific to Scala.js for ** (or new.target) but is a problem for any code targeting JS.

On can argue that the combination of 2 + 4 is a problem for this specific case (especially BigInt, is there any downside to use Math.pow over **?).
Solutions 3+4 above address this by providing 1.
The eval proposal addresses this by baking in a hacky mechanism to solve 4 into core. Arguably a library could do the same.
My "in general" comment above questions backing down on 1 (in general).
Maybe it makes sense to investigate whether we can provide better support for 2? (now that I think about it globalFallback for JSImport solves a similar issue but for module styles).

Hmm... By hard stop you mean irrecoverable exception on usage or failure to load module on presence (IIUC with strict mode, eval is always recognizable statically)?

I'm not sure what's the worst that can happen. But there is already a pretty bad situation with CSP enabled in a web page. It can be configured to actively report any violation of the policy (instead of or in addition to blocking the evaluation), such that even a feature test will report a violation. That's not something we can afford, I think.

In general, I fully agree that proposing polyfills for user-space is not something we do. And we shouldn't set a general precedent for that.
What's unique about **, which made me consider it at all is the following:

We can feature-test bigints overall, and they can be used as fast-path to implement some operations (possibly even all of java.math.BigInteger) when they are available.
** is the only way to access native exponentiation on bigints, so we'd like to be able to use based on linkingInfo.esVersion. And we'd like to do that in libraries (including the javalib).
But we cannot actually do that because the linking behavior is such that an error must be reported before the optimizer can constant-fold it away.

If any of these were not true, then it would clearly not be worth it. So it's like you said for 2+4.

Maybe it makes sense to investigate whether we can provide better support for 2? (now that I think about it globalFallback for JSImport solves a similar issue but for module styles).

Scala Native has something like that, but at a significant cost in complexity for their equivalent of our Analyzer. If it were only about esVersion, it could remain manageable, but in general we may want other forms of conditions. It's unclear where to draw the boundary if we start in that direction.

Since it's unclear what's best, perhaps we should just go with the conservative option, i.e., disallow ** when emitting ES < 2016.

Yes, I agree. I don't think there is any doubt about what should happen when ES >= 2016. And by restricting it for ES < 2016, we can improve later without breaking compatiblity.

repo: scala-js/scala-js


text:
Support for Multiversal Equality

With multiversal equality in Dotty (https://github.com/lampepfl/dotty/issues/1247), it would seem inconsistent not to use it for operations based on == such as contains and indexOf, which are currently pretty unsafe:
scala> List(1,2) contains 'ko
val res3: Boolean = false

It has been agreed on before that these methods could benefit from M-E. Indeed, one can write things like:
scala> def contains[A,B](ls: List[A], b: B)(implicit eq: Eq[A,B]) = ls.exists(_ == b)
scala> contains(List(1,2), 'ko)
-- Error: <console>:5:2 --------------------------------------------
5 |  contains(List(1,2), 'ko)
  |                         ^
  |         Values of types Int^ and Symbol^ cannot be compared with == or !=

In order to make that work with current Scala, we could have a single Eq implicit available there so that contains would always work (as before).
One thing I noticed that may or may not be a problem is that adding a subtyping constraint to one of the type parameters makes the code type check again...
scala> def contains[A,B >: A](ls: List[A], b: B)(implicit eq: Eq[A,B]) = ls.exists(_ == b)
scala> contains(List(1,2), 'ko)
res0: Boolean = false

One thing I noticed that may or may not be a problem is that adding a subtyping constraint to one of the type parameters makes the code type check again...

That appears to be intended, because an instance of B could be an A (see top post in https://github.com/lampepfl/dotty/issues/1247), but it is unfortunate.

I've done a few experiments about how to type methods like ++. Discussion on https://www.reddit.com/r/programming/comments/6elim6/announcing_dotty_012rc1_a_major_step
_towards/diigfus/ points out that such methods might require extra parameters. Indeed, if such methods don't rely on eqAny they must all take extra instances, and if they rely on eqAny I think they lose assurances.
The results might be affected by https://github.com/lampepfl/dotty/issues/2707.
//import dotty.DottyPredef.{eqAny => _, _}
import scala.{Eq => _, _}
object Main {
  def equal[S, T](s: S, t: T) = s == t // it seems this should fail without eqAny.

  def contravWitness[A, B >: A](e : Eq[A, B]): Eq[A, A] = e
  //def contravWitness[A, B >: A](e : Eq[A, B]): Eq[B, B] = e
  def contains[A,B >: A](ls: List[A], b: B)(implicit eq: Eq[A,B]) = ls.exists(_ == b)
}

class Cell1[+T : [T] => Eq[T, T]](val value: T) {
  def contains[U >: T : [U] => Eq[U, T]](that: U) = value == that
}

class Cell2[+T](val value: T)(implicit _e: Eq[T, T]) {
  def contains[U](that: U)(implicit eq: Eq[T, U]): Boolean =
    value == that
}

class Cell3[+T](val value: T)(implicit _e: Eq[T, T]) {
  def contains[U >: T](that: U) = value == that
  def append1[U >: T](u: U): Cell3[U] =
    new Cell3(u) //uses eqAny
  def append2[U >: T](u: U)(implicit eq: Eq[T, U]): Cell3[U] =
    new Cell3(u) //uses eqAny
}

class ListCell[+T](val values: List[T])(implicit _e: Eq[T, T]) {
  def contains0[U >: T](that: U): Boolean =
    values.map(new Cell3[T](_)).exists(_.contains(that))
  def contains[U](that: U)(implicit eq: Eq[T, U]): Boolean =
    values.map(new Cell2[T](_)).exists(_.contains(that))
  def append1[U >: T](u: U): ListCell[U] =
    new ListCell(values :+ u) //uses eqAny
  def append2[U >: T](u: U)(implicit eq: Eq[T, U]): ListCell[U] =
    new ListCell(values :+ u) //uses eqAny
  def append3[U >: T](u: U)(implicit eq: Eq[U, U]): ListCell[U] =
    new ListCell(values :+ u)
}

I don't understand why you want to put an implicit on the CellN class itself instead of on the method. Any particular reasons?
As for classes such as Set and Map which implementations are based on equality internally, I don't think they need an implicit at all. It is understood that when you make a Set[A], the equals and hashCode of A are going to be used, and I cannot think of a case where having the implicit would prevent a common mistake (do you have some in mind?). From my own experience it feels like that's much less a source of errors than passing incompatible arguments in bare calls to == and contains, which is what Eq was designed to fix AFAICT.

I don't understand why you want to put an implicit on the CellN class itself instead of on the method. Any particular reasons?

@LPTK thanks for the comments.
CellN classes are just a minimal model of what you need for collections using equality like Set and Map. ListCellN is only a bit more realistic, but I agree you should use Map or Set.
I agree that having implicit arguments for contains-like method is a clear use case. For Map, that includes get and apply. There might be more such methods. But you might need more annotations to catch them all.
When writing these classes, do you hide eqAny or not?

if you disable it, it seems you need to show that the key/element type can be compared with itself, so you need extra implicit arguments to the class, and as a consequence also to methods like append (but also map). The only implementation of append above that doesn't use eqAny is ListCell.append3, and it does need an extra Eq instance.
if you keep eqAny enabled, you need to ensure manually that all methods like contains take an Eq argument. You might be able to check for that if you maintain enough negative tests. Past experience suggests the chance for bitrot cannot be neglected.

We can look at it this way:
It never makes sense to write 1 == "ok" or (_:Set[Int]) contains "ok", because that always returns false.
On the other hand, it sometimes makes sense to write Set(1, "ok") — the validity of a set does not, in general, depend on whether it makes sense to compare each individual element for equality. Therefore, the Eq constraint should not be used to parameterize Set.
As far as I understand,  Eq

Ok, that makes some sense, though supporting it stays hard. But can you know use contains on your Set of 1 and "ok", if it asks for an Eq instance? Thinking a bit about it, it seems that's only possible using eqAny, and I think this use would be valid. But this probably needs more investigation.

I think there's a much simpler solution to the issue with contains that does not involve Eq. The core problem is that the signature of contains is not what we want:
class ListCell[+T](val values: List[T]) {
  def contains[U >: T](that: U) = values.contains(that)
}

object Test {
  new ListCell(List(1,2,3)).contains("foo") // compiles because we can set U=Any
}

Everything would be fine if we wrote contains(that: T) but that's not possible because of variance checks. However, here it's perfectly fine to ignore variance, it's just that the compiler is not smart enough to see that, but we can force its hand:
import scala.annotation.unchecked.uncheckedVariance

class ListCell[+T](val values: List[T]) {
  // This use of uncheckedVariance is safe because we won't store `that` anywhere
  def contains(that: T @uncheckedVariance) = values.contains(that)
}

object Test {
  new ListCell(List(1,2,3)).contains("foo") // does not compile, as expected
  new ListCell(List(1,2,3)).contains(42) // but this works
}

If using @uncheckedVariance shocks you consider that the collection strawman already uses it in several places:  https://github.com/scala/collection-strawman/search?utf8=✓&q=uncheckedvariance&type=  :)

What about searching Numbers among other Numbers? You know, numbers of
different type? Or proxies? Repeat for any Eq instance across types.
If you go this way, do you show or hide uncheckedVariance in the docs?
On Jun 8, 2017 14:35, "Guillaume Martres" notifications@github.com wrote:

I think there's a much simpler solution to the issue with contains that
does not involve Eq. The core problem is that the signature of contains
is not what we want:
class ListCell[+T](val values: List[T]) {
def contains[U >: T](that: U) = values.contains(that)
}
object Test {
new ListCell(List(1,2,3)).contains("foo") // compiles because we can set U=Any
}
Everything would be fine if we wrote contains(that: T) but that's not
possible because of variance checks. However, here it's perfectly fine to
ignore variance, it's just that the compiler is not smart enough to see
that, but we can force its hand:
import scala.annotation.unchecked.uncheckedVariance
class ListCell[+T](val values: List[T]) {
// This use of uncheckedVariance is safe because we won't store that anywhere
def contains(that: T @uncheckedVariance) = values.contains(that)
}
object Test {
new ListCell(List(1,2,3)).contains("foo") // does not compile, as expected
new ListCell(List(1,2,3)).contains(42) // but this works
}
If using @uncheckedVariance shocks you consider that the collection
strawman already uses it in several places: https://github.com/scala/
collection-strawman/search?utf8=%E2%9C%93&q=uncheckedvariance&type= :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/scala/collection-strawman/issues/100#issuecomment-307089813,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AARsqK4qRWk6bumMEUXO7n3HI5MIavSFks5sB-qJgaJpZM4NxOKr
.

What about searching Numbers among other Numbers? You know, numbers of different type? Or proxies? Repeat for any Eq instance across types.

Just use .exists(_ == foo) instead of .contains(foo)

If you go this way, do you show or hide uncheckedVariance in the docs?

You need to be honest and show them, or fix the compiler so that they're not needed ;)

But can you know use contains on your Set of 1 and "ok", if it asks for an Eq instance? Thinking a bit about it, it seems that's only possible using eqAny

What's the problem with eqAny?

You need to be honest and show them, or fix the compiler so that they're not needed ;)

I think the compiler works exactly as intended here. By having ListCell be covariant, you're saying ListCell[A] can be used at any type B :> A.
So it should not be possible to allow breaches such as the one you suggest because the implementation of contains should  not be able to use the fact that that is exactly of type A, which would be unsound when the ListCell[A] object is used at type ListCell[B].
Here is your example slightly expanded:
import scala.annotation.unchecked.uncheckedVariance

// Your proposal:
class ListCell[+T](val values: List[T]) {
  def contains(that: T @uncheckedVariance) = values.contains(that)
}

// Now consider this:
def anyListCell: ListCell[Any] = new ListCell[Int](Nil) {
  override def contains(that: Int) = that + 1 > 0
}

anyListCell.contains("oops")

Exception in thread "main" java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Integer

Good point, you'd also need to make contains final in ListCell I guess, which should not be too annoying.

But can you know use contains on your Set of 1 and "ok", if it asks for an Eq instance? Thinking a bit about it, it seems that's only possible using eqAny
What's the problem with eqAny?

With eqAny in scope you can still write questionable comparisons—between Reddit and arising issues that seemed clear. Luckily, you can use it explicitly if it is not in scope. And it's not clear a Set(1, "ok") is ever a good idea: at best, one can wonder about how to make that fail more gracefully. (A warning somewhere for inferred Foo[Any] might not be a stupid idea).

If you go this way, do you show or hide uncheckedVariance in the docs?

You need to be honest and show them, or fix the compiler so that they're not needed ;)

It's not clear if the compiler can be soundly fixed (nobody proved that a final contains is sound). And part of the point of this rewrite was to have simple signatures (see the whole business with use cases and CanBuildFrom).
I claim that a signature with @uncheckedVariance is not clearly "simple enough" to show. We might have to accept it, but it isn't great. I don't

What about searching Numbers among other Numbers? You know, numbers of different type? Or proxies? Repeat for any Eq instance across types.

What I meant: we should be consistent in these situations.
When you write:

I think there's a much simpler solution to the issue with contains that does not involve Eq.

the overall result is "let's use one complicated solution for == and a different solution for contains, which isn't completely trivial". @smarter, can we agree more consistency is desirable if possible?

Just use .exists(_ == foo) instead of .contains(foo)

Well, on HashSet that means "just use a O(N) algorithm rather than a O(1) algorithm". Convert your foo to the right type seems a better idea, but not always possible.
Also, lots of the complexity of multiversal equality arises exactly to support comparisons across different types. If this isn't fully supported in a consistent way everywhere, one might want to reconsider that extra complexity.

My impression from the discussion here (and around multiversal equality in Dotty) so far is that it's too soon to incorporate this into the collection design. I suggest to explore this further in Dotty in a fork or once we're done with the integration into Scala 2.13. Adding Eq parameters to the collections and a fake Eq typeclass to Scala 2.13 would be premature at this point.

I agree more research seems indeed needed.
Should we move these questions to the Dotty repo? And what's the process for these language changes?
I also wonder how such language changes are going to be decided upon. Will multiversal equality be subject to the SIP before it's in the stable language?

While we're here: I just realized that @smarter proposal arguably exploits a typechecker misbehavior in Scala and Dotty, violating in some sense the Liskov Substitution Principle: everything possible on values of T must be possible on values of subtypes of T.
I'm not implying that's necessarily a bug.
Here's an example, that gives the same behavior in Scala and Dotty's REPLs (including workarounds for https://github.com/lampepfl/dotty/issues/2789):
import scala.annotation.unchecked.uncheckedVariance

class ListCell[+T](val values: List[T]) {
  final def contains(that: T @uncheckedVariance) = values.contains(that)
}
(new ListCell(List("")).contains(_: Any)) //fails
((new ListCell(List("")): ListCell[Any]).contains(_: Any))

That means that operations are possible in (new ListCell(List("")): ListCell[Any]) that aren't possible on new ListCell(List("")), and this seems a (syntactic) violation of the Liskov Substitution Principle. At least it's inconsistent: in OCaml's you always have to upcast manually, but in Scala you essentially never need to.

Note that this is not the only occurrence of the violation. I can write Nil.size but not ???.size although Nothing <: Nil.type.

authors: Blaisorblade LPTK smarter szeiger

repo: scala/collection-strawman


text:
Switch between java 7/8 on master

So that we can run scabot on Java 8, while keeping Jenkins on 7 (doesn't yet officially support 8?)

LGTM

and because Play 2.4 requires Java 8, and we're playing with adding a Play-based web UI for sabot

Switch as follows:
 . /usr/local/share/jvm/jvm-select
jvmSelect openjdk 8

authors: SethTisue adriaanm

repo: scala/scala-jenkins-infra


text:
Invalid variance inferred / variance check failed

Compiler version
3.5.0
Minimized code
trait Foo[-L] {
  def test[LF, F[_ >: L] >: LF]: Unit
}

Output
contravariant type L occurs in covariant position in type [_$1 >: L] >: LF of type F

Expectation
Should compile.
This works for example and I am not sure that the outer lower bound should change anything.
trait Foo[-L] {
  def test[F[_ >: L]]: Unit
}

This also doesn't work
trait Foo[-L] {
  def test[F[_ >: L] >: Unit]: Unit
}

But this does:
trait Foo[-L] {
  def test[F[_ >: L] >: Nothing]: Unit
}

Even funnier:
trait Foo[+L] {
  def test[F[_ >: L] >: Unit]: Unit
}

this complains that a covariant type occurs in ... contravariant position.

Firstly F[_ >: L] >: LF is our syntax for F >: [_ >: L] =>> LF.  When we check the lower bound we flip to contravariance.  But when we try to figure out what the variance of that L is, we accidentally bias to being in a covariant position, when we're actually in contravariant position.  So seems like it should be an easy fix (waiting for CI).

authors: dwijnand hobwekiva


text:
[WIP] Retry constraint.replace after constraint.updateEntry

Checking isSub on the resulting bounds may have introduced new constraints, which might allow us to replace the type parameter entirely.
Adapted from #20200
@jchyb can you test if this also addresses the performance issue in #20120 ?

These changes also solve #19955 independently of the changes in #20175, with I think a much more general solution.

Sure, let me check

Hmm. it doesn't seem to fix the performance here, unfortunately (typer still takes vastly more time in T1, which is the val that summons the implicit with the intersection type which causes the TypeBounds constraint)

I couldn't figure out how to test the changes with -Yprofile-trace.
Async profiler reports a 59% improvement in the Typer phase though.

Perfomance measurements:
Before changes:

T0: 52ms
T1, T1bis: 189, 79 ms
T2, T2bis: 5, 4 ms

After changes:

T0: 28ms
T1, T1bis: 13, 25 ms
T2, T2bis: 9, 6 ms

authors: EugeneFlesselle jchyb


text:
Backport "bugfix: Choose correct signature is signatureHelp for overloaded methods" to LTS

Backports #19707 to the LTS branch.
PR submitted by the release tooling.
[skip ci]

No regressions detected in the community build up to lts-19080.
Reference


text:
Sbt Dependency Submission reports wrong scala-library

https://github.com/erikvanoosten/metrics-scala/network/dependencies shows:

while 2.13.8 is not used in this project. Only scala versions 3.1.3, 2.13.10, 2.12.17 and 2.11.12 are used.

The scala3-library:3.1.3 depends on the scala-library:2.13.8:
https://repo1.maven.org/maven2/org/scala-lang/scala3-library_3/3.1.3/scala3-library_3-3.1.3.pom

repo: scalacenter/sbt-dependency-submission


text:
[Question] Does adding BinaryAndSourceCompatible for the first time make the next release binary incompatible?

Hi, first of all thanks for this plugin.
If this plugin is added for the first time to a library, and the intention is
ThisBuild / versionPolicyIntention := Compatibility.BinaryAndSourceCompatible

Does that make the next release binary incompatible with the current release?
I suppose the answer is no, but this happened here in scala-java8-compat library version 1.0.0-RC1 and it wasn't changed until 1.0.1. But in one of my projects I see a conflict between version 0.9.1 and 1.0.0.
[error] (dependencyTreeIgnoreMissingUpdate) found version conflict(s) in library dependencies; some are suspected to be binary incompatible:
[error]         * org.scala-lang.modules:scala-java8-compat_2.13:1.0.0 (early-semver) is selected over 0.9.1
[error]             +- com.typesafe.akka:akka-actor_2.13:2.6.17           (depends on 1.0.0)
[error]             +- io.getquill:quill-jasync_2.13:3.7.1                (depends on 0.9.1)

Cheers and thanks in advance.

Hi @naderghanbari,
What you see in your project is an error reported by the fact that akka depends on scala-java8-compat 1.0.0 and quill depends on scala-java8-compat 0.9.1, and those versions of scala-java8-compat are not binary compatible.
You need to either downgrade akka to a version that uses scala-java8-compat 0.9, or upgrade quill to a version that uses scala-java8-compat 1. By the way, I think the akka team should have bumped their major version number when they bumped their dependency to scala-java8-compat from 0.9 to 1, but that’s another story.
That being said, I didn’t answer your question. When you add versionPolicyIntention := Compatibility.BinaryAndSourceCompatible you ensure that your next release will be both binary and source compatible with your last release.

Thanks for your answer @julienrf .

those versions of scala-java8-compat are not binary compatible

When you add versionPolicyIntention := Compatibility.BinaryAndSourceCompatible you ensure that your next release will be both binary and source compatible with your last release

Timeline

version 0.9.x (doesn't have any versionPolicyIntention, does not depend on sbt-version-policy)
version 1.0.0 (introduces versionPolicyIntention := Compatibility.BinaryAndSourceCompatible)
version 1.0.1 (changes versionPolicyIntention accidentally)
version 1.0.2 (fixes the accidental change)

My understanding is

1.0.0 is binary compatible with 0.9.x
1.0.1 is binary incompatible with 1.0.0 and 0.9.x
1.0.2 is binary compatible with 1.0.1 and incompatible with 1.0.0 and 0.9.x

Where is the flaw in my understanding?

Hi,
That’s a good point that when 1.0.0 was released its versionPolicyIntention was BinaryAndSourceCompatible (although it is usually Compatibility.None when we cut a major release). However, MiMa was configured to compare 1.0.0 with 1.0.0-RC1. This means that 1.0.0 was checked to be compatible with 1.0.0-RC1, not 0.9.x.
That being said, maybe 1.0.0 is effectively binary compatible with 0.9.x, I don’t know this project well enough. But the fact that they bumped the major version number and they declare the versioning scheme early-semver means that tools (such as sbt) assume that 0.9.x and 1.0.0 are incompatible.

Maybe @SethTisue can shed some light about the actual state of compatibility between 0.9.x and 1.0.0, and the motivation for bumping the major version number?
In case 1.0.0 is indeed compatible with 0.9.x, you can tell it to sbt with:
libraryDependencySchemes += "org.scala-lang.modules" % "scala-java8-compat" %% "always"

But  make sure to remove this line when your project does not depend on 0.9.x anymore.

The primary motivation for going to 1.0 for scala-java8-compat was to signal future binary compatibility, not to signal any incompatibility between 0.9.x and 1.x.

Thanks @julienrf and @SethTisue. always workaround works fine in my case, until we move off of 0.9.x.

authors: SethTisue julienrf naderghanbari

repo: scalacenter/sbt-version-policy


text:
Use proper Sync.blocking for things that block

Avoids blocking the compute pool which can starve due to this/deliver less performance when its threads get blocked. Cats Effect's Console uses blocking as well, see https://github.com/typelevel/cats-effect/blob/66d829c8dac75949526bf9082175a12013dea7b1/std/shared/src/main/scala/cats/effect/std/ConsoleCrossPlatform.scala#L176
By making the type a param, users can restore the old behaviour of executing on the compute pool which is especially relevant if you use a slf4j logger that you know to be async.

MiMa fails, but I think that's easy to fix if this is supposed to be released in the 0.14 series. But given it's a behavioural change, releasing it in a 0.15 might make more sense anyway. Let me know if I shall update.

Sounds good! Bump tlBaseVersion in build.sbt to 0.15.

Thanks for the contribution! ❤ 🙌🏽

authors: aartigao ybasket

repo: scalafreaks/odin


text:
Update sbt to 1.7.1

Updates org.scala-sbt:sbt from 1.6.2 to 1.7.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scala-sbt", artifactId = "sbt" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Closing in favour of https://github.com/scalameta/munit/pull/559

authors: scala-steward valencik

repo: scalameta/munit


text:
Don't print test suite name if no test is being run

These changes make munit print only the test suite names of suites for which it actually ran tests, rather than printing all suite names (even those for which all tests are being filtered out), as it's been doing up to now.
For example, instead of printing things like
$ ./mill -i -w scala.integration.test "almond.integration.KernelTestsSimple3.completion"
…
almond.integration.KernelTestsSimple3:
  + completion 17.073s
almond.integration.KernelTestsTwoStepStartup3:
almond.integration.KernelTestsSimple213:
almond.integration.KernelTestsTwoStepStartup212:
almond.integration.KernelTestsTwoStepStartup213:
almond.integration.KernelTestsSimple212:

it now prints
$ ./mill -i -w scala.integration.test "almond.integration.KernelTestsSimple3.completion"
…
almond.integration.KernelTestsSimple3:
  + completion 15.468s

I find the latter to be more readable.

Not sure how to test that, or if it needs to be tested. (Going to see if it break things on the CI here…)
Manual tests show that it works as expected, at least.


text:
consider changing Term.Apply to take Seq[Seq[Term.Arg]]

Otherwise, we're going to need unsatisfying workarounds like SyntacticXXX in scala.reflect. E.g. see #277. I find this prospect suboptimal.
This is probably not 1.0 material, because the fallout may be too strong at the moment.

@olafurpg @johannegger Could you comment on this please?

My preference would be to have Term.Apply take a Seq[ArgList] and an ArgList would have a Seq[Term.Arg].
Why? In scalafmt I often have an opening ( owned by a Term.Apply. The problem is that it gets quite tricky to find out which argument lists "owns" that (. If there was something like an ArgList tree node then I could trivially find the owner of ( and query stuff like how many arguments are in that list.

I agree with @olafurpg, his proposal is neat. But introducing the proposed change breaks consistency of Meta tree nodes. The convention of using Seq[Seq[Term.Arg]] for representing parameter lists is very present in the Meta trees, as well as Scalac and Dotty. Doing so could lead to confusion, so there's probably a tradeoff here.

Example problem I've struggled with: given a Defn.Def, find the closing parenthesis (if one exists) of the last param list.
If we attach a tree node to each param lists, this would be trivial but currently I to do all sorts of collections gymnastics to cover a bunch of corner cases. However, I agree with @jvican that changing the tree structure may not be the best choice here. A contrib module with utilities to do stuff like the problem above might be enough to satisfy me.

We're on the verge of releasing 2.0, and afterwards we plan to start being really conservative about breaking changes. The matter discussed in the ticket can probably be improved, but there's not enough interest to justify potential breakages.

@olafurpg @xeno-by wanted to revisit this decision, especially given #2820.

@kitbellew I'm not active with Scalameta these days, but I recommend avoiding all breaking changes. Breaking changes have a huge hidden cost and in the case of the Scalameta AST, it's often possible to avoid breaking changes by introducing new toplevel AST type. For example, there could be a Defn.ClauseDef that encodes the new syntax idiomatically. If you really want to parse all defs as clause defs, then you could add an option on the dialect to emit ClauseDef for regular/old-style def, allowing downstream users to gracefully upgrade to the new syntax when they're ready to do so.
Breaking changes are particularly frustrating when downstream users have to make changes in their code to support the old syntax. It's fine to require downstream users to make changes to handle new syntax.

but I recommend avoiding breaking changes at any cost.

That has been my feeling as well, we had some initial implementation added for clause interleaving, but the idea was that we would either create a 5.x release or rather introduce AST alongside it(I am thinking more of doing that). The syntax is not yet changed, so this is still not needed.

authors: jvican kitbellew olafurpg tgodzik xeno-by

repo: scalameta/scalameta


text:
Scala 2.13 supports by-name implicits

Resubmitting this PR (originally #1879) as requested by the CLA error message in CI. I'm sure I've signed these CLAs before but I did them both again.
I've just copied the relevant tests from the Dotty dialect test suite—I'm happy to expand them if people want.

This time the failure looks definitely spurious instead of just probably spurious.

The CI failure is definitely spurious, I've cleaned the cache and rested the failing job. Let's see

Ok, all ✅ now!

authors: gabro travisbrown


text:
Make Equivalence serialisable

This helps when you capture an instance of Equality/Equivalence in some class that has to be serialised.
In my particular case, I use it to match invocation arguments on mocks in mockito-scala and for some scenarios said mocks have to be serialisable.

@cla-bot[bot] check

authors: bbonanno plinlor

repo: scalatest/scalatest


text:
version 1.5.5 is not compatible with devise 4.2

Throws following error
Exiting
/home/siva/.rvm/gems/ruby-2.3.0/gems/activesupport-4.2.5/lib/active_support/core_ext/module/aliasing.rb:32:in `alias_method': undefined method `attributes_for' for class `Devise::ParameterSanitizer' (NameError)
Did you mean?  attr_writer
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/activesupport-4.2.5/lib/active_support/core_ext/module/aliasing.rb:32:in `alias_method_chain'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/devise_invitable-1.5.5/lib/devise_invitable/parameter_sanitizer.rb:12:in `included'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/devise_invitable-1.5.5/lib/devise_invitable/rails.rb:20:in `include'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/devise_invitable-1.5.5/lib/devise_invitable/rails.rb:20:in `block in <class:Engine>'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/activesupport-4.2.5/lib/active_support/lazy_load_hooks.rb:36:in `execute_hook'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/activesupport-4.2.5/lib/active_support/lazy_load_hooks.rb:45:in `block in run_load_hooks'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/activesupport-4.2.5/lib/active_support/lazy_load_hooks.rb:44:in `each'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/activesupport-4.2.5/lib/active_support/lazy_load_hooks.rb:44:in `run_load_hooks'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/railties-4.2.5/lib/rails/application/finisher.rb:62:in `block in <module:Finisher>'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/railties-4.2.5/lib/rails/initializable.rb:30:in `instance_exec'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/railties-4.2.5/lib/rails/initializable.rb:30:in `run'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/railties-4.2.5/lib/rails/initializable.rb:55:in `block in run_initializers'
	from /home/siva/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/tsort.rb:228:in `block in tsort_each'
	from /home/siva/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
	from /home/siva/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/tsort.rb:431:in `each_strongly_connected_component_from'
	from /home/siva/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/tsort.rb:349:in `block in each_strongly_connected_component'
	from /home/siva/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/tsort.rb:347:in `each'
	from /home/siva/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/tsort.rb:347:in `call'
	from /home/siva/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/tsort.rb:347:in `each_strongly_connected_component'
	from /home/siva/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/tsort.rb:226:in `tsort_each'
	from /home/siva/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/tsort.rb:205:in `tsort_each'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/railties-4.2.5/lib/rails/initializable.rb:54:in `run_initializers'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/railties-4.2.5/lib/rails/application.rb:352:in `initialize!'
	from /home/siva/work/phalcomm/config/environment.rb:5:in `<top (required)>'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/activesupport-4.2.5/lib/active_support/dependencies.rb:274:in `require'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/activesupport-4.2.5/lib/active_support/dependencies.rb:274:in `block in require'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/activesupport-4.2.5/lib/active_support/dependencies.rb:240:in `load_dependency'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/activesupport-4.2.5/lib/active_support/dependencies.rb:274:in `require'
	from /home/siva/work/phalcomm/config.ru:3:in `block in <main>'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/rack-1.6.4/lib/rack/builder.rb:55:in `instance_eval'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/rack-1.6.4/lib/rack/builder.rb:55:in `initialize'
	from /home/siva/work/phalcomm/config.ru:in `new'
	from /home/siva/work/phalcomm/config.ru:in `<main>'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/rack-1.6.4/lib/rack/builder.rb:49:in `eval'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/rack-1.6.4/lib/rack/builder.rb:49:in `new_from_string'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/rack-1.6.4/lib/rack/builder.rb:40:in `parse_file'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/rack-1.6.4/lib/rack/server.rb:299:in `build_app_and_options_from_config'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/rack-1.6.4/lib/rack/server.rb:208:in `app'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/railties-4.2.5/lib/rails/commands/server.rb:61:in `app'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/rack-1.6.4/lib/rack/server.rb:336:in `wrapped_app'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/railties-4.2.5/lib/rails/commands/server.rb:139:in `log_to_stdout'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/railties-4.2.5/lib/rails/commands/server.rb:78:in `start'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/railties-4.2.5/lib/rails/commands/commands_tasks.rb:80:in `block in server'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/railties-4.2.5/lib/rails/commands/commands_tasks.rb:75:in `tap'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/railties-4.2.5/lib/rails/commands/commands_tasks.rb:75:in `server'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/railties-4.2.5/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
	from /home/siva/.rvm/gems/ruby-2.3.0/gems/railties-4.2.5/lib/rails/commands.rb:17:in `<top (required)>'
	from bin/rails:4:in `require'
	from bin/rails:4:in `<main>

Do we need to maintain compability? If not, would it better if we document this?

You must upgrade devise invitable to latest version which supports devise 4.2

authors: scambra sivagollapalli


text:
customization 18n

Support multi language customization blocks, for standard UI.
Minimal:

login
user register
user approval

close with #259

repo: scc-digitalhub/AAC


text:
Remove 0 - from error messages

Hello . Really Nice plugin . thank you so much
Just wonder how to remove  " 0 - " at the beginning of all error messages.
Please advice
Thank again.

Hi,
I have the same question, Is it possible to remove "0 -" from error messages?
Thanks

authors: anamostafa cosmoskia

repo: scdoshi/jquery-ajaxchimp


text:
Modified PPMEncoder for FlySky RC Radio

Modified PPMEncoder .h & ,cpp files with example .ino Sketches for use with FlySky FS-i6x transmitter and FS-iA6B receiver.
Also included are video oscilloscope traces for the above Sketches.

Please ignore this Pull Request. It was intended to clean up the Branch that I forked to
https://github.com/adaptivercsailing/PPMEncoder. Unfortunately it moved all the up the chain to your Main Branch.  So far, I have not been able to Revert (revoke, cancel, delete) my erroneous request. Thank you for your patience.

repo: schinken/PPMEncoder


text:
🛑 xrm.rocks is down

In 18c8073, xrm.rocks (https://xmr.rocks) was down:

HTTP code: 0
Response time: 0 ms

Resolved: xrm.rocks is back up in 8cf9e00 after 1 minute.


text:
Calculate indices from JSON mesh data

Hello,
Having trouble understanding how to pass the second parameter (indices) of the cannon.trimesh( ) class. I have a JSON file exported from blender with the following object properties.
"faces": [ ],
"vertices": [ ],
"metadata": { },
"uvs": [ ],
"normals": [ ],
"colors": [ ],
"materials": [ { } ]

How do you calculate the indices so it can be passed into cannon.trimesh( )? Assuming you triangulated the blender mesh before exporting it to three.js JSON so that the entire mesh is tri's instead of quads.

Could I texture a height field with a seamless tiled image?


text:
Use poyo instead of libyaml

https://pypi.python.org/pypi/poyo
gets rid of the brew install libyaml requirement

Wont fix - we need to write yaml too and poyo is read only.

repo: schwa/punic


text:
docs: include GitHub button in GitHub dropdown

Also moves a few things to the standard locations per https://jupyterbook.org/customize/config.html

My last local build might be missing the GitHub button, will check tomorrow.

My last local build might be missing the GitHub button, will check tomorrow.

Will revert to html_theme_options, opened an issue here:  https://github.com/executablebooks/jupyter-book/issues/1194

Will revert to html_theme_options, opened an issue here:  https://github.com/executablebooks/jupyter-book/issues/1194

A lot of these options used to not work outside of sphinx_config. JupyterBook has been changing too rapidly—I didn't like how the docs kept breaking because of upstream changes.
The configuration parameter that I want most is show_navbar_depth: 2, and I see that's still there. The second-tier topics in the left-bar were written to be visible at all times. They used to be grouped by section headers, but that feature was removed from JupyterBook, so my next-best approximation was to make them nested within fake pages whose content is a manually-maintained table of contents for that section, and then the default navbar depth was dropped to 1, making them hidden again. I'm afraid I might have adopted this too early!
When this is ready for review, I should check it out and look at the documentation it produces, since the visual layout is not something that can be caught by a test. (Note: even the "doctest-awkward (JupyterBook py38-np*)" is new. Until recently, we had no automated test to ensure that those notebook examples were correct! At least there's that.)

A lot of these options used to not work outside of sphinx_config. JupyterBook has been changing too rapidly—I didn't like how the docs kept breaking because of upstream changes.
The configuration parameter that I want most is show_navbar_depth: 2, and I see that's still there. The second-tier topics in the left-bar were written to be visible at all times. They used to be grouped by section headers, but that feature was removed from JupyterBook, so my next-best approximation was to make them nested within fake pages whose content is a manually-maintained table of contents for that section, and then the default navbar depth was dropped to 1, making them hidden again. I'm afraid I might have adopted this too early!
When this is ready for review, I should check it out and look at the documentation it produces, since the visual layout is not something that can be caught by a test. (Note: even the "doctest-awkward (JupyterBook py38-np*)" is new. Until recently, we had no automated test to ensure that those notebook examples were correct! At least there's that.)

My last local build might be missing the GitHub button (which was the point of this!), will check tomorrow.

In some documentation, I've deliberately removed the "edit on GitHub" button because the sources were auto-generated and don't exist in the git repo. Not this one, though: every one of the pages in docs-src are hand-written (Jupytext, sometimes edited in Jupyter, sometimes manually). The "edit on GitHub" button would be a good addition, especially since any errors introduced into the code examples will be tested by the "doctest-awkward (JupyterBook)."

My last local build might be missing the GitHub button (which was the point of this!), will check tomorrow.

In some documentation, I've deliberately removed the "edit on GitHub" button because the sources were auto-generated and don't exist in the git repo. Not this one, though: every one of the pages in docs-src are hand-written (Jupytext, sometimes edited in Jupyter, sometimes manually). The "edit on GitHub" button would be a good addition, especially since any errors introduced into the code examples will be tested by the "doctest-awkward (JupyterBook)."

Edit on GitHub is already there, the "repository" button was the one missing.

But I'd like to see:

I'm testing locally, so I'll have to move a few things back until the linked Issue gets resolved in juptyer-book. The idea is to have no visual change expect for the addition of the missing menu item.

Edit on GitHub is already there, the "repository" button was the one missing.

But I'd like to see:

I'm testing locally, so I'll have to move a few things back until the linked Issue gets resolved in juptyer-book. The idea is to have no visual change expect for the addition of the missing menu item.

Eventually we might be able to refactor a bit, but this is simple and adds what I wanted to see. :/ Don't quite know why I was losing the button entirely with the version that put the values in the "standard" places, maybe it doesn't merge correctly, or maybe it was my error.

Eventually we might be able to refactor a bit, but this is simple and adds what I wanted to see. :/ Don't quite know why I was losing the button entirely with the version that put the values in the "standard" places, maybe it doesn't merge correctly, or maybe it was my error.

I just checked it out, ran the documentation-generator, and visually inspected it. That new "repository" item in the drop-down menu correctly links to the main GitHub page. Also, the left-bar is still expanded, which is what I wanted to maintain.

I just checked it out, ran the documentation-generator, and visually inspected it. That new "repository" item in the drop-down menu correctly links to the main GitHub page. Also, the left-bar is still expanded, which is what I wanted to maintain.

authors: henryiii jpivarski


text:
Using GPU when calculating the Cholesky decomposition

Is there a way to tell the Cholesky decomposition to use a GPU. I know its possible to do this in the CHOLMOD library.

Due to the CHOLMOD documentation this might be possible using
export CHOLMOD_USE_GPU=1

before using scikit-sparse and CHOLMOD.

I tried doing
import os
os.environ["CHOLMOD_USE_GPU"] = "1"
import sksparse.cholmod

But it doesn't seem that my code uses the GPU...

authors: jor- matthieuheitz rwolst

repo: scikit-sparse/scikit-sparse


text:
Documentation

I need to spare some time to create proper documentation including system design, how-to use, development guide.

Things to be documented in detail:

Flag-based control commands

I think this is outdated.

authors: SimonHeybrock YooSunYoung

repo: scipp/beamlime


text:
Equation written incorrectly in scipy.stats.pearsonr documentation

This is a very minor issue, but I just wanted to bring it to your attention.
The equation in scipy.stats.pearsonr is written incorrectly in the documentation
The summation needs to be in front of both terms in the denominator:
\sqrt{ \sum (x-m_x)^2 \sum (y-m_y)^2 }
This is a minor issue, as the correct equation is coded.

@lgloege Thanks for reporting. Do you mind sending in a pull request for this?

this has been fixed in #9143 already.

(not yet released)

authors: chrisb83 ilayn lgloege

repo: scipy/scipy


text:
CI: fix 32-bit Linux build failure on Azure CI runs

Azure uses Ubuntu Bionic (16.04 LTS) including backports; that now picks up gcc-7 in addition to gcc-5, and by default builds with gcc-7. Only gfortran-5 is available though, not gfortran-7.
So explicitly use gcc-5 and g++-5

Okay that fixed the build, just one test accuracy issue left:
___________________ TestPdist.test_pdist_jensenshannon_iris ____________________
[gw1] linux -- Python 3.6.9 /usr/bin/python3.6
scipy/spatial/tests/test_distance.py:1156: in test_pdist_jensenshannon_iris
    _assert_within_tol(Y_test1, Y_right, eps)
        X          = array([[5.1, 3.5, 1.4, 0.2],
       [4.9, 3. , 1.4, 0.2],
       [4.7, 3.2, 1.3, 0.2],
       [4.6, 3.1, 1.5, 0.2],
  ...],
       [6.3, 2.5, 5. , 1.9],
       [6.5, 3. , 5.2, 2. ],
       [6.2, 3.4, 5.4, 2.3],
       [5.9, 3. , 5.1, 1.8]])
        Y_right    = array([0.02116356, 0.00455073, 0.02306109, ..., 0.02608019, 0.01550743,
       0.02274677])
        Y_test1    = array([0.02116356, 0.00455073, 0.02306109, ..., 0.02608019, 0.01550743,
       0.02274677])
        eps        = 1e-12
        self       = <scipy.spatial.tests.test_distance.TestPdist object at 0xdadcd0ac>
scipy/spatial/tests/test_distance.py:222: in _assert_within_tol
    assert_allclose(a, b, rtol=rtol, atol=atol)
E   AssertionError:
E   Not equal to tolerance rtol=0, atol=1e-12
E
E   (mismatch 0.0357941834451907%)
E    x: array([0.021164, 0.004551, 0.023061, ..., 0.02608 , 0.015507, 0.022747])
E    y: array([0.021164, 0.004551, 0.023061, ..., 0.02608 , 0.015507, 0.022747])
        a          = array([0.02116356, 0.00455073, 0.02306109, ..., 0.02608019, 0.01550743,
       0.02274677])
        b          = array([0.02116356, 0.00455073, 0.02306109, ..., 0.02608019, 0.01550743,
       0.02274677])
        rtol       = 0
        verbose_   = False

This fixed the CI failure (the one ILP64 was a random Azure worker crash) and is straightforward, so I'll go ahead and merge it.

Thanks @rgommers !

authors: larsoner rgommers


text:
MAINT:linalg: Remove redundant det and lu Fortran files

#18358 finalized replicating the work that these old Fortran files were used for. This PR removes the files themselves.

Opinions on also getting rid of flinalg.py and _flinalg.py too? Last time around there was some concerns about the 2.0.0 deprecation warning. Since then, the only two functions left now have a warning saying they will be removed in this release as they are not part of the linalg namespace which would leave an empty module
In [2]: scipy.linalg.flinalg.__all__
Out[2]: ['get_flinalg_funcs', 'has_column_major_storage']

In [3]: scipy.linalg.flinalg.get_flinalg_funcs
<ipython-input-3-2f187ec6e743>:1: DeprecationWarning: `scipy.linalg.flinalg.get_flinalg_funcs` is deprecated along with the `scipy.linalg.flinalg` namespace. `scipy.linalg.flinalg.get_flinalg_funcs` will be removed in SciPy 1.13.0, and the `scipy.linalg.flinalg` namespace will be removed in SciPy 2.0.0.
  scipy.linalg.flinalg.get_flinalg_funcs
Out[3]: <function scipy.linalg._flinalg_py.get_flinalg_funcs(names, arrays=(), debug=0)>

In [4]: scipy.linalg.flinalg.has_column_major_storage
<ipython-input-4-e9709a88fd27>:1: DeprecationWarning: `scipy.linalg.flinalg.has_column_major_storage` is deprecated along with the `scipy.linalg.flinalg` namespace. `scipy.linalg.flinalg.has_column_major_storage` will be removed in SciPy 1.13.0, and the `scipy.linalg.flinalg` namespace will be removed in SciPy 2.0.0.
  scipy.linalg.flinalg.has_column_major_storage
Out[4]: <function scipy.linalg._flinalg_py.has_column_major_storage(arr)>

Oh I completely forgot those. Let me check what they do.

so seems a little pointless to leave around

I agree, removed them now.

flinalg also has references in mypy.ini, scipy\_lib\tests\test_public_api.py, scipy\linalg\__init__.py, scipy\linalg\_basic.py, scipy\linalg\basic.py, and scipy\linalg\decomp_lu.py.

Oh my if it is not a hassle please go ahead, I don't know how I missed them. Thanks for the drill down though.

CI happy, just need to decide whether https://github.com/scipy/scipy/blob/e00a5948a9dddd81954d2039d71e7b0ffe8a36bc/scipy/linalg/_basic.py#L947-L955 should stay/be reworded/be deleted.

That comment has no relevance anymore hence I removed it. It was when we tried to use F or C linalg based on the array flag but that's long gone.

Thanks @lucascolley for the emergency save, @j-bowhay

authors: ilayn j-bowhay lucascolley


text:
BLD: switch to more robust git hash determination

Fixes the spurious line:
fatal: bad revision '^v1.13.0'

that shows up in CI logs and locally when the current repo doesn't have a local v1.13.0 tag.
There is no longer a need to determine a commit count. The method in this commit (taken over from NumPy) adds the date of the last commit instead. That achieves the same purpose, namely to have well-defined ordering between two dev builds, in a simpler way.
This also syncs the rest of version string handling with how NumPy does it; that NumPy version was done more recently and is more complete.
Note that this also drops the commit_count attribute. This field is useless, and a code search shows it isn't used at all - that seems better than either making up a wrong number or setting it to None.
That same code search showed that some other attributes are used, so add a test for them (noting they're not actually public).
Closes gh-21345

The CI failures on CircleCI and in the 32-bit manylinux container are real. The cause for the latter seems to be that git isn't available, and the version string changed from 1.15.0.dev0+Unknown to 1.15.0.dev0. I'm inclined to go with the latter and adjust the test:
___________________________ test_valid_scipy_version ___________________________
scipy/_lib/tests/test_scipy_version.py:18: in test_valid_scipy_version
    assert res is not None
E   assert None is not None
        dev_suffix = '(\\.dev0\\+.+([0-9a-f]{7}|Unknown))'
        res        = None
        version_pattern = '^[0-9]+\\.[0-9]+\\.[0-9]+(|a[0-9]|b[0-9]|rc[0-9])'

Sounds reasonable just to adjust the test. The +Unknown is essentially implied anyway just by absence of the date.

The one CI failure is unrelated - this is ready for review now.

I plan to merge this soon, since this is basically just a sync of code from numpy that fixes a confusing warning, and CI is green.


text:
Refactored multivariate normal example (trivial)

Use of dstack seems slightly more concise than declaring empty array with tuple concatenation, etc.

Merged, thank you!

authors: larsmans ltiao