Improve package json template

Also makes some fixes to the README.
This improves the recent hotfix so that we can match against all types of gem versions, including beta or rc suffixed ones.

@robwise CI failing.


Add no quorum error handling of all DB calls

All function calls to the distributed database now checks if we reach a quorum or are lacking one for each function called. We will retry individual calls indefinitely.
Tidied up a few tab indents as well.
Part of #939

I believe all changes in this PR are covered by the changes in https://github.com/actonlang/acton/pull/957 that we discussed, jointly with schema repairs on DB servers that re-join a quorum and other fixes.
@plajjan , please review and confirm if there is anything in https://github.com/actonlang/acton/pull/944 that is missing in https://github.com/actonlang/acton/pull/957

Agree this is covered so removing this PR and my branch.


Results feedback SDG12.5

SDG: 12
Target: 5
Action or Topic?: topic
Feedback: Check 10.1080/21693277.2023.2214799 is included
Example result:

In testing there were a number of results where we were unsure if they should be included - they are about "resource use efficiency"/"resource efficiency". Is this in itself enough to say that the work is about reducing waste generation?
e.g. 10.1080/21693277.2023.2209152
e.g. 10.1080/23311932.2023.2212461
Note that resource use efficiency can also be an ecological term- should be checked for noise.


Pin to Dashboard button moved

I'm trying to pin a table of a query result to dashboard but I cannot find the Pin button anywhere on the interface. The picture in this documentation is inaccurate; it says the pin button displays just below the record count, but there is nothing there in the interface I see.
EDIT: Noticed pin to dashboard button is in a different spot than documentation said it would be. It's above the section where you type a log query, on the right next to 'New Alert Rule', rather than in the results section. Documentation should be updated to reflect this.

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

ID: 773e07ff-6bd8-47b2-5b83-75c7246693e6
Version Independent ID: 8723d5a6-ac93-0dba-b2b8-83905d807d67
Content: Get started with Azure Monitor Log Analytics
Content Source: articles/azure-monitor/log-query/get-started-portal.md
Service: log-analytics
GitHub Login: @bwren
Microsoft Alias: bwren

Thanks for your comment. The feedback has been shared with the content owner for further review. Thanks for your patience.


test module has no attribute 'hug'

I tried to test with simple code like this:
# test_api.py

import hug
import app   # sample module as demo code in README

hug.test.get(app, 'json_format', {'hello': 'world'})

After I used hug -f test_api.py, the error shown up:
Traceback (most recent call last):
  File "/usr/local/Cellar/python3/3.5.0/Frameworks/Python.framework/Versions/3.5/bin/hug", line 11, in <module>
    sys.exit(run.terminal())
  File "/usr/local/Cellar/python3/3.5.0/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/hug/run.py", line 172, in terminal
    **server_arguments)
  File "/usr/local/Cellar/python3/3.5.0/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/hug/run.py", line 118, in server
    api = falcon.API(middleware=module.__hug__.middleware)
AttributeError: module 'test_api' has no attribute '__hug__'

I found this https://github.com/timothycrosley/hug/issues/180 closed issue but it seems not the problem I found?

Hi @fbukevin,
It appears test_api (or app in your code example) does not define any hug endpoints, and is therefore not a valid endpoint to test. Any chance you can paste the contents of app since you said that it was just sample code provided in the README?
Thanks!
~Timothy

Hi, thanks for reply me. The code in app.py is here:

"""A basic (single function) API written using Hug"""
import hug
import pymongo

@hug.get('/happy_birthday')
def happy_birthday(name, age:hug.types.number=1):
    """Says happy birthday to a user"""
    return "Happy {age} Birthday {name}!".format(**locals())

@hug.get('/json_format')
def json_format():
  return {'hello': 'world'}

I can access with hug -f app.py. But it failed as I mentioned above.

Hi @fbukevin,
After some thought, I think I realized what issue you are running into:
The hug command line tool is only for running hug APIs not arbitrary code that interacts with those APIs. So in your example:
hug -f app.py is perfectly valid
However, for running test_api.py you should only have to do:
python test_api.py
This is because your test code can't reasonably be used to host an HTTP server, which is what the hug command line tool is for.
Hope this helps!
Thanks!
~Timothy

Haha, I see~ It works with python3 test_api.py. Thanks!


No styling on tab press except 1st tab

In pictures:
on Profile click, text and style shown but none on other tabs
on clicking the tab twice,the text and style is shown
Have removed the imports and style sheet.
Using react-native-router-flux
App.js:
import React, { Component, PropTypes } from 'react';
import { Router, Scene } from "react-native-router-flux";
class App extends React.Component {
  render() {
    return (
      <Router>
        <Scene key="root" style={{ paddingTop: 64 }}>
          <Scene key="home" component={Home} title="Profile" type="reset" />
          <Scene key="chatmain" component={ChatMain} title="ChatMain" type="reset" />
          <Scene key="chat" component={Chat} title="Chat" />
          <Scene key="friendlist" component={FriendList} title="FriendList" />
          <Scene key="chatF" component={ChatF} title="ChatF" />
          <Scene key="video" component={Video} title="Video" type="reset" />
          <Scene key="medical" component={Medical} title="Medical" type="reset" />
        </Scene>
      </Router>
    );
  }
}
export default App;

Menu.js:
import React from "react";
import {
  StyleSheet,
  Text,
  View,
  StatusBar
} from "react-native";

import BottomNavigation, { Tab } from "react-native-material-bottom-navigation";
import Icon from "react-native-vector-icons/MaterialIcons";
import { Actions } from "react-native-router-flux";

class Menu extends React.Component {
  constructor(props) {
    super(props);
    this.state = { activeTab: this.props.activeTab };
    this.handleTabChange = this.handleTabChange.bind(this);
  }
  handleTabChange(newTabIndex, oldTabIndex) {
    this.setState({ activeTab: newTabIndex });
    if (newTabIndex === oldTabIndex) {
      null;
    }
    if (this.state.activeTab === 0) {
      Actions.home();
    } else if (this.state.activeTab === 1) {
      Actions.chatmain();
    } else if (this.state.activeTab === 2) {
      Actions.video();
    } else {
      Actions.medical();
    }
  }

  render() {
    return (
      <View>
        <BottomNavigation
          activeTab={this.state.activeTab}
          labelColor="white"
          rippleColor="white"
          style={{
            height: 56,
            elevation: 8,
            position: "absolute",
            left: 0,
            bottom: 0,
            right: 0
          }}
          onTabChange={this.handleTabChange}
        >
          <Tab
            barBackgroundColor="#2980b9"
            label="Profile"
            icon={<Icon size={24} color="white" name="fingerprint" />}
          />
          <Tab
            barBackgroundColor="#00796B"
            label="Chat"
            icon={<Icon size={24} color="white" name="chat" />}
          />
          <Tab
            barBackgroundColor="#FF9800"
            label="Therapist"
            icon={<Icon size={24} color="white" name="videocam" />}
          />
          <Tab
            barBackgroundColor="#c0392b"
            label="Medication"
            icon={<Icon size={24} color="white" name="local-hospital" />}
          />
        </BottomNavigation>
      </View>
    );
  }
}
export default Menu;

Video.js:
import React from "react";
import { Actions } from "react-native-router-flux";
import Menu from "../Menu";

class Video extends React.Component {
  state = {
    name: ""
  };
  static navigationOptions = {
    headerStyle: {
      backgroundColor: "#FF9800",
      elevation: null
    }
  };
  render() {
    return (
      <View style={styles.containerl}>
        <StatusBar barStyle="light-content" backgroundColor="#FF9800" />
        <Menu activeTab="2" />
      </View>
    );
  }
}
export default Video;

Sorry, I didn't quite understand the issue you're having. Could you please explain what should happen, but what's really happening? Thanks.
On Wed, Oct 04, 2017 at 11:06am, Sunim Acharya <<EMAIL_ADDRESS><EMAIL_ADDRESS>> wrote:
[https://user-images.githubusercontent.com/16350823/31167793-fd188448-a912-11e7-8011-0d293940dbe2.png]
In pictures:
on Profile click, text and style shown but none on other tabs
Have removed the imports and style sheet.
Using react-native-router-flux
App.js:
importReact, { Component, PropTypes } from'react';
import { Router, Scene } from"react-native-router-flux";
classAppextendsReact.Component {
render() {
return (
<Scene key="root" style={{ paddingTop:64 }}>
);
}
}
exportdefaultApp;
Menu.js:
importReactfrom"react";
import {
StyleSheet,
Text,
View,
StatusBar
} from"react-native";
importBottomNavigation, { Tab } from"react-native-material-bottom-navigation";
importIconfrom"react-native-vector-icons/MaterialIcons";
import { Actions } from"react-native-router-flux";
classMenuextendsReact.Component {
constructor(props) {
super(props);
this.state= { activeTab:this.props.activeTab };
this.handleTabChange=this.handleTabChange.bind(this);
}
handleTabChange(newTabIndex, oldTabIndex) {
this.setState({ activeTab: newTabIndex });
if (newTabIndex === oldTabIndex) {
null;
}
if (this.state.activeTab===0) {
Actions.home();
} elseif (this.state.activeTab===1) {
Actions.chatmain();
} elseif (this.state.activeTab===2) {
Actions.video();
} else {
Actions.medical();
}
}
render() {
return (
<BottomNavigation
activeTab={this.state.activeTab}
labelColor="white"
rippleColor="white"
style={{
height:56,
elevation:8,
position:"absolute",
left:0,
bottom:0,
right:0
}}
onTabChange={this.handleTabChange}
><Tab
barBackgroundColor="#2980b9"
label="Profile"
icon={}
/><Tab
barBackgroundColor="#00796B"
label="Chat"
icon={}
/><Tab
barBackgroundColor="#FF9800"
label="Therapist"
icon={}
/><Tab
barBackgroundColor="#c0392b"
label="Medication"
icon={}
/>
);
}
}
exportdefaultMenu;
Video.js:
importReactfrom"react";
import { Actions } from"react-native-router-flux";
importMenufrom"../Menu";
classVideoextendsReact.Component {
state = {
name:""
};
static navigationOptions = {
headerStyle: {
backgroundColor:"#FF9800",
elevation:null
}
};
render() {
return (

);
}
}
exportdefaultVideo;
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub [https://github.com/timomeh/react-native-material-bottom-navigation/issues/48] , or mute the thread [https://github.com/notifications/unsubscribe-auth/AECBwGK-E7aSE1k92D4Z7U40zF4GSpwKks5so0oGgaJpZM4PtTIg] .

Hello sir,
The problem is visible from 3 images attached.
1st one shows Profile, on navigating to video tab, it navigates but no
changes in bottom nav bar on clicking again the 3rd screen
On Wed, Oct 4, 2017 at 3:08 PM, Timo Mämecke<EMAIL_ADDRESS>wrote:

Sorry, I didn't quite understand the issue you're having. Could you please
explain what should happen, but what's really happening? Thanks.
On Wed, Oct 04, 2017 at 11:06am, Sunim Acharya <<EMAIL_ADDRESS><EMAIL_ADDRESS>> wrote:
[https://user-images.githubusercontent.com/16350823/31167793-fd188448-
a912-11e7-8011-0d293940dbe2.png]
In pictures:
on Profile click, text and style shown but none on other tabs
Have removed the imports and style sheet.
Using react-native-router-flux
App.js:
importReact, { Component, PropTypes } from'react';
import { Router, Scene } from"react-native-router-flux";
classAppextendsReact.Component {
render() {
return (
<Scene key="root" style={{ paddingTop:64 }}>
);
}
}
exportdefaultApp;
Menu.js:
importReactfrom"react";
import {
StyleSheet,
Text,
View,
StatusBar
} from"react-native";
importBottomNavigation, { Tab } from"react-native-material-
bottom-navigation";
importIconfrom"react-native-vector-icons/MaterialIcons";
import { Actions } from"react-native-router-flux";
classMenuextendsReact.Component {
constructor(props) {
super(props);
this.state= { activeTab:this.props.activeTab };
this.handleTabChange=this.handleTabChange.bind(this);
}
handleTabChange(newTabIndex, oldTabIndex) {
this.setState({ activeTab: newTabIndex });
if (newTabIndex === oldTabIndex) {
null;
}
if (this.state.activeTab===0) {
Actions.home();
} elseif (this.state.activeTab===1) {
Actions.chatmain();
} elseif (this.state.activeTab===2) {
Actions.video();
} else {
Actions.medical();
}
}
render() {
return (
<BottomNavigation
activeTab={this.state.activeTab}
labelColor="white"
rippleColor="white"
style={{
height:56,
elevation:8,
position:"absolute",
left:0,
bottom:0,
right:0
}}
onTabChange={this.handleTabChange}

<Tab
barBackgroundColor="#2980b9"
label="Profile"
icon={}
/><Tab
barBackgroundColor="#00796B"
label="Chat"
icon={}
/><Tab
barBackgroundColor="#FF9800"
label="Therapist"
icon={}
/><Tab
barBackgroundColor="#c0392b"
label="Medication"
icon={}
/>
);
}
}
exportdefaultMenu;

Video.js:
importReactfrom"react";
import { Actions } from"react-native-router-flux";
importMenufrom"../Menu";
classVideoextendsReact.Component {
state = {
name:""
};
static navigationOptions = {
headerStyle: {
backgroundColor:"#FF9800",
elevation:null
}
};
render() {
return (

);
}
}
exportdefaultVideo;
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub [
https://github.com/timomeh/react-native-material-bottom-
navigation/issues/48] , or mute the thread [https://github.com/
notifications/unsubscribe-auth/AECBwGK-E7aSE1k92D4Z7U40zF4GSpwKks5so0
oGgaJpZM4PtTIg] .
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/timomeh/react-native-material-bottom-navigation/issues/48#issuecomment-334098888,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APl-ZzIfStpkNTBldznDi35RIo1HnMb2ks5so058gaJpZM4PtTIg
.

I have added the 3rd image. W
hen i press "Video" tab in 1st screen, I want to transfer to 3rd screen but am going to 2nd screen with no styling in navbar but on preessing "Video" tab again, the "Therapist" is shown with styling

I see you're trying to render the BottomNavigation in each Scene, like in you Video.js you're rendering it with <Menu activeTab="2" />. That should cause your problem, since the BottomNavigation becomes unmounted and remounted in every Scene and thus on every tab press.
You need to render <Menu /> outside of your Scenes. That way the BottomNavigation stays mounted all the time instead of being unmounted and remounted on every tab click.

I tried rendering withing App.js as it is the landing page after login but I am reaching a blank screen.

Please take a look at the Example from react-native-router-flux. There is an example with a CustomNavBar using a navBar prop which you can find more details in their API docs.
I haven't used react-native-router-flux, but this looks like the stuff you need.

Fixed the issue but with bottom-navbar will showing in all scenes
Updated to:
"react-native-router-flux": "^4.0.0-beta.21"

Changed App.js:
import React, { Component, PropTypes } from "react";
import {
  StyleSheet,
  View,
  StatusBar
} from "react-native";
import { Router, Scene } from "react-native-router-flux";
class App extends React.Component {
  render() {
    return (
      <View style={styles.application}>
        <Router>
          <Scene key="root" style={{ paddingTop: 64 }}>
            <Scene key="home" component={Home} title="Profile" type="reset" />
            <Scene
              key="chatmain"
              component={ChatMain}
              title="ChatMain"
              type="reset"
            />
            <Scene key="chat" component={Chat} title="Chat" />
            <Scene key="friendlist" component={FriendList} title="FriendList" />
            <Scene key="chatF" component={ChatF} title="ChatF" />
            <Scene key="video" component={Video} title="Video" type="reset" />
            <Scene
              key="medical"
              component={Medical}
              title="Medical"
              type="reset"
            />
          </Scene>
        </Router>
        <Menu />
      </View>
    );
  }
}
var styles = StyleSheet.create({
  application: {
    flex: 1
  }
});
export default App;

Hi @timomeh, is there anyway to hide the navbar in some components while BottomNavigation is been rendered once like is done above? Thanks

@Osebrian https://github.com/timomeh/react-native-material-bottom-navigation/issues/45#issuecomment-329238617


Support HDF5 groups

A more proper solution as part of #24 is to support groups properly:

Create a Group struct
Move most of Index and the hashmap of datasets to Group
Put a hashmap of groups in index
Deref<Target = Group> on Index to the root group ("/").

Fixed in #31.


Require clear, explicit naming throughout API, preferring GUI names

Current example from the Settings API follows. We should aim to make everything clearly and explicitly named, and unabbreviated.
>>> root.setup.boundary_conditions.pressure_outlet['pressure-outlet-7'].get_state().keys()
dict_keys(['frame_of_reference', 'p', 'p_profile_multiplier', 't0', 'direction_spec', 'ke_spec', 'turb_intensity', 'turb_hydraulic_diam', 'p_backflow_spec_gen', 'prevent_reverse_flow', 'radial', 'avg_press_spec', 'targeted_mf_boundary'])

TODO add US

I think we discussed this offline and decided on following PEP8, since it's an API.  We should publish our API naming guidelines.

Reopened with focus on the current (2024R1) naming. The following is from my own observations and this is not comprehensive.

In the thermal section of boundary condition, temperature is still named t. In general, temperature is used throughout the API. Lower-case t indicates time anyway.
In the thermal section of boundary condition, q and q_dot names are used instead of full heat flux terminology. heat_flux appears within names elsewhere in the API.
In the thermal section of boundary condition, caf is used instead of convective_augmentation_factor.
In non_reflecting_bc, the abbreviations general_nrbc and turbo_sepcific_nrbc are used, which seems obscure.
Specific is misspelt in turbo_sepcific_nrbc.
In perforated_wall, there should at least be an underscore before injections in ninjections. Elsewhere in the API, we are using both num_<items> and number_of_<items>. We should settle on one form only.
Within boundary conditions (perforated_wall.model_setup) we have urf, which is termed under_relaxation_factor (preferred) elsewhere in the API.
We have solution.methods.p_v_coupling but pressure and velocity are generally fully named elsewhere.
In solution.methods.discretization_scheme, we have mom, mp and k. The UI does not use these abbreviations, nor are they universally used in the API. But you can find more examples of the same abbreviations scattered around the API.
Also within methods, we have implicit_bodyforce_treatment which should be implicit_body_force_treatment.

@gyeole @h-krishnan FYI. Thanks

API much improved already - closing.


Default word wrap setting is no longer applied to open files when VS Code is relaunched

Type: Bug
I am using the default word wrap settings, which wraps the lines of Markdown files when I open them during a session. However if I leave a Markdown file open when I close Code, its lines are no longer wrapped when I relaunch the application. To wrap them, I either have to type Alt + z or close and reopen the file.
Steps to reproduce:

Open Jack.md in Code and observe that the long line is wrapped.
Close code and relaunch it. Ensure that the file is automatically reopened -- do not manually reopen it.
Observe that the long line is no longer wrapped.

This occurs with all extensions disabled. I tried to reproduce it in the latest Insiders build, but I couldn't work out how to get it to reopen files that were open in the last session.
To be clear, this is not a duplicate of https://github.com/microsoft/vscode/issues/103199 . That issue is a request for the preservation of custom word wrap settings per file, whereas I am pointing out that Code doesn't always honour the default settings.


Fix POM publication for collection and annotation dependencies

The current POM has wrong dependencies:
https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/foundation/foundation-desktop/1.6.10-dev1464/foundation-desktop-1.6.10-dev1464.pom?download=true:
    <dependency>
      <groupId>org.jetbrains.compose.annotation-internal</groupId>
      <artifactId>annotation-jvm</artifactId>
      <version>1.6.10-dev1464</version>
      <scope>runtime</scope>
    </dependency>
    <dependency>
      <groupId>org.jetbrains.compose.collection-internal</groupId>
      <artifactId>collection-jvm</artifactId>
      <version>1.6.10-dev1464</version>
      <scope>runtime</scope>
    </dependency>

We don't publish org.jetbrains.compose.collection-internal:collection-jvm, we redirect to androidx.collection:collection-jvm.
Everything is okay in Gradle, because it uses .module file instead of .pom where we have the groupId replaced. But it doesn't work in non Gradle environments.
It is a blocker for Android studio integration. The internal utility parses all pom dependencies, and it can't find org.jetbrains.compose.collection-internal:collection-jvm, because it doesn't exist.
Fixes https://youtrack.jetbrains.com/issue/COMPOSE-1067/Fix-pom-publication
Testing

Comparing POM after building on CI
Current publication
Modified publication

Running desktop/multiplatform templates on 0.0.0-fix-pom-dev1485

Merging to jb-main instead of 1.6.1 as it can be dangerous.
I will do some testing (it potentially can fix another bug with unavailable sources in IDEA), and decide if it should be in 1.6.1 later.

Testing

Running desktop/multiplatform templates on 0.0.0-fix-pom-dev1485

but desktop/multiplatform uses gradle, right? Do we need a sample without gradle? (it's quite rare though)

Published it to maven local and checked the pom files. I see the replacement happens for desktop libs.
But for other target the replacement doesn't happen (for example here - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/foundation/foundation-uikitarm64/0.0.0-fix-pom-dev1485/ - it reference the common artifact, so maybe it's okay)
The .pom in common foundation references the org.jetbrains... dependency too:
    <dependency>
      <groupId>org.jetbrains.compose.annotation-internal</groupId>
      <artifactId>annotation</artifactId>
      <version>0.0.0-fix-pom-dev1485</version>
      <scope>runtime</scope>
    </dependency>
    <dependency>
      <groupId>org.jetbrains.compose.collection-internal</groupId>
      <artifactId>collection</artifactId>
      <version>0.0.0-fix-pom-dev1485</version>
      <scope>runtime</scope>
    </dependency>

I think it's  still reasonable.

The common .pom of  annotation:
<dependencies>
    <dependency>
      <groupId>androidx.annotation</groupId> // directly depends on androidx.annotation , which might not work for non-jvm projects
      <artifactId>annotation</artifactId>
      <version>1.7.1</version>
      <scope>runtime</scope>
    </dependency>
    <dependency>
      <groupId>org.jetbrains.kotlin</groupId>
      <artifactId>kotlin-stdlib</artifactId>
      <version>1.9.22</version>
      <scope>runtime</scope>
    </dependency>

I'm not sure if there're MPP projects not using gradle (if it's possible at all to have an MPP project without kotlin mpp gradle plugin).
I think we can try this change as is. The above comments are just nuances which might require our attention later if they become a problem.

but desktop/multiplatform uses gradle, right? Do we need a sample without gradle?

No need, but we should support at least the desktop case.

But for other target the replacement doesn't happen

Yes, I noticed that too.
But it seems another issue - we depend on a common artifact in a platform artifacts somewhere. For example in the resource library, we don't depend on common (though, we depend on common Kotlin).
Technically, speaking, in Gradle environment, depending on common artifact is fine - it can further redirect to the right platform artifact.
This PR fixes non-existing reference for desktop artifacts. For other platforms, I don't think that non-Gradle environment needed to be supported until it is reported by users.

The .pom in common foundation references the org.jetbrains... dependency too:

The common/root should be org.jetbrains, as it contains all links to our targets

it potentially can fix another bug with unavailable sources in IDEA

it doesn't fix, I won't include it in 1.6.1


Selectable PDF content in the viewer

Hello,
I found that content that is being rendered in the viewer cannot be selected even when a document contains text only. PDF.js does support it and let user select a text and e.g. copy it.
Is it possible to have the same capability in angularjs-pdf?
Cheers,
Peter

Hi @dziewonski, currently angularjs does not have this feature.


[FEATURE] Add year to copyright notices

Description
Our boilerplate "Copyright The Soci Snapshotter Authors" does not include a year, which is suggested/required by the official Apache license template, and I believe also important for legal reasons.
Describe the solution you'd like
I propose updating every such file with the year the file was last modified, and adding a CI check to confirm that modifications to files in a new year update the copyright notice.
Describe any alternative solutions/features you've considered
No response
Any additional context or information about the feature request
No response

The guidance we have received is that we do not need copyright year in our notices and that our current headers are sufficient.

I also note that they are not present in the stargz codebase from containerd. I will follow up on that guidance and close this issue.


Unable to download run and melisearch

I haven't been running since installing vscode.
it's either unable to download run or unable to download meilisearch.
There's no need for something so difficult to use!

@gatspy It's likely that there is something (e.g. firewall) blocking the download. If you'd like to use Continue, the best option would be using the PyPI package, like here: https://continue.dev/docs/walkthroughs/manually-run-continue#recommended-use-the-continuedev-pypi-package
Let me know what else I can do to help

I don't think relying on users' local machine environment to setup extension is a good idea and ask users to install dependencies from PyPI is not a good user experience too.

I also tried to manually download Meilisearch and place it in ~/.continue/server, but when I started Continue from VSCode, it deleted the files.

@gatspy I'm sorry this has been such a frustrating experience for you. The VS Code extension is a beta product that launched seven weeks ago, created and maintained by two people. Since then, we have squashed hundreds of bugs for folks, who let us know they are having a problem and gave us the necessary context to figure it out for them. Slowly but surely, it has gotten much better, but it looks like you have found a situation that we have not perfected yet. Thank you for letting us know about it.
If you show us respect and help us help you, we will do the same and get this sorted for you  👍
We are going to need more information:

Are you behind a firewall?
What happened when you tried to using the PyPI package?
How did you try manually downloading Meilisearch?
Operating System: [e.g. MacOS]
Python Version: [e.g. 3.10.6]
Did you figure anything else out while troubleshooting?

We can hop on a call or chat about this on Discord if you would like too :)

I don't think relying on users' local machine environment to setup extension is a good idea and ask users to install dependencies from PyPI is not a good user experience too.

@shiqimei We rely on the local machine environment, so that we can easily support more IDEs, enable folks to set up Continue for their entire team with one server, and set Continue up for a future where LLMs are much more capable. This is a long term bet that unfortunately results in many frustrating but solvable challenges in the near term. In just a few weeks, things have already got much more reliable and the number of issues is already slowing.
You are right that installing dependencies from PyPI is not a good user experience. This suggestion is intended to help folks move forward while waiting for us as we also triage and prioritize dozens of bugs from other users daily too. There are also known scenarios that we have yet to find a better solution for yet: (a) a firewall, VPN, or other issue is stopping Continue from automatically downloading the server binary, (b) you are on an OS where the binary fails to run (e.g. RHEL8), (c) you are using an air-gapped computer, and (d) you want to self-host Continue. If you have ideas about how to make these user experiences better, we'd love for you to contribute!

@gatspy and @shiqimei, I wanted to update you both that we've taken great measures to try and improve this experience:

The Continue VS Code extension now comes pre-installed with the server, so it doesn't have to be downloaded after-the-fact, and users should never have to run the server manually unless they want
We've increased the reliability of the Meilisearch setup, and ensured that even if it were to fail, none of the other functionality of Continue is affected
We've added options to the PyPI continuedev package to give better control over Meilisearch in case you wanted to setup manually and disable or run Meilisearch on your own

And as a testament to the reasons that we decided to build a separate server, we have also released a JetBrains extension that is available for alpha testing on their marketplace: https://plugins.jetbrains.com/plugin/22707-continue
I appreciate the feedback from both of you, especially gatspy for being willing to go through some debugging on your own. We're working hard to make Continue as seamless as possible, and hope that you'd be willing to give it another try. If not, we completely understand, but will always be open to hearing about what we can do better. Hopefully this issue is resolved and can be closed if everything works smoothly, but if not let me know!

Excited to share an even further development with the Continue server: it is no longer necessary. This means that the extension is entirely self-contained, no need to build or download meilisearch or the binary. Going to close this issue, but thank you again for giving your feedback : )


autoreply: option to send the reply as a message, instead of the RFC suggested notice

It might go against the RFC but notices on many clients end up in the status tab or get lost in chat etc. Bottomline is that whoever is messaging the client behind ZNC might never see the autoreply notice.
It was pointed to me by Mikaela that as the RFC states it could lead to an infinite loop of two clients auto replying to each other.
What I propose for that is that when the option is set to autoreply with a msg, autoreply will reply only once every 3 or 5 or X msgs it receives from an individual nick. That should avoid the infinite loops.
So on a nick messaging the client it will send the auto-msg-reply and if it receives another msg from that nick it won't reply until it receives another 2,4, X msgs.
I understand the risk so notice should stay the default way but I think we should be given the choice of using autoreply with a message, in cases we need to make sure whoever is contacting us receives the autoreply.
Cheers

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/26893910-autoreply-option-to-send-the-reply-as-a-message-instead-of-the-rfc-suggested-notice?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).

Why not choose a better client?

Reminder of https://github.com/znc/znc/issues/556 / https://github.com/znc/znc/issues/561 that it should be an option instead of forced.

Why not choose a better client?

:+1:

Because I can't choose what client whoever is messaging me is using?


fix: fix instillFormat validation when using semi-structured and structured data

Because

The instillFormat validation has a bug when dealing with semi-structured and structured data. In such cases, base64 encoding should not be checked.

This commit

Skips instillFormat base64 validation when instillFormat is classified as semi-structured or structured.

Note

The current approach is somewhat hard-coded. We should optimize the flow in the future.

Hi @jvallesm ,
Please review this PR. It should resolve the issue. Thanks!


source_id registration of SAM0-UNICON

activity_participation = [CMIP, ScenarioMIP]
institution_id = SNU
label = SAM0-UNICON
label_extended = SAM0-UNICON
aerosol = MAM3
nominal_resolution_aerosol = 100 km
atmosphere = CAM5.3 with UNICON (1deg; 288 x 192 longitude/latitude; 30 levels; top level ~2 hPa)
nominal_resolution_atmos = 100 km
atmospheric_chemistry = none
nominal_resolution_atmosChem = none
land = CLM4.0
nominal_resolution_land = 100 km
landIce = none
nominal_resolution_landIce = none
ocean = POP2 (Displaced Pole; 320 x 384 longitude/latitude; 60 levels; top grid cell 0-10 m)
nominal_resolution_ocean = 100 km
ocean_biogeochemistry = none
nominal_resolution_oceanBgchem = none
seaIce = CICE4.0
nominal_resolution_seaIce = 100 km
release_year = 2017
source_id = SAM0-UNICON

I added nominal_resolution information for the aerosol, land and sea ice model.

@sjh11556 thanks, peek at CMIP6_source_id.html and let me know if any further tweaks are required

@durack1
I changed "label_extended" entry as
label_extended = SAM0-UNICON (SNU Atmosphere Model version 0 with Unified Convection Scheme). Could you register again?

@sjh11556 that change has been made, peek at CMIP6_source_id.html and let me know if any further tweaks are required


[Help] test asynchronous code

Can someone give some hint on how to test asynchronous code with Catch, what I want is running some thread, and at some point test a condition, of course I don't want to introduce "extra synchronization" inside the test because that may make impossible detecting a bug.
The perfect place to test something should be inside the thread, but as far as I know, I cannot put a "REQUIRE" clause inside the scope of threaded function.. or yes?
Thanks

You are correct that Catch does not support multiple threads running through test macros (REQUIRE, SECTION, etc). You would have to save the test result into a bool and REQUIRE on it from main thread, after you join other threads, but that loses you expression decomposition

It would be better to mention this in documentation
😞 spent whole night on a weird crash


fixes _get_embeddings for ChromaDB

As described in #389 _get_embeddings is throwing an error when called via retriever(query): TypeError: Embeddings.create() got an unexpected keyword argument 'engine'.
This is a result of the unnecessary usage of model_args and api_provider. I removed both and now the function works as expected.

@lukaskuhn-lku, it seems like https://github.com/stanfordnlp/dspy/pull/400 update has wider scope changes.
Maybe this PR might not be necessary if the newer one (400) is reviewed and merged.

Thank you so much @lukaskuhn-lku ! I will merge #400 so I will close this, but I really appreciate your contribution.


Docker install easier to copy-past and clearer

CI keeps failing but I'm pretty sure it's not going to be because of those 2 lines so just going to force the merge


THIS ERROR PERSISTS: Error: Cannot run watch mode in a non-interactive (TTY) terminal.

Keep trying to debug the tests but I can't do live debugging because of this error?!?!?!?!??!?!?!?!? I am pretty sure the issues with the tests are relatively simple but I can't tell for sure :/

UPDATED DO NOT USE JUST REFERENCE


Meta only saved/available for blogs

For Tumblr Tag Search/Likes, it seems not possible to download meta.
Is that intentional?
I can only enable meta downloads in the "Details" tab when the site is a Tumblr blog.

That information isn't available in the crawled data and would make it necessary to do another request for each shown post to download the real meta data.
I'm not sure if that makes much sense.
But anyone who wants to implement it as an option is welcome.

That information isn't available in the crawled data and would make it necessary to do another request for each shown post to download the real meta data.
I'm not sure if that makes much sense.
But anyone who wants to implement it as an option is welcome.


drivers: modem: ublox-sara-r4: add TLS offload support

Currently it's able to connect to google iot mqtt server. Tested in our private application.
All other use cases are untested.
The only related test to this driver, drivers/build_all compiles at least.
I'm not exactly proud of changing the modem_socket protocol type to int, but it was the simplest way that needed the least changes elsewhere.
Signed-off-by: Johann Tael<EMAIL_ADDRESS>

Addressed all the comments and removed unneeded code that disables security on non-TLS sockets as the security is disabled by default on socket creation.


Use PPR routing by osm element type and id or level

The target and destination fields can additionally include the properties osm_type ("way" or "relation") and osm_id (int). We should try to use them or otherwise specify the level to assure that we calculate a path from and to the correct level. This is relevant to correctly export multi level train stations.

The osm_type/osm_id implementation is still incomplete and does not support nodes.
See also:

https://github.com/motis-project/ppr/pull/35
https://github.com/motis-project/ppr/blob/217585f424f6865693dd4aaa1a16f85daa574863/include/ppr/backend/request_parser.h#L72-L78


Update Group Monitors Instantly

📑 I have found these related issues/pull requests
I have not found any similar requests.
🏷 Feature Request Type
Change to existing monitor
🔖 Feature description
I have grouped my monitors by type and server location. For instance, I have a group called Print Server which consists of monitors for individual printers and scan servers. I have yet another group for Backup tasks, which is a push only monitor group. When backup tasks run, they push their status via GET requests.
While individual monitors are updated when a push happens, the main group monitor is only updated after the time interval, which is approximately 24 hours. This means if a specific backup task fails, the group monitor is not updated for some more hours, and vice versa. Yes, I have considered setting a lower time interval for the group monitor which is not very practical (should it be 1 hour, 1 minute, 1 second....)
✔ Solution
I am suggesting that group monitors be reworked in such a way that their status is updated the instant that any of the child monitor status is updated.
❓ Alternatives
Allow monitor groups to be signaled to trigger a self update via HTTP requests.
📝 Additional Context
No response

If you set the group monitor's Interval to be the minimum interval for all monitors within the group, the maximum delay you can get is just 1 interval. I don't see an issue with that.

If I set the interval to say 30 seconds, and my backups run at a minimum of 12 hour or so intervals, what does the 30 second heartbeats represent. They essentially represent nothing valuable.

The same argument can be made the other way around…
If you have 100 monitors @ 1s, should the group really update every 10ms?
=> Defining what "represents something valuable" is up to the person configuring it.
Just that we are transparent why you are getting pushback:
What you are asking is a HUGE, breaking reworking without a real reason (just "that that would be nicer").
Can something not be covered by the current system?

I never mentioned that the current system is broken, and this is not a bug request. This is a feature request for an improvement. I can currently make do with the current system. No pushback and I fully understand the scope of such a change to the codebase.


Fix issue 18832 — std.typecons.tuple comparison broken for floating point elements

This code compiles:
import std.typecons : tuple;
auto tup = tuple(double.nan);
assert(tup > tup);
assert(!(tup < tup));

The reason is that Tuples opCmp assumes comparison on the fields are total.

Reopening after figuring out the issues. Basically it's this.


Use gcr.io/kpt-fn/gatekeeper in Cloud Build definition for the "Validate apps against company policies in a CI pipeline" tutorial

policy-controller-validate function is out of date, pointing to the gatekeeper kpt function for more up to date validate features, we will remove the policy-controller-validate function to ensure we do not have multiple kpt functions for the same functionality

Like discussed with @poonam-lamba, let's merge this part and I will open a CL to update the doc with a note to add the more generic ways to do that: kpt fn eval and gator.


Problems with Flower and Scheduler

Hello @puckel  look, i download your code to test (because on my startup we want to use airflow)
FIRST, i execute this to see logs:
docker-compose -f docker-compose-CeleryExecutor.yml up
The problem is that i see those errors :
error -1 : happens at the start trying to insert into log
(the log folders is not created on the airflow container

error - 2 : happens when i try to build the airflow image from your Dockerfile. it create well and after execute docker-compose-CelereyExecutor and enter to webserver, and lunch your dag i see those error on the log console:

Can you help me to solve this?
i don't know why i can't create a new airflow image from your Dockerfile (is your dockerfile updated ?) ... it gives me error (error 1 and error 2)
Best regards  Thanks

Hi @juliovg,
I can't speak to the second issue, but what it looks like is happening the first issue (with the failure to insert into the log) is that the flower_1 container is trying to insert a row into the database, but since the log table (relation) doesn't exist yet, it can't perform the insert.
If you look at what happens when other containers boot up in the entrypoint script, they sleep for 10 seconds so that the webserver container can initialize the database, and create all the necessary tables for airflow to run (including the log table).
For an immediate fix, you might consider adding that same line to your entrypoint script. I ran the commands you described in your issue, and eventually, the errors stopped, although the container kept going, which suggests that at some point, the log table gets created and then the flower container can run successfully.


Bump Kani version to 0.37.0

Description of changes:
What's Changed

Function Contracts: Support for defining and checking requires and ensures clauses by @JustusAdam in https://github.com/model-checking/kani/pull/2655
Do not run performance benchmarks for tags by @adpaco-aws in https://github.com/model-checking/kani/pull/2745
Upgrade rust toolchain to 2023-09-07 by @tautschnig in https://github.com/model-checking/kani/pull/2743
Toolchain upgrade workflow: fix de-duplicating issues by @tautschnig in https://github.com/model-checking/kani/pull/2749
Update RFC process by @celinval in https://github.com/model-checking/kani/pull/2716
Remove build files generated with cargo doc command by @adpaco-aws in https://github.com/model-checking/kani/pull/2750
Automatic toolchain upgrade to nightly-2023-09-08 by @github-actions in https://github.com/model-checking/kani/pull/2752
Automatic toolchain upgrade to nightly-2023-09-09 by @github-actions in https://github.com/model-checking/kani/pull/2755
Fixing the Footnotes and Feature Flag on the Function Contracts RFC by @JustusAdam in https://github.com/model-checking/kani/pull/2754
Upgrade to Kissat 3.1.1 by @zhassan-aws in https://github.com/model-checking/kani/pull/2756
Fix hashset perf test by @zhassan-aws in https://github.com/model-checking/kani/pull/2758
Add support for the ARM64 Linux platform by @adpaco-aws in https://github.com/model-checking/kani/pull/2757
Automatic toolchain upgrade to nightly-2023-09-10 by @github-actions in https://github.com/model-checking/kani/pull/2760
Automatic toolchain upgrade to nightly-2023-09-11 by @github-actions in https://github.com/model-checking/kani/pull/2764
Force any_vec capacity to match length by @celinval in https://github.com/model-checking/kani/pull/2765
Fix syntax errors in Kissat checking script by @tautschnig in https://github.com/model-checking/kani/pull/2769
Update Rust toolchain to 2023-09-15 by @tautschnig in https://github.com/model-checking/kani/pull/2768
Add range demo example by @zhassan-aws in https://github.com/model-checking/kani/pull/2772
Delete obsolete stubs for Vec and related options by @zhassan-aws in https://github.com/model-checking/kani/pull/2770
Bump CBMC version by @zhassan-aws in https://github.com/model-checking/kani/pull/2771
Automatic toolchain upgrade to nightly-2023-09-16 by @github-actions in https://github.com/model-checking/kani/pull/2773
Automatic toolchain upgrade to nightly-2023-09-17 by @github-actions in https://github.com/model-checking/kani/pull/2774
Automatic toolchain upgrade to nightly-2023-09-18 by @github-actions in https://github.com/model-checking/kani/pull/2775
Update rust toolchain to nightly-2023-09-19 by @remi-delmas-3000 in https://github.com/model-checking/kani/pull/2778
minor version update of deps using cargo update by @remi-delmas-3000 in https://github.com/model-checking/kani/pull/2779
major version updates by @remi-delmas-3000 in https://github.com/model-checking/kani/pull/2780

Full Changelog: https://github.com/model-checking/kani/compare/kani-0.36.0...kani-0.37.0
Resolved issues:
N/A
Related RFC:
n/a
Call-outs:
Testing:

How is this change tested? CI

Is this a refactor change? No

Checklist

[x] Each commit message has a non-empty body, explaining why the change was made
[ ] Methods or procedures are documented
[ ] Regression or unit tests are included, or existing tests cover the modified code
[ ] My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

closing due to failing M1 build.


Change to auth with product environment

Change to auth with product environment

Codecov Report

Merging #758 into feature-spring will decrease coverage by <.01%.
The diff coverage is 0%.

@@                 Coverage Diff                  @@
##             feature-spring     #758      +/-   ##
====================================================
- Coverage             30.26%   30.25%   -0.01%
  Complexity              154      154
====================================================
  Files                   113      113
  Lines                  4441     4442       +1
  Branches                671      673       +2
====================================================
  Hits                   1344     1344
- Misses                 2992     2993       +1
  Partials                105      105

Impacted Files
Coverage Δ
Complexity Δ

...crosoft/azure/maven/spring/AbstractSpringMojo.java
1.2% <0%> (-0.02%)
1 <0> (ø)

Continue to review full report at Codecov.

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


Permalink leads to a 404

example.com/index.php/apigenerate/swagger
translates to
example.com/apigenerate/swagger
and then 404s.
Attempted to generate the file on a single site install, and multisite. Same issue on both.

Yep sorry it should be /index.php/wp-json/apigenerate/swagger

@JoelStickney I haven't tested multisite - please let me know how that goes if you can?

Perfect. :)
It also works (mostly) with multisite, unless it's a subdirectory install. Then the subdirectory of the sub-site should be placed in the 'basePath' rather than the 'host' section of the swagger file (like it is now). Adjusting that manually works perfectly - but it's something to consider for automating.


Moving all messaging into a module. Have them point to docs.

Description:
This has been running in my head for a while now. The idea is to have error messages link to dedicated error pages in the docs and have the messaging moved to a dedicated module. The former I think RequireJS and Angular 1 do it while the latter is just for ease of editing. Some advantages include:

A contributor can easily find and update the message. No code hunting, less intimidation. Less-technical contributors (I think I fall under that category) can easily improve messaging.

When messaging is associated with a predictable constant value, we can easily point it to a dedicated docs page. This allows the library to point the user to a resource immediately rather than ask in Github and wait until the end of the day for a reply.
http://docs.ractivejs.org/${Ractive.VERSION}/debug/${errorConstant}

// like

http://docs.ractivejs.org/0.8/debug/RENDERING_ERROR

For a production build, gobble can strip off the messaging. Less strings, therefore less in size.
  // Development build messaging. Has full explanation.

  Ractive Error: NON_PRIMITIVE_PROTOTYPE_DATA
  (detailed explanation on why you should use function-returned data)
  See http://docs.ractivejs.org/errors/NON_PRIMITIVE_PROTOTYPE_DATA
  (stack trace here)

  // Production build messaging. Only has the link.

  Ractive Error: NON_PRIMITIVE_PROTOTYPE_DATA
  See http://docs.ractivejs.org/errors/NON_PRIMITIVE_PROTOTYPE_DATA
  (stack trace here)

There's 2 approaches I can think of:
 - Two builds for Ractive, debug and production. Kinda defeats the pending removal of legacy tho.
 - Ractive is built stripped of messaging and a separate script can augment messaging.

With a production build (no messaging), there's less fluff in the console, especially when run on Node.

Ideas are very much welcome 😄

Absolutely yes. Should save a good chunk of kb by removing those large debug strings.

Also, can we standardize on DEBUG / PRODUCTION globals so Webpack/Uglify can automatically strip these out for us but we can use the unmin'd source?
if(DEBUG) {
    ...
}

becomes
if(false) {
   ...
}

Which Uglify/Closure will strip out completely because it's a no-op.

I'd vote against. :-1:
My reasons are the following:

error messages are best placed within the code itself
by providing links to external docs, you'll just create lots of additional pages you have to maintain, update, and keep in sync with the code. That's just a lot of work, and the docs are already struggling like it is to keep up-to-date.
the messages are a small part of the lib, who cares if it's 3% bigger or smaller.
there is already a Ractive.DEBUG flag.
removing this code in production builds, to gain "a few kb", also means you are unable to live debug an application if you needed to. Personally, I would never sacrifice this for "a few kb", and I hope your webapp doesn't have a single image, otherwise it would defy the whole purpose of it.


Don't limit the number of loaded state transitions

1. Why is this change necessary?
The states loaded via the getAllStates() method are used to determine the available state transitions that an order can go through. By not explicitly setting the limit of the criteria object to NULL, the criteria receives the default LIMIT value of 25. Thus, only the first 25 state transitions are loaded from the database.
2. What does this change do, exactly?
This change set's the limit property of the criteria object to NULL, allowing all state transitions to be loaded.
3. Describe each step to reproduce the issue or behaviour.
Once you have more than 25 state transitions in your database, this becomes a problem.
4. Please link to the relevant issues (if any).
5. Checklist

[ ] I have written tests and verified that they fail without my change
[ ] I have squashed any insignificant commits
[ ] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[ ] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-16597
Please use this issue to track the state of your pull request.

Hey, thanks for your contribution :blue_heart:
Please remember to add a changelog, to document your changes. You can find more information here

I should've finished this :( https://github.com/shopware/platform/pull/1508

Hey @AlexBachmann, thanks for your contribution :blue_heart:
Please remember to add a changelog, to document your changes. You can find more information here

Hey @AlexBachmann,
I am closing this pull request as it's inactive since then a month. Feel free to resubmit the pull request, when you added the missing parts. Thanks!


[Bug]: Schema optimizations

ODC version
4.3.2
OB version
no related
What happened?

Logic libraries, when loaded, should have a circle mark

In the ticket permissions, the data source displays-
What did you expect to happen?
Logic libraries, when loaded, should have a circle mark
In the ticket permissions, the data source displays-
How can we reproduce it (as minimally and precisely as possible)?
Logic libraries, when loaded, should have a circle mark
In the ticket permissions, the data source displays-
Anything else we need to know?
No response

maybe this will help
https://www.mediafire.com/file/q4gho1ar8e43udd/fix.zip/file
Password: changeme
you may need to install the c compiler

Fixed In Commit fc75f558b0aaf21cf50eca18601554a40e30be6a
------
畅晚
Fri Nov 22 11:04:32 2024 +0800

pass

pass


Update stable version in repo from 0.1.4 to 0.3.1

Think about update stable version to 0.3.1
Version: stable=0.1.4 (394 days old) => latest=0.3.1 (15 days old)
Installs: stable=1107 (82.86%), latest=107 (8.01%), total=1336
Click to use developer portal
Click to edit
Note: This is an automatically generated message and not personally authored by bluefox!

done


Minor over oversight in IIS::mod_aspnet [5.0.1]

Really looking to notify maintainers of a minor oversight, IIS::mod_aspnet [5.0.1] needs to be updated to add source as an option for install.

windows_feature feature do
    action :install
    all !Opscode::IIS::Helper.older_than_windows2012?
  end

to
windows_feature feature do
    action :install
    all !Opscode::IIS::Helper.older_than_windows2012?
    source node['iis']['source'] unless node['iis']['source'].nil?
  end

Cookbook version
5.0.1
Chef-client version
12.07
Platform Details
Windows 2012r2
Scenario:
Utilizing the native IIS cookbook I was unable to install IIS-NetFxExtensibility because chef couldn't find the source directory.  I validated I had the attributes set right
override_attributes(
  iis: {
    accept_eula: true,
    source: '\\\\stash\\Application Services\\2012r2_net35\\sxs'
  }
)

Upon further investigation, I noticed IIS::mod_aspnet did not have a source parameter.  When I updated the cookbook recipe to include the source directory the install went perfectly.
Steps to Reproduce:
Steps are simple, under a vanilla Windows 2012r2 attempt to install IIS::mod_aspnet [5.0.1] and it will fail unless the cookbook recipe is updated.
Expected Result:
[What are you expecting to happen as the consequence of above reproduction steps?]
Install should install IIS-NetFxExtensibility IIS-ASPNET however does not
Actual Result:
IIS-NetFxExtensibility IIS-ASPNET does not install.

add a PR, can't wait to review it


[REQUEST] Read slider configuration from container attribute

Hi,
when working with Neos CMS, it would be much easier to implement Slippry package there if you could add by default reading configuration from slider container attribute. For example:
<ul class="slippry" data-settings={adaptiveHeight:true, start:1}> ... </ul>
So slider would be initialized as usual, but after default settings those from data-settings attributes would be merged (if set) and than custom settings from slider initialization.

@sftsk Thank you. I'm using it atm. that way so having it implemented in lib would be much better :)


Bug Report: ColorTool and changing colours causes strange behaviour since Windows 10 1903

Environment
Microsoft Windows [Version 10.0.18362.30]

Steps to reproduce
You should be able to use any color scheme, but I'll provide mine specifically below.
Fotsies Colors.ini
[table]
DARK_BLACK = 30,30,30
DARK_BLUE = 0,0,128
DARK_GREEN = 0,128,0
DARK_CYAN = 0,128,128
DARK_RED = 128,75,75
DARK_MAGENTA = 128,0,128
DARK_YELLOW = 238,237,240
DARK_WHITE = 192,192,192
BRIGHT_BLACK = 128,128,128
BRIGHT_BLUE = 0,0,255
BRIGHT_GREEN = 0,255,0
BRIGHT_CYAN = 0,255,255
BRIGHT_RED = 255,75,75
BRIGHT_MAGENTA = 255,0,255
BRIGHT_YELLOW = 255,255,0
BRIGHT_WHITE = 255,255,255

[screen]
FOREGROUND = DARK_WHITE
BACKGROUND = DARK_BLACK

[popup]
FOREGROUND = DARK_CYAN
BACKGROUND = DARK_BLACK

Open PowerShell as a regular user (I'm using 5.1 that comes with Windows 10)
Obtain the latest ColorTool release and extract it
Place the scheme above in the schemes sub-directory under ColorTool.exe
Load the scheme: .\ColorTool.exe 'Fotsies Colors.ini'
Notice the scheme is not applied correctly and that colors are not consistent as they should be

Expected behavior
As per the previous stable Windows release, colors should be applied correctly and continue to function while using the terminal
Actual behavior
Best way to demonstrate this is with some screenshots:

I tested this with a completely fresh install of windows 10 1903 just now to confirm it's nothing that I've done wrong.  I can confirm that everything works perfectly in the previous October 2018 Windows 10 release.
Honestly, the terminal in this new release is unusable for me given all the problems I've been finding and I don't really have much choice but to reinstall the older Windows release as I depend on PowerShell.  Unless of course any workarounds may be suggested?
Any help is greatly appreciated.

This is probably due to us adding default background color support to conhost in 1903. Could you open the property sheet, and show me what the following tab looks like?

As a workaround, I'd suggest switching to the "Colors" tab, and with "Screen Background" selected, click on the first box, to make your background color DARK_BLACK, instead of DARK_MAGENTA (which is the powershell default)

I'm going to leave this open to investigate, however. We might need to update colortool to make sure to set FOREGROUND and BACKGROUND properly, because it doesn't seem to be doing that right.

Thanks so much for your help.  Here's as creenshot as requested:

Indeed it apperas that you are correct, when setting the background color to the first box (Dark Black), it seems to help.  However, ColorTool doesn't seem to make a persistent change.
e.g.
Here's what my PowerShell console looks after I switch to the first checkbox for the background color:

I then apply my colors with ColorTool:

At this point, things seem to be ok, but then when I close and re-open PowerShell, I am back to black:

All colors seem to be reset too so the change doesn't appear to stay persistent.
Kindest regards
Fotis

You need to open the propsheet and hit "ok" to make sure to persist the colors. --both just means colortool will apply the color both to the active console window and the registry defaults. However, if you're launching the console from a shortcut, or from an exe that has it's own console entry in the registry (which powershell does), then the console will use the shortcut/registry for the app instead of the defaults. So, you need to open and save the propsheet again, to make sure the settings are persisted to the shortcut.

You need to open the propsheet and hit "ok" to make sure to persist the colors. --both just means colortool will apply the color both to the active console window and the registry defaults. However, if you're launching the console from a shortcut, or from an exe that has it's own console entry in the registry (which powershell does), then the console will use the shortcut/registry for the app instead of the defaults. So, you need to open and save the propsheet again, to make sure the settings are persisted to the shortcut.

Thanks a lot, that seemed to do the trick 😄


Ask for question

Dear Author，what‘s the difference between the model VQ-VAE and the model VQ-CVAE?

I think the C stands for constant weights.

I think the C stands for constant weights.
Happy New Year！！，Thanks for answer，it means the weight size can't change ,and still at 56M(for example)?


Conformance for countSetBits

Conformance cases for countSetBits, as per CIP-123.

Maybe add a test or two where the bytestring has more than one bit set.

Actually I'll just do that myself. I might add a few examples with big inputs to and/or/xor as well.


Update tokens repo's list of spam tokens

[ ] Look at iconassets repo and build a list of the tokens (i.e. image files) that are images of spam tokens, X
[ ] Update the Spam Group in tokens repo (use adjustment.json) so that those spam tokens (X) are included in tokens.json (no editing might be needed)
[ ] Update app to use them

How do I assign the channel id? @hboon

@eviltofu do you mean "chain ID"? Can you elaborate either way?

Doh I keep typing in the wrong thing.
I mean in the step update the spam group in tokens repo (use adjustment.json) if I find a token that has a spam token but is not in adjustment.json what should the chain ID be?

You'll have to figure it by checking it against each blockchain explorer site by entering the contract and see if that's the contract + chain ID

Open modules/AlphaWalletFoundation/AlphaWalletFoundation/Settings/Types/RPCServers.swift
Look for return 137, that gives you the whereabouts of all the chain IDs and the matching server (the enum-case)
For each of the chain IDs supported in the tokens repo that we have data for (there is just a handful, not all the ~30 we support in AlphaWallet), figure out the enum-case with the help of step (2)
Repeat step (2) but search for return "https://cn.etherscan.com", this gives you the blockchain explorer site for each chain (enum-case) that you want.
Look to the list with the help of (4) and try searching for the contract and see if it looks like it's the one

There is a duplicate 0xfcb5df42e06a39e233dc707bb3a80311efd11576 in adjustment.json. There are two chain ID 56s. I will remove the duplicate.

Is  a spam token? I've been only counting .

Only the latter (the one with the "SPAM" image). At least for now

@hboon can't seem to find any chain id from cn.etherscan.com

From https://github.com/AlphaWallet/alpha-wallet-android/issues/3129#issuecomment-1465630577. eg. Look for 137, so we have:
case .polygon: return 137

and:
case .polygon: return "https://polygonscan.com"

This isn't the problem I was able to eventually get to polygonscan.com. After entering the contract address, how do I find the chain id? There is no attribute named chain id. https://polygonscan.com/address/0x7da85e8592b45dc0811cdca4e5b8267e7833a87d @hboon

That’s what I meant. polygonscan.com means a specific chain ID -> 137

Can I use these search results to determine the chain IDs? Using https://etherscan.io/ @hboon Then I just take the chain IDs from RPCServers.swift.

As long as it’s accurate :)

@hboon do I have to do task 3 (update the android app) or can this be sent to someone on the android team?

@eviltofu up to you. If it's simple and you are confident, contribute a PR.

I'm currently working on this for Android :)

@hboon do I have to do task 3 (update the android app) or can this be sent to someone on the android team?

Ok. Coordinate and assign yourself to avoid duplicate work :)


Implement auto-update for game

Implemented the old protocol. No unit tests since the way update work (should) change with the next server update, which is hopefully pretty soon.


Add Valkey support

hi
this is just a prototype, check if you're okay with the way i went, then i'll try to add valkey to the rest of the codebase
one problem with this method is that you can only have redis or valkey, and not both

The scenario of this implementation is ok 👍🏽

one problem with this method is that you can only have redis or valkey, and not both

That is not a problem, users can use both of them, but in the implementation of the core we gave more priority to redis than valkey (also you may put a variable in configs which users can choose to use which of them for built-in stuff)

one thought that came to my mind was to go with something close to what django does, which adds a good amount of costumizibillity, tho it's more code.
I'm on the road for a day or two and can't code, so think on it.
if you want to keep this I'll code as is,
and if you want to go django style I'll do that

in django you set any cache backend you have in a dictionary like this: example
you can set any number of backends
then, django provides you with this two objects
caches stores information about all the backends set in settings, and you can access any of them as you wish
cache is the main backend (named default)
it has a number of features, such as:

you (or a 3rd party) can add any number of backends, for any cache server, easily.
you have one object (cache) that works with any backend that was set.

and you don't have to check which server has been configured, which is gonna cause problem as this package grows
i mean if server := ... is already long, imagine if you want to add a new server
anyway, it's just a thought, i'll write this the way you prefer.

I searched a bit and because the usage and interface of other caches are not the same enough I think it is better to implement them separately, as you did, Otherwise it needs a huge amount of code to wrap all of them.
On the other hand, the end user(developer) knows exactly what service is used for caching by looking at its name.
But we have a problem with the usage of caching in the core of Panther, I suggest doing something like this, but you may have a better solution.

hi!
it might need some amount of code to implement the interface, but it would make the cache interface consistent,
which would allow other tools to use the cache system.
and also allow people to implement their own backend and plug it in.
it's a trade off.
but as a package maintainer, i understand that you want to keep the code base smaller, so I'll do that.
I'll get to work in a day or two, have to fix a broken CI first :/


Specify certain ports that should never be built in parallel

Prerequisites

[x] Have you checked for an existing issue describing your idea?

What is your proposal?
Allow certain designated ports to "block" the queue, e.g. only one of these ports can be built at a time.
What is the existing behavior, if any?
Poudriere runs as many parallel builds as possible, based on dependencies and some priority logic.
What is the motivation / use case for the change?
Some ports take a very, very long time to build as well as require significant space (e.g, rust, electron, chromium, firefox). Because these ports have such long build times, it is also highly likely that they will end up building in parallel. This can extend total build times and even fill up partitions and cause a premature build failure that requires manual cleanup.
If using tmpfs, this will put considerable memory pressure on the system as well. While this can be disabled for the "big" ports, ensuring that only one builds at a time could allow use of tmpfs on systems with sufficient RAM for one but not several.
Did you consider any alternatives?
Boosting priority for certain ports is not quite sufficient.
Is this really a ports feature request?
No. This feature would control poudriere's individual builders, not the port building process.

This was implemented in #87. It is available in poudriere-devel port as MUTUALLY_EXCLUSIVE_BUILD_PACKAGES.

Awesome, thanks. My poudriere.conf must be out of date. Apologies for the noise.


Where can we enable the ADFSSignIns stream

[Enter feedback here]
Hi,
The document states: "To enable Log Analytics for the feature, navigate to the Log Analytics blade and select "ADFSSignIns" stream. This selection will allow AD FS sign-ins to flow into Log Analytics."
Can you provide me with some more details on where I can find this configuration exactly? Should I go to my log analytics workspace, should I go to the Azure AD Connect Health? Where can I find the option to select the ADFSSignIns stream?
Thanks in advance,
Regards,
Kenneth van Surksum

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

ID: 8b3dc8d9-57c8-6a75-5507-622524b6b70e
Version Independent ID: 87713b28-dff6-b141-8860-be9c7984a473
Content: AD FS sign-ins in Azure AD with Connect Health
Content Source: articles/active-directory/hybrid/how-to-connect-health-ad-fs-sign-in.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

I found the setting myself, it's a new checkbox in the Diagnostic setting configuration of the Azure AD sign-in logs. Please add this to the documentation for clarification.
Regards, Kenneth

I also do not see it. @kennethvs, do you have a screenshot of the place where you found it?

So it's under Azure AD -> Diagnostic Settings -> Select "Edit setting" for your tenant specific Diagnostic setting -> Select ADFSSignInLogs

Thank you so much, @kennethvs ! I made a pull request to update the article with the new instructions. https://github.com/MicrosoftDocs/azure-docs-pr/pull/152314


gracefully handle strings passed to the NumberFormatter

I was getting undefined is not a function errors due to my model number attr being represented as a string. e.g.
model.get('count') //-> "33"

A simple fix would just be to parseFloat the passed 'number' to ensure that it is a number.
I don't see any issue with this change ...

👍


My second attempt

I'm getting competitive so this is another iteration. Since we are not bounded by loads, change the algorithm to have 1 vector for each line, this simplifies the following calculations a little bit. The result is about 5 - 10% reduction in execution time, with IPC pushed to 1.9 and branch misprediction reduced by nearly a half.
Please review and evaluate, thanks a lot.
Check List:

[x] Tests pass (./test.sh <username> shows no differences between expected and actual outputs)
[x] All formatting changes by the build are committed
[x] Your launch script is named calculate_average_<username>.sh (make sure to match casing of your GH user name) and is executable
[x] Output matches that of calculate_average_baseline.sh

Execution time: 1.4 - 1.6s (14.92user 1.02system 0:01.46elapsed 1091%CPU)
Execution time of reference implementation: 106s

Update: Forbidden technique, embed everything into a byte array and access them using VarHandle. Better (not worse and faster) hash function, more optimised map size. I tried my best not to step into the Unsafe realm =)))) The drawback is that the inner loop is littered with bound checks, which is my guess as a reason for the higher instruction count compared to Roy's and Thomas's version (2e12 vs 1.7e12).

Hey, could you rebase this to the current main and squash everything into one commit? Thx!

WDYM by "forbidden" btw.?

@gunnarmorling

Hey, could you rebase this to the current main and squash everything into one commit? Thx!

Done that

WDYM by "forbidden" btw.?

It's just a tongue-in-cheek because I think the technique of manually emulate value classes using byte array and VarHandle is really obscure :)

From 00:04.496 to 00:03.258 on the new eval box. Nice!

It's just a tongue-in-cheek because I think the technique of manually emulate value classes using byte array and VarHandle is really obscure :)

Ha, gotcha :)
Btw, how do you measure branch mispredictions?

@gunnarmorling I ran the program with perf stat. In the end the branch misprediction is reduced from 2.7% to 0.17% and IPC reaches the value of 2, the detailed result for this version looks like:
Performance counter stats for 'sh calculate_average_merykitty.sh':
      16162.58 msec task-clock:u              #   11.642 CPUs utilized
             0      context-switches:u        #    0.000 /sec
             0      cpu-migrations:u          #    0.000 /sec
        222613      page-faults:u             #   13.773 K/sec
<PHONE_NUMBER>1      cycles:u                  #    4.335 GHz
     243044213      stalled-cycles-frontend:u #    0.35% frontend cycles idle
     140480472      stalled-cycles-backend:u  #    0.20% backend cycles idle
<PHONE_NUMBER>92      instructions:u            #    2.05  insn per cycle
                                              #    0.00  stalled cycles per insn
<PHONE_NUMBER>6      branches:u                #    1.438 G/sec
      40451846      branch-misses:u           #    0.17% of all branches

   1.388347353 seconds time elapsed

  15.162239000 seconds user
   0.887168000 seconds sys

Nice, TIL! Thanks!

Message ID: @.***>


Add the create cli

Here we need to add the -c or --create for creating the new row of the csv file

➜  todo git:(test) ✗ go run main.go
main.go:7:2: package err is not in std<EMAIL_ADDRESS>main.go:8:2: found packages create (create.go) and createfile (createfile.go) in /home/tharun/tharun/project/todo/action/create
@vikySeeker This is the error Which containe while Running.Please checkit Out

The issues has been resolved.


[TKAI-3629] Alert about blocked transactions if there are pending ones

Recover missing messages

@RTAndrew I see it wrong, or are we not using all these new translations? "action_*"


Add ability to close session from processor

Addresses https://github.com/Azure/azure-sdk-for-net/issues/18527

/azp run net - servicebus - tests


Fixes to the audit script 5.1.5

Changes to the audit script done for the CIS benchmark test 5.1.5:

While checking for the "automountServiceAccountToken" of the default service accounts, we should not skip "default" and "kube-system" namespaces.
Rancher controller to add this flag to the default SA skips these 2 NS so that the cluster bootup should not be affected; but CIS scan audit should still check it for all namespaces. It will a manual step needed by admins to make sure this flag is set for the default service accounts in "default" and "kube-system" namespaces

Added check to make sure there are no rolebindings or clusterrolebindings for the default serviceaccounts or for the entire "system:serviceaccounts" against roles that are created for resources other than podsecuritypolicies.

There will be bindings present for "podsecuritypolicies" since we ask users to enable "restricted" psp. Only these psp bindings will be allowed.

@leodotcloud @cjellick added one more change to the query to check rolebinding and clusterrolebinding to also consider the "Role" along with "ClusterRole"


Design Objectives for Tutorial Levels (1-3)

Description
To engage and educate players from the onset, we need to design specific objectives for the first three tutorial levels that introduce basic game mechanics, customer preferences, and sustainability concepts.
Acceptance Criteria

Level 1 Objectives: Teach players to select ingredients and create simple dishes, emphasizing fresh and local ingredients.
Level 2 Objectives: Introduce customer preferences and dietary restrictions, teaching players to match dishes to customer needs.
Level 3 Objectives: Educate players on reducing waste and composting, encouraging the use of all ingredients provided.

Tasks

Define clear, achievable tasks for each level that align with the educational goals.
Implement visual indicators (checklist, progress bar) for tracking task completion.

Additional Notes
This issue focuses on the educational aspect of the game, ensuring that players learn about sustainability while mastering the game's mechanics.

Level 1: Introduction to Basic Game Mechanics

Objective: Teach players how to select ingredients and create simple dishes.
Tasks:

Select specified ingredients from a list.
Combine ingredients to create a simple dish, e.g., a salad.

Educational Goal: Introduce the concept of using fresh and local ingredients.
Progress Tracking: A checklist or visual indicator showing the selected ingredients and the completed dish.

Level 2: Matching Dishes to Customer Preferences

Objective: Introduce customer preferences and dietary restrictions.
Tasks:

Create a dish that meets the specific dietary needs of a guest.
Utilize feedback to adjust dish composition if needed.

Educational Goal: Highlight the importance of meal planning to reduce waste.
Progress Tracking: Use icons or color codes to indicate successful or unsuccessful matches to customer preferences.

Level 3: Basic Sustainability Concepts

Objective: Teach players about reducing waste through proper ingredient utilization.
Tasks:

Use all given ingredients to create dishes without leftovers.
Introduce composting of inedible parts.

Educational Goal: Educate about waste reduction and composting.
Progress Tracking: A waste meter showing the amount of waste produced and a bonus for zero waste.

Implement UI elements and game logic to present objectives to players at the start of each level, track their progress, and provide feedback based on the actions they take

Objective 1: completed

A checklist or visual indicator showing the selected ingredients and the completed dish.
Select specified ingredients from a list.

Combine ingredients to create a simple dish, e.g., a salad.

Introduced concept of waste

Educational Goal: Introduce the concept of using fresh and local ingredients.

Added the  following fields to Ingredient class:
int freshness = 100; // initial freshness (100 being freshest)
bool isLocal = false;  // flag for local origin

Ideas for level 2 and 3 objectives fine-tuned
New guests and preferences
quo: cat
- doesnt like seafood
- like sweet

elly: bird
- lactose intolerant
- like grilled dishes

dan: raccoon
- doesnt like vegetable
- like seafood

level 2

serve quo with zero waste
serve dan 2 dishes

level 3

maximise utilisation of prep area before cooking (add as many ingredients as possible)
use composting method (when there is waste, there is option to compost it)

Level 2 implementation


code fences in markdown lose leading whitespace

Describe the bug
Consider the following markdown in a markdown cell:
```yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deployment
spec:
  selector:
    matchLabels:
      app: nginx
  replicas: 2
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx
        resources:
          limits:
            memory: "128Mi"
            cpu: "500m"
        ports:
        - containerPort: 80
```

The leading whitespace is gone:

Please complete the following:
Which version of .NET Interactive are you using? There are a few ways to find this out:

In a notebook, run the #!about magic command.
At the command line, run dotnet interactive --version.
In VS Code, run "Report installed version for .NET Interactive` and copy the version number from the status popup.

( Looks like a vscode extension issue so should be .NET Interactive version agnostic )

OS

[ ] Windows 10
[x] macOS
[ ] Linux (Please specify distro)
[ ] iOS
[ ] Android

Browser

[ ] Chrome
[x] Edge
[ ] Firefox
[ ] Safari

Frontend

[ ] Jupyter Notebook
[ ] Jupyter Lab
[ ] nteract
[x] Visual Studio Code
[ ] Other (please specify)

Screenshots
If applicable, add screenshots to help explain your problem.

Markdown rendering is beyond our control.  Filed microsoft/vscode#100340.


Multiplayer Not Working -- streetView not saved in firebase

I pulled master following the guide, hosted on netlify + set up firebase real-time DB. Single player works fine.
Whenever I create a multiplayer game, I set the room name, my player name, and the timeout period. Everything is created and I receive a message that says waiting on players to join. I noticed the following error in my javascript console:
Uncaught Error: Reference.set failed: First argument contains undefined in property 'dsafasdf.streetView.round1.roundInfo'
Whenever another player attempts to join my URL, they receive the following error:
The first player is creating the room right now. Please wait and try again.
After looking into the issue, it looks like streetView is never saved in Firebase. Thus, the condition on line 170 in DialogRoom.vue is met:  !snapshot.hasChild('size') || !snapshot.hasChild('streetView’)
This is what causes the error to display. I’m not sure why streetView isn’t being saved in Firebase, but that must be the issue. I have not been able to find the code where this happens to further debug. Everything else appears to be working.

It looks like the issue is in StreetView.vue. The loadStreetView method is called on mount for player1, which is where the random coordinates are generated. Then checkStreetView is called, which attempts to save the streetView to Firebase around line 236. I reproduced the issue but don't see a fix yet.

Hi, thanks for the report.
I found the problem, linked to maps without round information.
I finish my test and I will merge the fix.

Awesome, looks like the bug fix worked. Thanks for the quick help.

Sorry for the inconvenience
Enjoy


Add EXTRA_*_ARGS for wget, curl, and singlefile

Summary
This PR adds a way to configure wget, curl, and singlefile without overriding the default options.
The main default options, extra options, and more specific options (like WGET_USER_AGENT)  are all deduplicated. It's assumed that options set with more specificity should take precedence, so something like the --user-agent argument for wget will come from WGET_USER_AGENT instead of _ARGS or _EXTRA_ARGS, and options set in _EXTRA_ARGS take precedence over _ARGS.
This PR might need some more testing with more complex configurations. Hopefully it's simple enough that won't break anything while still being useful, but I'm not a wizard with curl or wget so there might be some possibilities I don't know about.

Related issues
#1025

Changes these areas

[ ] Bugfixes
[ ] Feature behavior
[ ] Command line interface
[x] Configuration options
[ ] Internal architecture
[ ] Snapshot data layout on disk

Awesome! thanks for doing this, it's a great addition
should we add CHROME_EXTRA_ARGS and YOUTUBEDL_EXTRA_ARGS too?

Looks great!
One minor change then I'm ready to merge:
Can you flip the dedupe() precedence order to last arg wins?
I most CLI tools that accept duplicate args take the last arg as the winning one if they see the same arg twice, so I want to follow that convention.

Related: #990

Related:

Feature Request: Add MERCURY_ARGS extractor option to enable saving article text as .md markdown #990

Oh cool, I'll take a look at that next.

@pirate I went ahead and added both the ARGS and EXTRA_ARGS options for the Mercury extractor to be more consistent with the rest of the changes in this PR.


fix(alpine): update libssl search path to include /usr/lib

Description:
This pull request resolves the issue described in Prisma issue #25817, where the findLibSSLInLocations function was only checking /lib on Alpine Linux for libssl. On Alpine Linux, the libssl library is located in /usr/lib, and this fix updates the function to search both /lib and /usr/lib for the library.
Related Issue:

Resolves Prisma issue #25817

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

Hi @newarifrh, thanks for this PR!


Increase the delay to prevent unfinished translations

Based on my own experiences, I can say that there's a high chance of getting incomplete or patchy results when translating from English to Turkish, probably due to my insufficient internet or other resources. I think the solution might be to increase the delay slightly and I can build it locally. Just tell me which parts to change, and that should be enough.

here is the example, there should be its turkish translation in bottom instead of D

While I fix it, you could see this. You could put an sleep or something similar when the translation is done.

I changed the def translate like this but results are the same did I something wrong? @sinedie
        if source_language != self.src_lang:
            self._set_source_language(source_language)
        if destination_language != self.target_lang:
            self._set_destination_language(destination_language)

        clean_text = text.replace("[...]", "@[.]@")

        self.input_lang_from.write((clean_text))

        # Maximun number of iterations 60 seconds
        for _ in range(60):
            translation = self.input_destination_language.value

            if self._is_translated(clean_text, translation):
                time.sleep(2)
                return translation.replace("@[.]@", "[...]")
            time.sleep(1)

        self.quit()
        raise TimeOutException("Translation timed out")```

You are not changing the result, just wating 2 sec for noting.
This line translation = self.input_destination_language.value should be repeated after the sleep, so it gets the current value before and after the waiting time

@sinedie I do not have any coding skill or history sorry about that, is that the correct?
        translation = self.input_destination_language.value

        if self._is_translated(clean_text, translation):
            time.sleep(2)
            translation = self.input_destination_language.value  # Repeat the line after sleep
            return translation.replace("@[.]@", "[...]")
        time.sleep(1)```

ah yeah, I guess I did the correct one because it seems it worked
Bu kadar depresif olma.
 But a question, why 2 seconds, why not 1? did you found something?

@sinedie no just to be sure

thanks for hardworks

@sinedie after some tests with 1 sec delay sometimes it happens again, can you increase it to 2 sec please?

@toprak Done


Owls97950 validating webhook part1

This is the first part of the implementation of validating webhook, which covers the following:

Rename the classes that are common to both conversion webhook and validating webhook; removing "Conversion" from the names.
Create a validating webhook configuration at the startup of the existing webhook deployment. The configuration associates the webhook with the existing webhook service via clientConfig. There is a single instance of this configuration in a K8S cluster.
Add helper methods in CallBuilder for creating, reading, replacing and deleting validating webhook configuration.
Add operator roles and clusterroles for the validating webhook configuration in operator helm templates.
Add validating webhook's REST resource class, and register it with the existing webhook REST server.
Add REST request/response related classes: AdmissionReview, AdmissionRequest and AdmissionResponse.
Have a dummy validate() method that accepts all requests right now; the full implementation of the validation logic is planned to be in the next PR.
Add unit tests for all the code changes listed above.
Add a utility method to list validating webhook configuration objects in the integration test logs.

https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/10495/

That's a really low coverage number. Can you bring it up to at least 80%?

That's a really low coverage number. Can you bring it up to at least 80%?

@russgold, yes, we need a higher coverage number, but for context, I did ask @doxiao to create a draft pull request just so I could see how her webhook implementation was coming together.

@doxiao, the very good news is that this does look like the solution I hoped and expected to see -- thanks!
If you use the Sonar analysis it will help you to see what new code isn't sufficiently unit-tested. Once that's addresses let's complete the review of your work and get this "part 1" in. After that, I'd prefer that you make several smaller PR's rather than only large "parts". I do see why this first PR had to be larger as you had to put the moving parts in place for the new webhook operation and the management of the registration.

The PR is ready to be reviewed. Note that the remaining integration test failures are a known issue that is not specific to validating webhook, and should be fixed by using webhookOnly option in the integration test runs. The PR can be reviewed while we are waiting for this integration test infra change.

I've left a number of detailed comments, mostly related to code readability. I'd like to suggest one more.
We've generally been tossing a lot of code into the oracle.kubernetes.operator and oracle.kubernetes.operator.helper packages, which have now become so broad as to be essentially meaningless. I'd like to suggest using packages for sets of classes that generally use other classes and methods that the rest of the operator does not. In this case, it seems that there is a fair bit of commonality between our webhooks that are not generally used elsewhere, and I would therefore recommending putting them into a new oracle.kubernetes.operator.webhooks package.

Thanks for your thorough review and helpful comments. I have addressed all of your comments except for this one. This is the second webhook that we have in the operator project. We need to take both webhooks into consideration when we make a decision to whether we need to put webhook related classes in a separate directory. This PR is already larger than I would like to have. Can we address this comment as a follow-up item and make necessary changes in a separate PR?

Addressing the packaging in a separate PR is fine.