Update links to newest website

I noticed the links on this Github repo in the description and readme.md are still pointing to the old (dead) links, instead of to the new site at http://hpgl.mit-ufa.com. While I realize from #1 that there are no active developers working on this anymore, it would greatly increase access to your lib if the links in the description and readme.md could be updated. If you do it, you might as well update the version number from 9.3 to 9.9 which doesnt seem to have been updated in the readme.md, just to avoid confusion.

Thank you karimbahgat, I will update links and readme very soon.

@karimbahgat I updated version, readme file and removed bad links


springfox-boot-starter: Provide a way to disable swagger2 completly by dependency exclusion

Feature Request.
Tested on springfox-boot-starter 3.0.0
Hi,
I thought it could be useful to be able to disable swagger 2 documentation completely by excluding it from starter, like :
        <dependency>
            <groupId>io.springfox</groupId>
            <artifactId>springfox-boot-starter</artifactId>
            <version>3.0.0</version>
            <exclusions>
                <exclusion>
                    <groupId>io.springfox</groupId>
                    <artifactId>springfox-swagger2</artifactId>
                </exclusion>
            </exclusions>
        </dependency>

Actually it results in errors when starting the app.
I'm trying to disable it completely from my project and the only solution I found was springfox.documentation.swagger.v2.enabled=falsewhich can be overrode unfortunately.
And I don't want to go the skip springfox-boot-starter road neither
Best regards,
Nicolas

Could also be useful with swagger-ui BTW !


TS2305: Module '"fela-dom"' has no exported member 'renderToMarkup'.

Version: 6.0.3
Environment: DOM / Server / Both
Type: TS2305: Module '"fela-dom"' has no exported member 'renderToMarkup'.

Description
When using renderToMarkup, getting the following type error.
TS2305: Module '"fela-dom"' has no exported member 'renderToMarkup'.

Code Example:
import { createRenderer, IRenderer } from 'fela';
import prefixer from 'fela-plugin-prefixer';
import fallbackValue from 'fela-plugin-fallback-value';
import unit from 'fela-plugin-unit';
import lvha from 'fela-plugin-lvha';
import validator from 'fela-plugin-validator';
import logger from 'fela-plugin-logger';
import  {renderToMarkup}  from 'fela-dom';
import perf from 'fela-perf';
import beautifier from 'fela-beautifier';
import fontRenderer from 'fela-font-renderer';

export default (fontNode) => {
    const renderer = createRenderer({
        plugins: [prefixer(), fallbackValue(), unit(), lvha(), validator({})],
        enhancers: [/*perf(),*/ beautifier(), fontRenderer(fontNode)],
    });
    if ( __SERVER__) {
        return renderToMarkup(renderer);
    }
    return renderer;
};

Looks like a TypeScript warning right? Feel free to send a PR fixing this. I'm not using TypeScript and don't update these definitions as well.

@rofrischmann I didn't find export of createStyleTagMarkup function in fela-utils. This is not typescript warning only.

There'll be a fela-dom patch later today which fixes this export. Sorry about that.

I used version 5.0.8. Sorry, seems like 6.0.3 has no problems


feat(relay): default portal URL

Instead of having portal URL and token optional, we default the portal URL and decide based on the presence of the token, whether we should connect to the portal on startup. This allows the relay to be used/tested standalone and keeps the number of config options and error cases small.
We require the user to config the full path of the websocket and thus avoid the need for duplicating the connlib function. Given that most users will never need to override this option, this seems like a good trade-off.

Fixes firezone/product#614


Save .pb model

Hello,
please can you explain how to save the .pb model from the last chekpoints as well as the input tensor and the output tensor name/shape.
Thank you

Hello,
please can you explain how to save the .pb model from the last chekpoints as well as the input tensor and the output tensor name/shape.
Thank you
Have you solved your problem？If the problem is solved, please share the method with me.Thank you


Option to set-unset enable

Given this example:
packagecloud_repo "chef/stable" do
  type "rpm"
end

I'd like to be able to set enable false (like in yum_repository) so that it won't auto-update things (e.g. chef-client or chef-server) automatically.

Hi:
sorry for the delayed reply, something is up with my GitHub email notifications.
I'm not sure I totally understand what you mean by "so that it won't auto-update things" -- the packagecloud_repo code updates yum cache, but doesn't install any packages.
Actually, after thinking about it a bit... Is the issue you are seeing that the yum cache is updated and you have an unversioned package "example" that is updating the example package since the yum metadata has been updated?

The enabled flag means that yum upgrade and yum install won't search that repository without the --enablerepo flag.

Sounds great. If this is something you'd be able to submit a PR for we'll accept it!


Fixup metrics for socket_refused_connections

systemd_socket_refused_connections_total is named as though it's a counter. However, it's not a counter, it's a gauge. Either rename or internally make it a counter

Looks like this is also an issue in Node exporter
https://github.com/prometheus/node_exporter/blob/2477c5c67dff7e7655a9d466450235e9c9eac193/collector/systemd_linux.go#L306-L308

I think it needs to be a counter not an gauge
as looking at the code, stuff gets incremented:
https://github.com/systemd/systemd/blob/de5ae832f26cc9b049ee28b61df816669a69e306/src/core/socket.h#L70
https://github.com/systemd/systemd/blob/7c286cd6a615fa9bce8a2830133bcf89becfbf9f/src/core/socket.c#L2659

Currently PR in progress https://github.com/povilasv/systemd_exporter/pull/10


Latest NotoColorEmoji.ttf (Aug 2018) doesn't support Android 6 or lower?

Hi
If I use the latest NotoColorEmoji.ttf under Android M, the application crashes.
But no probrem with Android N or higher.
Where can I check the Android version supported by NotoColorEmoji?
I think NotoColorEmoji.ttf that supports Unicode 10 distributed on Google Noto Fonts site was able to use with Kitkat or higher.
When I create Typeface instance:
Typeface typeface = Typeface.createFromAsset(getAssets(), "fonts/NotoColorEmoji.ttf")

app crashes with this log:
E/Minikin: addFontFromAsset failed to create font fonts/NotoColorEmoji.ttf
E/AndroidRuntime: FATAL EXCEPTION: main
    java.lang.RuntimeException: Unable to start activity ComponentInfo{[my package name]/[my activity class name]}: java.lang.RuntimeException: Font asset not found fonts/NotoColorEmoji.ttf

Thanks

Sorry to dig this old topic. I found out that Version 2.040;GOOG;noto-emoji:20231016:92a58ea6b2cfcad2560c2271855bc9c77eab6c51 works with KitKat now.
https://github.com/googlefonts/noto-emoji/blob/main/fonts/NotoColorEmoji-emojicompat.ttf


[BUG] NavBar Placements in About section

Description of the bug
The navbar in about page is placed in the middle of the page instead of being at the top. Also the navbar is different for different pages which seems confusing to look at.
@codingkatty  Please assign this issue to me if you like the idea.

Ohk no worries!
On Wed, 16 Oct, 2024, 16:57 Lim Xin Ying, @.***> wrote:

Hi, sorry but I think someone else had opened a similar issue.
—
Reply to this email directly, view it on GitHub
https://github.com/codingkatty/mathpylearn/issues/98#issuecomment-2416526833,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCHWC2DEW7X5OBMWWMXGJU3Z3ZERTAVCNFSM6AAAAABQBEF4J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJWGUZDMOBTGM
.
You are receiving this because you authored the thread.Message ID:
@.***>


Calling synchronous methods on native modules is not supported in Chrome

Call the synchronized api, this appears:

React Native version:

React Native Environment Info:
System:
OS: macOS 10.14.6
CPU: (4) x64 Intel(R) Core(TM) i7-4578U CPU @ 3.00GHz
Memory: 19.07 MB / 16.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 12.7.0 - /usr/local/bin/node
Yarn: 1.3.2 - /usr/local/bin/yarn
npm: 6.10.0 - /usr/local/bin/npm
SDKs:
iOS SDK:
Platforms: iOS 13.0, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
Android SDK:
API Levels: 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 7, 8, 9
Build Tools: 22.0.1, 23.0.1, 28.0.0, 28.0.1, 28.0.2, 28.0.3, 29.0.0, 29.0.1, 29.0.2
System Images: android-28 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.5 AI-191.8<IP_ADDRESS>91312
Xcode: 11.0/11A420a - /usr/bin/xcodebuild
npmPackages:
react: 16.8.3 => 16.8.3
react-native: 0.59.10 => 0.59.10
npmGlobalPackages:
react-native-cli: 2.0.1
react-native-create-library: 3.1.2
Steps To Reproduce

Describe what you expected to happen:
Snack, code example, screenshot, or link to a repository:

@react-native-bot
I have updated to the latest version, but I still have this error.
info Fetching system and libraries information...
System:
    OS: macOS Mojave 10.14.6
    CPU: (4) x64 Intel(R) Core(TM) i7-4578U CPU @ 3.00GHz
    Memory: 30.93 MB / 16.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 12.7.0 - /usr/local/bin/node
    Yarn: 1.3.2 - /usr/local/bin/yarn
    npm: 6.10.0 - /usr/local/bin/npm
  SDKs:
    iOS SDK:
      Platforms: iOS 13.0, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
    Android SDK:
      API Levels: 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 7, 8, 9
      Build Tools: 22.0.1, 23.0.1, 28.0.0, 28.0.1, 28.0.2, 28.0.3, 29.0.0, 29.0.1, 29.0.2
      System Images: android-28 | Google APIs Intel x86 Atom
      Android NDK: 20.0.5594570
  IDEs:
    Android Studio: 3.5 AI-191.8<IP_ADDRESS>91312
    Xcode: 11.0/11A420a - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.2 => 0.61.2
  npmGlobalPackages:
    react-native-cli: 2.0.1
    react-native-create-library: 3.1.2
    react-native-git-upgrade: 0.2.7

imho, it should this be in
https://github.com/react-native-community/react-native-device-info/issues/776

@zhigang1992 the error string is from:
/node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js line 186:
if (__DEV__) {
      invariant(
        global.nativeCallSyncHook,
        'Calling synchronous methods on native ' +
          'modules is not supported in Chrome.\n\n Consider providing alternative ' +
          'methods to expose this method in debug mode, e.g. by exposing constants ' +
          'ahead-of-time.',
      );
    }

It seems that the api with the sync mark has this error.
ios: RCT_EXPORT_BLOCKING_SYNCHRONOUS_METHOD
android: isBlockingSynchronousMethod=true

@i7soft Did you ever find a solution for this problem? Currently experiencing this right now, and not being able to use a debugger is rough.

@TheNoodleMoose no💔,i am waitting a solution

@i7soft Was react native the only thing you have updated? Ours was working after our React Native upgrade to the latest version, what broke it was a different package being upgraded. We used git bisect to find the culprit.

@TheNoodleMoose i try this:

react-native init demo👈 the lastest version
2.add package "react-native-device-info" to the demo
3.add code to App.js:

import DeviceInfo from 'react-native-device-info';
console.log(DeviceInfo.isCameraPresentSync());👈 call a sync function

4.open debug mode
5.restart app,then show:
Invariant Violation: Calling synchronous methods on native modules is not supported in Chrome.

 Consider providing alternative methods to expose this method in debug mode, e.g. by exposing constants ahead-of-time.

@i7soft So since it seems to be the react-native-device-info package, I think they figured out the solution was to have a check for whether you: 1. Have a debugger or 2. Are in development mode. If either of those is present, then just mock the sync value. It's a shame but there was good reasoning behind it. Here is link discussing the solution: https://github.com/react-native-community/react-native-device-info/issues/776#issuecomment-533410011

@TheNoodleMoose I use react-native-device-info just for example. In fact, I need to develop synchronous native features. I found that when debugging, I can't use the synchronous method. I don't know if it's my problem, or react native will improve this in the future.

I also meet this problem, i can not find any method to debug when i use synchronous method

Ran into this problem when upgrading to react native 0.62.0. Still present.
We are using react-native-device-info version 5.5.3.

Same here. Removing calls to Appearance in version 0.62 solved it.
I reverted back to using expo/react-native-appearance package

Can confirm that this happens with the Appearance API on the latest version (0.62)

hey folks, thanks for surfacing this issue - we are putting it in front of the team that worked on it so that they can help us understand how to get this fixed.

Still getting this, but in react-native-svg on Path.isPointInFill() method.
Unsure if it's a react-native-svg or react-native problem?

Still facing this on v0.63.3, although temporarily commenting out the sync method works.

Still facing this on v0.63.3, although temporarily commenting out the sync method works.

We are experiencing the same issue on 0.63.3

We are experiencing the same issue on 0.63.3

you can use this temporary solution https://stackoverflow.com/a/66583605/8079868

same here

@kelset Did anything ever come from the team taking a look at this? I'm having the same issue attempting to debug with React Native Debugger.

@madroneropaulo @stdavis i made PR https://github.com/facebook/react-native/pull/31153 . but they closed PR by saying this is a feature. you have to patch react native like this https://stackoverflow.com/a/66583605/8079868

@nomi9995 That patch from SO led to other errors for me.

@nomi9995 @stdavis I opened a new Issue, since I think the new one is related to the AuthRequest and not this one. https://github.com/expo/expo/issues/12712

why is this closed when it still occurs ?

@29er they will not handle this on chrome. you can see #31153. if you wanna run this on chrome then you can use patch https://stackoverflow.com/a/66583605/8079868

I'm getting this warning in the default ReactNative demo on running the application in debug mode (No dependencies added).
},
 "dependencies": {
   "react": "17.0.2",
   "react-native": "0.65.1"
 },
 "devDependencies": {
   "@babel/core": "7.15.5",
   "@babel/runtime": "7.15.4",
   "@react-native-community/eslint-config": "2.0.0",
   "babel-jest": "26.6.3",
   "eslint": "7.14.0",
   "jest": "26.6.3",
   "metro-react-native-babel-preset": "0.66.0",
   "react-native-codegen": "^0.0.7",
   "react-test-renderer": "17.0.2"
 },

@deepakaggarwal7  I have the same exact issue; I tried multiple solutions but no luck.

@deepakaggarwal7 just created a new issue related to this with detailed info, feel free to comment there if you need

+1, facing the same. Would be great if someone can help. Unable to debug the app on iOS and android.

experiencing exact same issue. It only happened after transition to react-native 0.65.1
worked totally fine before that.
Tried to apply different solutions, but they all lead to some other issues.

experiencing exact same issue. It only happened after transition to react-native 0.65.1
worked totally fine before that.
Tried to apply different solutions, but they all lead to some other issues.

1+ facing the same issue after just upgrading to 0.65.1

same issue on 0.65.1

Same issue on 0.65.1 please help us

I'm facing the same issue, it happens when debug mode is active, please help!
`NativeUIManager.getConstantsForViewManager('Text') threw an exception. Invariant Violation: Calling synchronous methods on native modules is not supported in Chrome.
Consider providing alternative methods to expose this method in debug mode, e.g. by exposing constants ahead-of-time.
CountBadge@http://localhost:8081/index.bundle?platform=android&dev=true&minify=false&app=com.apolloxendit&modulesOnly=false&runModule=true:80660:35
RCTView
View
RCTView
View
TouchableWithoutFeedback@http://localhost:8081/index.bundle?platform=android&dev=true&minify=false&app=com.apolloxendit&modulesOnly=false&runModule=true:79148:36
LogBoxButton@http://localhost:8081/index.bundle?platform=android&dev=true&minify=false&app=com.apolloxendit&modulesOnly=false&runModule=true:80889:33
RCTView
View
LogBoxLogNotification@http://localhost:8081/index.bundle?platform=android&dev=true&minify=false&app=com.apolloxendit&modulesOnly=false&runModule=true:80587:25
RCTView
View
RCTView
View
_LogBoxNotificationContainer@http://localhost:8081/index.bundle?platform=android&dev=true&minify=false&app=com.apolloxendit&modulesOnly=false&runModule=true:80445:16
LogBoxStateSubscription@http://localhost:8081/index.bundle?platform=android&dev=true&minify=false&app=com.apolloxendit&modulesOnly=false&runModule=true:22856:38
RCTView
View
AppContainer@http://localhost:8081/index.bundle?platform=android&dev=true&minify=false&app=com.apolloxendit&modulesOnly=false&runModule=true:76863:36
RootComponentWithMeaningfulName@http://localhost:8081/index.bundle?platform=android&dev=true&minify=false&app=com.apolloxendit&modulesOnly=false&runModule=true:84232:24 index.bundle:20995:28`

guys, please refer to this open issue:
https://github.com/facebook/react-native/issues/32197
it's better to report this on an open issue


tests: mem_pool: convert legacy test in ztest

Make legacy test case use of ztest test api to support
test framework
Signed-off-by: Punit Vara<EMAIL_ADDRESS>

@SavinayDharmappa can you please review ?

LGTM


dark theme

add dark theme

idea: click the time-space triangle to switch to full-screen time-space in dark


Gib dataset boss

Could you upload the dataset too? If not, at least tell us how big it was. ;-;

bump


keepalive/persistent doesn't persist

Reproducing code
<?php

require 'vendor/autoload.php';

$client = new \Zend\Http\Client('http://example.com', [
	'keepalive' => true,
	'persistent' => true
]);

$start = microtime(true);
$client->send();
echo microtime(true) - $start . "\n";

$start = microtime(true);
$client->send();
echo microtime(true) - $start . "\n";

When executed, it will output something similar to
0.22347211837769
0.11083388328552

This is expected but only on the first execution. On the following executions the previously made connection should persist and the times should be almost identical. It works the same way with CLI and FPM.
I'm using PHP 7.2 and installed zend-http with composer require zendframework/zend-http

@rinu why are you expecting the same time?

on the first request the Socket adapter will connect and make the request
on second request the Socket adapter should be still connected and make the 2nd request

So I think it's correct that the 2nd request is faster than the 1st one.

What I want is currently not supported by PHP. It can't cache connections between processes.

It's not possible on different processes but it's possible with child process (eg: with apache, php-fpm)

Closing as inapplicable - not really an issue for zend-http to solve, but rather for the underlying layers.


Ordering bug for processor clauses

The following program generates an error I can't understand: https://gist.github.com/schuster/8e3cae9dfac839a7b055
It seems like in this case the ordering of processor clauses must match the order in the grammar, which shouldn't be necessary. The error message also doesn't make clear what the error actually is.

Found a simpler instance of what appears to be the same issue, but with with-output-language: https://gist.github.com/schuster/6543997ae8617c43add3
@LeifAndersen points out that it's likely because primop calls and function calls in this grammar are both "tagless" items with the same structure.


Automatically use mypy.ini or pyproject.toml when not in the root directory of the workspace

When using the Mypy linter, our standard is to have a mypy.ini in the project's root with a bunch of config values. Currently we have our developers use this setting for vscode:
  "python.linting.mypyArgs": [
    "--config-file=${workspaceFolder}/mypy.ini"
  ]

However, if a project doesn't have a mypy.ini file linting fails silently (which can cause a lot of issues as a dev might think that mypy worked fine).
I think that auto-detecting and using the mypy.ini file should be a part of the plugin itself.

There is a cwd setting that can be used to set the this. By default, it is the workspace directory, if you want it to run in the same directory as the file you can set it to ${fileDirname}, and cwd will change to the parent directory of the file.

@karthiknadig can we please reopen? ${fileDirname} is not working for very many cases, such as when you have multiple sub folders.
What does seem to work without any hiccups is the following:

    "mypy-type-checker.args": [
        "--config-file=${workspaceFolder}/pyproject.toml"
    ]

However, it would be nice not to have to specify this since it is quite boilerplate configuration

@evbo Can you elaborate on your scenario? like what is the directory structure and where are your config files.
From your what is see above it looks like you have a single pyproject.toml in your workspace folder. that means you don't need to specify mypy-type-checker.args. The cwd by default is your workspace folder, and mypy should pickup pyproject.toml.
The ${fileDirname} is useful if you have different configurations for different parts of your project. From what I understand that is not your case.

It is a mono repo, like:
project_root
    python_module_a
        pyproject.toml
        venv
        folder
            source.py
        source.py
    python_module_b

Do you have a settings file you can share? and also do you have or tried using *.code-workspace?

@evbo This really is a bug on mypy to add the ability to find config in parent directories (similar to pylint, ruff, flake8, etc). I can see that this might be useful until such support is added to mypy.
I recommend creating an issue, and we are open to a PR on this.
Things to consider:

check the args and if it does not already have a config, and the cwd does not have a config initiate the search.
Ensure that this search happens every time for mypy case, but produces and warning for dmypy. dmypy does not re-read configuration.

The changes should happen in here:
https://github.com/microsoft/vscode-mypy/blob/85a7af33526bca54e327e0b451f1922050cba3a0/bundled/tool/lsp_server.py#L204


I need to consolidate these accounts

No issues. I was too new when I created and just didn't understand what I was making an issue about.


Proposed inclusion of .b grad file format into specification

Would belong in BIDS raw specification rather than BIDS DWI derivatives, since it is equally applicable to BIDS Raw data

Would necessitate description within BIDS raw specification of difference between .bvec and .b, as it is not only a transpose but also a change in reference axes between image and scanner space

(Related: Reminder to self to check whether or not the neurological assumption of .bvec was incorporated into the main specification)

See also https://github.com/bids-standard/bids-specification/issues/349

see also https://github.com/bids-standard/bids-specification/commit/1d50d14bed67e97892d29ee4edcfbc68a8388d59#r35716642

Hi @Lestropie, as Ariel and Franco are posting, there is an initiative ongoing that is very much related - your feedback there is very welcome. I guess the most straightforward link is https://github.com/bids-standard/bids-specification/pull/352 (Ariel linked the issue that prompted that PR and Franco linked one of the ramifications of the PR).
That PR was advancing fast, but got stuck with this https://github.com/bids-standard/bids-specification/pull/352#issuecomment-879877873 - I guess the feedback of the three of you would be very clarifying. The person proposing changes actually drafted how they could be implemented in https://github.com/mattcieslak/bids-specification/pull/2
Do you want to take a look and maybe help push that one into the spec including your ideas for the .b grad file format if it cannot be represented as a .tsv file?

I suspect I may have missed a number of BIDS discussions where I was tagged because my email has been forwarding anything BIDS-related to a dedicated folder, and that will happen regardless of whether or not I'm tagged. I'll have to try to sort that out so that I actually see anything I'm tagged in.


Bug 1849094: Use quay.io/openshift/origin-cli:4.2 as base image for upstream

This image contains a version of oc run that still creates
deploymentconfig and this is required by our e2e tests

/lgtm

/test e2e-aws-jenkins

/hold

/retest
Ben's disablement of the problematic client plugin tests with oc.run has merged in openshift/origin

/hold cancel


Installation failure on linux due to directory /usr/share/ollama not exists

What is the issue?
Installation failure on linux due to directory /usr/share/ollama not exists
➜  ~ curl -fsSL https://ollama.com/install.sh | sh

Downloading ollama...
######################################################################## 100.0%##O#- #                                                           ######################################################################## 100.0%
Installing ollama to /usr/local/bin...
请输入密码
验证成功
Adding ollama user to render group...
Adding ollama user to video group...
Adding current user to ollama group...
Creating ollama systemd service...
Enabling and starting ollama service...
Downloading AMD GPU dependencies...
chmod: 无法访问'/usr/share/ollama': 没有那个文件或目录

What did you expect to see?
Install success.
Steps to reproduce
Just run the command curl -fsSL https://ollama.com/install.sh | sh  on Linux machine.
Are there any recent changes that introduced the issue?
No response
OS
Linux
Architecture
amd64
Platform
No response
Ollama version
No response
GPU
AMD
GPU info
No response
CPU
AMD
Other software
No response

You can probably start by where your model blobs are stored, if it is not your first time installing Ollama. Depending on how you use Ollama, model blobs can be located at /usr/share/ollama/.ollama/, $HOME/.ollama/, or /root/.ollama/. Even in Linux, depending on how you use Ollama, model blobs can be in locations other than the Linux default location in /usr/share/ollama/.ollama/ by default.

@hualet I don't see the output from this section of the script, which indicates you already have an ollama user on your system, and the home directory must not be /usr/share/ollama otherwise the directory should exist.
You might want to follow our docs on uninstalling first (which includes removing the ollama user), then re-run the install and it should work properly
If that doesn't work, let us know and we can do more troubleshooting.


Infections from external sources

To model a population in a global context and with community spread elsewhere in the world, we need to model a steady stream of new infections from outside the simulation population.

This is implemented in PR #23.


Unrecognized token '<' when running

Question
I downloaded the react translation example. When I start the app everything seems to render fine, but as soon as I press translate, nothing happens and I get this error in the console on the browser:
Unhandled Promise Rejection: SyntaxError: JSON Parse error: Unrecognized token '<'
I've gotten this same issue trying to run other models keeping things very basic as found here: https://huggingface.co/docs/transformers.js/pipelines
UPDATE: This error only happens in Safari, but it works fine in Chrome.
If I try to make the simplest example with react like in the tutorial link it fails in both chrome and safari

Hi there 👋 This is most likely a duplicate of https://github.com/xenova/transformers.js/issues/472. Could you try adding the following to the top of your code:
import { env } from '@xenova/transformers';
env.allowLocalModels=false;

Please note you may need to reset your cache, since the local version (which does not exist) may have been cached.

That was it. Thanks!


piculet should respect additional AWS cli environment variables

It would be nice if the tool would make use of additional environment variables as outlined here
I'm specifically thinking of the following:

AWS_CONFIG_FILE: equivalent to --credentials-path
AWS_DEFAULT_PROFILE: equivalent to --profile
AWS_DEFAULT_REGION: equivalent to --region

If a user does not specify the above in CLI arguments when invoking piculet, then it should fall-back to any of the above ENV variables if they exist.
End result is that if I already have my desired profile configured in my shell session, I don't need to explicitly tell piculet what profile to use.
Examples
Current state:
$ export AWS_DEFAULT_PROFILE=development
$ piculet -a --dry-run
Apply `Groupfile` to SecurityGroup (dry-run)
[ERROR]
Missing Credentials.
$ piculet -p development -a --dry-run
Apply `Groupfile` to SecurityGroup (dry-run)
No change

Desired state:
$ export AWS_DEFAULT_PROFILE=development
$ piculet -a --dry-run
Apply `Groupfile` to SecurityGroup (dry-run)
No change

Fixed by #31

Thanks!


Add consume_topic to kafka_tools

This just adds a simple producer that will dump a few messages to a file or stdout.  Mostly useful for testing.
Along the way I noticed some Python 3 issues with kafka_tools, so I fixed those.

It works now!


[Zip][WiX] New package: Mobatek.MobaXterm version <IP_ADDRESS>42

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.2 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Could it be merged now?

https://github.com/microsoft/winget-pkgs/issues/87300

Thank you for adding Mobaxterm :) looking forward to this being merged!

I believe this one fails b/c it detects malware, even tho this is untrue:
PS C:\Users\WDAGUtilityAccount\Desktop\winget-pkgs\manifests\m\Mobatek\MobaXterm\<IP_ADDRESS>42> winget install --manifest=. --ignore-local-archive-malware-scan
Found MobaXterm [Mobatek.MobaXterm] Version <IP_ADDRESS>42
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Successfully verified installer hash
Archive scan detected malware. Proceeding due to --ignore-local-archive-malware-scan
Extracting archive...
Successfully extracted archive
Starting package install...
Successfully installed

https://www.virustotal.com/gui/url/35dcaeaa3ac8ed72edfee834517468904bf11f01ed72644ce9d70b5c1f808c77
Install went well in my sandbox enviroment.

Also, this PR closes:
https://github.com/microsoft/winget-pkgs/issues/77910
https://github.com/microsoft/winget-pkgs/issues/27576

virustotal.com/gui/url/35dcaeaa3ac8ed72edfee834517468904bf11f01ed72644ce9d70b5c1f808c77

You need to manually upload the file to VirusTotal instead:
https://www.virustotal.com/gui/file/668550319b08dbc690290b13d129d337b3d82383b7def31afaecff4e793b5c1d

virustotal.com/gui/url/35dcaeaa3ac8ed72edfee834517468904bf11f01ed72644ce9d70b5c1f808c77

You need to manually upload the file to VirusTotal instead: https://www.virustotal.com/gui/file/668550319b08dbc690290b13d129d337b3d82383b7def31afaecff4e793b5c1d

I see, both luckily come out fully safe :)
I hope ya PR gets merged nevertheless!

@wingetbot run

2023-02-09 05:01:53.888 [CLI ] Archive malware scan failed
2023-02-09 05:01:53.889 [CLI ] Terminating context: 0x8a150060 at D:\a\_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\ArchiveFlow.cpp:29

Interesting, I thought this was disabled. I'm going to try it once more to be sure

@wingetbot run

@wingetbot run

Can this PR be merged now with the approvals?

Can this PR be merged now with the approvals?

Not until it has a successful pipelines run or is manually validated by Microsoft

I created an alternative package for this application here:
#97869
Please consider fixing this PR or accepting my version. Thank you

I created and tested a working alternative package for this application here: #97869
Please consider fixing this PR or accepting my version. Thank you

The referenced PR has the same issue, and the manifest in this PR is both complete and accurate. This application cannot be added until the pipelines are updated or a manual review by Microsoft occurs.

I created and tested a working alternative package for this application here: #97869
Please consider fixing this PR or accepting my version. Thank you

The referenced PR has the same issue, and the manifest in this PR is both complete and accurate. This application cannot be added until the pipelines are updated or a manual review by Microsoft occurs.

Sorry to miss this for so long. Feel free to @ me for a manual review in the future.


if I manually close the app does not work?

Hi,
when I have the app in the foreground and in the background it works because it sends me notifications but if I manually close the app then everything stops working.
(it does not send me any more notifications and in the logs it does not add anything anymore)
Your Environment

Plugin version: ^0.5.0-alpha.35
Platform: iOS
OS version: mac 10.13.4, iphone 11.4
Device manufacturer and model: iPhone 7 plus
React Native version: 0.56.0
Plugin configuration options:
desiredAccuracy: BackgroundGeolocation.HIGH_ACCURACY,
stationaryRadius: 5,
distanceFilter: 3,
notificationTitle: 'Background tracking',
notificationText: 'enabled',
debug: true,
startOnBoot: true,
stopOnTerminate: false,
saveBatteryOnBackground: false,
locationProvider: BackgroundGeolocation.DISTANCE_FILTER_PROVIDER,
interval: 10000,
fastestInterval: 5000,
activitiesInterval: 10000,
stopOnStillActivity: false

Context
So what I want to know is, does it work if the app is manually closed or I have a wrong configuration?
Thanks

'stopOnTerminate: false' is currently Android only feature. If you terminate your app on iOS it will just stop sending locations. I was working on iOS implementation, but due lack of time and resources it's progressing slowly.

I should correct docs though.

Thanks for the quick response.
Ah okok, so theoretically on ios can you implement this thing right?
On ios it's possible (objective c/swift) but in this library it does not work? (at moment)
Because I watched this repo for a feature that I need in an app, I need to detect when a user is near in an area (gps position).
Could this library fit for this task?

@mauron85 thank you. Will it start tracking after phone reboot?

I did pull request in ios implementation. https://github.com/mauron85/background-geolocation-ios/pull/7
It works after phone reboot. RAW_PROVIDER and DISTANCE_FILTER_PROVIDER are supported.


Fixed time formatting in ec2/models.py

The format returned by Amazon's API follows what was created in the utc_date_and_time() function already in this file, not datetime.utcnow().isoformat(). Made running tests on comparisons by creation date difficult since the test format would return different than the real API. Haven't checked if this problem occurs anywhere else.

Coverage decreased (-0.08%) to 94.191% when pulling 10f66fcb6f0b26036950aaa7fd4a4678d7a122db on SectorNine50:master into 5c3d9b4ae144f76ee8cac8182c48db8450aa8f4a on spulec:master.

Coverage decreased (-0.08%) to 94.198% when pulling 10f66fcb6f0b26036950aaa7fd4a4678d7a122db on SectorNine50:master into 5c3d9b4ae144f76ee8cac8182c48db8450aa8f4a on spulec:master.

Coverage decreased (-0.08%) to 94.204% when pulling 8845d5785ff61797e97214cfe1c8e881978df84d on SectorNine50:master into 05c6fc673896c9a500bf5cb7f6fa34510db1d50b on spulec:master.

Coverage remained the same at 94.28% when pulling 8845d5785ff61797e97214cfe1c8e881978df84d on SectorNine50:master into 05c6fc673896c9a500bf5cb7f6fa34510db1d50b on spulec:master.

The test that failed (test_layers.test_describe_layers) appears to be due to a race condition in the test itself:

X['ResponseMetadata']['HTTPHeaders']['date'] is 'Mon, 14 Nov 2016 17:58:36 GMT' whereas Y['ResponseMetadata']['HTTPHeaders']['date'] is 'Mon, 14 Nov 2016 17:58:37 GMT'

We should be able to use freezegun for this test in order to get it passing.


Wiki to explain the working of the application in a concise manner, for developers

It would be really great to have a wiki to start explaining the working of the application. Starting from the database schema and how things are inserted into and read from it.
And I see some permissions related feature in the application, which I haven't tried properly, but it would be great to know how it all works, so that when new developers come in, they can easily contribute by knowing what's going on and what's the expected outcome of the application and the modules, so that they can fix bugs if they notice any other outcomes

This is a very valid point - I'm currently working on a setup guide for manual installation. Prior to this, I'm going to submit a PR improving the development flow of the app. Leveraging the Wiki for this purpose is certainly something I'll look at.

I'm going to prioritise this as it would make it much easier for people to contribute, I'll have a full manual installation/development guide up within the next few days.

Cool !

Also, we have to make PR against staging or master ? Because I see two branches. But for now both are at the same point I guess

For the moment - the old staging branch had diverged from master so significantly I replaced it. PRs should point to staging from this point onwards, ideally.

Yes, so that we always keep the master branch stable and not broken. And we can merge staging to master later after a few PRs, may be during a release.
Also, we need to mention this in the Documentation while talking about Contribution

Done


Plugin no longer downloading music from YouTube

This is a reference to the same issue which was closed without fixing or any other reason given.
#64

Doesn't work for me either.

same here


Add definition for ventral nerve cord [sf#46]

Reported by cmungall on 2014-12-29 22:51 UTC
(low priority)
PMID:21062451 has the somewhat vague "A cluster of neurons that is the most prominent longitudinally extending condensed part of a nervous system"
VNC is currently a subtype of ganglion in FBbt, so a def that better fits with this would be better, e.g. surrounded by connective tissue sheath

Commented by mmc46 on 2015-02-11 13:59 UTC
Hi Chris,
I've added the def "A cluster of neurons that extends posteriorly from the embryonic and larval brain and is surrounded by a connective tissue sheath."

Updated by mmc46 on 2015-02-24 17:52 UTC

status: open --> closed


ockam status --all could list more of the available nouns

Current behavior
At the time of writing ockam status --all appears to only list identities, and linked nodes with names and status. Other resources, local or otherwise, do not appear.
Desired behavior
It would be useful if ockam status --all could prove an overview-level lists of more (local) resources. The question I was hoping to answer was "What kind of background processes have ockam commands started on my behalf, are they still running, and what kind of shape are they in?"
Initial requested behavior is to list out instances of each noun that already has a list subcommand implemented, including but not limited to:

[ ] forwarder
[ ] identity
[ ] tcp-listener
[ ] tcp-inlet
[ ] tcp-outlet
[ ] vault
[ ] worker

Design/UX input will be needed for whether this behavior should be opt-in, opt-out, a distinct flag from --all, etc. but the desire is that more than one category of information will be displayed as the output of one single command invocation.
Prior art that I would compare the idea to would be things like docker ps -a, kubectl get all -n ..., kubectl tree plugin, etc.

We love helping new contributors!
If you have questions or need help as you work on your first Ockam contribution, please leave a comment on this discussion.
If you're looking for other issues to contribute to, checkout this discussion and labels -  https://github.com/build-trust/ockam/labels/good first issue or https://github.com/build-trust/ockam/labels/help wanted

@EliKalter Hi Eli, if you're looking for a little more active mentorship on making your first Rust contributions, you might try asking in our community Discord chat here, which is also linked to on our website footer:
https://discord.gg/RAbjRr3kds
I can't guarantee that someone will be available to take you under their wing. We are still a small team, and distributed across multiple timezones. If it seems like no one is able to offer the style of help you're looking for, there are also several other Rust community chats available as well. You can find those listed on https://www.rust-lang.org/community under "Chat platforms".
It's also very welcome for community members to read up on our recent PRs or issues marked "good first issue", join our Discussions page, or even just read through the existing code, and leave us some comments to ask for clarification on changes or code that you'd like to know more about. That's a great low-pressure way to get involved while you're still learning. A lot of our codebase makes use of asynchronous Rust and Tokio, which can be both be pretty big topics in their own right. I really enjoyed the Tokio tutorial when I was first getting used to the library.
I hope at least something I mentioned is helpful to you! 🚀

@shanesveller Thank you so much!
A lot of what you said was sin fact useful!
I am already contributing to a rust project but it is kinda slow,
I'll watch your project as well and start trying to figure out what is going on,
I'll also follow the rest of your suggestions,
The main problem for me when coming to a new project is being introduced to.the way the project works and to the key technologies and libraries etc that I'm not familiar with, for example in your project I don't know at all how to work with cli interfaces, it's an entire thing I'm completely foreign to (on the development side of things, I can use a cli).


Datepicker breaks modal layout

Select one ...  (check one with "x")
[x] bug
[ ] feature request
[ ] enhancement

Initial state of modal:

After datepicker icon was clicked:

Environment details

Angular version: 5.2.9

Clarity version: 0.11.9

OS and version: Windows 10

Browser: all

@jansivans: The issue here is with the current forms. Since the .form-group has position: relative on it, it interferes with the positioning all popovers under it. @gnomeontherun is currently are working on a new version of forms. You can follow the progress here: https://github.com/vmware/clarity/issues/932
We will test this use case as part of the implementation.

Is there no workaround for this? Because this issue basically means the datepicker cannot be used in modals at the moment.

Do you have any estimation, when this bug will be fixed?
We can't go with any workaround, we have to use pure clarity solution.
Thanks!

@gnomeontherun
Was this fixed with the new grid? Any advice or a stackblitz to give us an idea of the changes required to address this with the new grid?

The new grid should fix this, even if you are using the old forms. Closing as resolved.

I am still facing the same issue.
Did anyone find a solution?
I am using the latest clarity and angular versions.

@SGauts This is pretty old and I'm not sure exactly what you are doing. There are a few cases where the date picker gets clipped due to position relative, which should be fixed soon with our updated popovers. However, if you are using a date picker in a place with relative positions around it, this may still happen (like in a modal) and for now you have to manually position the date picker so it has space. Otherwise, create a demo of your specific case and open a new ticket.


Doesn't exist anymore apparently.

When I run devenv /resetaddin I get
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\devenv" /ResetAddin
Microsoft Visual Studio 2017 Version 15.0.27130.2010.
Copyright (C) Microsoft Corp. All rights reserved.
Invalid Command Line. Unknown Switch : ResetAddin.

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

ID: b69f4b92-06df-e530-8376-4bd834152b7c
Version Independent ID: d6217fc3-c4a8-7f6d-7ec9-3b95ab433983
Content
Content Source
Service: unspecified

@keyoti thanks for the feedback. I will see if this switch has been removed from the product.

@keyoti I have removed this topic from the documentation. Thanks for helping us improve docs!


Start new experiment when user presses play (Trac #48)

If the user performs steps in realtime prior to pressing play (i.e., running a protocol), the realtime steps show up in the experiment log. It would be preferable to start a new experiment when the user presses play, which would differentiate between the realtime and automated parts of the experiment.
Migrated from http://microfluidics.utoronto.ca/ticket/48
{
    "status": "closed",
    "changetime": "2015-01-13T08:37:18",
    "description": "If the user performs steps in realtime prior to pressing play (i.e., running a protocol), the realtime steps show up in the experiment log. It would be preferable to start a new experiment when the user presses play, which would differentiate between the realtime and automated parts of the experiment.",
    "reporter": "ryan",
    "cc": "",
    "resolution": "fixed",
    "_ts": "1421138238797413",
    "component": "core",
    "summary": "Start new experiment when user presses play",
    "priority": "minor",
    "keywords": "",
    "version": "0.1",
    "time": "2012-02-20T03:41:37",
    "milestone": "Microdrop 1.0",
    "owner": "ryan",
    "type": "enhancement"
}

Trac update at 20120828T16:16:39: ryan commented:

As of v0.1-629-gba11ee3, steps run in real-time mode don't show up in the experiment log. Steps are only added to the experiment log when a protocol is running. So this ticket should be changed to:

Record data for steps run in real-time mode (save the experiment log if the id/device change or the program exits).
Start a new log in response to an on_protocol_run signal if real-time steps exist in the experiment log.

Trac update at 20140312T20:02:01: ryan changed milestone from "1.0" to "1.1"

Trac update at 20140313T20:00:48: ryan changed milestone from "1.1" to ""

Trac update at 20150105T18:08:41: cfobel changed milestone from "" to "Microdrop 1.0"

Trac update at 20150113T08:37:18:

ryan commented:

Fixed in commit changeset 2ff927c142c84a4d1dac26c3070b955aaa1d89e1.

ryan changed resolution from "" to "fixed"
ryan changed status from "new" to "closed"


[@kadena/Chainweb-stream-client] Receive heights event, improve reconnection strategy

Implements consumption of the heights event. Needed for the reconnection improvements outlined here. Server PR is here
This changes the .lastHeight client property to track the highest block seen across all chains based on the server's corresponding cw-node. The reconnection property minheight is now sent as .lastHeight - CONFIRMATION_DEPTH - 3 (max chain height span)

Raising against a new base branch, as the upcoming release will require a deduplication module to only emit each event once

Nuked this as it was used to fix the CI issues


How can I switch the disabling of the form fields using v 6 Field or FieldArray?

Hi,I'm new to the v6 and currently using redux-form v6 and material-ui to set up my form. Now Because of some requirements I need to disable the form fields like groupCode etc as code below.
So I tried to pass a fieldDisabled prop(defalutvalue=false) to MyViewForm and set the fieldDisabled = true after clicking a button outside, but it turned out the field wasn't disabled.
It looks like the Field(same as FieldArray?) wont be rendered even if any props of the MyViewForm change??
what should I do to disable the field?
My code here:
class MyViewForm extends React.Component{

	render(){
			  const {
				fieldDisabled,
				handleSubmit} = this.props;

			  console.log("fieldDisabled=======================>",fieldDisabled);//can see the change here.

			  return (

					<form id="fieldForm" onSubmit={handleSubmit}>
						---------TextField wont be disabled.-------------
						<Field name="groupCode"
							component={(groupCode)=><TextField {...groupCode} id="groupCode" disabled={fieldDisabled} errorText={groupCode.error}/>}/>
					</form>

			);
	}

}

MyViewForm = reduxForm({
  form: 'myViewForm'
})(MyViewForm)

export default connect(
  state => ({
    initialValues: state.fillout.data   //this works fine.
  })
)(MyViewForm)

I think this was fixed by #940. I will expedite the next release.

@erikras thanks. As I looked into #940 and i upgraded to alpha 9 but i happened to encounter a same problem as #961.  It seems there is still no proper solution to the issue?

Oh, oops. I thought #940 hadn't been published yet. Sorry about that.

Have you tried something like this?
const EnhancedTextField = props => (
  <TextField {...props} id={props.name} errorText={props.error} />
)

class MyViewForm extends React.Component {
  render() {
    const {fieldDisabled, handleSubmit} = this.props
    return (

        <form id="fieldForm" onSubmit={handleSubmit}>
          <Field name="groupCode"
            disabled={fieldDisabled}
            component={EnhancedTextField}
          />
        </form>

    )
  }
}

Passing arrow functions to component is heavily discourage.
See https://github.com/erikras/redux-form/issues/961#issuecomment-219785684 and answers.

@ooflorent yes, that works...thank you.


Detecting binary files and not allowing to read them

See e.g. fort.9 in the test archive.

Closed via #6


How to catch the abnormal situation during battery operation by  Petlion

Hi MarcBerliner.  I want to catch the outlier during battery operation, that is, if the temperature is set too high, the current and voltage will change abnormally during battery operation. BBut in my previous attempts, if I set it this way, the program would report an error. May I ask if this data can be obtained through Petlion? If so, is there a suitable example? Looking forward to your reply, thank you.

To clarify, is your simulation failing at high temperatures but you still want to receive the output?

Yes, but what I want to know more is how to get the outlier through the status of the Petlion battery crash.

This isn't explicitly accounted for, but there is a workaround.  Say you want to run a CC-CV simulation
p = petlion(LCO)

sol = simulate(p, I=5, SOC=0)
simulate!(sol, p, V=:hold)

which crashes with the message
julia> ERROR: Model failed to converge at t =<PHONE_NUMBER>999999

To save the output, first initialize the solution object sol and enclose your simulation loop in a try/catch block. The solve still fails, but you can access the final states before failure.
sol = solution()

try
    simulate!(sol, p, I=5, SOC=0)
    simulate!(sol, p, V=:hold)
catch
    # input catch here
end

julia> PETLION simulation
 --------
 Run:     I
 Time:    485.27 s
 Current: 3.5487C
 Voltage: 4.3 V
 Power:   446.03 W/m²
 SOC:     0.6485
 Exit:    Above max. voltage


global.proxy.privileged=true - how do we set in patch to enable tcpdump in side car

Describe the bug
Side car proxy does not support tcpdump command when executed using kubectl exex
Steps to reproduce the issue:
kubectl exec it pods/ -c istio-proxy -- sh sudo tcpdump
Expected behavior
sudo tcpdump should run
What value should be set in istio operator patch
e.g. is below command right?
kubectl patch istio my-istio -n istio-system --type=json -p='[{"op": "replace", "path": "/spec/proxy/privileged", "value": true}]'

The patch command looks right and then the pod with the sidecar proxy should be restarted so that it gets the new config. Doesn't it work?

yes, thanks it works.


Look for any open pull requests in the repository with the title "e2e-tests update" and
see if there are recent e2e-tests updates that will be applicable to your change.

Just for a demo


Function get_bearer_token_provider is not JSON serializable

A warning about using the AzureOpenAI is displayed in version 2.5.2. The recommendation is to use dspy.LM. I get the serialize exception when I change this the client from this:
from azure.identity import DefaultAzureCredential, get_bearer_token_provider

token_provider = get_bearer_token_provider(
    DefaultAzureCredential(), "https://cognitiveservices.azure.com/.default"
)

model=os.environ["AZURE_AI_MODEL_GPT_4o"]

llm_gpt_4o = dspy.LM(
    model="gpt-4o"
    api_version=os.environ["OPENAI_API_VERSION"],
    api_base=os.environ["AZURE_OPENAI_ENDPOINT"],
    azure_ad_token_provider=token_provider,
    max_tokens=3000,
)

to this:
llm_gpt_4o = dspy.LM(
    model=os.environ["AZURE_AI_MODEL_GPT_4o"],
    api_version=os.environ["OPENAI_API_VERSION"],
    api_base=os.environ["AZURE_OPENAI_ENDPOINT"],
    azure_ad_token_provider=token_provider,
    max_tokens=3000,
)

Thanks @arthurgreef ! What is the serialize exception? Basically what's the error?
You can also get a much more complete error message by doing:
import litellm
litellm.set_verbose=True # 👈 this is the 1-line change you need to make

Also what's in os.environ["AZURE_AI_MODEL_GPT_4o"]? It should probably start with azure/ or something like that for LiteLLM.

I took another look. This works great. Thanks.
from azure.identity import DefaultAzureCredential, get_bearer_token_provider

azure_ad_token = get_bearer_token_provider(
    DefaultAzureCredential(), "https://cognitiveservices.azure.com/.default"
)()

model=os.environ["AZURE_AI_MODEL_GPT_4o"]

llm_gpt_4o = dspy.LM(
    model="azure/"+os.environ["AZURE_AI_MODEL_GPT_4o"],
    api_version=os.environ["OPENAI_API_VERSION"],
    api_base=os.environ["AZURE_OPENAI_ENDPOINT"],
    azure_ad_token=azure_ad_token,
    max_tokens=3000,
)

dspy.configure(lm=llm_gpt_4o)

I am now having a problem with tracing in Phoenix using the adaptors. Is there something that needs to be updated in Pheonix. Here is the code that works with the AzureOpenAI client.
    # Needs to be before dspy import to get token tallies
    os.environ["DSP_CACHEBOOL"] = "False"
    import dspy

    from openinference.instrumentation.dspy import DSPyInstrumentor
    from openinference.instrumentation.openai import OpenAIInstrumentor
    from opentelemetry import trace as trace_api
    from opentelemetry.exporter.otlp.proto.http.trace_exporter import OTLPSpanExporter
    from opentelemetry.sdk import trace as trace_sdk
    from opentelemetry.sdk.resources import Resource
    from opentelemetry.sdk.trace.export import ConsoleSpanExporter, SimpleSpanProcessor

    from phoenix.otel import register
    endpoint="http://<IP_ADDRESS>:6006/v1/traces"
    register(endpoint=endpoint)

    resource = Resource(attributes={})
    tracer_provider = trace_sdk.TracerProvider(resource=resource)
    tracer_provider.add_span_processor(SimpleSpanProcessor(OTLPSpanExporter(endpoint)))
    tracer_provider.add_span_processor(SimpleSpanProcessor(ConsoleSpanExporter()))

    trace_api.set_tracer_provider(tracer_provider=tracer_provider)

    DSPyInstrumentor().instrument()
    OpenAIInstrumentor().instrument()

Yeah, the design of tracing (Phoenix and LangFuse) needs to change since the library is different internally for dspy.LM (DSPy 2.5 onwards).
By the way, you may also want to set:
os.environ["DSPY_CACHEBOOL"] = "False" # notice the Y, for 2.5 clients

Requested a new feature to support DSPy 2.5.

Really appreciate your initiative on this @arthurgreef !

This has been fixed https://github.com/Arize-ai/openinference/issues/1050


conver string to float for common domainlab args in benchmark

Codecov Report

Merging #585 (d947ff1) into master (b974cac) will decrease coverage by 0.01%.
The diff coverage is 92.30%.

:exclamation: Current head d947ff1 differs from pull request most recent head 5d5066f. Consider uploading reports for the commit 5d5066f to get more accurate results

@@            Coverage Diff             @@
##           master     #585      +/-   ##
==========================================
- Coverage   95.42%   95.41%   -0.01%
==========================================
  Files         131      131
  Lines        4721     4733      +12
==========================================
+ Hits         4505     4516      +11
- Misses        216      217       +1

Flag
Coverage Δ

unittests
95.41% <92.30%> (-0.01%)
:arrow_down:

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

Files
Coverage Δ

domainlab/exp_protocol/run_experiment.py
81.44% <92.30%> (+1.44%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


A different Handlebars.print for re-printing an AST back to source code

I'm not quite sure what to call it yet, other than Handlebars.print. Currently, Handlebars.print prints stuff like "BLOCK PARAMS[actual code]" https://github.com/wycats/handlebars.js/blob/master/lib/handlebars/compiler/printer.js#L30
It'd be great to have a utility function for just reprinting an AST. The reason for this being I'm working on some tools to help users of Ember upgrade some of their deprecated syntax and check the result of that back into version control without otherwise changing the source code. Ideally, you could parse a template, pass the AST into this function, and have the string returned be identical to the template you parsed.
I can definitely work on this, I'm just wondering whether this belongs here or in its own project.
Thanks!

I'm fine with it in the core library as long it is not included in the
client builds.
On Tue, Jan 6, 2015 at 11:59 AM Stanley Stuart<EMAIL_ADDRESS>wrote:

I'm not quite sure what to call it yet, other than Handlebars.print.
Currently, Handlebars.print prints stuff like "BLOCK PARAMS[actual code]"
https://github.com/wycats/handlebars.js/blob/master/lib/handlebars/compiler/printer.js#L30
It'd be great to have a utility function for just reprinting an AST. The
reason for this being I'm working on some tools to help users of Ember
upgrade some of their deprecated syntax and check the result of that back
into version control without otherwise changing the source code.
I can definitely work on this, I'm just wondering whether this belongs
here or in its own project.
Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/wycats/handlebars.js/issues/935.

@fivetanley are you bailing on this goal in addition to the PR?

Changing direction a bit. Will probably be a standalone library similar to benjamn/recast.

@fivetanley I wrote something like this for Handlebars: https://github.com/zeppelin/handlebars-serializer
Dunno if that helps, or you need any help regarding the same feature for HTMLBars

It is by no means feature-complete, but it does cover my use cases: https://github.com/zeppelin/handlebars-serializer/blob/master/packages/handlebars-serializer/tests/serializer-test.js

You can Try https://github.com/handlebars-lang/handlebars.js/issues/169#issuecomment-1772483796


Allow building sail to run PHP as root

Hi,
Today, I tried running Sail in a rootless Podman container, and the experience was less-than-ideal. You might better recognize the class of issues as being similar to Docker Desktop - this would be precisely right: it's the same all over again.
The reason boils down to the follow: the image, as it is laid out currently, has its entrypoint running as root, and its main functionality (i.e. php) running as the sail user. This means that root inside the container is the host user I'm using to run the container, and sail is some random UID.
Some relevant supporting documentation and references to previous issues:

Rootless containers with Podman: The basics -- from Red Hat, Recaps the basics of rootless containers and why running rootless containers is a good thing
Understanding rootless Podman's user namespace modes -- from Red Hat, explains the issue of Linux's user namespaces very effectively
#81 #459 #536 #548 etc.

The proposed proof-of-concept patch simply allows setting the $SUPERVISOR_PHP_USER env variable to run PHP in the container as root. Users should be instructed about this by the "getting started" documentation, to avoid spending an evening figuring it out (or not) like I just did.
In my opinion this is the only valid long-term solution for rootless containers, as:

There is a lot of voodoo around the web and even in some of the issues linked above. The bottom line is that rootless unprivileged users (like sail in the sail container) have an effective ("host") UID that will not in any case be able to access /var/www/html (i.e. the user's project files), regardless of the value of --userns, if the files themselves are not chowned to this unprivileged by either Podman (U flag for bind mounts) or something running on the host. This is because root in the container is mapped to the user launching the container, and all other uids in the container are mapped to random junk host uids (usually >100000). It's simple to test this: open a root shell in a Sail container, and run touch /var/www/html/example && chown sail:sail /var/www/html/example; go on that directory outside the container, the UID will be some junk number. You can also run cat /proc/self/uid_map inside the container to see the mapping
For that exact reason, bind mounts are only accessible by root inside the containers (unless the files in the bind mounts have world r/w permissions of course)
It follows from this that PHP in Sail rootless containers should run as root

This will effectively make PHP have the permissions and capabilities of the launching user, which imho is the standard expectation for a dev environment. Furthermore, in a world where people don't just go around launching containers as root, this would also be a sensible default setting, but since the real world is the insurmountable single point of truth I won't advocate for that.
So, to recap:

By default, rootless containers map root in the container to the user running the container (meets expectations: Laravel runs as the user who launches the command)
Root inside a rootless container is NOT root on the host, even if it escapes the container (secure)
This patch adds support to build the Sail container to run rootless
If the idea accepted, the patch should, at a minimum, be should be supplemented by adequate documentation
If you want to pursue this but you feel like the patch is not adequate, please feel free to request any changes that would make the patch more adherent to your coding customs; I will be glad to oblige

Well done and thank you @vmsh0! Thanks to your PoC, I was able to publish the files locally with the command sail exec service.name php artisan sail:publish.

Well done and thank you @vmsh0. Your explanation and PoC were helpful to me.

Thank you for merging this, I'm glad to see it's useful to people.
Please, help me with the next steps to improve this:

Right now this functionality is pretty hidden. I would say that a reference should be added to the various "getting started" paths of Laravel suggesting the use of Laravel Sail. Do you agree?
Should this be added to any other documentation pages?
Is there anything else that should be built upon this PR to ensure the best possible user experience and maintainability?


Tech debt: Remove usages of aws_lambda_powertools.shared.types

Why is this needed?
Remove usages of aws_lambda_powertools.shared.types imports and replace them by either types from the standard library that are already compatible with Python >= 3.8 or types from typing_extensions. Remove the aws_lambda_powertools.shared.types package too.
Which area does this relate to?
Other
Suggestion
No response
Acknowledgment

[X] This request meets Powertools for AWS Lambda (Python) Tenets
[ ] Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

Closed via #4896


easyfig 2.1.0 (new formula)

Easy genome comparison figures.
EasyFig is a Python application for creating linear comparison figures of
multiple genomic loci with an easy-to-use graphical user interface (GUI).

Will you keep the comments in any case? That's what we've been doing in Homebrew/science. It helps a lot, in fact, to be able to brew cask edit foo and see this information.

Thank you for the contribution. It needed some fixes, so they were made in a0efa1994bb9627ab1414dd752e89cedba6ae642. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.

Comments were removed since we don’t intend to become a discoverability service. It is not part of the goals of homebrew-cask. Amongst other things, the logistics are unsustainable.
Keeping comments that are actually unworking code from homebrew makes no sense, especially if only a select few casks have them. We need consistency, now.
On another note, you can brew cask cat <cask_name> to see its contents.

#{version.to_f}

Nice hack. I haven't seen that one before. It scares me though that to_f doesn't blow an assertion when there are unconverted characters.

Since Homebrew supports desc (and I know they debated this addition for the same reason you mention above), I think Homebrew Cask should also support desc.

Thanks for merging.

Nice hack.

to_f is ugly right now (but it works, and is more readable than gsub) but it should be better in the future.

Since Homebrew supports desc

We’re separate apps with separate maintainers and policies. What works for one does not necessarily work for the other.

I think Homebrew Cask should also support desc.

Not going to happen. At least not in the near future for sure. As I said, the logistics are unsustainable and we have a whole lot of things to worry about before than can even enter into consideration again.

Thanks for merging.

Thank you for the contributions.


Merge new MV3 branch into Main

This entails:

[x] Making sure @OliverWang13 and @sophieeng don't have outstanding work that would get lost in the merge.
[x] Make sure MV2 changes since branch issue-175 was made don't get lost in the merge.

After we finalize the open PR, let's double check that all of the work done since we opened issue #175 was merged correctly and is functional. Note that testing on Firefox will be difficult as FF doesn't yet support MV3 extensions.


Use boilersuite for boilerplate verification

Removes the need for Python in development environments for trust-manager!
This also requires some small boilerplate changes since boilersuite is a little more exacting than the old script was.

/approve
/lgtm
Thanks for this improvement!


Smart Wallet Addresses Hook

Added new Smart Wallet Addresses hook which will return all the computed addresses that are found in the React Components for each chain.

Added hooks code, interfaces
Updated example

@poocart ready for rereview mate


Change tab with keyboard doesn't change the entire tab

Description
When you use a keyboard shortcut to change to the previous or next tab (Ctrl + Shift + Tab or Ctrl + Tab), sometimes it will change the folder contents but not the toolbar and address bar, other times it won't change at all...
In the gif, check for example that the second time changing from home to Music, it will keep the widgets button instead the folder buttons, and the address bar says "Nueva pestaña" instead my Music path.
Steps To Reproduce

Open several tabs with differents folder.
Start to change tabs with the keyboard shortcut (Ctrl + Shift + Tab or Ctrl + Tab)
Check the address bar and see that sometimes it shows an incorrect address.

NOTE: For some reason apening settings and closing it seems to fix the issue until you open a new tab.
Expected behavior
It should show the proper address and toolbar.
Files Version
V <IP_ADDRESS>
Windows Version
OS Version: Windows 10 21H1 10.0.19043.1202
Relevant Assets

Log files:
debug_fulltrust.log
debug.log

@BanCrash do you want to work on this issue?

@BanCrash do you want to work on this issue?

Yeah, I already had on my to do to check if I can fix it 👍🏻

Is this still an issue in the preview version? https://files.community/download/preview

Is this still an issue in the preview version? https://files.community/download/preview

Yes, it is.

It seems to happen when it cycles back to the first tab 🤔

It seems to happen when it cycles back to the first tab 🤔

In my case is not necessary, just switching to another tab and going back will make that happen. Just tested with 3 tabs, switching to 3, then switching back to 2 and again to 3. Issue happens.
All my attemps of solving it were a dead end.

@cinqmilleans fyi

FYI, this is not fixed in <IP_ADDRESS> @yaira2

The fix wasn't included in v2.4.60 but you can test it in main.

The fix wasn't included in v2.4.60 but you can test it in main.

Yep, you are right, in main is fixed, my bad!


rmr report "no such file or directory" when file exist.

What happened:
https://github.com/juicedata/juicefs/actions/runs/3060700916/jobs/4939536789

start rmr
run_cmd:dd if=/dev/urandom of=/tmp/sync-test//file_to_rmr bs=1048576 count=3
3+0 records in
3+0 records out
3145728 bytes (3.1 MB, 3.0 MiB) copied, 0.0708432 s, 44.4 MB/s

run_cmd succeed
run_jfs_cmd:./juicefs-1.1.0-dev rmr /tmp/sync-test//file_to_rmr --debug
   --trash-days value       number of days after which removed files will be permanently deleted (default: 1)
run_jfs_cmd return code: 0, output:
run_jfs_cmd succeed
rmr succeed
start dump
run_jfs_cmd:./juicefs-1.1.0-dev dump tikv://<IP_ADDRESS>:2379 dump.json --debug
run_jfs_cmd return code: 0, output: 2022/09/15 13:13:16.725644 juicefs[11646] <INFO>: Meta address: tikv://<IP_ADDRESS>:2379 [interface.go:411]
[2022/09/15 13:13:16.725 +00:00] [INFO] [client.go:378] ["[pd] create pd client with endpoints"] [pd-address="[<IP_ADDRESS>:2379]"]
[2022/09/15 13:13:16.728 +00:00] [INFO] [base_client.go:350] ["[pd] switch leader"] [new-leader=http://<IP_ADDRESS>:2379]/ [old-leader=]
[2022/09/15 13:13:16.728 +00:00] [INFO] [base_client.go:105] ["[pd] init cluster id"] [cluster-id=7143593052261163827]
[2022/09/15 13:13:16.728 +00:00] [INFO] [client.go:673] ["[pd] tso dispatcher created"] [dc-location=global]
[2022/09/15 13:13:16.829 +00:00] [WARN] [pd.go:152] ["get timestamp too slow"] ["cost time"=100.756022ms]
2022/09/15 13:13:16.845838 juicefs[11646] <WARNING>: Secret key is removed for the sake of safety [tkv.go:2592]
2022/09/15 13:13:16.846724 juicefs[11646] <INFO>: Dump metadata into dump.json succeed [dump.go:80]

run_jfs_cmd succeed
dump succeed
start rmr
run_cmd:dd if=/dev/urandom of=/tmp/sync-test//file_to_rmr bs=1048576 count=3
3+0 records in
3+0 records out
3145728 bytes (3.1 MB, 3.0 MiB) copied, 0.0631098 s, 49.8 MB/s

run_cmd succeed
run_jfs_cmd:./juicefs-1.1.0-dev rmr /tmp/sync-test//file_to_rmr --debug
<FATAL>: subprocess run error, return code: 1 , error message: 2022/09/15 13:13:17.324990 juicefs[11658] <FATAL>: RMR /tmp/sync-test//file_to_rmr: no such file or directory [rmr.go:105]

What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?
Environment:

JuiceFS version (use juicefs --version) or Hadoop Java SDK version:
Cloud provider or hardware configuration running JuiceFS:
OS (e.g cat /etc/os-release):
Kernel (e.g. uname -a):
Object storage (cloud provider and region, or self maintained):
Metadata engine info (version, cloud provider managed or self maintained):
Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage):
Others:

Reason: rmr doesn't invalid the kernel cache.


[WFLY-10013] Upgrade WildFly Core 5.0.0.Alpha1

Upgrade all domain XML configuration to urn:jboss:domain:7.0
JIRA: https://issues.jboss.org/browse/WFLY-10013

passivation issue in Linux JDK9 job is not related to the PR

@jmesnil feel free to merge this. I am not sure if the JDK9 failure is valid or not, but have retriggered that job


_ViewStart disabled

Hi,
Is there a way to reactivate _ViewStart? Currently it won't even get loaded even if I create one.
Thanks,
Chris

Where you put your _ViewStart?. It should be in the "Views" of every module


Question: Why do you freeze batch norm layers?

Hello,
First, thank you for the repo!
in  EfficientDet.init line 55
[...]
self.freeze_bn()
If I want to retrain on custom data. I'd want to retrain the entire net, no?
Thanks!

In my option. it depends on your batch size.
if your batch size is small, you'd better to freeze them
you can reference RetinaNet's methods

@adizhol You might be confusing freezing batchnorm layers with freezing backbone layers. Calling self.freeze_bn() does NOT freeze the whole backbone, you'll still be training the entire net.

in my fork I added freeze_backbone and freeze_bn options so that you can first freeze the backbone in order to adjust the retina heads weights. After that you can retrain the whole network by freezing the bn layers. Adding freezing bn layers avoids the bn stats numbers for small batch size.


Cleanup unused branches

Coming from https://github.com/opensearch-project/opensearch-clients/issues/64, cleanup unused branches.
For some unused branches we probably want to save state, so maybe note the last revision of any branch being deleted in this issue as it's being closed.

Catch All Triage - 1 2 3 4 5 6


[Q] How to persist cron scheduled jobs?

Hi, there.
In your example about scheduler and cron you suggest to use node-cron, or node-schedule. Both essentially are setTimeout wrappers without any possibilty to restore restarted task. With restore i mean full app restart with redeploy e.g.
So my question is what is recommended way to persist such things? If any availabled now of course.
Thanks.

The use of a node-cron-like timer will only be running on one process to enqueue jobs.  The jobs that it enqueues will, in fact, survive a restart as they will persist in redis.  Also, if you have more than one process which can hold the role of 'master' and scheduler, another one can take over if the first process exits.
With resque, you have have to create your jobs with 1) idempotency and 2) recovery, as with a distributed system, any part can fail.  If you job is simply "do a thing every hour", you will have problems.  Instead, create a job like "every minute check if it has been 60min+ since the last time I did the thing, and if so, do the thing".

Sorry to revive an old issue,
but i am having this problem. I use pm2 and after the pm2 restart the tasks scheduled with this https://github.com/taskrabbit/node-resque/blob/master/examples/scheduledJobs.js gets killed and does not continue after the restart.
is this the normal behaviour or i am doing smt wrong? thanks


move privacy declarations to their own table

❗ Contains migration; check downrev before merge
Closes #3036
Moves the objects stored in the JSON blob (array) column of System.privacy_declarations into their own table, privacydeclarations. All fields previously on the privacy_declaration objects are now columns on this new table. Additionally each record in the new table points via FK to their associated System record (identified by its fides_key); we also are able to make a proper FK link to the associated DataUse records, which are also identified by fides_key - previously, this was just a string field on the JSON object.
Maintains backward compatibility with existing "system" API by manually handling the privacy declarations defined inline on system create/update requests. There were already special-cased endpoints for System objects outside of the generic crud.py API due to special handling for system manager permissions - we build out those special-cased endpoints a bit further here. We're able to leverage the existing pydantic models (stored in fideslang) just about as-is - there was only a trivial fideslang update needed (v1.3.4) to set orm_mode = True on the PrivacyDeclaration model class.
Note that at this point, there's no API to interact with PrivacyDeclaration records directly. We may want to build that out in the future, but for now, keeping the API interactions through the System will support the existing UI just fine, and it allows us to limit our surface area of these changes a bit.
Code Changes

create a new PrivacyDeclaration table and associated SQLAlchemy model

include a data migration to populate the table based on System.privacy_declaration data
FK links to System (which will cascade deletes, i.e. System is the "parent" object) and to DataUse, which means that the declaration MUST point to an existing DataUse

update System APIs to create and maintain PrivacyDeclaration records

update the special-cased PUT/update function to upsert PrivacyDeclaration records associated with the System, as defined by their DataUse
make a new special-cased POST/create function for systems to create PrivacyDeclaration records associated with the System
make a new special-cased /upsert function to perform the update logic above for bulk upserts. note that we did not already have a special-cased /upsert function for System, i'm not exactly sure on the permissions implications

some other minor code updates for compatibility. generally, though, not much needs to change - we're still able to access privacy_declarations off of a System record via the back-populated relationship, so things mostly look the same for other parts of the codebase interacting with these records.

Steps to Confirm

from what I can tell, the UI seems to still be able to manage privacy declarations just fine

Pre-Merge Checklist

[ ] All CI Pipelines Succeeded
Documentation:

[ ] documentation complete, PR opened in fidesdocs
[ ] documentation issue created in fidesdocs

[ ] Issue Requirements are Met
[ ] Relevant Follow-Up Issues Created
[ ] Update CHANGELOG.md
[ ] For API changes, the Postman collection has been updated

Description Of Changes
As privacy declarations (i.e. the data uses associated with a system) become more central to our application, it will benefit us to have them in their own table, with proper FK links to System records and DataUses. This will allow us to manage and query them much more easily moving forward.
The specific motivation for this change was to allow custom fields to apply to a given PrivacyDeclaration record, which wouldn't have been possible if they were defined as embedded JSON.

This is still a bit rough around the edges, so i'll look to finalize some testing and polish, but in the meantime i wanted to get some preliminary eyes on it since i'm hoping this is how things will look generally, and want to know if there are any red flags.
@ThomasLaPiana - i think you're most familiar with Systems and the generic crud API, so would you mind looking over this change?
@pattisdr - tagging you too since it's always good to have your eyes on DB movements :) also, this interacts pretty heavily with a lot of the recent consent plumbing
@allisonking - you'd mentioned in the linked issue that you may be able to evaluate things on the FE. things looked good when i used the UI in testing, but it would be great to get a more discerning set of eyes on how the FE code is interacting with things. afaik, the API should be completely backward compatible, but i want to make sure nothing snuck in!

codecov is complaining about a lot of places that i'm just about positive are covered by tests i've added (mainly in tests/ctl/core/test_api.py). perhaps @ThomasLaPiana you may have some ideas?

I suspect those workarounds combined with something in this change is creating this bug. I can look into it, but curious if you have any immediate thoughts first @adamsachs ?

ah yes thanks for pointing this out @allisonking! i'd assumed that a given System can only have one privacy declaration with a given DataUse. Some of the BE API logic I implemented assumes that to be the case. We could certainly adjust that, though, if it's not desired behavior - which I think is more of a product question.
So tagging in @mfbrown and @rsilvery  - do we want to allow for more than one 'privacy declaration' pointing to a particular DataUse on a given System?

I suspect those workarounds combined with something in this change is creating this bug. I can look into it, but curious if you have any immediate thoughts first @adamsachs ?

ah yes thanks for pointing this out @allisonking! i'd assumed that a given System can only have one privacy declaration with a given DataUse. Some of the BE API logic I implemented assumes that to be the case. We could certainly adjust that, though, if it's not desired behavior - which I think is more of a product question.
So tagging in @mfbrown and @rsilvery - do we want to allow for more than one 'privacy declaration' pointing to a particular DataUse on a given System?

@mfbrown  didn't this come up with Momentive and we changed it so you could have the same data use so long as the purpose for processing was different?

I suspect those workarounds combined with something in this change is creating this bug. I can look into it, but curious if you have any immediate thoughts first @adamsachs ?

ah yes thanks for pointing this out @allisonking! i'd assumed that a given System can only have one privacy declaration with a given DataUse. Some of the BE API logic I implemented assumes that to be the case. We could certainly adjust that, though, if it's not desired behavior - which I think is more of a product question.
So tagging in @mfbrown and @rsilvery - do we want to allow for more than one 'privacy declaration' pointing to a particular DataUse on a given System?

@mfbrown didn't this come up with Momentive and we changed it so you could have the same data use so long as the purpose for processing was different?

That is correct. There is a need to have the same data use more than once on a system and the check for uniqueness is against both the Use + Activity (which is the declaration name in the BE, i believe)

thanks @adamsachs ! let me know if you want me to take a look again. if you update the BE to have that behavior and the FE still isn't behaving, let me know, since it could definitely be that the FE logic is no longer relevant. regardless, once this PR is in, I'll make a follow up ticket to update some of the FE, since I don't think it'll need to do as many checks as it is doing right now :)
one other thing I noticed—I tried to autogenerate some typescript types based off of the openapi spec and noticed the spec for a PrivacyDeclaration didn't have any changes. I'd expect it to have an id now that it has its own table? I just poked around a bit, and I'm guessing it's because the model in fideslang doesn't have an id? anyway, it's not urgent or anything, and I wouldn't want it to break anything with how systems can be updated right now, but just want to make sure I'm understanding things right

marking this as ready for review as i think i've addressed all the major concerns/decisions from the initial review!
@allisonking i've pushed a new tag 2.11.1a4 that can be used for some testing if you'd like. i ran through things (though not in plus) on my end in the UI, and they looked good, including the edge-ish case you'd identified.

hi @pattisdr @ThomasLaPiana, a friendly nudge on this for another round of BE review as i'd like to get this merged ASAP since there are a few subsequent pieces of functionality due this sprint that depend on this. i'll be out for most of the earlier part of the day on monday but should be able to circle back to address any feedback monday evening, if either of you are able to take a look earlier in the day. i would really appreciate it!

thanks @adamsachs don't worry I haven't forgotten!


How to reference not-imported types from ES6 modules?

I have something like the following:
Foo.js:
export default class Foo {
    // code
}

Bar.js:
export default class Bar {
    /**
     * @param {!Foo} foo
     */
    constructor(foo) {
        // code
    }
}

Note that Bar.js uses an instance of the class from Foo.js but does not need to import Foo.js. What is the correct way to declare that Bar’s constructor takes a Foo in that situation? In the old namespace system, I was able to reference Foo by its full namespace, without having to goog.require('namespace.Foo');. The code above doesn’t compile:
$ java -jar node_modules/google-closure-compiler/compiler.jar --js Foo.js --js Bar.js --compilation_level ADVANCED_OPTIMIZATIONS --jscomp_warning '*'
Bar.js:3: WARNING - Bad type annotation. Unknown type Foo
	         * @param {!Foo} foo
	                    ^

0 error(s), 1 warning(s), 100,0% typed

That makes sense, because the compiler can’t know if I really mean the class in Foo.js. I’m looking for some way to reference the class in Foo.js.
I could import Foo.js into Bar.js:
import Foo from './Foo';
export default class Bar {
    /**
     * @param {!Foo} foo
     */
    constructor(foo) {
        // code
    }
}

But then I have an unused import:
$ java -jar node_modules/google-closure-compiler/compiler.jar --js Foo.js --js Bar.js --compilation_level ADVANCED_OPTIMIZATIONS --jscomp_warning '*'
Bar.js:1: WARNING - 'module$Foo' required but not used
import Foo from './Foo';
^

0 error(s), 1 warning(s), 100,0% typed

Which isn’t a good solution, either. In JSDoc, I believe I could do:
Foo.js:
/**
 * @module namspace/Foo
 */
export default class Foo {
    // code
}

Bar.js:
export default class Bar {
    /**
     * @param {!module:namespace/Foo} foo
     */
    constructor(foo) {
        // code
    }
}

But closure compiler does not accept that syntax:
$ java -jar node_modules/google-closure-compiler/compiler.jar --js Foo.js --js Bar.js --compilation_level ADVANCED_OPTIMIZATIONS --jscomp_warning '*'
Bar.js:3: WARNING - Bad type annotation. expected closing }
	         * @param {!module:namespace/Foo} foo
	                          ^

Bar.js:3: WARNING - Bad type annotation. expecting a variable name in a @param tag
	         * @param {!module:namespace/Foo} foo
	                          ^

Bar.js:5: WARNING - Function must have JSDoc.
		    constructor(foo) {
		    ^

0 error(s), 3 warning(s), 100,0% typed

So what is the expected way to reference the class from Foo.js in Bar.js without importing Foo.js?

This is something best asked on stackoverflow or the Google group. In fact, it's already been answered there: https://groups.google.com/d/msg/closure-compiler-discuss/nW5nbGcerJw/RECwK40cBAAJ


New API enpoint

First API endpoint added to retrieve build data.

Waiting for https://github.com/openshift-eng/art-dashboard-server/pull/24 to be merged, to fix conflicts if any.


props.theme is undefined when testing a component

v2.0.0-17
Everything renders fine but with create-react-app, running test:
it('renders without crashing', () => {
  const div = document.createElement('div')
  ReactDOM.render(<Heading />, div)
})

throws error: TypeError: Cannot read property x of undefined.
x for me is colors property of theme object passed to ThemeProvider:
const theme = {
  colors: { primary, secondary, etc... }
}

Test fails because props.theme is undefined. But everything renders fine. Is this a bug?

I just tested this and it looks fine to me. Here's a webpackbin I've just pointed at 2.0.0-17: https://www.webpackbin.com/bins/-KkTI7hqsV0qvukYj3d6

What browser are you using? Could it be related to #765?

I'm using chrome. I don't think it's related to #765. The theme provider passes its props fine and the component renders correctly in browser. The error only shows up with create-react-app test console. I tried it with and without extendWith.

Oh, it's not failing in the browser, just in the test?

Yeah, it renders fine. Everything works except it fails test.

Oh wait, can you post your actual code? Is it something like ${props => props.theme.x.y}?

Yep exactly.
<ThemeProvider theme={theme}>
  ...
</ThemeProvider>

And then somewhere in a child component
${props => props.theme.x.y}
throws test error
TypeError: Cannot read property x of undefined.

@cocacrave I'm assuming the child component is being tested in isolation? If that is the case, your issue is probably that it has no way of getting the theme without the parent component.
You can fix this by explicitly passing the theme in for your test case, or by setting defaults for the theme on the component so it can render when a theme isn't provided. @geelen and crew may have other ways to fix this, but this is how I've handled it.

Got it, thanks!

@cocacrave I'll carefully close this now. I hope you don't mind. Feel free to further comment if you have more problems with testing themed components :)

@bhough @philpl I understand that wrapping the component in the ThemeProvider will work because of the missing context. But isn't there a more comfortable way of testing this? You see, I don't want to wrap every single component in a ThemeProvider. Maybe there is a way setting a default context for all tests in jest/enzyme?

I'm also feeling the pain of having to wrap my ThemeProvider around each component. Has anybody found a better method for doing this?

@nicholasmaddren I'd make a utility function that adds it
function mountWithTheme(jsx) {
  return enzyme.mount(
    <ThemeProvider theme={theme}>{jsx}</ThemeProvider>
  );
}

or something like that

Get the same problem, theme is undefined, does anyone have a solution for this?

@lednhatkhanh there are plenty of proposed solutions here, but please open a new issue if you need further help 🙌 this issue is already almost a year old and closed


Made ReadMe file for KUOSC.

Made a readme file for KUOSC.
#7 solved.

Done @aadarshadhakalg

@felixop7  Still some issues need to be addressed. If you can manage some more time to work on this that would be appreciated.


Is this repo maintained?

I see that the last commit for this repo was done like 3 years back. Is this being maintained? If not is there an active fork?

https://github.com/verocloud/obsidian-mindmap-nextgen


Error on Fetching Local Integer Data

App Crashes while a integer data  is requested from Shared Preferences userInfo which goes like
SharedPreferences userInfo =  this.requireActivity().getSharedPreferences("userInfo", Context.MODE_PRIVATE);
        SharedPreferences.Editor editor = userInfo.edit();
        editor.apply();

Data Created by command -
editor.putInt("pass",0);
editor.commit();

Problem while fetching integer with line -
passView.setText(userInfo.getInt("pass",0));
Error -
FATAL EXCEPTION: main
    Process: com.priyanshnama.technical_fest, PID: 17361
    android.content.res.Resources$NotFoundException: String resource ID #0x0

Concerned File - ProfileFragment.java

Solved


fix: Align identifier bytes correctly in ResourceLocator

Adjust the starting index of System.arraycopy to correctly align the identifier bytes within the given array length. This change ensures that shorter identifiers are aligned at the end of the array, improving data consistency and correctness.
Pad right and trim

Add some golden content tests, similar to the ones here: https://github.com/opentdf/client-web/pull/338/files#diff-bf61ddc3e1b6824287643ae59fd2d22f3305e3495e9a8380576d671492ac769e
I'm pretty sure the current code is correct for encoding, but yes you should add the trim method on line 224 (I think? I'm not sure that new string doesn't do this for you)

added golden identifier tests
getIdentifier() will return byte[] without trim, getIdentifierString() does trim


Verify BitUSD vs BitGLD in Unit Tests / Regression Tests

https://github.com/BitShares/bitshares/commit/164404a2755adb7c6ce313aa4c20d1c59d432483

This test crashes the client for me.  I get a failed FC_ASSERT in https://github.com/BitShares/bitshares/blob/164404a2755adb7c6ce313aa4c20d1c59d432483/libraries/cli/print_result.cpp#L972-985 which is coming from https://github.com/BitShares/bitshares/blob/164404a2755adb7c6ce313aa4c20d1c59d432483/tests/regression_tests/wallet_market_usd_vs_gold/alice.log#L12050
The code there doesn't check if (status), causing dereference to fail.  The whole block looks like it should be wrapped in if ( status.valid() ) but I am not sure what the proper action in the else would be, because I'm not sure of the semantics of what status.valid() actually means in that case.

I also suggest running debug_enable_output false before publishing feeds, and debug_enable_output true afterwards.  Just to make the size of the test log more manageable.

At a quick look, !status.valid() would seem to mean that the market has yet to even be initialized (no orders and no feeds yet for that market pair).


Fails when Better BibTeX is not installed

The documentation seems to suggest Better BibTeX is optional, but on a clean install I get an error.

Installing the plugin fixes it. Seems like either it should be made to work without it, or making it part of the instructions as a requirement.

ohhh this is so helpful!! couldn't find my problem for hours


[Question] LightGBM GPU version for setuptools

Hi,
I would like to include "lightgbm --install-options=--gpu" in the install_requires in setup.py for building wheel.
However, install_requires argument doesn't allow --install-option.
Any solution to that?

I'm going to close this issue as the original feature request should be redirected to the setuptools project.
If you have any further suggestions for lightgbm-gpu package, please feel free to share them in #2263.


Set up an onboarding node type

FEATURE OVERVIEW
User Story
As a campaign lead I want to create an onboarding experience
Additional Information (optional)
Each "slide" to have titles, copy, and an optional image (the titles and copy should be add another+)
There should be the option to add another "slide"
All fields should be translatable
Eventually we will want to create fields for first signup vs additional signups that will show different copy
Why This Matters
This should probably be a node type, because eventually we will want different experience for new users, and return users. This also might need to be a translatable thing so I think a node would be easiest here.

smash this! we are doing hardcoded onboarding types


[Confluence] Allow API Token authorization

Extension
https://www.raycast.com/tbrown/confluence
Description
Similar to https://www.raycast.com/raycast/jira, allowing two methods to login:

Through OAuth (which is already supported)
Through API Token (requested feature).

Who will benefit from this feature?
Employee under organization that disallow normal users to authorize OAuth apps but allowing create an API Token.
Anything else?
Thank you for this already great plugin.

This is needed please help take a look!


Cannot GET /app/heroes

Error 404 not found. I followed the same way decribed in tutorial. I am not getting how this api would work.
I am using angular-in-memory-web-api

You must import modules in order
imports: [
    BrowserModule,
    FormsModule,
    HttpModule,
    InMemoryWebApiModule.forRoot(InMemoryDataService),
    AppRoutingModule
],

@NugzarGaguliya thanks it works!
they didn't mention in the tutorial to put it in order

@NugzarGaguliya  Thanks . @pirey  yeah true

The initial /api/heroes call works for me,
but I tried using getHero to call /api/heroes/12 and that gives me 404.
In fact if I leave the older implementation of getHero, it tries to call /api/heroes again, and that time it returns 404.

@scottseeker  The url in the tutorial  is  const url =  '${this.heroesurl}/${hero.id}';
and I changed to const url = this.heroesUrl + '/' + id , then it works. I am not sure whether you have the same problem.

@Angela931228 it seems in your example you have single quotes ' instead of backticks `.  That may have been your issue.  I'll have to check it out at home though, thanks for the reply!

@scottseeker I had the same problem, using backticks instead of single quotes solved it, I personally can't make sense of the rules of when to use backticks and when to use single quotes

It is interesting that it works also with other order:
imports: [
    ...
    AppRoutingModule,
    HttpModule,
    InMemoryWebApiModule.forRoot(InMemoryDataService)
  ],

and fails only if HttpModule is imported after InMemoryWebApiModule. I guess InMemoryWebApi depends on Http and if the latter is not imported, InMemoryWebApi cannot work.

@salami350 using backticks is a Javascript (es6)/Typescript feature to use string interpolation. It allows to use variables inside the string instead of having to use + everywhere.

@banan314 Yes, that's documented on in-memory-web-api's GitHub, but not on this tutorial:

Always import the InMemoryWebApiModule after the HttpModule to ensure that the XHRBackend provider of the InMemoryWebApiModule supersedes all others.

closing since this was rewritten with the CLI

Thank you for your answer.

Can I suggest updating the documentation here: https://angular.io/tutorial/toh-pt6#simulate-the-web-api?
I just had the same ordering problem, and apparently I'm not the only one. A lot of headaches could be spared by including a line like this: "Be aware, the order of declarations matters! For it to work, the InMemoryWebApiModule must be listed after the HttpModule

i also getting 404 error in compiling, i think there is a problem in systemjs.config.js , but i don't know how to solve it.

Currently, I found the solution to this tutorial's mind-crippling problem. Under hero.service.ts, delete the .data included in getHeroes(). see image below. Good luck guys

Please update the tutorial !!!

@choekstra thanks to you. I had the same problem and you solved it for me. 🥇

Thanks to @choekstra i could solve this issue. I didn't know what was wrong in the code and as a newbie i was thinking i could never find it. Thanks a lot.

Angular 2-5 404 error
You can refer to this site and my solution also which solve this problem
https://discuss.emberjs.com/t/apache-rewrite-rule-for-html5-browser-history-url-bookmarkability/1013/11?u=amit_choudhary

I've had a 404 code with message {error: "Collection 'heroes' not found"} during Tour of Heroes tutorial. In my case I forgot to put the curly braces on the return statement of "in-memory-data.service.ts". It was: "return heroes"; and I had to change to "return {heroes};". The tutorial had the correct syntax, but I accidentally skipped those curly braces.
Hope it helps someone else.

@pedrocesarsa thanks to you. I had the same problem and you solved it for me. 😆